alexryd / homebridge-shelly Goto Github PK

Hello,
is it possible to add the support of new device Shelly EM?

Thanks

Hi there I have some shelly 2.5 in roller shutter mode. So in it works great. But at my living room i have combined two motors width an relais so i can't calibrate.

Would it possible to add featurer to work without callibrating. And work with open and close time?

I have this error in homekit

Error: cannot GET /settings (404) (device SHSW-1 942587, at 192.168.0.10)

I can use the shelly with alexa and with the cloud system of shelly but I have this error with the shelly. 192.168.0.10 is the local ip of the homebridge not of the shelly device, and I don't understand why select the IP of the homebridge.

When I remove the plugin the shelly devices still stay connected to HomeKit.
How can they be removed?

Hello there,

Current plugin works great! Would be even better if we could set specific Shelly to act as GarageDoorOpener.

Thanks

Any plans for supporting the Shelly-HT device?

Hello,

when open slider for controlling roller shutter in Home app, the relay of Shelly 2.5 starts clicking while adjust the percentage. Is there a possibility to wait for releasing the slider and then adjusting roller shutter ? Just like in shelly app.

hello
i have installed shelly plugin and my devices was recognize but I have this error message :

[17/07/2019 à 06:23:24] [Shelly] Failed to load device settings
[17/07/2019 à 06:23:24] [Shelly] Wrong username or password (device SHSW-21 5A45F9, at 192.168.1.46)

i have inserted username and password on my config.json but this message always appears.

do you have a solution? where automatic devices parameters were saved? If it's possible i prefer entered them manually.

Thank you for you answer

With 1.5.2 or 1.5.1 turning On don’t work.
Do you have a Bulb?

I think they changed something... I can turn them off. But not on.

• Is now a dimming possible?
  Here the new device output:

