Shelly on Different Subnet than homebridge about homebridge-shelly HOT 6 CLOSED

That's not supported, since Shelly devices broadcast status updates in the subnet that they are in, and so setting a static IP address of a device in another subnet would make the on/off state in the Home app not reflect the actually state of the Shelly1 switch.
In your case I think you need to go with an MQTT setup. I've been considering adding MQTT support to this plugin but that's probably going to take a while so in the meantime you unfortunately need to find another solution.

from homebridge-shelly.

Thank you for clarification. I moved them to my main LAN where homebridge runs and they work OK.
Looking forward to MQTT support.
Keep up the good work, thanks!

from homebridge-shelly.

Same problem here.

My workaround: I switched to the plugin homebridge-http-switch. It is more generic and needs a bit more config. It allows to pull the status. This is not very elegant, but it is still working, if the Shellies are in another (sub)net.

For my Shelly PlugS I added the accessory to my config.json:

{
    "accessory": "HTTP-SWITCH",
    "name": "Switch",
    "switchType": "stateful",
    "onUrl": {
        "url": "http://shellyplug-s-XXXXXX/relay/0?turn=on",
        "method": "GET",
        "auth": {
            "username": "yourUsername",
            "password": "yourPassword"
        }
    },
    "offUrl": {
        "url": "http://shellyplug-s-XXXXXX/relay/0?turn=off",
        "method": "GET",
        "auth": {
            "username": "yourUsername",
            "password": "yourPassword"
        }
    },
    "statusUrl": {
        "url": "http://shellyplug-s-XXXXXX/relay/0",
        "method": "GET",
        "auth": {
            "username": "yourUsername",
            "password": "yourPassword"
        }
    },
  "statusPattern": "\"ison\":true",
  "pullInterval": 1000
}

You have to substitute the six 'X' in the URLs with the ID of your Shelly and change the username and password.

Shelly's API-documentation is very helpful.

from homebridge-shelly.

Hi, @thoschworks, this was helpful as I have a Shelly 1 on a different WiFi than my Synology where Homebridge runs. However, I only use the Shelly to obtain temperature readings from a Shelly Temp Addon, which is not supported by the Shelly plugin. Do you have any idea whether this route would expose the temperature measurements to HomeKit?

from homebridge-shelly.

[...] I only use the Shelly to obtain temperature readings from a Shelly Temp Addon, which is not supported by the Shelly plugin. Do you have any idea whether this route would expose the temperature measurements to HomeKit?

Perhaps homebridge-http-advanced-accessory could solve your use case.

from homebridge-shelly.

Hmm, seems interesting, yes. However, I am not sure what would be the right URL to obtain the temp readings? It can't be as "easy" as the IP of the Shelly 1, I presume?

from homebridge-shelly.