[APP][Pro&Cloud] Shelly

People … :face_with_raised_eyebrow:

1 Like

I guess a ptp or the latest fw with cloud connected.

:grinning_face_with_smiling_eyes:

No, it’s an issue with the Homey SDK. The dim duration of a Shelly light has a maximum of 5 seconds but the Homey SDK does not allow me to limit it. So people can set the action card to use a dimming duration of for instance 20 seconds resulting in an error. I still need to catch that in my code and return a clear error message.

Had same issue again.

Solution:

I unpaired the Shelly from homey, then I reset the Shelly to factory, then I paired with the native Shelly app, then I paired to Homey. Only at the last action (to homey) I saw the updates of the input state again. After that I fixed the IP. So far so good, fingers crossed.

Would it be possible to have the option ‘pressed twice’, or maybe even more? Like the Fibaro?

That could mean endless possibilities.

Delay in communication means coap traffic is not working. Upon pairing I update a Shelly device with the IP address of Homey which listens to coap updates. Next time you should check in the setting (under developer settings and called CoIot) in the Shelly device is still active and contains the IP address of Homey.

Shelly devices do not support this.

Thanks for your quick response.

I don’t quite understand where to update the Shelly device with the IP adress of Homey. And I don’t see where I can find Colot.

1 Like

Thank you. That is directly on the IP of the Shelly?

Yes

1 Like

Hello all,

Sorry, my mistake.
This is indeed a code for the developer.
I forgot to add the info in the message.

@Phuturist:
Thanks for the quick response and the information why the error message is shown.

Hi, I love the shelly devices and I love the fact that there is a good maintained app but since a few months I have a real issue with it.

I have a Shelly 1 WiFi switch installed with a fixed IP. And when the switch is changed I want Homey to switch on/off another light, not connected to the fysical switch.

I have made a flow for this but there seems to be an enormous delay. Most of the time nothing happens, sometimes I see the light turn on or off almost a minute later. Homey doesn’t see on time when the fysical switch has changed.

I have tried different cards (input) but nothing helps. Last week it seemed to be working again but now the problem is back.

Is this a bug in the Homey (2019) itself? I used to have problems with Zigbee and knie this was a bug in Homey but not with WiFi.

Read the troubleshooting guide from the first post in this topic.

Hey there! I’d love to rename the inputs and temperature sensors of my shelly devices because I tend to mix them up all the time and it would make creating flows so much easier if they had real names (e.g. “Hot Water Tank” instead of “Temperature Sensor 1”). Would you please consider adding this possibility in the app? Thanks a lot!
Felix

If I coudl I would. The Homey SDK wont allow me to add such a feature.

1 Like

Now that sucks. Thank you very much.

Felix

I replaced my shelly 1 versions for multiple shelly plus 1 versions (had with the old ones, lot of troubles with my mesh network) the only problem what i have now is that i can’t control them via homey because in the i enabled the option auth pass (if i disable this option i can control the shelly’s but enabled i get a a 401 error.)

what do i need to fill in at the username ??, or do i miss something here…

Screenshot 2022-01-21 080341

Hmm, I see now that device authentication differs from the gen1 devices where you need to enter a username and password. Normally you would enter these during pairing or if you you add authentication after pairing you can update the device in Homey under it’s device settings. But I’m not sure if that is going to work for gen2/plus devices. I’ll look into this some time this weekend.

2 Likes

I have looked at this all day. Authentication of GEN2 devices uses digest authentication which differs from the basis authentication on GEN1 devices. After hours of trial and error I have been unable to get a working implementation. It will take longer to get this fixed.

1 Like

It can not always be easy:-), but I’m confident that you will find a solution.