Version: 2022.1 (build 14318)
ZwaveJS2Mqtt 6.13.0
ZwaveJS 9.5.0
got a big mess with a Fibaro RGBW device. At the beginning it was included as Node 4 and later on as Node 19. After each restart of the system old ID#s coming up form the first inclusion. While deleting all ID's with the _4- in the description they appear after reboot. I thought this is a problem of ZwaveJS or ZwaveJS2Mqtt because there are fragments in the store of ZwaveJS. After they analysed the startup log and the hardware dump they responded there is no Node 4 and the problem seems to be in Domoticz. Today I excluded the Node 19 as well and deleted also all ID's with _4- and _19- from the device list. After restart the system all ID's still appear. Any help is welcome.
Get not rid of ID's under MQTT Topic is solved
Moderator: leecollings
-
- Posts: 8
- Joined: Saturday 18 September 2021 21:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Get not rid of ID's under MQTT
- Attachments
-
- devices.JPG (233.03 KiB) Viewed 369 times
- heggink
- Posts: 978
- Joined: Tuesday 08 September 2015 21:44
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 12451
- Location: NL
- Contact:
Re: Get not rid of ID's under MQTT
Did you enable the retain flag? If so, then mqtt retains the messages of these devices causing domoticz to recreate them. Either disable retain our delete the retained messages from the mqtt broker.
Sent from my SM-G980F using Tapatalk
Sent from my SM-G980F using Tapatalk
Docker in Truenas scale, close to latest beta
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
Who is online
Users browsing this forum: No registered users and 1 guest