Type: SHBLB-1 CoAP description: {"blk":[{"I":1,"D":"RGBW"}],"sen":[{"I":111,"T":"Red","R":"0/255","L":0},{"I":121,"T":"Green","R":"0/255","L":0},{"I":131,"T":"Blue","R":"0/255","L":0},{"I":141,"T":"White","R":"0/255","L":0},{"I":151,"T":"Gain","R":"0/100","L":0},{"I":161,"T":"Temp","R":"3000/6500","L":0},{"I":171,"T":"Brightness","R":"0/100","L":0},{"I":181,"T":"VSwitch","R":"0/1","L":0}],"act":[{"I":211,"D":"RGBW","L":0,"P":[{"I":2011,"T":"Red","R":"0/255"},{"I":2021,"T":"Green","R":"0/255"},{"I":2031,"T":"Blue","R":"0/255"},{"I":2041,"T":"White","R":"0/255"},{"I":2051,"T":"Gain","R":"0/100"},{"I":2061,"T":"Temp","R":"3000/6500"},{"I":2071,"T":"Brightness","R":"0/100"},{"I":2081,"T":"VSwitch","R":"0/1"}]}]} CoAP status: {"G":[[0,111,0],[0,121,128],[0,131,255],[0,141,199],[0,151,100],[0,161,6465],[0,171,100],[0,181,0]]} HTTP Settings:: {"device":{"type":"SHBLB-1","mac":"60019479173D","hostname":"shellybulb-79173D","num_outputs":1},"wifi_ap":{"enabled":false,"ssid":"shellybulb-79173D","key":""},"wifi_sta":{"enabled":true,"ssid":"abloy","ipv4_method":"static","ip":"x","gw":"x","mask":"x","dns":"x"},"wifi_sta1":{"enabled":false,"ssid":null,"ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"mqtt":{"enable":false,"server":"192.168.33.3:1883","user":"","reconnect_timeout_max":60,"reconnect_timeout_min":2,"clean_session":true,"keep_alive":60,"will_topic":"shellies/shellybulb-79173D/online","will_message":"false","max_qos":0,"retain":false,"update_period":30},"sntp":{"server":"x"},"login":{"enabled":false,"unprotected":false,"username":"admin","password":"admin"},"pin_code":"","coiot_execute_enable":false,"name":"","fw":"20190821-094813/v1.5.2@4148d2b7","build_info":{"build_id":"20190821-094813/v1.5.2@4148d2b7","build_timestamp":"2019-08-21T09:48:13Z","build_version":"1.0"},"cloud":{"enabled":false,"connected":false},"timezone":"Europe/Berlin","lat":48.5667,"lng":13.4319,"tzautodetect":true,"time":"18:10","hwinfo":{"hw_revision":"prod-1.3","batch_id":1},"mode":"color","lights":[{"ison":false,"red":0,"green":128,"blue":255,"white":199,"gain":100,"temp":6465,"brightness":100,"effect":5,"default_state":"last","auto_on":0,"auto_off":0,"power":0,"schedule":false,"schedule_rules":[]}]} HTTP Status:: {"wifi_sta":{"connected":true,"ssid":"x","ip":"x","rssi":-70},"cloud":{"enabled":false,"connected":false},"mqtt":{"connected":false},"time":"18:10","serial":1,"has_update":false,"mac":"60019479173D","lights":[{"ison":false,"mode":"color","red":0,"green":128,"blue":255,"white":199,"gain":100,"temp":6465,"brightness":100,"effect":5}],"meters":[{"power":0,"is_valid":"true"}],"update":{"status":"idle","has_update":false,"new_version":"20190821-094813/v1.5.2@4148d2b7","old_version":"20190821-094813/v1.5.2@4148d2b7"},"ram_total":51032,"ram_free":40212,"fs_size":233681,"fs_free":171433,"uptime":69379}

Does your plugin not support Shelly 1 with Tasmota ?
I have 1 Shelly 2.5 with original FW and 3 Shelly 1 with Tasmota 6.6.0.
Only Shelly 2.5 is recognized and displayed in Homekit.

I added two H&Ts to my network, afterwards I excluded them in the config for each instance.

But in Homekit the devices are still there. Did you forget to clear the cached accessories if the config changes?

Another annoying problem I never had with plugins is that your plugin causes a homebridge crash if it is not configured in the config. This behaviour is really annoying with multiple instances.

Is there anything I can do, to remove the 20 duplicated devices from every instance.

Thanks!

Hi!
Could you please add support for shelly flood!?!?
Thanks a lot!

I want to connect shelly 2.5 to the valve, how to change the type of device in homekit? Is it possible to display in homekit as a valve?

Hi,

Today I added the homebridge-shelly module to homebridge. I have 2 shelly switches 2. After configuring 1 shelly switch in my iphone I see (Home app) Shelly2 32BB26 # 0 and Shelly2 32BB26 # 1. Is it possible to assign to these switches in homebridge friendly names such as Lamp_on_livingroom_1 Lamp_on_livingroom_2 ?
Regards
Marcin Kowalik

Hi Alex,

I am using Shelly2.5 for roller shutter. More precisely it is an external blind (raffstore).

For the control of the roller I would expect that when I tap on the tile it starts to close and when I tap again it stop.
But in my case it switchs directly from close to open.

Do you know if I can influence the behavior somewhere?

I have the latest homebridge, homebridge-shelly and firmware installed.

Thanks and regards,
Thomas

[4/25/2019, 9:31:40 PM] [Shelly] 0 devices loaded from cache
[4/25/2019, 9:31:41 PM] Homebridge is running on port 51827.

thats is all i see now i had it running before the update.. then i deleted cache because my plug and sense did not show up in home kit or in debug.

if i run "shellies listen" they all come.. like

[Device discovered] 2019-04-25T19:39:34.539Z
Type: SHSEN-1 ID: ******* Host: 192.168.0.4
Property: motion Value: false
Property: charging Value: false
Property: temperature Value: 25.434078
Property: humidity Value: 43.936286
Property: illuminance Value: 0
Property: battery Value: 100

i usually run homebridge as a user, but i have try'd as root to and an clean user node_modules folder.. no dice i'm afraid.

the app and node-red and my mqtt server all sees them all..

to reproduce.. make a clean setup..

I have 5 instances of homebridge, after installing shelly plugin and defining config.json on one instance, reboot instance and everything ok, but if i reboot the other instances the plugin itself without any entry on the config.json is creating devices, duplicating one per instance.

I run Shelly1 on different subnet as homebridge.
How can I set the static IP of Shelly1, so that plugin will find it?
Thanks!

Hello,

Last week I added the plugin to my local homebridge on the RPI3 and worked fine.
I have recently installed docker to test hass.io. Worked ok too. But I think that I didn't reboot RPi.
Today I have updated and upgraded Raspbian, so the RPi has been reseted. I started to receive addMembership EADDRINUSE error, and entered in infinite loop.
I have decided to delete local installation of Homebridge and install it on docker.
First instance worked fine with homebridge-shelly plugin. When added started with same addMembership EADDRINUSE error.
So I decided to create a second instance of Homebridge on docker, to don't shut down the first one.
The error still appear. This is part of the log:

homebridge-shelly_1 | Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
homebridge-shelly_1 |
homebridge-shelly_1 | ┌────────────┐
homebridge-shelly_1 | │ 292-25-059 │
homebridge-shelly_1 | └────────────┘
homebridge-shelly_1 |
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] [Shelly] 0 devices loaded from cache
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] Homebridge is running on port 52724.
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] [Shelly] New device discovered: SHSW-PM E677F4 at 192.168.1.114
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] [Shelly] New device discovered: SHSW-PM E5DEA3 at 192.168.1.115
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] [Shelly] New device discovered: SHSW-25 688491 at 192.168.1.116
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] [Shelly] New device discovered: SHSW-PM E67B9C at 192.168.1.113
homebridge-shelly_1 | [9/2/2019, 11:49:46 PM] Error: addMembership EADDRINUSE
homebridge-shelly_1 | at Socket.addMembership (dgram.js:581:11)
homebridge-shelly_1 | at /homebridge/node_modules/homebridge-shelly/node_modules/coap/lib/server.js:233:24
homebridge-shelly_1 | at Array.forEach ()
homebridge-shelly_1 | at Socket. (/homebridge/node_modules/homebridge-shelly/node_modules/coap/lib/server.js:232:42)
homebridge-shelly_1 | at Object.onceWrapper (events.js:286:20)
homebridge-shelly_1 | at Socket.emit (events.js:198:13)
homebridge-shelly_1 | at startListening (dgram.js:128:10)
homebridge-shelly_1 | at state.handle.lookup (dgram.js:249:7)
homebridge-shelly_1 | at process._tickCallback (internal/process/next_tick.js:63:19)
homebridge-shelly_1 | [9/2/2019, 11:49:46 PM] Got SIGTERM, shutting down Homebridge...
homebridge-shelly_1 | [9/2/2019, 11:49:46 PM] [Config] Homebridge Config UI X v4.6.1 is listening on :: port 8081
homebridge-shelly_1 | -U /homebridge -P /homebridge/node_modules -C

