Homey Self-Hosted Server on Windows | Megathread

That likely uses the cloud connection, so not related here. Why don’t you use the regular web app?

This one connects using the same method as the mobile app

Thank you very much! That worked!

But, it is weird that I cannot access it locally, don’t you think?

It should be possible, but you’d first enable a local account?
https://support.homey.app/hc/en-us/articles/22924537226268-Set-up-Local-Users-on-Homey-Pro
(Sounds simple; however, this functionality is just introduced a while ago, until then it was impossible to access any Homey locally :face_with_peeking_eye: )

The actual HSHS IP address you’ll need to use, can be found here
https://my.homey.app/settings/system/general
at the ‘System Information’ part.

It did work! Thank you so much!!!

I just posted a question on the Zigbee routing topic about ZigBee existing routers. If you could please help me on that one as well, I would appreciate it.

Thanks! :blush:

Maybe obvious to everyone already, but it caught me out. Change your Windows update settings to prevent being caught out by an automatic reboot after maintenance is applied.

Stephen

Hi, I’m having problems updaten my SHS on VirtualBox. It stays on 12.10.1 even after multiple reboots (of VM and inside Homey). When I look at My Homey (local webbrowser) it shows a new version 13.2.1 and an option to download and install it, but after clicking the button there is an error: Invalid Endpoint: ManagerUpdates.installUpdate. Also the checkbox Automatic Update is not enabled (and can’t be changed with / because of error)

Also the diagnostic report shows an error: Overload Me

Whats’s weird is that My Homey shows that Wifi and Ethernet are not connected (connected No).
Is there a problem with the VM (whih shows an bridget connection).

Added:
On the console there is an error
Error 400: Invalid Endpoint: ManagerUpdates.installUpdate

Hi Joost,

This particular part, “install update”, is only usable for physical Homey models.
Updating HSHS is done by (automatically) downloading an updated Docker image;

Maybe your VM can’t reach the Athom servers.
Did you already try this VirtualBox setting:

instead of NAT mode?

To update Homey your VirtualBox host, check the howto in the knowledge base
Snippet:

Now that seems the same ‘procedure’ like you’ve tried already.
You probably should reboot the VirtualBox host machine as well if you didn’t already?

Please to use the appropriate thread for your particular host for additional questions:
https://community.homey.app/t/homey-self-hosted-server-on-windows-megathread/146434

Hi, I have Homey on a Raspberry Pi as a SHS server. After every update I see that the storage is “growing” (from ­­± 6gb to 14,6 gb at this moment).

Claude says it is a known Homey phenomenon (I can’t find it on the forum), Homey doesn’t clean old files etc. Claude suggests to solve this with a DO Raspberry Pi card “Uitvoeren/Execute” with the command “docker system prune -f”.

Claude also tells me it is safe and it won’t touch running containers but hey… I am a user (not a code programmer), so I can’t judge if this is true or that Claude is hallucinating :grinning_face: .

Therefor my question is, is this a safe way to clean old files etc, has anyone experience with this?

Thanks in advance!

That sounds like the “old” image is still there. Maybe you’d have to bin it yourself?

Not meant as being smartass, but you can think of creating a backup or copy first (but you already have a backup system in place I presume), and then plunge into the deep and test if Claude is fooling you, or not, on the live container.

Hi Peter,

Thanks for your reply which I, btw, don’t consider as a smartass one :smile: , I am glad that you reacted.

I do have a backup of the /homey-shs/ folder so I could try it like you suggested it. But I was hoping someone had allready tried this :slight_smile: because more people should have had the same issue as I have.

Anyway… as impatient as I am, I’ve used several AI tools and they all confirmed the same solution. So I 've tried the command “sudo docker system prune -f” (instead of the earlier mentioned command) and it worked (back to 6 gb).

My flow is now like this (maybe helpfull for others).

Ah, nice to hear you took the plunge​:wink:
Docker docs would be the most reliable source imho :saluting_face: (me is not that into AI hehe):

And,
Entering this at the prompt (should) returns valid commands and their flags
$ man docker

Hi, I tried both network setting. Unsuccessful.

Also the suggested restart of the host (VirtualBox) No succes

Any idea how to force the update or see what’s causing it not to update?

One more question:
I get an error on start:
Error response from daemon: No such container: homey-shs

Could this be related?