[APP][Pro&Cloud] Shelly

On your Phone :wink:

1 Like

I have the same issue as PhilippeMa. My all shelly devices and the app has not been responding since upgrade to v1.25.0.

we have to same problem but we have restart shelly app and he do it

v1.25.3 - 2020-06-04

  • Fix for Shelly HT and Shelly Button 1 crashes
  • Fix for custom device icon for devices with multiple device
1 Like

Quick question. I have bought a Shelly 2.5 to try and control my automatic blinds. Now this isn’t going to work unfortunately because all electric wires are drilled into the wall and cannot be reached (which sucks because if there is something wrong I cannot reach them either, without tearing down everything).

So now I have a spare 2.5. Can I somehow use it like the 1PM? I guess so, but just wanted to confirm.

@Phuturist, I really love the SVG images! :slight_smile: :slight_smile:

I’ll donate some beers, cheers!

1 Like

If not in roller mode its a 2PM or PM2, 2 relais and 2 buttons to switch individual stuff.

1 Like

So, 2 inputs and 2 outputs, which means you could use this one device with 2 external devices? That’s even better than anticipated.

Hi,
Is this fix for the problem reported about app not responding to the Shelly relays? (v1.25.3)
I just realized that almost all of my devises are no longer responding when using the app.
If i use Shelly’s original app outside Homey it works fine. But not within Homey.
If I remove the device, and add again then it works. But have not found a workaround for all the devices I have. It is quiet a few so I prefer not to remove and add again, so I don’t have to redo/adjust all flows.
I’ve tried to restart the app two times and rebooted Homey two times as well, but no luck.
Any ideas for a workaround?

Thanks

No, that’s unrelated. Having offline devices in Homey usually means network issue. Did you assign static IP addresses to the devices in your router? Looks like the IP address of the devices might have changed.

Feel free to submit a crash log from the app settings so I can see the actual errors.

They have all static IP addresses. I also verified that the IP addresses are correct.
In Homey they don’t show as offline, looks like they are working fine, but nothing is happening when i press ON or OFF. Not responding to any flows and I don’t get any error message.
I’ll send you a diagnostic report shortly

I see timeout message for only one device in the log, a Shelly1 with IP 92.168.4.21. A timeout suggests the device is not reachable for Homey. Either it’s out of range, the IP is incorrect or the network stack from Homey is playing a part in it (I see this more and more with users that have a lot of WiFi devices). I dont see any other errors for different devices in this log.

2020-07-09 14:06:40 [log] [ManagerDrivers] [shelly1] [1] FetchError: request to http://192.168.4.21/status failed, reason: connect ETIMEDOUT 192.168.4.21:80
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1455:11)
    at ClientRequest.emit (events.js:311:20)
    at Socket.socketErrorListener (_http_client.js:426:9)
    at Socket.emit (events.js:311:20)
    at emitErrorNT (internal/streams/destroy.js:92:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  message: 'request to http://192.168.4.21/status failed, reason: connect ETIMEDOUT 192.168.4.21:80',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT'
}```

That was probably because I just restarted the WIFI and a flow was triggered.

I just remembered that I installed an updated firmware on all Shelly devices a few days ago. Could the update cause this?

Might be worthwhile to determine if it’s linked to specific router/AP brands. My experience with the KPN Experiabox and Ziggo’s Connectbox are that, in terms of WiFi, they are pretty horrible. Combine that with the not-so-stellar WiFi performance of Homey itself, and you have a recipe for disaster :frowning:

I feel pretty confident to rule out WIFI issue. The devices are working perfectly if I use Shelly’s own app (outside Homey). And all devices are connected to the network distributed over three different Ubiquiti access points.

I’m starting to think it is related to the update of firmware on the devices I did the other day. Going to check if I can go back to the earlier firmware on the devices.

Can you configure those so that Homey will always use the same physical access point?

It’s worth investigating but my Shellies 1 are working as intended on the latest firmware. If this was the actual cause I would have expected a bigger shitstorm here by other users effected by this. So I dont think this is the case.

You could try and send me a clean log. Make sure your WiFi is stable, reboot the app and then send me a crash log.

I have both Shelly 1 and 2. Only two of three Shelly 1 works from Homey and none of the Shelly 2.
I think I will just remove them and add them again. Looks like it is time to update my flows anyway.
Is there any Windows interface available now days, so it’s easier to work with them?

You can pair devices using the developer tools: Homey Developer Tools

You can edit flows using the web based flow editor: https://flow.homey.app/

1 Like

Don’t think that’s possible with unifi systems. I’m running them too. But if a device is flipping between AP’s, that means there is something wrong with the coverage. THen you either should set it to AI or adjust the powerlevel of the ap’s your self.

@LinaN did you create a seperate 2g only network for homey? Maybe give that a try and connect your shelly’s to that network too. I run it like that (separate SSID on 2g only) and everything runs just fine (got 4 unifi ap’s).

Any help would be appreciated.
i’ve just connected a shelly 2.5 relay, which works fine, i can control both points. on & off
But if setup the same one as a rollershutter, the app reports it as unreachable.

{“wifi_sta”:{“connected”:true,“ssid”:“Domo”,“ip”:“192.168.1.32”,“rssi”:-62},“cloud”:{“enabled”:false,“connected”:false},“mqtt”:{“connected”:false},“time”:“13:53”,“unixtime”:1594821230,“serial”:1,“has_update”:false,“mac”:“98F4ABF2C7FC”,“relays”:[{“ison”:true,“has_timer”:false,“timer_started”:0,“timer_duration”:0,“timer_remaining”:0,“overpower”:false,“overtemperature”:false,“is_valid”:true},{“ison”:true,“has_timer”:false,“timer_started”:0,“timer_duration”:0,“timer_remaining”:0,“overpower”:false,“overtemperature”:false,“is_valid”:true}],“meters”:[{“power”:0.00,“is_valid”:true,“timestamp”:1594821230,“counters”:[0.000, 0.000, 0.000],“total”:0},{“power”:0.00,“is_valid”:true,“timestamp”:1594821230,“counters”:[0.000, 0.000, 0.000],“total”:0}],“inputs”:[{“input”:0,“event”:"",“event_cnt”:0},{“input”:0,“event”:"",“event_cnt”:0}],“temperature”:70.13,“overtemperature”:false,“tmp”:{“tC”:70.13,“tF”:158.24, “is_valid”:true},“update”:{“status”:“idle”,“has_update”:false,“new_version”:“20200601-122849/v1.7.0@d7961837”,“old_version”:“20200601-122849/v1.7.0@d7961837”},“ram_total”:48872,“ram_free”:36660,“ram_lwm”:21392,“fs_size”:233681,“fs_free”:150349,“voltage”:240.82,“uptime”:3098}