Sadly it did not, it was just he Compute Module itself. Which to be fair is what the listing at Raspberry.dk did indicate, so I can;t be mad at that really.
Your listing does indicate more things included, so hey there you go
If that should add up to 40 euros difference … well that is up for debate.
If it runs better as a SHS, frankly I don’t know. Im not setting one up as the hardware is more then capable for my purposes (without the board upgrade it was fine, but I was lacking RAM a bit)
Before I reach the RAM cap now with the new board, well that likely is not going to happen any time soon. Storage, well … unless I do something crazy … not even in the upcoming decades.
Compared to the old board, yeah speed-wise it just seems to have the overhead so that it can now do stuff without getting bottlenecked. SHS on various hardware could supersede my setup in specs that’s for sure, but SHS in most cases is on hardware that lacks all the antenna’s etc that are onboard in the Homey Pro package. And yes you could get a Homey Bridge to combat most but protocols … then you are running multiple devices for you smart home control. (Which can be fine. but I myself I want to have as minimal as needed to run it all)
Yep seen that one as well, it seems combining the original Homey Pro Early 2023 package with a Pi5 CM board simply does not work. Not entirely sure why but it might be something checking for a certain range or something. (This is just pure speculation on my point)
Building a SHS version of a Pi5 Compute module with specific compatible antenna’s … in theory .. should work. But if you are going an SHS route … I think there might be better configs price/spec-wise you could achieve.
I now cool an early23, an early26 and a Raspberry Pi (Home Assistant) with an 80 mm fan. The fan speed is controlled by a Shelly RGBW depending on the temperature.
I use Flows to ensure that the temperature remains between 30 and 40°C. These temperatures are very consistent, regardless of whether it is summer or winter.
The additional housing (3D printed), which can be attached to the Homey without tools, offers enough space for the fan and the Shelly. However, it requires its own 12-volt power supply.
PS:
I already have a Homey SHS running on a Raspi 5 with 16 GB RAM. If you add up all the costs (including bridge and lifetime licence), you’ll need to budget around €450.
The plan is to install Homey and HA on a NUC 13. With a Core i7, it offers many times the performance of a Raspberry. However, the NUC will not be any faster in terms of speed. Even the Raspi 5 offers only very slight speed advantages over the CM4. The apps start up a little faster. The biggest advantage is the RAM.
The CM module has 8GB storage, but to use it you need to jailbrake your homey, for just memory upgrade there is no jailbrake needed, only repacement of the CM and restoring USB backup.
I have still 1.5GB of free space (of the 4GB), so currently no use for more storage.
There was price and deliver time difference between the 8GB and 32GB module, the 32GB was not in stock for a few weeks. My Homey was hitting the limits constantly and the 8GB was in stock, this was at the moment the quickest way to solve the problem.
But also keep in mind, if I run out of space I stil can get the 4GB extra storage by jailbraking my Homey to 8GB. At the moment I don’t see the need for even more space.
But feel free to buy your own CM module and increase storage space, but keep in mind you do need to jailbrake it eachtime again after a new homey update is released and is installed (this is what I read somewhere)
I am also not sure what is gonna happen if you use actually use more space then 4GB and a new Homey update is installed. The storage is then set back again to its original size 4GB, I could guess youre setup is then corrupted….
But maybe the jailbrake is not lost at all after an homey update and then there is nothing to worry about, I could not find this info yet.
the memory, aka RAM, is mentioned above the storage aka eMMC/SSD/disk/drive, the place to store your files and OS.
The RAM/MEMORY is different for the three, Pro 23: 2GB, Pro mini: 1GB, Pro 26: 4GB
The storage is not: Pro 23: 8GB, Pro mini: 8GB, Pro 26: 8GB
So when you want to restore Homey OS to
only 4GB flash storage… it needs 5.3 GB for both partitions, not to mention additional user space.
Not true ! Or at least I doubt that its necessary anymore (with my lately experience and also the release of Homey SHS) Begin of december (25) I upgraded my Homey Pro 2023 to a CM410832 Module, so 8GB Memeory and 32 GB of storage. after restoring my USB image with Homey firmware version 12.90 and expaded the storage (partition) from original 8GB to 32 GB (once!!) I already have updated to Homey Pro 2023 firmware version 12.92 and later to version 12.10 without ! any changes after the firmware update and so also not required “jail breaking” again to adjust/expand the storage (partition) to 32 GB again. Did it so ONLY ONCE at the CM4 upgrade and never again (until now) ! And Also did a full cloud backup successful with the 8Gb memory and 32 GB storage (in full use!).
So everything (firmware & Cloud backup) is COMPLETELY working and stays so after you have swapped the CM4 module and expanded the storage partition to full capacity (mine is 32 GB) ONCE ! by what you call “jail breaking”. (I rather would call it a minor once and for all adjustment/correction. )
I do hope the ‘jailbrake’ keeps working after an update, but again in my case there is at the moment no need to jailbrake it , the original partition is more then enough for now.
It can’t unfortunately - Athom is using legacy Raspberry Kernel Linux version 6.1.21-v8+, which is not compatible with CM5 (actually maybe it is, but it would be un-stable/un-tested/not recommended) and is using old GPIO approach. With the announcements of OTA updates, I’m not sure if they will be switching kernel at this moment…
You can read more on :
More over, new LTS Kernel will be 6.18 - so it would make sense from Athom to move to this Kernel version, which require :
switching from SYSFS to the libgpiod
required OS dependent changes, starting scripts, GPIO assignments etc.
required homey-pro container adjustments to the GPIO changes
I was able to switch to the new Kernel already before but GPIO related actions were not working as it should - eg. reset button, Wifi setup etc… I gave up, the best and smoothest way is currently to use simply CM4108032 (extended space available only after repartition) or CM4108016 (same as 32 - repartition required) or CM4108008.
But strangely there is Homey SHS version that is for the raspberry pi available and If I’m not mistaken its not specifically only gor the raspberry pi 4. So If it’s also compatible with raspberry pi 5 then also CM5, isn’t it ?
I doubt they have made a special version for only the raspberry pi/CM5 models. An update to standard/main compatibility of the complete Homey software/firmware to the 5 series is more likely in my humble opinion.