Is it possible to add that a condition is triggered if the connection is not established in x seconds/minutes? Then you don’t have to worry about it if everything starts working normally again.
The same applies if the device becomes unavailable. Sometimes the device just reconnects do another mashed router and between that, I get the notification that the device is unavailable but was just a false alarm.
Everything is possible but this requires some refactoring and adding of functionality which to me is out of proportion to the number of users that will use this. It’s therefor not something I wanna spend my free time on unless you get other users interested in this feature.
Same as above.
I understand.
What about at least an and card if the device is unavailable and if the connection to Shelly Cloud is established? Then I can solve it simply with a delay.
Good day,
I have a problem adding Shelly 1PM to Homey pro. If I install the shelly application in homey and want to add 1pm shells, I can’t do it. It doesn’t find it automatically, so I’ll try to add it manually. If I write the IP address, email and password for the shelly account and click on second generation and click on Test connection, it gives me the error message cannot read properties of null (reading ‘data’). Can you advise me how to proceed so that I can sell Shelly 1PM to Homey Pro.
Thank you very much.
Sincerely
Michal Rozboril
Can you delay when conditions are being tested in Homey? Or it’s this not what you mean. Although creating these condition cards is probably doable I don’t think it is what you are looking for.
If it’s not discovered and can’t be added manually that probably means that Homey and the Shelly device are not on the same wifi network. You need to look into your network configuration.
I added Shelly1PM in shelly without any problems, but I can’t even find it in Homey. It appears as unavailable. Could there be a mistake somewhere in Homey for me? because I asked other users who have Homey pro and they had no problem with adding Shelly1PM.
Did you follow the troubleshooting guide from the first post in this topic (and reboot Homey and the Shelly device)?
when I restarted Homey and Shelly, I already see the Shelly1PM device in Homey, but again the second error message. I am sending a screenshot of the screen.
And what was the result of the various steps from the troubleshooting guide?
As I read in the manual, I updated the shells to the latest firmware, restarted the shells and homey and tried to add it to Homey pro. The result was the one I sent in the post above. Did I do it right or something wrong? Have you encountered this problem?
well thank you
Oh yes, it’s pretty much always users with misconfigured networks. For instance where network isolation has been enabled or users creating separate networks for 2.4GHz and 5Ghz so one device can not reach the other. It’s not up to me to fix this though.
At home we have 2 networks as you write. So if I disable the 5ghz network, that should solve my problem if I understood you correctly.
Possibly yes, although completely disabling 5GHz is just a workaround.
Hi. Just got my Homey pro and added all my shelly devices to it. I was going to make a flow which includes longpress from shelly 1PM input, but I couldn’t find any card referring to longpress. Is there some other preferred way to use the longpress infromation from my shelly or is it not just available currently?
BR
Vesa
Read the first post of this topic.
I meant that an additional AND condition is added for checking if the connection to Shelly Cloud is established or the device is unavailable. Then it is possible to add a delay between the WHEN and AND condition.
Something like that:
Hi.
Ah yes the event trigger card. I must have been blind as I didn’t see that part.
Thank you!
I also tried turning off the 5ghz network completely, but no change. Is this problem caused by Shelly 1pm and Homey pro not being on the same wifi network? I have Homey pro connected to an ethernet cable. How do I find out which Wi-Fi network Homey pro is running on. Since I set Shelly to the network I have at home.
Homey and Shelly need to be on the same network segment/VLAN. If Homey is connected with an ethernet cable, it’s not using WiFi, so the “ethernet network segment” of your Homey needs to be the same as the “WiFi network segment” of your Shelly.
And that network should not have enabled the client isolation option in your router.
