Hello Matthijs,
noticed that virtual switches are removed, but now “custom control” is not working in ~79 , returns Unable to access the service endpoint:/victron/services/input-custom
is this a problem of my node-red installation?
greetings from Austria
Leopold
Hi! I don’t know what a custom control is, but will pass the message along - thanks!
Custom Control node.
@GadingeL If it is not working may be a function of what device/ parameter you are accessing rather than the custom control node itself.
1 Like
Hi, thanks for quick response! attached a simple Test-flow, created and successfull tested on V3.55 - updated CerboGX to V3.60~79 and gives results shown in attached picture.
Hope this additional info can help
Test-flow V3.60~79.txt (5,7 KB)
@mpvader I can confirm the findings above. The custom input and output nodes already in my flow are still working but I can not create new custom input or custom output nodes and get the same error message.
2 Likes
Thanks for the report. Managed to reproduce the problem and am working on a fix for it.
2 Likes
I’m getting the similar results trying to add a new VE.Bus system node as well - existing one already in the flow seems to work. Assume it’s connected so won’t add a new topic.
Same Problem here. Existing Nodes do work, but I can not change them. Or add new nodes.
Venos OS is V3.60~79
Hi all, solved per v3.60~80.
Thanks for the reports. And please confirm if all is ok now, also @AdrianChen
3 Likes
Yes all good - many thanks…
1 Like
With v3.60-80 it is working. Thanks for the quick fix!
1 Like
Working here also
Thanks for the fix, great job during weekend !!!
There is one minor issue that possible can be fixed or documentation update, I posted already.
Have a nice weekend!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.