And this is th docker-compose.yml created:

version: '2'
services:
homebridge:
image: oznu/homebridge:raspberry-pi
restart: always
network_mode: host
volumes:
- ./config:/homebridge
environment:
- PGID=1000
- PUID=1000
- HOMEBRIDGE_CONFIG_UI=1
- HOMEBRIDGE_CONFIG_UI_PORT=8080
homebridge-shelly:
image: oznu/homebridge:raspberry-pi
restart: always
network_mode: host
volumes:
- ./config-shelly:/homebridge
environment:
- PGID=1000
- PUID=1000
- HOMEBRIDGE_CONFIG_UI=1
- HOMEBRIDGE_CONFIG_UI_PORT=8081

I have removed Hassio from docker, checked that anything still remain in Raspbian, without luck.

Maybe you can help me. The plugin worked flawlessly until the reboot.

Lot of thanks.

I currently use 3 shelly's including the 2.5 for my shutters. De shelly's 1 working fine.
the 2.5 gives an error message:
[9/2/2019, 11:28:30 AM] [Shelly] Failed to set roller shutter position
[9/2/2019, 11:28:30 AM] [Shelly] Error: cannot GET /roller/0?go=to_pos&roller_pos=0 (400) (device SHSW-25 68D0D9, at 192.168.1.24)

I us the firmware: The current Firmware version of your Shelly device is 20190822-102551/v1.5.3@1c2d4dd5 No newer firmware available.

and my config.json is:

    {
        "platform": "Shelly",
        "name": "Shelly",
        "devices": [
            {
                "id": "68D0D9",
                "username": "admin",
                "password": "password"
            },
            {
                "id": "7A3689",
                "username": "admin",
                "password": "password"
            },
            {
                "id": "7A339C",
                "username": "admin",
                "password": "password"
            }
        ]

The "id": "68D0D9" is my shelly 2.5. Also the "{ "id": "74B5A3", "exclude": true }, dont work...

Do you have a solution??

Regards,
Ad

And can Not set anything of the Shelly bulb with the New FW 1.5.1

Hi,

I know for sure that this isn't an issue related with your plugin (that I really appreciate a lot so I also donated), but I hope that you have suggestions about this.

I run homebridge inside docker on a QNAP nas, network in host mode so no bridge. Everything worked perfectly until I had to change the home internet connection from copper to optic-fiber, so I had to change router, setting up a "Technicolor AGHP - DGA 4132".

Since then, the plugin hasn't been able to connect to the shellies anymore. If I visit the shelly's ip, I see the web interface and everything works. If I execute shellies description <ip> I see the output about my shelly, but nothing shows up with shellies listen.

I'm quite sure it is a problem with UDP broadcast propagation, but I looked all the router web UI for some kind of option to tune about it, found nothing.

I also tried with wireshark, when I visit the web UI of the shellies I see traffic in response from them. When I press the buttons to turn on the light, no packet is sent on the network announcing the event.

Any hint? I'm rellay running out of ideas. Thanks

Any plans? I dont owen one but i want to buy und them.

After restart the plugin generate this error and homebridge cannot start.

Homebridge is installed on docker-compose

homebridge_1 | [8/18/2019, 1:40:20 PM] Error: addMembership EADDRINUSE
homebridge_1 | at Socket.addMembership (dgram.js:581:11)
homebridge_1 | at /usr/local/lib/node_modules/homebridge-shelly/node_modules/coap/lib/server.js:233:24
homebridge_1 | at Array.forEach ()
homebridge_1 | at Socket. (/usr/local/lib/node_modules/homebridge-shelly/node_modules/coap/lib/server.js:232:42)
homebridge_1 | at Object.onceWrapper (events.js:286:20)
homebridge_1 | at Socket.emit (events.js:198:13)
homebridge_1 | at startListening (dgram.js:128:10)
homebridge_1 | at state.handle.lookup (dgram.js:249:7)
homebridge_1 | at process._tickCallback (internal/process/next_tick.js:63:19)
homebridge_1 | [8/18/2019, 1:40:21 PM] Got SIGTERM, shutting down Homebridge...

Hello Alexander. Thanks for the work you're putting into this plugin. It's really handy.

I've been testing the plugin with my two Shelly 2s in roller shutter mode. Most of the time it works really well. I did however notice some issues with the HomeKit status getting out of sync with the actual device state, even as reported in the Shelly app.

I'm not yet sure how to reproduce this. Initially I thought it just happened when the devices are modified outside of HomeKit (physical switches or MQTT), but I also noticed that that status sometimes remains stuck even if I make changes via Siri.

Do you have any pointers on how I could debug this further? Would it be worth considering some sort of polling interval to reduce the chance that the system is out of sync?

Hi, is it possible and where to set the Shelly to report to HomeKit as Outlet?

Thanks

Hej Alex!
Is there a way to bind a permanent name to a shelly-ID?
After a wlan/power-loss all shellies are re-detected, but appear in homebridges default room.
So I need to rename them all and assign a room every time I experience a network issue.

Hi, really wanting to get a decent light strip module for HomeKit, and shelly's RGBW2 seems like a good solution, guessing home bridge-shelly doesn't support it yet. Is this a no go area or would this be possible through your plugin if I help with getting output from the device to you etc. Ta

Thanks for the great plugin.

Unfortunately, since some days my two shellies (Shelly 1) are unregistered.

Followed the log entries:
[2019-4-13 20:43:22] [Shelly] Device SHSW-1 32C852 is stale. Unregistering its accessories.
[2019-4-13 20:43:24] [Shelly] Device SHSW-1 32CD98 is stale. Unregistering its accessories.

Now the plugin does not find the shellies any more. I have rebooted my raspy and the shellies. I have updated all devices, homebridge and the plugin. I also could ping my shellies from raspy.

I don’t know what’s happening and I do not know how I can fix this.

I hope you can help me.

My config.json:
"platforms":[{
"platform": "Shelly",
"name": "Shelly",
"username": null,
"password": null,
"networkInterface": "192.168.178.24"
}]

I have the latest stable version of the plugin and when i try to operate a SH1 that works perfectly from both app and website but when operated from homebrige or Eve it works only one way (the oposite to what it was during reboot (in my example 2C02E1 was on during reboot and 55ED91 was off during one

0|homebrid | [7/29/2019, 4:46:08 PM] Loaded plugin: homebridge-shelly 0|homebridge | [7/29/2019, 4:46:08 PM] Registering platform 'homebridge-shelly.Shelly' 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Initializing Shelly platform... 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Configuring cached accessory for device SHSW-1 55ED91 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Configuring cached accessory for device SHSW-1 5556E8 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Configuring cached accessory for device SHSW-1 25A0C7 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Configuring cached accessory for device SHSW-1 25A9AB 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Configuring cached accessory for device SHSW-1 2C02E1 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Configuring cached accessory for device SHSW-1 5543F7 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] 6 devices loaded from cache 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Device SHSW-1 55ED91 came online 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Loading settings for device SHSW-1 55ED91 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Device SHSW-1 5556E8 came online 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Loading settings for device SHSW-1 5556E8 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Device SHSW-1 25A9AB came online 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Loading settings for device SHSW-1 25A9AB 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Device SHSW-1 5543F7 came online 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Loading settings for device SHSW-1 5543F7 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Device SHSW-1 25A0C7 came online 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Loading settings for device SHSW-1 25A0C7 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] State of relay #0 on device SHSW-1 2C02E1 changed to true 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Device SHSW-1 2C02E1 came online 0|homebridge | [7/29/2019, 4:46:11 PM] [Shelly] Loading settings for device SHSW-1 2C02E1 0|homebridge | [7/29/2019, 4:46:29 PM] [Shelly] Setting state of relay #0 on device SHSW-1 55ED91 to true 0|homebridge | [7/29/2019, 4:50:14 PM] [Shelly] Setting state of relay #0 on device SHSW-1 2C02E1 to false 0|homebridge | [7/29/2019, 4:50:29 PM] [Shelly] Setting state of relay #0 on device SHSW-1 2C02E1 to false 0|homebridge | [7/29/2019, 4:50:33 PM] [Shelly] Setting state of relay #0 on device SHSW-1 2C02E1 to false 0|homebridge | [7/29/2019, 4:50:35 PM] [Shelly] Setting state of relay #0 on device SHSW-1 2C02E1 to false 0|homebridge | [7/29/2019, 4:50:44 PM] [Shelly] Setting state of relay #0 on device SHSW-1 55ED91 to true 0|homebrid | [7/29/2019, 4:50:14 PM] [Shelly] Setting state of relay #0 on device SHSW-1 2C02E1 to false 0|homebrid | [7/29/2019, 4:50:29 PM] [Shelly] Setting state of relay #0 on device SHSW-1 2C02E1 to false 0|homebrid | [7/29/2019, 4:50:33 PM] [Shelly] Setting state of relay #0 on device SHSW-1 2C02E1 to false 0|homebrid | [7/29/2019, 4:50:35 PM] [Shelly] Setting state of relay #0 on device SHSW-1 2C02E1 to false 0|homebrid | [7/29/2019, 4:50:44 PM] [Shelly] Setting state of relay #0 on device SHSW-1 55ED91 to true 0|homebridge | [7/29/2019, 4:51:05 PM] [Shelly] Shelly 1 55ED91 at 192.168.88.41 identified 0|homebridge | [7/29/2019, 4:51:13 PM] [Shelly] Setting state of relay #0 on device SHSW-1 55ED91 to true 0|homebridge | [7/29/2019, 4:51:16 PM] [Shelly] Shelly 1 55ED91 at 192.168.88.41 identified 0|homebridge | [7/29/2019, 4:51:21 PM] [Shelly] Setting state of relay #0 on device SHSW-1 55ED91 to true 0|homebridge | [7/29/2019, 4:51:35 PM] [Shelly] Setting state of relay #0 on device SHSW-1 55ED91 to true 0|homebridge | [7/29/2019, 4:51:44 PM] [Shelly] Setting state of relay #0 on device SHSW-1 55ED91 to true 0|homebridge | [7/29/2019, 4:51:50 PM] [Shelly] Shelly 1 55ED91 at 192.168.88.41 identified 0|homebridge | [7/29/2019, 4:51:55 PM] [Shelly] Setting state of relay #0 on device SHSW-1 55ED91 to true
any idea what is not right?

the plugin does not connect to shelly1 by http with web authentication.
Is it normal?

Hi!
I have a problem witch the roller shutter, it started 6 hours ago.
The error is this, I have 4 roller shutter:

[2019-8-20 17:30:16] [Shelly] Failed to set roller shutter position
[2019-8-20 17:30:16] [Shelly] Error: cannot GET /roller/0?go=to_pos&roller_pos=0 (400) (device SHSW-25 BA7F4B, at 192.168.X.X)
[2019-8-20 17:30:16] [Shelly] Failed to set roller shutter position
[2019-8-20 17:30:16] [Shelly] Error: cannot GET /roller/0?go=to_pos&roller_pos=0 (400) (device SHSW-25 BA7F4B, at 192.168.X.X)
[2019-8-20 17:30:17] [Shelly] Failed to set roller shutter position
[2019-8-20 17:30:17] [Shelly] Error: cannot GET /roller/0?go=to_pos&roller_pos=0 (400) (device SHSW-25 BA7F4B, at 192.168.X.X)
[2019-8-20 17:30:18] [Shelly] Failed to set roller shutter position
[2019-8-20 17:30:18] [Shelly] Error: cannot GET /roller/0?go=to_pos&roller_pos=0 (400) (device SHSW-25 BA7F4B, at 192.168.X.X)

Thanks in advance.

First off when this works it's an awesome plugin! Problem I have as follows:

• I start home bridge and devices are detected
• I set staleTimeOut to 999 to try solve my issue
• Devices appear in home app and work fine
• I rename the devices and change their type to lights (as I'm using them for light switches which means I can use Siri to turn on and off lights)
• Everything works great!
• I go to bed and next morning devices are gone from home app
• I check on the shelly app to see if devices still connected and I can see and control them no problem
• I restart homebridge and repeat above steps

Any ideas greatly appreciated!

Hi Alex,
Thanks for this great piece of software, it works like a charm. Do you have any plans to integrate fakegato-history? It would be nice to see trends for humidity and temperature sensors and power consumption for the Shelly 1PM.
In case you don‘t know it, have a look here: https://github.com/simont77/fakegato-history
Best
Timo

I have homebridge config-uix on port 8080
all working well but after upgrade to 0.10.0 (shelly) the port is occupied and I did not see the config ui x page.
my config:

{
"platform": "Shelly",
"name": "Shelly"
},

node:25850) UnhandledPromiseRejectionWarning: Error: Bad Request

at Request.callback (/usr/local/lib/node_modules/homebridge-shelly/node_modules/superagent/lib/node/index.js:782:15)

at IncomingMessage.parser (/usr/local/lib/node_modules/homebridge-shelly/node_modules/superagent/lib/node/index.js:1014:18)

at IncomingMessage.emit (events.js:187:15)

at endReadableNT (_stream_readable.js:1098:12)

at process.internalTickCallback (internal/process/next_tick.js:72:19)

(node:25850) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)

