Hi Guys, after updating from v3.70 -61 to v3.70 -74 I lost the settings of all virtuell device groups and names. After backup to v3.70-61 all groups and names are in correct order again. Could you please investigate?
Do you have a bit more context on this? As you are mentioning groups and names I assume it is about the virtual switches, right?
yes talking about virtual switches and these groups and names. After update all inputs disappeared. The devices in cerbo gx are all present- just the names and groups disappeared
1 Like
I can confirm it happened on my virtual switches also, I just input the Group and Names again.
1 Like
I have experienced this today as well. Updating from ~61 to ~74. Left the system running, opened Node Red via GUI v2 link, changed a thing and fully-re-deployed and everything seems to be back.
1 Like
just testet v3.70 -78 - the problem ist still the same - name and group desappeares with update from -61 to -78. To help eleminating the issue this information might help: I changed the names and groups after initial deploy in the guiv2 instead of in NodeRed
Thanks for that. I see that Virtual Device (switch) is being deprecated. Unfortunately, the replacement (Virtual Switch) is broken. You can only see one in the Remote Console GUI. With the older Virtual Device (switch), I had 2 and both appeared in the GUI. When I replaced them with Virtual Switches, only 1 ever shows up in the GUI. I created a third, same thing, only 1 shown in the GUI. There’s also a lot of weirdness combining Virtual Device (switch) and Virtual Switches and Groups.
Going back to Virtual Device (switch) and everything is as expected in the GUI.
Unfortunately, the replacement (Virtual Switch) is broken. You can only see one in the Remote Console GUI. With the older Virtual Device (switch), I had 2 and both appeared in the GUI.
Can you create an issue for that on GitHub · Where software is built, containing some screenshots what you exactly did? I tried to replicate, but on my system the new switches appear as expected.
Thank you for your response.
I can certainly do that. Before I do, I’ll admit that I have dbus-serialbattery installed. But I did do testing with the startup scripts disabled and still see the issue.
If you still think that could contribute to the issue even when the scripts are disabled, I will need to remove it before creating the issue on Github. Edit: I created a Github issue with dbus-serialbattery scripts disabled.
Please let me know if I need to completely remove dbus-serialbattery.
I believe it is very unlikely that dbus-serialbattery has anything to do with this. So for me no need to remove that.
Like reportet already for v3.70-78 :A few days ago I updated to v3.70 - 81 and all groups and names were in the right order. Today Update to v3.70-83 and the names and groups disappeared again
Did you set the name and group in the Node-RED flow or via the console (gui-v2)?
Note that the name and group are taken from the Node-RED configuration. If you adjust those later on via the console, these values get lost and overwritten with the values from the Node-RED configuration on reboot or when updating the firmware.
Background is that there can be only one source of truth for these values, which is the Node-RED configuration. This used to behave slightly differently.
With a lot of manual work I changed all switches to the new switches in Nodered and updated to v3.70-86 and put all names and groups in Nodered now. Sems to work again now
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.