fragments left after replacing a dead node with a new device

[Thaui57]

Like to know how I can remove some fragments from a replaced dead node which I replaced with a new node. After each restart of my homesystem (Domoticz) the old device names will be discovered beside the new existing device. I have not found any possibility to find out where to delete the data. In Domoticz I have deleted the fragments and the system seems to be clean. But if I reboot the old data appears again. I have 6 device with this behaviour. The replaced device under the old node ID is working correct.

!--StartFragment--

	381	Razberry7pro	zwavejs2mqtt_0xdbf01f81_4-51-0-currentColor	1	Deckenlampe-Licht AZ LED_rgb_dimmer	Color Switch	RGBWZ	Off	-	-		2022-06-26 14:55:28
		382	Razberry7pro	zwavejs2mqtt_0xdbf01f81_4-38-1-currentValue	1	Deckenlampe-Licht AZ LED_dimmer_1	Light/Switch	Switch	Off	-	-
		383	Razberry7pro	zwavejs2mqtt_0xdbf01f81_4-38-2-currentValue	1	Deckenlampe-Licht AZ LED_dimmer_2	Light/Switch	Switch	Off	-	-
		384	Razberry7pro	zwavejs2mqtt_0xdbf01f81_4-38-3-currentValue	1	Deckenlampe-Licht AZ LED_dimmer_3	Light/Switch	Switch	Off	-	-
		385	Razberry7pro	zwavejs2mqtt_0xdbf01f81_4-38-4-currentValue	1	Deckenlampe-Licht AZ LED_dimmer_4	Light/Switch	Switch	Off	-	-
		386	Razberry7pro	zwavejs2mqtt_0xdbf01f81_4-38-5-currentValue

!--EndFragment--

[robertsLando]

What do you mean with 'fragments'?

[Thaui57]

here are some pictures to understand better what I mean. I do not have a node No.4. The discovery list from Domoticz is showing ID's with a node no.4. The real node is node no.19. The question is how do I get rid of the fragments.

[AlCalzone]

Okay, I'll need to see a driver log from the startup of zwavejs2mqtt, on loglevel debug. Please attach it as a file here.
Here's a description how to do that.

During your attempt at removing the failed node, there was definitely a response from a node, so something still has ID 4.

[Thaui57]

when I changed the General like in the description I get this page. I do not have a PW for zwavejs2Mqtt

[AlCalzone]

@robertsLando ?

[robertsLando]

I think he has enabled auth in general section by error. BTW the default user and psw are admin and zwave

[Thaui57]

as requested attached find the log file after booting and the dump file of all nodes Von: AlCalzone <> Gesendet: Freitag, 1. Juli 2022 10:36 An: zwave-js/zwavejs2mqtt ***@***.***> Cc: Thaui57 ***@***.***>; Author ***@***.***> Betreff: Re: [zwave-js/zwavejs2mqtt] fragments left after replacing a dead node with a new device (Discussion #2486) Okay, I'll need to see a driver log from the startup of zwavejs2mqtt, on loglevel debug. Please attach it as a file here. Here's a description <https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/generating-logs?id=driver-logs> how to do that. During your attempt at removing the failed node, there was definitely a response from a node, so something still has ID 4. — Reply to this email directly, view it on GitHub <#2486 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVRC3LE33XMEDBHTGX6ZAXTVR2UVFANCNFSM5Z34NZJQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AVRC3LEL37Z4P2FMCREEODLVR2UVFA5CNFSM5Z34NZJ2YY3PNVWWK3TUL52HS4DFWFCGS43DOVZXG2LPNZBW63LNMVXHJKTDN5WW2ZLOORPWSZGOAAXLUCA.gif> Message ID: ***@***.*** ***@***.***> >

[AlCalzone]

You'll need to upload the file via the Github UI. Attaching it to the email doesn't work.

[Thaui57]

zwavejs_2022-07-02.log

[Thaui57]

nodes_dump.log

[AlCalzone]

There are no references at all to a node 4 in the log or the nodes dump. I'm not sure how Domoticz determines which data to show.
Can you verify if zwavejs2mqtt shows anything regarding Node 4? If not, I think this is a bug in Domoticz.

[robertsLando]

@Thaui57 I think you may have some nodes left there from retained topics, try to clean up them using mqtt explorer,

[Thaui57]

Thx. Will doAm 07.07.2022 08:13 schrieb Daniel Lando ***@***.***>: @Thaui57 I think you may have some nodes left there from retained topics, try to clean up them using mqtt explorer, —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>