Closed Vlad-Star closed 3 years ago
The z-wave integration and the most recent open z-wave configs linked in your issue description are not compatible...
@frenck hmm... my assumption was that the device definitions were pretty much abstract from the service calls.
So, the question is how do I make it compatible? 1) Comment out "config_path: /config/open-zwave/config" line, then remove and re-add the lock? 2) Disable standard zwave integration and install/enable "openzwave" community addon? What happens to the existing 40+ zwave devices in this case? Will I have to exclude and re-include all zwave devices?
Thanks!
The master branch for the openzwave project is based on OpenZWave 1.6. The zwave
integration uses OpenZWave 1.4, the device definitions are not compatible. The latest available device database for 1.4, is already shipped with Home Assistant.
The openzwave integration is currently in beta (and based on OpenZWave 1.6). There is a community guide available in case you want to try: https://community.home-assistant.io/t/how-to-test-the-ozw-beta-without-fully-switching-over/211282
Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with an integration (zwave
) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
lock.get_usercode service returns the following error: expected int for dictionary value @ data['code_slot'] Lock itself is recognized and working correctly in HA, showing its status in HA, can be locked/unlocked etc.
The service call is made via Developer Tools -> Services -> Service: "lock.get_usercode"
Environment
Hassio 0.114.4 with standard Z-Wave integration and the most recent Openzwave configs
Hardware:
Systems Info:
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
core.device_registry
core.entity_registry: