[bug] Unknown product/type

[larstobi]

Version

Build/Run method

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

Zwave2Mqtt version: 3.2.1 Openzwave Version: 1.6.1123

Describe the bug All the product descriptions show unknown or "()".

ID	Type	Product	Name	Location	Secure	Status	Last Active
1	Static PC Controller	ZW090 Z-Stick Gen5 EU (AEON Labs)	No	Alive	5/22/2020, 5:27:07 PM
2	Binary Power Switch	Unknown: type=0000, id=0000 (Unknown: id=0000)	No	Alive	5/22/2020, 5:32:09 PM
3	Multilevel Power Switch	Unknown: type=0000, id=0000 (Unknown: id=0000)	No	Alive	5/22/2020, 5:32:09 PM
4	Multilevel Power Switch	Unknown: type=0000, id=0000 (Unknown: id=0000)	No	Alive	5/22/2020, 5:32:09 PM
5	Multilevel Power Switch	()	No	Alive	5/22/2020, 5:34:29 PM
6	Multilevel Power Switch	()	No	Alive	5/22/2020, 5:34:29 PM
7	Multilevel Power Switch	Unknown: type=0000, id=0000 (Unknown: id=0000)	No	Alive	5/22/2020, 5:32:09 PM
9	General Thermostat V2	Unknown: type=0000, id=0000 (Unknown: id=0000)	No	Alive	5/22/2020, 5:30:24 PM
15	Binary Power Switch	Unknown: type=0000, id=0000 (Unknown: id=0000)	No	Alive	5/22/2020, 5:32:09 PM
18	Valve Open Close	Unknown: type=0000, id=0000 (Unknown: id=0000)	No	Alive	5/22/2020, 5:30:44 PM

To Reproduce Steps to reproduce the behavior:

1. Start the container
2. Leave it for a while
3. Observe the Product column

Expected behavior The product is recognized with name and model number.

Additional context I have enabled auto update database, run first time with refresh node info, and then turned it off. I have also run the docker cp openzwave folder step and mounted it in the running container.

[larstobi]

@Fishwaldo robertsLando said on Slack that you might be able to help?

[robertsLando]

Try to also add here OZW_LOG so we can debug this better

---

Daniel - Software Engineer

Support me at: Github sponsors

On 22 May 2020, at 17:59, Lars Tobias Skjong-Børsting notifications@github.com wrote:

 @Fishwaldo robertsLando said on Slack that you might be able to help?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or unsubscribe.

[larstobi]

I tried ozwdaemon, but it also has the same issue. https://gist.github.com/larstobi/7e35d71619411892d2efb33b9f36b566

[robertsLando]

@Fishwaldo

[besynnerlig]

Any progress on this?

[robertsLando]

It's not a butg with z2m but something with underling lib (or a user error/ device error), I cannot do anything to fix this on my side

[besynnerlig]

It's not a butg with z2m but something with underling lib (or a user error/ device error), I cannot do anything to fix this on my side

OK thanks. I just bought new devices and will replace them to get rid of the problem.

[darkbasic]

I had the same issue, this is due to some communication error occurred when openzwave queried for the node. The solution is to stop zwave2mqtt, remove the node from ozwcache_xxx.xml and restart it to let it requery the node.