Closed TabakM4n closed 3 years ago
agners
commented
3 years ago Hm, other than the update to the latest stable Linux kernel I don't see a change which might influence ZB Stick behavior.
Is your OS 6.2 installation fully up-to-date (same Core/Supervisor version as the 6.3 installation?).
Can you also check the Host log (Supervisor -> System -> Host) and see if you see a difference?
TabakM4n
commented
3 years ago Everything is updated with the latest version. I see some differences in the host logs, but I do not know what I am searching for.
The logs from the same VM just switching between HA OS versions:
Let me know if you need anything more.
tjharman
commented
3 years ago I found with 6.3 that presses of my Zigbee Button (An Xiaomi Aqura button) sometimes doesn't work, sometimes is very delayed (I'll press it and between 0-10 seconds will laps before it works)
I have rolled back to 6.2 and all it working as expected again. My other Zigbee devices seemed to function OK (Xiaomi power plugs)
I use a Zig a Zig Ah stick.
I realise this is a pretty usless post with zero logs, only offered as another datapoint for the "something's changed in 6.3 that's impacting Zigbee"
My System: Phsyical Hardware running Proxmox 7.0 HAOS in a VM, with the Zigbee Stick passed through directly.
agners
commented
3 years ago @tjharman Make sure to check CPU load.
There is really nothing special with 6.3, just a regular kernel update. Make sure to downgrade to 6.2 to double check if it is really related to the OS. In you case it seems that the integration can detect the ZHA adapter, so i don't think its related to the OP's issue.
agners
commented
3 years ago @TabakM4n
The 6.2 log shows a network related stack trace, I am surprised that this does not lead to issues on 6.2 :sweat_smile:
In both 6.2 and 6.3 the Linux kernel seems to detect a ch341 based USB to serial adapter which I guess is the POPP ZB-Stick. It is attached as ttyUSB0 in both cases. What device are you referencing in the ZHA integration?
TabakM4n
commented
3 years ago @agners
In both cases:
EZSP = Silicon Labs EmberZNet protocol: Elelabs, HUSBZB-1, Telegesis/dev/ttyUSB0 115200hardwareExactly as it is specified in the PDF, except 5 because probably this option is added to home assistant after this tutorial was made.
https://elelabs.com/wp-content/uploads/2020/07/ELU013_UG_11_HomeAssistant_Hassio_0.112.4.pdf
I see the device in Supervisor -> System -> Host -> Hardware
It connects in both versions and correctly pick up the /dev/serial/by-id/..... path but in 6.3 I get errors and I cannot add devices.
What is strange about it - is that when I add the integration in 6.3 and then downgrade to 6.2 -> the integration starts on boot without any problems.
pedrolamas
commented
3 years ago Kernel update is the reason for this problem, as described here: https://github.com/Koenkk/zigbee2mqtt/issues/8623#issuecomment-913202614
I experienced this issue myself with zigbee2mqtt and managed to confirm that previous kernels are working fine, but 5.10 and above can repro the problem with some Aqara devices (such as the door contact sensor)
tjharman
commented
3 years ago @pedrolamas Thank you so much. I shall bow out of this thread, sorry for the noise.
puddly
commented
3 years ago The kernel update seems to only affect the CH340 driver, but the Elelabs stick (and I think the POPP Zb-Stick) uses a Silicon Labs CP210x chip, which has its own driver. I don't think this was changed as well, was it?
puddly
commented
3 years ago Ignore my last comment, the Elelabs ELU013 / POPP ZB-Stick sticks definitely use the CH340 according to their docs:
This kernel change should break many CH340 devices, like the zzh! coordinator and most cheap Arduino and ESP8266/ESP32 dev kits.
agners
commented
3 years ago Linux 5.10.62 indeed fixes a CH340/CH341 related issue, specifically: https://bugzilla.kernel.org/show_bug.cgi?id=214131
I'll update the kernel to the latest version for 6.4.
agners
commented
3 years ago Only now reading @pedrolamas comment :see_no_evil: . But yeah that seems to be the culprit.
agners
commented
3 years ago For now, if you experience issues with CH340 devices, please revert back to 6.2 until 6.4 is out:
ha os update --version 6.2
bossgos
commented
3 years ago For now, if you experience issues with CH340 devices, please revert back to 6.2 until 6.4 is out:
ha os update --version 6.2
Today HASS OS 6.4 has been released. Is it still affected with this bug?
tjharman
commented
3 years ago Where do you see 6.4?
bossgos
commented
3 years ago Where do you see 6.4?
aww sorry my mistake... I was check Home Assistant Core :( with 4 at the end...
TabakM4n
commented
3 years ago I can confirm that after upgrading to HASS OS 6.4, the integration started working.
agners
commented
3 years ago This is addressed in HAOS 6.4 and newer (via kernel update PR #1536).
Hardware Environment
Home Assistant OS release:
System Health
Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 6.3 -- | -- update_channel | stable supervisor_version | supervisor-2021.09.0 docker_version | 20.10.7 disk_total | 30.8 GB disk_used | 2.7 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Visual Studio Code (3.6.2), Log Viewer (0.11.1)Lovelace
dashboards | 1 -- | -- resources | 0 mode | auto-genSupervisor logs:
Journal logs:
Kernel logs:
Description of problem:
Hello
With POPP ZA-STICK I created 4 installs of HAOS 2 on Proxmox with versions 6.2 and 6.3 2 on VM box under window with versions 6.2 and 6.3
When I try to add the integration using this turorial in both 6.2 versions ( under Proxmox and VM box) it worked perfectly fine
After trying the same in version 6.3 the integration does not work.
Furthermore I updated both 6.2 VMs to 6.3 and the integration stopped working.
Also I tried to downgrade both 6.3 to 6.2 and guess what - the integration started working again.
Log Provider Core: