I’m still finding my way with the new homey equipment and have got an issue I don’t understand at all.
I’m running the server from my ugreen Nas visa docker. Tonight it said there were updates I had to do, so I did them and now the server won’t connect. All the stuff I can find on the internet seems to come from a position of knowing how all of this works already and it’s all new to me.
Because it was the first one I set up the self-hosted server (shs) is the primary and my homey pro is secondary as far as homey link is concerned. The couple of things I set up on the Pro are still connecting but all the devices on the shs are incommunicado and the apps all say that the shs is offline.
I’ve tried everything I can think of so far but to no avail. What the heck have I done wrong?
Can you check More->Homey SHS (your Homey name)->Add new Homey->Self-Hosted Server. Does it show up there?
If it’s visible there, you might have erased your Homey configuration. Do you have backups?
No, no sign of it there at all. The l option only comes up under the homey pro, although the option to select the SHS is there a step earlier. No, no backups as of yet because 1) I’m experimenting with hardware and the SHS to see which setup I want to stick with. 2) I want aware of options to make backups as I’ve not looked into that due to #1.
Might it be easiest at this point to delete it and re-add?
Slainte,
Jim
What exactly said there were updates? Ugreen Nas or Homey SHS?
We all have to start somewhere 
I don’t have a Ugreen NAS, but using the screenshots in the installation guide:
- Is the docker container currently running?
- What’s visible in the “logs” tab?
It was the NAS that asked for the updates, I think, as it was the Docker stuff needing it. Can’t see Homey asking for that to be done. I was careless and just followed my phone notifications without really reading them which I know is kinda dumb but I wasn’t thinking. I’m normally more careful than that.
What’s currently running:
Log file is attached, assuming it comes over from this email.
I’m a bit annoyed with Homey today, tbh. I ordered a Mini to try out whilst awaiting Curry’s to contact me about the re-furbed Pro I was sent as new. The Mini is also a refurb but this time sent from Homey’s Amazon page. THREE sets of security stickers applied on top of each other, the plastic cover obviously re-applied by hand and no USB cable in the box. If I didn’t like the way Homey works as much as I do this might have been enough to get me to give up on it all together.
(Attachment export_log_20260603165941.txt is missing)
That log file didn’t attach so here’s the txt:
toTime: all
level: all
operator: all
content: all
fromTime: all
create_time level operator content
2026-06-01 22:31:03 info gonk homey-shs container restart successfully
2026-06-01 22:30:57 info gonk ghcr.io_athombv_homey-shs-1 container restart successfully
2026-06-01 22:25:03 info gonk Successfully created ghcr.io_athombv_homey-shs-1 container
2026-06-01 22:24:05 info gonk Successfully deleted ghcr.io/athombv/homey-shs: image
2026-06-01 22:20:59 info system one-click update task execution completed
2026-06-01 22:20:59 info system container ‘homey-shs’ updated successfully, its image ‘Package homey-shs · GitHub’ has been updated to the latest version.
2026-06-01 22:19:59 info gonk starting one-click update task: Package homey-shs · GitHub
2026-06-01 20:46:29 info system docker engine status change to online
2026-06-01 20:44:39 info system docker engine status change to online
2026-06-01 20:44:39 warn system Engine startup failed, reason: Get “http://%2Fvar%2Frun%2Fdocker.sock/_ping”: context deadline exceeded
2026-05-10 23:20:01 info gonk successfull deploy project ‘homey-shs’
2026-05-04 15:16:39 info system docker engine status change to online
2026-05-04 15:16:39 warn system Engine startup failed, reason: Get “http://%2Fvar%2Frun%2Fdocker.sock/_ping”: context deadline exceeded
2026-05-01 17:38:09 warn system Engine startup failed, reason: Get “http://%2Fvar%2Frun%2Fdocker.sock/_ping”: context deadline exceeded
2026-05-01 17:38:08 info system docker engine status change to online
2026-05-01 11:06:48 info system docker engine status change to online
2026-05-01 11:05:17 warn system Engine startup failed, reason: Get “http://%2Fvar%2Frun%2Fdocker.sock/_ping”: context deadline exceeded
2026-05-01 11:05:17 info system docker engine status change to online
2026-04-14 00:33:08 info system successfull down project ‘homeassistant’
2026-04-14 00:33:08 info system Successfully deleted ugreen/home-assistant:v2 image
2026-04-14 00:18:48 info system docker engine status change to online
2026-04-14 00:18:48 warn system Engine startup failed, reason: Get “http://%2Fvar%2Frun%2Fdocker.sock/_ping”: context deadline exceeded
2026-04-14 00:15:49 warn system docker engine status change to offline
2026-03-31 13:35:25 info system successfull start project ‘homeassistant’
2026-03-31 13:29:02 info system docker engine status change to online
2026-02-13 11:53:55 info system docker engine status change to online
2026-02-03 13:28:02 info system docker engine status change to online
2026-01-21 19:59:36 info system docker engine status change to online
2026-01-17 18:13:41 warn system docker engine status change to offline
2026-01-17 18:09:22 info system docker engine status change to online
2025-12-29 19:54:22 info system docker engine status change to online
2025-12-29 15:37:09 info system docker engine status change to online
2025-12-29 15:35:36 warn system docker engine status change to offline
2025-12-29 15:35:21 info system docker engine status change to online
2025-12-18 01:15:07 warn system docker engine status change to offline
2025-12-02 13:52:40 info system docker engine status change to online
2025-12-02 13:51:16 info system docker engine status change to online
2025-11-09 13:41:41 info system successfull start project ‘jellyfin’
2025-11-09 13:38:37 info system successfull start project ‘homeassistant’
2025-11-07 16:11:40 info system docker engine status change to online
2025-11-06 13:15:09 warn system docker engine status change to offline
2025-11-01 23:11:38 info system docker engine status change to online
2025-11-01 23:09:03 info system docker engine status change to online
2025-10-31 13:53:50 info system docker engine status change to online
2025-10-21 02:17:46 warn system docker engine status change to offline
2025-10-20 14:53:30 info system docker engine status change to online
2025-10-20 01:19:38 warn system docker engine status change to offline
2025-10-19 17:04:14 info system docker engine status change to online
2025-10-19 01:28:50 warn system docker engine status change to offline
2025-10-18 19:53:09 info system docker engine status change to online
2025-10-18 19:51:37 warn system docker engine status change to offline
2025-10-16 20:42:55 info system docker engine status change to online
2025-10-16 20:42:49 info system docker shared folder: /volume1/docker create success
2025-10-16 20:42:49 info system docker data path has set to /volume1/@docker
It seems two containers Homey-SHS are running. I’d suggest stopping both of them (homey-shs and ghcr.io_athombv_homey-shs-1) and then only start the first homey-shs.
I decided to just delete everything and start again. Nothing was important enough and resetting things let me do better flows than I had first tried. So, now there’s just one container, the app is finding and using both the Homey Pro and the SHS just fine. It’s even done a better job of adding the Ikea stuff this time around.
The only issue I now have is that the My.homey.app page on my PC can’t find either of them. I guess I have to reset that somehow, too?
Hi,
you first have to add a Homey SHS as new Homey by using the mobile app, to have it registered. When it succeeds, you should be able to reach it with my.homey.app as well.
You can find this info @ Knowledge Base
You can click your account image at the top right, and then you need to click your SHS. Then you need to refresh the page (it’s a bug in the Homey Webapp where if you had selected a removed Homey Cloud or SHS that you need to refresh after selecting another Homey)
Well, that was easy lol. Always is once you know the secret, of course. Many thanks.
I think it’s some kind of bug in the web app. But if I delete a Homey Cloud and open the web page, it’s always stuck in the “Not Found” screen until I refresh it
Yeah, that definitely works for me. I’ll need to try clearing the cache for the page and see if that makes the fix permanent as I have to do it every time.
Thanks for all your help. Now if I could just get my BG sockets working I’d be golden. Google has so far recommended 4 different apps that should make it work. I wish I were enough of a programmer to do my own integration for them. Save all this grief.
Which mobile app do the BG sockets use?
Depends on which day I ask Google. It has recommended three so far and none of them work.
The main recommendation is eWelink where you’re supposed to be able to log in with the credentials from the BG app and just use it. However, my credentials don’t sign into the app and the specific sockets aren’t an option on their app anyway (I set up a new account on it). I tried just connecting one of my sockets as a generic device but all that did was disconnect it from the BG app and Alexa and failed to add it to the eWelink app. I’ll get there in the end. TBH, one of them was a nightmare to connect to the BG app, I had to buy a wi-fi extender for it and it took days to get them all talking.
I just checked, and “BG Home” is a BroadLink SDK app, so no eWeLink. Maybe @Sharkys can help you here, since they are the developer of the BroadLink app for Homey.
I haven’t tried Broadlink yet - it was the most recent recommendation from Google.
Thanks for looking for me; greatly appreciated
J