(node:25850) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

After the last update it doesn´t works. They must be changed something. It is possible to revert to 1.5? or can be solved?
Thanks

usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:264

throw new Error("Cannot add a bridged Accessory with the same UUID as another bridged Accessory: " + existing.UUID);

Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: eadd6d5a-75a3-45a1-ad3a-e452edfc62d4

at Bridge.Accessory.addBridgedAccessory (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:264:13)

Hej Alex, installed my 1st shelly1 in the wall, and standalone it works just fine. No cloud connection.
Works with the app, works via its web-interface, pwd-protected. however, no trace of it in homebridge.
Log says nothing more than:
[2019-1-11 17:05:01] Loaded plugin: homebridge-shelly
[2019-1-11 17:05:02] Registering platform 'homebridge-shelly.Shelly'

Is this anywhere on your roadmap? ;)

[2019-10-5 8:30:16 PM] TypeError: updates is not iterable
at ShellyEM._applyUpdate (/usr/lib/node_modules/homebridge-shelly/node_modules/shellies/lib/device.js:199:25)
at ShellyEM.update (/usr/lib/node_modules/homebridge-shelly/node_modules/shellies/lib/device.js:189:10)
at Shellies._statusUpdateHandler (/usr/lib/node_modules/homebridge-shelly/node_modules/shellies/index.js:41:14)
at StatusUpdatesListener.emit (/usr/lib/node_modules/homebridge-shelly/node_modules/eventemitter3/index.js:181:35)
at handler (/usr/lib/node_modules/homebridge-shelly/node_modules/shellies/lib/status-updates-listener.js:22:37)
at OutgoingMessage.coap.request.on.res (/usr/lib/node_modules/homebridge-shelly/node_modules/shellies/lib/coap/index.js:50:11)
at OutgoingMessage.emit (events.js:203:15)
at Agent.handle [as _handle] (/usr/lib/node_modules/homebridge-shelly/node_modules/coap/lib/agent.js:274:7)
at Socket. (/usr/lib/node_modules/homebridge-shelly/node_modules/coap/lib/agent.js:84:10)
at Socket.emit (events.js:198:13)
at UDP.onMessage (dgram.js:628:8)
[2019-10-5 8:30:17 PM] Got SIGTERM, shutting down Homebridge...

