Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Device shows as Unknown product even though manufacturer, product and product code are detected correctly #3401

Closed
3 tasks done
chaosjug opened this issue Nov 2, 2023 · 7 comments
Labels
bug Something isn't working

Comments

@chaosjug
Copy link

chaosjug commented Nov 2, 2023

Checklist

  • I am not using Home Assistant. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog and my problem is not mentioned there.

Deploy method

Docker

Z-Wave JS UI version

9.3.1.f26b97e

ZwaveJS version

12.2.3

Describe the bug

I'm just starting with z-wave so I have only two devices. An UZB stick and FGR222.
In the control panel both show up as "Unknown manufacturer" / "Unknown product" but in both cases manufacturer, product and product code (the hex numbers) are correct and if I click on the link next to the ids the correct page on devices.zwave-js.io opens.
As a result I can't configure the devices.
Reinterviewing did not help.
image

To Reproduce

When I first started, both devices showed up correctly. Then I moved the docker to another machine. (I use a folder not volumes, so I just copied the folder). After starting up again I reconfigured the device for the z-wave stick (now tcp (ser2net) instead of local device). And now both devices are "Unknown product". As I don't know how to get back, I don't know if I could reproduce it that way.

Expected behavior

Devices should be detected correctly.

Additional context

No response

@chaosjug chaosjug added the bug Something isn't working label Nov 2, 2023
@robertsLando
Copy link
Member

robertsLando commented Nov 3, 2023

Please make a driver log, loglevel debug and attach it here as a file (drag & drop into the text field).

CC @AlCalzone

@apella12
Copy link
Contributor

apella12 commented Nov 3, 2023

Could also try to reinterview node (at least the device, not sure about controller)

@chaosjug
Copy link
Author

chaosjug commented Nov 3, 2023

Debug logging was already enabled so I had some files to choose from. I took the one from yesterday as zwave-js was restarted several times, I hope that gives more information than just the system running without much activity. Note that the host which provides the zwave stick with ser2net was offline for some time which caused the docker to restart several times.
zwavejs_2023-11-02.log.gz

If I should do something specific while logging please tell me.
Regarding the reinterview: As stated above, I did that already several times with both with no effect.

@kpine
Copy link
Contributor

kpine commented Nov 3, 2023

I would guess something is wrong with your installation because the device configuration files aren't being found.

2023-11-02T20:17:29.850Z CNTRLR   [Node 001] No device config found
2023-11-02T20:17:29.852Z CNTRLR   [Node 003] No device config found
2023-11-02T20:30:23.158Z CNTRLR   [Node 003] ConfigurationCC: skipping interview because CC version is < 3 and t
                                  here is no config file

Perhaps you can describe how you are running ZUI under docker, e.g. show your command line or docker compose file.

@chaosjug
Copy link
Author

chaosjug commented Nov 3, 2023

I start the docker with a systemd service with this command:
docker run --name=%n -p 8091:8091 -p 3000:3000 \
-v /opt/zwave:/usr/src/app/store \
zwavejs/zwave-js-ui:9

Everything what's in /opt/zwave/ came from the other machine, where I did originally set things up. Where should the device configuration files be and how do they get there? Can I trigger a download somewhere and do I need to map another directory in addition to /usr/src/app/store to keep those files permanently?

@kpine
Copy link
Contributor

kpine commented Nov 3, 2023

You could try stopping the container, then deleting the /opt/zwave/.config-db directory, then start it again. That should rebuild the local copy of the device files. Usually it's updated automatically, not sure if something happened with the migration.

@chaosjug
Copy link
Author

chaosjug commented Nov 3, 2023

That did the trick! Thanks a lot!
I moved the folder away so I could check the differences. A lot of files are missing in the old folder. From what I could reconstruct, I did not move that folder to the new host, as it is a hidden directory. What I don't understand is why it wasn't recreated correctly at first, but was recreated correctly now.
I'll close this issue for now. If I can reproduce the issue, I'll reopen or open new issue.

@chaosjug chaosjug closed this as completed Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants