I’m sorry, but I don’t think that this is a decoding issue. It’s just a forwarding of a RTSP Stream.
But I found out that it could be a network issue. Another Intergration (ANEL) isn’t working with the CM5. It’s a simple integration just using UDP. I’m using a HA yellow with POE.
So anybody else having network issues with the CM5? When I switch back to the CM4 everything works again.
Now I’m pretty sure that there are network issues with at least my CM5.
-I’ve laggy RTSP Streams with the CM5 and Ethernet connected with 1Gbit. When I switch back!! to 100MBit the streams are fine. Tested with Unifi, Cisco an Netgear Switches. No Problems with the CM4 at all.
-With the CM5 installed it seems not all UDP commands are send when the destination is in a different VLAN. So my Anel devices do not respond. When HA and the device are in the same VLAN, no problem…
This is again not the case with the CM4. Tested it in different network setups.
I only have one HA yellow (POE) and only one CM5, so I’m not sure wheather the HA yellow or the CM5 is the problem.
With the release of HAOS 14.2 I thought I’d try the CM5 again. Installed CM5 lite fine with NVMe, installed a fresh 14.2 and booted ok, and logged in with a new account without doing a restore. As soon as I tried to install the ZHA integration it errored with a 500 error, so still no Zigbee or Thread radio.
1 Like
Seeing the same things with a Yellow + CM5 8GB with an NVMe, this is the log
Logger: aiohttp.server
Source: /usr/local/lib/python3.13/site-packages/aiohttp/web_protocol.py:451
First occurred: 1:05:01 PM (1 occurrences)
Last logged: 1:05:01 PM
Error handling request
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 113, in list_serial_ports
yellow_radio = next(p for p in ports if p.device == "/dev/ttyAMA1")
StopIteration
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/aiohttp/web_protocol.py", line 480, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/web_app.py", line 569, in _handle
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 86, in ban_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
result = await handler(request, **request.match_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin
return await func(self, request, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper
return await method(view, request, data, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 172, in post
return await self._post_impl(request, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 179, in _post_impl
return await super()._post_impl(request, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 84, in _post_impl
result = await self._flow_mgr.async_init(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<2 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1315, in async_init
flow, result = await self._async_init(flow_id, handler, context, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1350, in _async_init
result = await self._async_handle_step(flow, flow.init_step, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 491, in _async_handle_step
result: _FlowResultT = await getattr(flow, method)(user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 546, in async_step_user
return await self.async_step_choose_serial_port(user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 188, in async_step_choose_serial_port
ports = await list_serial_ports(self.hass)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: coroutine raised StopIteration
Ended up just setting up zigbee2mqtt instead of ZHA
1 Like
Hej,
I am new to HA Yellow and was wondering if someone tested already the CM5 with both:
- the original HA Yellow heatsink (which is also used for the CM4)
- and the official Raspberry Pi 5 heatsink?
Is one of those better working in the HA Yellow or are both equally good options for the HA Yellow?
Same issue here. This is frustrating. They said it was just a simple swap cm4 lite to cm5 lite and everything works.
1 Like
Has anyone opened an issue in the Home Assistant OS repo about this? just curious, planning on buying a CM5 soon and I do use ZHA… wondering if maybe they just don’t know about this issue…
I am successfully using a CM5 with the HA Yellow’s built-in Zigbee radio under Zigbee2MQTT. I have not tried ZHA, though…
1 Like
Is Zigbee2MQTT able to add devices and entities directly into Home Assistant like Z-Wave JS UI or does it require the MQTT Broker? because I am done with MQTT, its honestly an unnecessary additional point of failure, at least in my setup…
Zigbee2MQTT does require a MQTT broker. I use the Mosquitto MQTT add-on.
Well, as many of you did an upgrade to Pi5 I would like to leverage on your experience
I am going to upgrade my yellow with power kit from:
CM4102000 - Raspberry Pi Compute Module 4 - WiFi - 2GB RAM - 0GB Storage (Lite) with 250GB M.2 SSD NVMe - Samsung 970 EVO Plus
To:
CM5116032 - Raspberry Pi Compute Module 5 - WiFi - 16GB RAM - 32GB Storage
(And plan to keep the SSD)
Do I have touse the simple or the more complex method?
Any other hints to observe?
Thanks to all
Based on the above, it sounds like your current HA Yellow is booting HAOS directly off of the m.2 NVME SSD drive, correct?
If yes, make sure yuo are running the latest version of HAOS, then create a full backup of your system. Make sure to copy the backup file off of the HA Yellow to your dekstop/laptop computer. This is simply in case something was to go terribly wrong. After you have a good backup file safely secured, you can perform an orderly shutdown of the HA Yellow. Then, remove power, swap out the CM4 with the new CM5, reconnect the wires, and you should be good to go! It was that easy for my upgrade.
Thanks,
Yes as my module 4 is a ‚lite‘ version with no internal storage it’s booting from the ssd.
The new module 5 does have internal storage, so it would be able to boot from this storage and I am not sure, whether it will instead boot from the ssd or if I have to flash the internal storage.
Did you upgrade from 4 lite to 5 lite or from 4lite to 5 with storage (eMMC)?
I upgraded from a CM4 with WiFi and eMMC, however I never booted it from the eMMC module. I upgraded to a CM5 module with WiFi and eMMC. I do not use the eMMC storage at all. I have a 1TB NVME SSD, which is much more reliable and performant than the eMMC drive.
If the CM5 finds no bootable operating system on the eMMC, it will then attempt to boot from the NVME drive. This is similar to how most PC BIOS systems will try booting from USB, then CD-ROM, then a SSD/HDD, and finally the network. The RPi also has a boot order that it uses. As long as the eMMC is empty on a CM4/CM5 module, it will skip over it and try to boot from the NVME drive.
sounds good, thanks
1 Like
ugh, wish I would have seen this thread before tonight. I was able to successfully get my CM4 swapped for a CM5 variant with more RAM. But alas i’m running into the dreaded Silicon Labs Multiprotocol error and ZHA and Thread are dead.
failed to connect, secondary seems unresponsive
Also seeing this after upgrading to a CM5 today.
Ugh.
Crisis averted. By some combination of resetting the Silicon Labs Multiprotocol add-on to its default settings and shutting down my HA yellow and physically power cycling it, my zigbee devices are back online. Now i’m not going to touch anything…
1 Like
Follow up: I successfully upgraded to CM5.
Physically it was pretty easy, I already got a new heatsink, which need to be installed a little bit different. It’s being fixed with screws, which are applied from underneath. So don’t fix the CM5 to the board with the screws but put the new heatsink from above and fixed with the applied longer screws from underneath.
The new boot process went smoothly, however I did have some unexpected issues afterwards.
a) I needed to reload the modus integration afterwards manually to make the connection work, this was only required after the first reboot.
b) Homekit bridges didn’t connect at all. I first tried to reboot, no difference. Then I deleted on of my bridges and configured a new one, added this to HomeKit and suddenly all others showed up as well. However I still have connection issues in between. I takes sometimes very long until the devices show up in HomeKit on a new device, although my AppleTV should handle all connections for all devices (iPhone, Mac, etc.)
No idea at all what’s behind those issues. Just wanted to let others know, that those issues may occur and may just as well be solved without any big changes.
1 Like