Hi,
since yesterday all my Shelly 2.5 devices remain in opening or closing status even if they stop to operate.

Hello,
the plugin has been working for one year with no issues. This morning I got the message from Homebridge (running in Raspberry):

[2019-9-16 10:29:05] [Shelly] Device XXXXX is stale. Unregistering its accessories.

In fact the device was no longer connected to the network. I reseted, I reconnected it but then I have not been able to make Homebridge find it again. In fact in the log I find:

[Shelly] 0 devices loaded from cache

I tried to delete cacahedAccessories files, to reboot homebridge but nothing. Then I tried to uninstall and reinstall the plugin but again no luck.

What can I try?

Thanks,
Dan

I have two shelly and none is discovered in homebridge, this is my configuration and the pass and user is correct.  

I no error log just the message of 0 shelly found.

{
"platform": "Shelly",
"name": "Shelly",
"username": "XX",
"password": "XXXX"
}

Dear friend,

I am tinkering with Raspberry Pi + Deconz and decided the best way for smart home management is the HomeKit solution.... and I have been using some homebridge plugins as well.

I am still trying to decide on a Roller Shutter system, to buy from scratch.
Your solution seems excellent, but I can only buy the Shelly 2.5 at the moment (the newly released upgrade to shelly 2).

Are you planning to support those new devices?
Bte... are you planning to support the RGBW2 ??

