Hello,
I just upgraded my installation to the Domoticz 2024.4 (coming from 2023.2) and also the newest images of zwave-js-ui and koenkk/zigbee2mqtt
Now I see that additional devices appear that e.g. get a name like "nodeID_8 (nodeID_8_config_switch_4)..." or "nodeID_5 (nodeID_5_config_switch_102_64)..." which are displayed in Domoticz to be light switches.
Node 8 is a Eurotronics thermostatic valve and node 8 is a Aeon Labs Multisensor 6.
Additionally I see a bunch of devices generated by zigbee2mqtt which make more sense (like permit join, version number, etc.).
I did not find any explanation for the lots of switches generated by zwave-js-ui, also not by searching on the internet.
Where can I find this information?
Thanks a lot in advance.
Best regards
Al
new devices discovered after upgrading to new zwave-js-ui and 2024.4
Moderator: leecollings
- waltervl
- Posts: 5148
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: new devices discovered after upgrading to new zwave-js-ui and 2024.4
Seems related https://github.com/zwave-js/zwave-js-ui/issues/3558
And I also think this is going to be fixed in Domoticz to skip creating those devices based on Zwave-JS-UI setting "enabled_by_default": false or true.
See https://github.com/domoticz/domoticz/issues/6021
And I also think this is going to be fixed in Domoticz to skip creating those devices based on Zwave-JS-UI setting "enabled_by_default": false or true.
See https://github.com/domoticz/domoticz/issues/6021
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
- Posts: 17
- Joined: Wednesday 01 August 2018 14:50
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: new devices discovered after upgrading to new zwave-js-ui and 2024.4
Now there is a way to disable these config devices in zwavejs-ui for people that have no need for them. (in my case there were almost more config devices than other devices.) from zwavejs-ui release 9.10.2
See https://github.com/zwave-js/zwave-js-ui/issues/3571
Just add in the docker-compose.yml file under the environment entry:
....
environment:
- SESSION_SECRET=mysupersecretkey
# added to disable discovery topics (-112-)
# https://github.com/zwave-js/zwave-js-ui/issues/3571
- DISCOVERY_DISABLE_CC_CONFIGURATION=true
# Uncomment if you want logs time and dates to match your timezone instead of UTC
# Available at https://en.wikipedia.org/wiki/List_of_t ... time_zones
#- TZ=America/New_York
....
See https://github.com/zwave-js/zwave-js-ui/issues/3571
Just add in the docker-compose.yml file under the environment entry:
....
environment:
- SESSION_SECRET=mysupersecretkey
# added to disable discovery topics (-112-)
# https://github.com/zwave-js/zwave-js-ui/issues/3571
- DISCOVERY_DISABLE_CC_CONFIGURATION=true
# Uncomment if you want logs time and dates to match your timezone instead of UTC
# Available at https://en.wikipedia.org/wiki/List_of_t ... time_zones
#- TZ=America/New_York
....
-
- Posts: 103
- Joined: Monday 04 March 2019 14:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.7
- Location: France
- Contact:
Re: new devices discovered after upgrading to new zwave-js-ui and 2024.4
Hello
I encounter the same issue in my Domoticz 2024.4 (build 15934) application with the creation of plenty of non desired devices (linked to 112 zwave configuration topics).
Currently I am using zwave-js-ui 9.8.3 version installed via docker.
I would like to upgrade to release 9.10.2 and set - DISCOVERY_DISABLE_CC_CONFIGURATION=true in docker-compose.yml
Could someone provide me the process to upgrade zwave-js-ui via docker ?
Many thanks in advance
BR
I encounter the same issue in my Domoticz 2024.4 (build 15934) application with the creation of plenty of non desired devices (linked to 112 zwave configuration topics).
Currently I am using zwave-js-ui 9.8.3 version installed via docker.
I would like to upgrade to release 9.10.2 and set - DISCOVERY_DISABLE_CC_CONFIGURATION=true in docker-compose.yml
Could someone provide me the process to upgrade zwave-js-ui via docker ?
Many thanks in advance
BR
meal
-
- Posts: 17
- Joined: Wednesday 01 August 2018 14:50
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: new devices discovered after upgrading to new zwave-js-ui and 2024.4
This is the way I update my zwavejs-ui
go to the directory where your docker compose file is stored (in my case: cd /home/pi/zwavejs2mqtt)
#update your docker compose file for zwavejs-ui if needed
docker-compose pull zwave-js-ui
docker-compose down
# now your docker container is stopped, you can use MQTT explorer to delete your zwavejs discovery entries and the zwavejs state topics as most likely, they are retained and will never be cleaned up.
docker-compose up -d --remove-orphans
docker image prune
# delete the config devices in Domoticz you don't need.
After that, you can restart Domoticz
go to the directory where your docker compose file is stored (in my case: cd /home/pi/zwavejs2mqtt)
#update your docker compose file for zwavejs-ui if needed
docker-compose pull zwave-js-ui
docker-compose down
# now your docker container is stopped, you can use MQTT explorer to delete your zwavejs discovery entries and the zwavejs state topics as most likely, they are retained and will never be cleaned up.
docker-compose up -d --remove-orphans
docker image prune
# delete the config devices in Domoticz you don't need.
After that, you can restart Domoticz
-
- Posts: 103
- Joined: Monday 04 March 2019 14:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.7
- Location: France
- Contact:
Re: new devices discovered after upgrading to new zwave-js-ui and 2024.4
Hello,
I have proceeded to the zwave-js-ui upgrade to 9.10.2 release successfully and updated docker-compose.yml accordingly in the environment section
- DISCOVERY_DISABLE_CC_CONFIGURATION=true
Still I get the follwing lines in dimoticz.log when rebooting domoticz
2024-04-12 15:16:27.021 Status: MQTT Auto Discovery: discovered: nodeID_10 (nodeID_10_config_number_1)/nodeID_10 (nodeID_10_config_number_1) (unique_id: zwavejs2mqtt_0xd414d57d_10-112-0-1)
2024-04-12 15:16:27.122 Status: MQTT Auto Discovery: discovered: nodeID_10 (nodeID_10_config_number_4)/nodeID_10 (nodeID_10_config_number_4) (unique_id: zwavejs2mqtt_0xd414d57d_10-112-0-4)
2024-04-12 15:16:27.223 Status: MQTT Auto Discovery: discovered: nodeID_10 (nodeID_10_config_number_5)/nodeID_10 (nodeID_10_config_number_5) (unique_id: zwavejs2mqtt_0xd414d57d_10-112-0-5)
2024-04-12 15:16:27.324 Status: MQTT Auto Discovery: discovered: nodeID_10 (nodeID_10_config_number_6)/nodeID_10 (nodeID_10_config_number_6) (unique_id: zwavejs2mqtt_0xd414d57d_10-112-0-6)
I don't have deleted yet the domoticz devices associated to the -112- topicz.
What am I missing ?
BR
I have proceeded to the zwave-js-ui upgrade to 9.10.2 release successfully and updated docker-compose.yml accordingly in the environment section
- DISCOVERY_DISABLE_CC_CONFIGURATION=true
Still I get the follwing lines in dimoticz.log when rebooting domoticz
2024-04-12 15:16:27.021 Status: MQTT Auto Discovery: discovered: nodeID_10 (nodeID_10_config_number_1)/nodeID_10 (nodeID_10_config_number_1) (unique_id: zwavejs2mqtt_0xd414d57d_10-112-0-1)
2024-04-12 15:16:27.122 Status: MQTT Auto Discovery: discovered: nodeID_10 (nodeID_10_config_number_4)/nodeID_10 (nodeID_10_config_number_4) (unique_id: zwavejs2mqtt_0xd414d57d_10-112-0-4)
2024-04-12 15:16:27.223 Status: MQTT Auto Discovery: discovered: nodeID_10 (nodeID_10_config_number_5)/nodeID_10 (nodeID_10_config_number_5) (unique_id: zwavejs2mqtt_0xd414d57d_10-112-0-5)
2024-04-12 15:16:27.324 Status: MQTT Auto Discovery: discovered: nodeID_10 (nodeID_10_config_number_6)/nodeID_10 (nodeID_10_config_number_6) (unique_id: zwavejs2mqtt_0xd414d57d_10-112-0-6)
I don't have deleted yet the domoticz devices associated to the -112- topicz.
What am I missing ?
BR
meal
-
- Posts: 17
- Joined: Wednesday 01 August 2018 14:50
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: new devices discovered after upgrading to new zwave-js-ui and 2024.4
Did you delete the zwavejs-ui discovery topics with MQTT explorer before starting before running docker-compose up -d --remove-orphans?
As most likely they are retained and will stay until you delete them with e.g. a tool like MQTT explorer
As most likely they are retained and will stay until you delete them with e.g. a tool like MQTT explorer
-
- Posts: 103
- Joined: Monday 04 March 2019 14:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.7
- Location: France
- Contact:
Re: new devices discovered after upgrading to new zwave-js-ui and 2024.4
Hello
I have now deleted the topics in MQTT explorer and it is now working.
In domoticz log I don't see the -112 topicz anylonger.
Thanks for your hints.
BR
I have now deleted the topics in MQTT explorer and it is now working.
In domoticz log I don't see the -112 topicz anylonger.
Thanks for your hints.
BR
meal
Who is online
Users browsing this forum: No registered users and 0 guests