home-assistant[bot]
commented
4 weeks ago Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `zwave_js` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zwave_js` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.(message by CodeOwnersMention)
zwave_js documentation zwave_js source (message by IssueLinks)
btbutts
The problem
I recently upgraded to a Z-Wave 800 series controller. I'm using the Zooz ZAC93 on a Raspberry Pi 5. I've been able to configure HA to use the Z-Wave GPIO HAT and when I configure the Official Z-Wave JS add-on via the add-on store, it sees
/dev/ttyAMA0without an issue.However, when viewing the Z-Wave JS Integration via the Devices & services page, configuring it (Add new Hub) and leave the default option "Use the Z-Wave JS Supervisor add-on" checked, the Z-Wave JS Integration only shows
/dev/ttyAMA10and two Sonoff ZBDongle-E sticks I'm using for Zigbee and Thread. The/dev/ttyAMA0is missing. This is of course a problem as for testing since I actually tried to setup a brand new HA instance on a new Home Assistant install (I'm running HASSOS), where I would then need to allow the Z-Wave JS Integration setup wizard to generate new Keys for the Legacy S0 and newer S2 and S2 LR networks.Without the Z-Wave JS integration showing
/dev/ttyAMA0, even though the official Z-Wave JS Add-On does, the Z-Wave JS Integration is unable to generate the keys I previously mentioned since it doesn't have a valid controller selected. I can force my way through this step by temporarily selecting/dev/ttyAMA10, which will of course fail (that's just the RPi5's console output) but it does allow the Integration to generate the required keys in the Official (Supervisor) Z-Wave JS Add-on. Then I need only to modify Z-Wave JS Add-on afterwards to use/dev/ttyAMA0once again and restart the Add-On. After that. The respective Z-Wave integration is updated, and I can now see my controller.Furthermore, I've been able to confirm that HA can successfully see my controller because I can see in the Z-Wave JS add-on logs that it is successfully connecting to the controller, scanning the nodes, and the controller information is visible in the integration config screen. I even used Simplicity Studio to import my Z-Wave network from a 500 series controller into the new 800 series controller (ZAC93), changed the keys appropriately in HA, and then watched as all of my nodes became visible in Home Assistant after a restart. I could control them too. The problem is that when I would try to add new nodes via the Z-Wave integration, that would fail. There would be two simple logs each time, regardless of the type of node I tried to add:
Now if I attempt to turn off a light, dim a light, etc... of a node that's already in the Z-Wave network. I can do that just fine. I even tried a firmware upgrade of the controller just to verify that the RPi5 has a valid I2C connection with the controller. the UART and I2C are working. The add-on seems to be working. It's the integration that's configuration doesn't seem to recognize the controller installed at
/dev/ttyAMA0and thus I believe where the problems start.Just for fun, I decided to remove the official Z-Wave JS add-on and integration and try out the Unofficial Z-Wave JS UI add-on just to see what would happen. It, just as the official add-on, has no issue connecting to the controller installed at
/dev/ttyAMA0. I was able to get the Official Z-Wave integration to connect to the "Z-Wave JS UI" add-on as well. However, when attempting to add new nodes via the integration, I saw the same behavior as I had with the official Z-Wave JS Supervisor add-on. No change at all. When I tried it with an existing Z-Wave network, I could control my nodes as well. It would appear that both add-ons seem to do their job just fine. However, the integration is where the issue exists.There seems to be some issue with the Z-Wave integration using controllers at
/dev/ttyAMA0for some reason, even though the add-on works with them just fine. There's no controller connection issues in the logs whatsoever actually.What version of Home Assistant Core has the issue?
core-2024.6.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Z-Wave JS
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave_js/
Diagnostics information
{ "home_assistant": { "installation_type": "Home Assistant OS", "version": "2024.6.1", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.12.2", "docker": true, "arch": "aarch64", "timezone": "America/Chicago", "os_name": "Linux", "os_version": "6.6.28-haos-raspi", "supervisor": "2024.06.0", "host_os": "Home Assistant OS 12.3", "docker_version": "25.0.5", "chassis": "embedded", "run_as_root": true }, "custom_components": { "hacs": { "documentation": "https://hacs.xyz/docs/configuration/start", "version": "1.34.0", "requirements": [ "aiogithubapi>=22.10.1" ] }, "ttlock": { "documentation": "https://github.com/jbergler/hass-ttlock", "version": "v0.6.2", "requirements": [ "pydantic" ] }, "tuya_ble": { "documentation": "https://www.home-assistant.io/integrations/tuya_ble", "version": "0.1.8", "requirements": [ "tuya-iot-py-sdk==0.6.6", "pycountry==22.3.5" ] }, "huesyncbox": { "documentation": "https://github.com/mvdwetering/huesyncbox", "version": "2.1.0", "requirements": [ "aiohuesyncbox==0.0.27" ] }, "ble_monitor": { "documentation": "https://github.com/custom-components/ble_monitor", "version": "12.11.2", "requirements": [ "pycryptodomex>=3.19.1", "janus>=1.0.0", "aioblescan>=0.2.14", "btsocket>=0.2.0", "pyric>=0.1.6.3" ] }, "smartthinq_sensors": { "documentation": "https://github.com/ollo69/ha-smartthinq-sensors", "version": "0.39.1", "requirements": [ "pycountry>=23.12.11", "xmltodict>=0.13.0", "charset_normalizer>=3.2.0" ] } }, "integration_manifest": { "domain": "zwave_js", "name": "Z-Wave", "codeowners": [ "home-assistant/z-wave" ], "config_flow": true, "dependencies": [ "http", "repairs", "usb", "websocket_api" ], "documentation": "https://www.home-assistant.io/integrations/zwave_js", "integration_type": "hub", "iot_class": "local_push", "loggers": [ "zwave_js_server" ], "quality_scale": "platinum", "requirements": [ "pyserial==3.5", "zwave-js-server-python==0.56.0" ], "usb": [ { "vid": "0658", "pid": "0200", "known_devices": [ "Aeotec Z-Stick Gen5+", "Z-WaveMe UZB" ] }, { "vid": "10C4", "pid": "8A2A", "description": "z-wave", "known_devices": [ "Nortek HUSBZB-1" ] } ], "zeroconf": [ "_zwave-js-server._tcp.local." ], "is_built_in": true }, "setup_times": {}, "data": { "versionInfo": { "driverVersion": "12.5.5", "serverVersion": "1.35.0", "minSchemaVersion": 0, "maxSchemaVersion": 35 }, "entities": [], "state": { "nodeId": 1, "index": 0, "status": 4, "ready": true, "isListening": true, "isRouting": true, "manufacturerId": 634, "productId": 1553, "productType": 4, "firmwareVersion": "1.10", "deviceConfig": { "filename": "/data/db/devices/0x027a/zac93.json", "isEmbedded": true, "manufacturer": "Zooz", "manufacturerId": 634, "label": "ZAC93", "description": "800 Series Long Range GPIO Module", "devices": [ { "productType": 4, "productId": 1553 } ], "firmwareVersion": { "min": "0.0", "max": "255.255" }, "preferred": false, "metadata": { "comments": [] } }, "label": "ZAC93", "interviewAttempts": 1, "isFrequentListening": false, "maxDataRate": 100000, "supportedDataRates": [ 40000, 100000 ], "protocolVersion": 3, "supportsBeaming": true, "supportsSecurity": false, "nodeType": 0, "deviceClass": { "basic": { "key": 2, "label": "Static Controller" }, "generic": { "key": 1, "label": "Remote Controller" }, "specific": { "key": 0, "label": "Unused" }, "mandatorySupportedCCs": [], "mandatoryControlledCCs": [ 32 ] }, "interviewStage": "Complete", "deviceDatabaseUrl": "https://devices.zwave-js.io/?jumpTo=0x027a:0x0004:0x0611:1.10", "statistics": { "commandsTX": 0, "commandsRX": 0, "commandsDroppedRX": 0, "commandsDroppedTX": 0, "timeoutResponse": 0 }, "isControllerNode": true, "keepAwake": false, "protocol": 0, "values": { "1-32-0-currentValue": { "endpoint": 0, "commandClass": 32, "commandClassName": "Basic", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 0, "metadata": { "type": "number", "readable": true, "writeable": false, "label": "Current value", "min": 0, "max": 99, "stateful": true, "secret": false } } }, "endpoints": { "0": { "nodeId": 1, "index": 0, "deviceClass": { "basic": { "key": 2, "label": "Static Controller" }, "generic": { "key": 1, "label": "Remote Controller" }, "specific": { "key": 0, "label": "Unused" }, "mandatorySupportedCCs": [], "mandatoryControlledCCs": [ 32 ] }, "commandClasses": [] } } } } }
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response