Thanks in advance!

Hi,

I installed the plugin in homebridge but get errors when homebridge is loading. I am using the Shelly 1 without username and password.

This is the error I get.

Load homebridge-shelly.Shelly

/homebridge/node_modules/homebridge-shelly/platform.js:127
      if (config.username && config.password) {
                 ^
TypeError: Cannot read property 'username' of null
    at new ShellyPlatform (/homebridge/node_modules/homebridge-shelly/platform.js:127:18)
    at Server._loadDynamicPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:347:30)
    at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:88:8)
    at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:45:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)

This is my config:

{
    "bridge": {
        "name": "Homebridge",
        "username": "CC:22:3D:E3:CE:30",
        "port": 51826,
        "pin": "031-45-154"
    },
    "description": "Your description here",
    "accessories": [
        {
            "accessory": "RaspberryPiTemperature",
            "name": "RaspberryPi CPU Temperature",
            "updateInterval": 1000
        }
    ],
    "platforms": [
        {
            "platform": "eWeLink",
            "name": "eWeLink",
            "email": "myemail",
            "password": "mypassword",
            "imei": "977A80C0-EE3A-4B47-8B7C-93D2436D3BB7"
        },
        {
            "platform": "Sonoff",
            "name": "Sonoff",
            "devices": [
                {
                    "name": "Sonoff test",
                    "hostname": "192.168.1.110"
                },
                {
                    "platform": "Shelly",
                    "name": "Shelly",
                    "username": null,
                    "password": null
                }
            ]
        }
    ]
}

Can you help me fix this?

Dear alex,

first of all many thanks for contributing and sharing your homebridge plugin!

I wanted to share my issue with you - fundamentally the plugin is working well with my shelly 1, however there is one annoying issue:

Homebridge does not send any updates to the home app, the home app first shows "updating", then "no response" - in other words it seems that homebridge is some how frozen or so.
Interesting enough, I can bring it back alive (and visible in home app) by manually triggering the shelly on and/or off, either with the physical switch or using the shelly app.

Seems like homebridge is waiting for shelly or so, but no response. Any clue what that could be?

thanks a ton!

Why are no log entries created in journalctl. After controlling a device, the journalctl remains empty?

Is it possible to set "staleTimeout" to unlimited. That the devices are not deleted automatically?

When I install this plugin Homebridge always crashes, doesn't matter if I put anything in the config file or if it's just installed.