That is correct. As far as I understand, he migrated from a stock HP23 to a (different) modded HP23. So to a Homey with a physically different Zigbee chip. That contributed to the issue he and several other users (including myself) faced and which is the focus of the other topic.
This is actually an interesting point.
@Jonathan_Draper: could it be that one of your (close) neighbors made changes in their WiFi network (e.g. changed internet provider and got a new WiFi router with unfavorable settings for your Zigbee network)?
I understand it that he has modded it himself 
…so no Zigbee chip change, only CM4 swap. Which reminds me potential soldering issue as well, which could be contributing factor. Yet, no Athom support naturally on something we mod yourself
[quote=“Jonathan_Draper, post:5, topic:147238”]
I have recently modded a Homey Pro 2023
[/quote]
Actually the chip changed 
;
- He has 2 Homey’s. Both are 2023 versions. The second one is the modded version.
- He made a backup from the first (unmoddrd) Homey and restored in on his second (modded) Homey.
- Although the models are the same, and use the same model of Zigbee chip, they are two physically different devices. Each Zigbee chip has its own hardware/IEEE address and its own Zigbee routing table. Both items are not part of the backup and restore (for reasons mentioned in the other topic), which causes difficulties for the new Homey to restore the Zigbee network. The larger the Zigbee network, the more likely Homey fails to rebuild the network. At least that was the info provided by Athom.
- If you are restoring a backup to the same device on which you made that backup then the above does not apply. As there is no change in Zigbee chip and the IEEE address remains the same.
Naturally, if he moved between two separate Homey”s, it’s obvious that the chip is different, however I haven’t noticed this in the message - glad you did.
Still, refer to my findings on the instabilities vs Zigbee issues - from my perspective, two different things, if you saw there was even move between two HP, then Zigbee issues are most probably related to the Zigbee restore and not instabilities issues, which is this thread primary about.
2 Likes
Overnight I had some inspiration and unplugged an in home device I got for my smart meter a week or so ago. That seems to have been the cause of this round of Zigbee issues, so I think unrelated to the backup issue and unrelated to the random reboots issue.
The search for anything correlated with the random reboots continues. Sorry to have polluted your thread @Sharkys . If I find anything else I think might be related, I’ve learned my lesson and won’t post it here.
1 Like
BTW @Sharkys you asked about undervoltage stats. Indeed it’s exactly the same and after the unexpected reboots, the rebootReason shows as “unexpected”. (Currently mine shows as ‘reboot’ because the most recent time I rebooted was actually me rebooting it. When I’ve checked it after the unexpected reboots, it does indeed show “unexpected” here.)
1 Like
Which confirms yours unexpected reboots might be the one I have… I just don’t get, wjy there is just few of us 
Hi. I bought a 2023HP, which worked fine. 2 weeks later the 2026HP came out. When I refunded the2023HP I just used that power cable with the 2026 model. They are exactly the same power cable right? Because I am having multiple issues, like everyone else.
Thanks
I think the cable is the same, but the power brick/adapter is different for sure:
Fingers crossed…
Fixed an issue that could cause Homey to crash when interacting with Insights.
1 Like
Oh the irony if the thing that’s been causing me to stare constantly at my system insights these past few weeks is crashes caused by insights
1 Like
Yeah, tell me something about that 
Yet, it must be still tested….in my case I would need 2-3 more days of uptime to confirm
So I would say, it’s fixed since I had the highest uptime this year, until I manually rebooted as part of regular reboots.
Yes I am also hopeful. I’ve not had a random reboot since moving to 12.12 beta yet (fingers crossed). I’m deliberately leaving it without planned reboot to see how long it goes. I did have a hiccup when the update step failed the first time and I was glad I’d taken a full system backup first. But in the end a reboot was enough to fix it and second attempt worked. Might have just been random. Never happened to me before though.
