Homey Self-Hosted Server on Synology | Megathread

It is my understanding that SHS only works directly with the Homey Bridge for extra antennas, like Zigbee. Not with third party antennas. I read that other users use intermediary tools like Zigbee2MQTT and/or HA and then import the devices via the respective apps in Homey.

@Doekse Already confirmed that third party Thread Border Routers can be used with Homey SHS.

With additional tooling:

Homey Self-Hosted Server can indeed work with any Thread Border Router on the local network

Yes I did, two monitors, my home pro on the left with everything I had and homey SHS on the right…. I cleaned some stuff up along the way that was not used anymore and actually found some mistakes :slight_smile:

Correct. And for a reason also. Ease.

Not all dongles are equal, the homey bridge is propriety Athom and so is the homey software so they way they work together is optimal…

If you go for home assistant there is a larger plethora of different types of dongles you can use (and have to maintain). It’s a choice.

You could throw a dongle in a home assistant configuration, link your zwave/zigbee to that and then Mqtt that towards homey… but you would have to like doing that… installing the bridge is 2 seconds and it just works.

1 Like

You could use also:

2 Likes

I have the same problem that I cannot login into the webinterface: did you solve it?

You do not logon to the server, you just add into your homey app.

Thank you! That works. Still wondering what kind of login this is, and what it will show.

That is for local access @Siepje, which you can configure when you go to http://my.homey.app and follow this guide:
https://support.homey.app/hc/en-us/articles/22924537226268-Using-Local-Users-on-Homey-Pro

(Make sure you select the right Homey first by clicking your profile photo/initials in the richt upper corner, if you have multiple Homey’s)

I’m using Homey SHS on Synology in combination with a SONOFF Dongle Max that is connected via ethernet.

In short, I have:

  • Homey SHS docker
  • Mosquitto docker as my MQTT broker. Alternatively you can use the MQTT Broker app on Homey
  • Zigbee2MQTT docker
  • Zigbee2MQTT app on Homey

I’m trying to use it with OpenThread, not with Zigbee.

OBTR doesn’t play well with Synology

May need to rethink Homey SHS on Synology. Just realized that when my DS224+ is backing up to my DS115 via HyperBackup, Homey SHS sometimes times out and prevents me from saving flows. Anyone else experiencing similar timeouts when the NAS is busy?

I think it is maybe a coincident with the problem of backingup a running sqlite DB described here: Homey SHS - Backup strategy for running docker - #11 by Olex

1 Like

I have known this behaviour with my regular HP23 since…forever

1 Like

Thank you. I’m new to Homey and unfamiliar with its idiosyncrasies. Appreciate the feedback.

Hi, I have been planning how to deal with potential performance and reliability consequences of SHS on Synology.

  • Homey Pro as dedicated platform optimised for low latency and high-frequency I/O
  • SHS on Synology (x86) optimised for (shared) general-purpose computing, storage, and virtualization

I’ve discovered several variables that could affect performance (my old DS918+ 8GB has Celeron CPU with 4 cores/4 threads/1.5Ghz-2.3 Ghz, cache 2MB L2, so only slightly faster than HP R-Pi CM4).

Compete for memory (assuming 8GB)

Container Manager (best on SSD if you can): High-frequency, random I/O

  1. Lower priority for Downloads (eg. NZBget)
    In container settings, set CPU low, hard memory limit to 1024MB each.

  2. High priority for SHS
    Project YAML configuration: CPI to high priority (weight 2048), hard memory limit to eg. 3072MB, soft memory limit to 2048MB

    services:
      homey-shs:
        image: ghcr.io/athombv/homey-shs:latest
        container_name: homey-shs
        restart: unless-stopped
        network_mode: host
        privileged: true
        # Added CPU Priority and Deploy Memory Resources
        cpu_shares: 2048
        volumes:
          - ./:/homey/user
        deploy:
          resources:
            reservations:
              memory: 2100M
            limits:
              memory: 3000M
    

Compete for storage, disk I/O (examples)

Container Manager: You can consider moving one container to another volume than SHS

Surveillance Station (best on HDD): High-frequency, sequential writes.

  1. Multiple pools: write to a different storage pool than SHS: Set camera recording storage pool to another volume
  2. One pool: use shared folder quotas to prevent SS from filling the entire drive and leaving no room for Container Manager or download

I would love to hear of your experience with SHS on Synology. Any hick-ups?

Tips welcome.

1 Like

Which is why HA also has its own set of dongles.

Another reason to use something other than the Bridge is because it’s outdated. It’s Zigbee chip cannot handle more than about 15 devices before instability can occur, for instance.

The aforementioned issue with saving flows when my NAS was backing up. I have a DS 224+ for reference. I’m now running the SHS add-on for Home Assistant instead and it’s been problem free. Very happy with the performance. No issues with Homey or HA since installation.