You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point I'm not sure if I'm doing something wrong or it is really a bug.
Control Panel -> Node -> Home Assistant presents discovered Devices and JSON which would be sent to the broker / HA. According to the documentation this JSON can be edited, Updated in memory, Stored in nodes.json file and sent to broker by pressing the button "Rediscover" however any edits will be gone upon re-selecting the device, not stored in nodes.json and only original one sent to broker.
Log file reflects the send but only with original JSON and not the modified one.
Clicked update, store, rediscover; select another device and went back, changes are gone:
P.s. would be good if Z-Wave JS UI can send "suggested_area" tag as part of the discovery, if needed I can create new feature request.
The text was updated successfully, but these errors were encountered:
Build/Run method:
[ ] Docker
[ ] Git Clone + npm install + npm run build + npm start
[X] Pkg
Z-Wave JS UI version: 9.27.7
Z-Wave JS version: 14.3.6
Describe the bug
At this point I'm not sure if I'm doing something wrong or it is really a bug.
Control Panel -> Node -> Home Assistant presents discovered Devices and JSON which would be sent to the broker / HA. According to the documentation this JSON can be edited, Updated in memory, Stored in nodes.json file and sent to broker by pressing the button "Rediscover" however any edits will be gone upon re-selecting the device, not stored in nodes.json and only original one sent to broker.
Log file reflects the send but only with original JSON and not the modified one.
Clicked update, store, rediscover; select another device and went back, changes are gone:
P.s. would be good if Z-Wave JS UI can send "suggested_area" tag as part of the discovery, if needed I can create new feature request.
The text was updated successfully, but these errors were encountered: