How did you add the Shelly Plus Plug S? Devices connected to a access point should not even show in the device list for pairing.
Did you manually add it using it’s IP and port?
How did you add the Shelly Plus Plug S? Devices connected to a access point should not even show in the device list for pairing.
Did you manually add it using it’s IP and port?
Hello Phuturist,
after you last implemented the angle setting for the wave shutters via the ShellyApp, I have the problem from time to time (sometimes daily) that the slat angle on one or more wave shutters cannot be controlled via the HomeyApp (iOS and WebApp). In this case, Homey displays the error ‘Missing Capability Listener: windowcoverings_tilt_set’. Raising and lowering the blinds still works at that moment. It is usually sufficient to restart the Shelly app manually and the angle setting will then work again.
Do you have any idea why the error is occurring or do you have time to look into the matter?
Thank you very much!
@Phuturist
Maybe you already no, there is a bug in the dashboard widget or i do something wrong, then please tell me.
My widget is empty like this…
The plug S was allready paired beore and ip-address in homey settings changed to ip of the extender (mini) on its own. Adding the port to the address in the settings does not work. Settings seem to save successfull, but after a few minutes the added port is gone again.
Hmmm, that’s a corner case which I wont put any effort into preventing. You should remove the Shelly Plug S (or connect it directly to your LAN). Device that are connected to an extender arent supported.
Could you send me a diagnostic report (if that even contains logging of widgets). Apparently something is wrong but I doubt it if I will be able to troubleshoot.
The empty select list is caused by some weird reference in the Homey SDK documentation which made me implement the dropdown incorrectly. I’ll fix that with the next release. The first option is check for stable release, the second option is check for beta release and the third is to check for both.
What version of the Shelly app for Homey are you using?
3.33.0
Do you see a pattern for instance after restarting Homey or the Shelly app. Or after changing some of the Zwave parameter settings?
The current code works like this. On app init it checks the device parameters and if configured as slats it will add this capability. It will also add this capability when the Zwave settings are changed and the device is configured as slats. It will only remove this capability when the settings are changed and the device is not configured as slats.
Assuming you arent changing the device config every time this happens fishy with this logic, Homey or the device is going on.
I just sent you the diagnostic report:
8ff09012-83b7-4d3f-ac05-66a6643fe946
Thank you for your efforts.
This is a very unprecise issue/stability report from me. I understand that it can’t really be taken further by the developer(s?).
I’m using Homey Cloud an of course the Shelly app since long time. It has been very stable for quite some time now.
I have a sense that I see synch problems of device status (mainly on/off) between the Homey Cloud and the Shelly Cloud since some days, possibly since 3.33.0.
Sorry I can not nail it more than this.
Anyone else also having such a sense? Are there known issues?
Hi.
I installed firmware 1.0.20 on my Shelly BLU DoorWindow yesterday, and since then, it no longer works in Homey. I deleted one from Homey and tried to add it again, but Homey no longer recognizes it at all. In the Shelly app, everything works fine, but not in Homey anymore. Is it possible to downgrade the firmware?”
It seems this firmware version changed something that broke the integration.
It’s fixed with version 3.33.1 of the app which is pending approval in the test channel.
Thank you very much for the quick help. They are working again, except for the one I deleted, which I still can’t connect to Homey.
Should be fixed with 3.33.2 as well.
I have this problem myself from time to time. I won’t say that the problem here is in the Shelly app for Homey, but rather I would say that these problems are from the Shelly cloud or even in the Homey’s infrastructure.
Before these problems occur, the WebSocket connection between Homey and Shelly Cloud is interrupted - quite often recently and several times in a row. After this incident, I noticed (not always) that the synchronization between Shelly Cloud and Homey does not work as it should for a while, even if the status in the Shelly app is as it should be.
A few days ago, Homey showed me for a few hours that I had movement in the house when there was none in those rooms. It did not help even if I restarted the Shelly app in Homey to get the latest status. After a while, everything returned to normal and since then I haven’t noticed any deviations.
You havent answered my question about any pattern on when this occurs.
Ohh sorry, always. If I want to install the widget.
It always remains black without any displays.
Please answer my question about the pattern when this occurs.
Replied to the wrong post, wanted to ask about a pattern for all issue with the Wave Shutter.