itnassol
July 12, 2023, 7:20am
1
Since the last update I have noticed that a number of my automations are not running, these are all linked to Z-Wave devices. If I add an automation from the device it sees the device but if I add it from scratch it’s not there. Any ideas?
rossk
July 12, 2023, 8:13am
2
Maybe the same issue that others have been reporting recently:
opened 01:15PM - 11 Jul 23 UTC
integration: zha
### The problem
In me Home Assistant I have both ZHA and Zigbee2MQTT. Most of m… y devices are on ZHA but some that dont work with ZHA are pair with Z2M network.
When I try create an automation and use DEVICE as trigger or condition, I start typing the name of my device and if is connected to ZHA is now showing up at all. If is connected to Z2M is showing fine, so it must be a ZHA integration bug from the past few 2023 versions (not sure when last worked).
I have reported the problem here and there are some screenshots:
https://community.home-assistant.io/t/ha-automations-bug-does-not-show-devices-in-automations-any-fix/590651
I have been using DEVICE for all my triggers before and it used to work fine, but since past 2-3 versions is not working anymore.
### What version of Home Assistant Core has the issue?
## System Information version | core-2023.7.1 -- | -- installation_type | Home Assistant Supervised dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.11.4 os_name | Linux os_version | 5.10.0-20-amd64 arch | x86_64 timezone | Europe/Sofia config_dir | /config <details><summary>Home Assistant Community Store</summary> GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4825 Installed Version | 1.32.1 Stage | running Available Repositories | 1276 Downloaded Repositories | 27 </details> <details><summary>Home Assistant Cloud</summary> logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok </details> <details><summary>Home Assistant Supervisor</summary> host_os | Debian GNU/Linux 11 (bullseye) -- | -- update_channel | stable supervisor_version | supervisor-2023.07.1 agent_version | 1.4.1 docker_version | 20.10.22 disk_total | 232.7 GB disk_used | 24.7 GB healthy | true supported | true supervisor_api | ok version_api | ok installed_addons | Plex Media Server (3.2.4), Spotify Connect (0.12.4), Samba share (10.0.2), File editor (5.6.0), Home Assistant Google Drive Backup (0.111.1), Cloudflared (4.1.9), Terminal & SSH (9.7.1), Mosquitto broker (6.2.1), Zigbee2MQTT (1.32.1-1), MariaDB (2.6.1), Advanced SSH & Web Terminal (15.0.3), motionEye (0.19.1), Studio Code Server (5.8.1) </details> <details><summary>Dashboards</summary> dashboards | 4 -- | -- resources | 17 views | 13 mode | storage </details> <details><summary>Recorder</summary> oldest_recorder_run | July 1, 2023 at 2:04 AM -- | -- current_recorder_run | July 11, 2023 at 3:50 PM estimated_db_size | 553.44 MiB database_engine | mysql database_version | 10.6.12 </details>
### What was the last working version of Home Assistant Core?
I DONT KNOW
### What type of installation are you running?
Home Assistant Container
### Integration causing the issue
## System Information version | core-2023.7.1 -- | -- installation_type | Home Assistant Supervised dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.11.4 os_name | Linux os_version | 5.10.0-20-amd64 arch | x86_64 timezone | Europe/Sofia config_dir | /config <details><summary>Home Assistant Community Store</summary> GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4825 Installed Version | 1.32.1 Stage | running Available Repositories | 1276 Downloaded Repositories | 27 </details> <details><summary>Home Assistant Cloud</summary> logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok </details> <details><summary>Home Assistant Supervisor</summary> host_os | Debian GNU/Linux 11 (bullseye) -- | -- update_channel | stable supervisor_version | supervisor-2023.07.1 agent_version | 1.4.1 docker_version | 20.10.22 disk_total | 232.7 GB disk_used | 24.7 GB healthy | true supported | true supervisor_api | ok version_api | ok installed_addons | Plex Media Server (3.2.4), Spotify Connect (0.12.4), Samba share (10.0.2), File editor (5.6.0), Home Assistant Google Drive Backup (0.111.1), Cloudflared (4.1.9), Terminal & SSH (9.7.1), Mosquitto broker (6.2.1), Zigbee2MQTT (1.32.1-1), MariaDB (2.6.1), Advanced SSH & Web Terminal (15.0.3), motionEye (0.19.1), Studio Code Server (5.8.1) </details> <details><summary>Dashboards</summary> dashboards | 4 -- | -- resources | 17 views | 13 mode | storage </details> <details><summary>Recorder</summary> oldest_recorder_run | July 1, 2023 at 2:04 AM -- | -- current_recorder_run | July 11, 2023 at 3:50 PM estimated_db_size | 553.44 MiB database_engine | mysql database_version | 10.6.12 </details>
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
### Diagnostics information
[config_entry-zha-1be608adfd5dabaaecaf06df5a0aa201.json.txt](https://github.com/home-assistant/core/files/12015014/config_entry-zha-1be608adfd5dabaaecaf06df5a0aa201.json.txt)
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
All my devices are working fine both on ZHA and Z2M network. All old automations are working fine, both with ZHA and Z2M devices. The only issue is when creating new automations or editing one automations. When selecting DEVICE as trigger or condition, the ZHA devices are NOT showing. Z2M devices are showing fine.