After the update to 13.3.0, the Homey SHS no longer starts up after an automatic reboot. I have the Homey reboot every night. But since the update, it doesn’t start up again afterwards. The only thing I can do then is restart in Proxmox. Are there other people experiencing this?
I don’t have much knowledge about SHS and proxmox, but I do have a few troubleshoot questions that perhaps could help you or others to solve the problem..
You said that automatic reboot is not working, does manual reboot from the UI work (so not the reboot option of the vm it self)?
I assume there is a log file in proxmox that shows what happens when you start/reboot/shutdown the VM. Does this give any error messages ?
Earlier this post was created with a reboot issue with the same software version Homey SHS reboot problem. Not sure if it is the same problem or if it has the same cause, but could be a bug in this version or this update changes a setting that you won’t expect.
For a while, some apps didn’t work properly if I didn’t do it. I already had this in my Homey 2019, so it moved with me ;-)… I don’t remember the exact reason anymore. But it is a bug now, in any case!
I reboot it with a flow, so not the VM itself. I have had to do that again the last few days, though, because it is no longer accessible after a software reboot.
Dit lijkt inderdaad een bug, hier meld iemand anders het ook. Ik heb zelf Homey (ook SHS op Proxmox) nog niet bijgewerkt. Met .0 releases wacht ik altijd even
So if I understand it correctly with the flow you reboot the device every day,(which is not working any more)
But did you try to reboot it manually via the webinterface of homey and does that still work?
Creating a support ticket as @Anoniemand suggested is a good idea, but I do think they will want to have event logs of what happens when the reboot is triggered.
The same problem occurs when I reboot it manually. I see in Proxmox that the memory usage drops from about 1.5 GB to 380 MB. Only after rebooting the container in Proxmox is everything back online!
This topic is in the English category. If you could please keep the conversation in English as much as possible, then more people will be able to participate and help you. Please translate your post into English, otherwise it will be deleted in three days to keep the thread in just one language as stated in the forum rules Welcome to the forum!
Than it seems to be a bug indeed and the same issue as in the linked post earlier.
The person in the other post did contact support and support did requested some log files so they are investigating that when they received them.
I cannot find a release note of this 13.4.0-rc.1 version, so I cannot say if this issue has been adressed, but lets hope it solves the problem, that would be a quick fix compared to all the troubleshooting
So please keep us updated after you have installed this version!
It is quite possible that only the Proxmox, or actually the SHS version, has the problem.
I had read his comment, which is why I continued in English. Although I do so with the translator. My English isn’t very good, and I want to come across clearly!
Since I have updated my Unraid Homey SHS to version 13.3.0 I have problem to acces Homey after each restart. This problem happen after a restart Unraid Homey SHS (Unraid restart after automatic backups) But also acces problem after restart in Homey app, I cannot acces Homey. The led of the Homey Bridge is red. I cannot acces Homey and devices can not be used.
I can resolved this issue to restart my Unraid SHS server together with the Homey Bridge, then Homey work great again, till Homey SHS, or Homey restart, then I have to restart Server en Bridge to acces Homey again
If I check in the Homey app, I don’t see the Homey Bridge in my Homeys. Is this normal?