Zwavejs2mqtt: [bug] Issue with HASS discovery

[haavardNO]

Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report

Version

Build/Run method

• [x] Docker
• [ ] PKG
• [ ] Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: 1.0.5
zwavejs version: 6.1.2

Describe the bug

After zwavejs2mqtt restart states will be repopulated in HASS and then retrigger automations.
Screenshot below is after delete data of device in mqtt explorer:

Screenshot below is after zwavejs2mqtt restart.

It has been a bit back and forth with this issue, and where to post it, so I hope I am doing it right 😊

[robertsLando]

After HASS first official release of zwave-js the number of issues have increased a lot. For this reason I have decided to focus on the issues related to the control panel functionalities and automatically close the ones related to MQTT discovery. I will not remove MQTT discovery support, I just prefer to focus on the control panel as the discovery is the focus of the zwavejs server now

[haavardNO]

@billiaz Did you have a chance to look at this?
I have had to disable my garage remote due to this behavior.
Can't risk my garage open in the middle of the night 😊

[billiaz]

@haavardNO you are using MQTT discovery i suspect?
if so please export the Node using export button, next to the node causing this issue.
I remember we need to set a default value for HASS to understand if state is 0! but I am curious how HASS stays on 0

Giving me that ZIP can probably help me get it

[haavardNO]

Can get you that zip later today.

[haavardNO]

@billiaz see below.
node_71.json.zip

[haavardNO]

@billiaz Did you get the needed info from the zip? Let me know if there is anything else I can do to help

[billiaz]

omg! I forgot this! yes and no. let me make a payload patch( and see if works). Will try to post asap the new payload

[haavardNO]

I have now actually put a small test environment with a dedicated pi and z-stick, so I can test on these devices without messing with the live z-wave network. So I am ready :)

[billiaz]

@haavardNO I am still scrambled :)
this is a sensor! and should translate all possible states to a name not number! but I see numbers.

I want to be sure you run a recent version!
Also when value is empty, what do you believe is the state we should show?

[haavardNO]

I am running the latest version.
When I was using zwave2mqtt the scene state would be set to "inactive" until a button was pressed, then it would represent pressed / hold / release etc... And after a second or so it would return to inactive.

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label

[github-actions[bot]]

This issue is now closed due to inactivity, you can of course reopen or reference this issue if you see fit.