1 Like
The diagnostics report from the Shelly app: 7471c555-0992-4e2b-9b0c-092ea7bc0e22
Firmware version of Shelly pro 4pm: 20220308-095610/0.10.0-g4eda0ff.
The log only contains a bad gateway error. This is a network related error that has been bugging Homey Cloud for a while now. Not sure if this could cause the behaviour you are seeing though.
Although the local API is different from the cloud API perhaps it helps if you send me the output from http://yourshellyip/rpc/Shelly.GetStatus.
Below the output you requested. Maybe it helps.
{“ble”:{},“cloud”:{“connected”:true},“eth”:{“ip”:null},“input:0”:{“id”:0,“state”:null},“input:1”:{“id”:1,“state”:false},“input:2”:{“id”:2,“state”:false},“input:3”:{“id”:3,“state”:false},“mqtt”:{“connected”:false},“switch:0”:{“id”:0, “source”:“UI”, “output”:true, “apower”:0.0, “voltage”:225.3, “current”:0.018, “pf”:0.00, “aenergy”:{“total”:9681.047,“by_minute”:[0.000,0.000,0.000],“minute_ts”:1646853159},“temperature”:{“tC”:47.9, “tF”:118.3}},“switch:1”:{“id”:1, “source”:“init”, “output”:true, “apower”:3.8, “voltage”:225.3, “current”:0.027, “pf”:0.00, “aenergy”:{“total”:46568.852,“by_minute”:[0.000,0.000,0.000],“minute_ts”:1646853159},“temperature”:{“tC”:47.9, “tF”:118.3}},“switch:2”:{“id”:2, “source”:“init”, “output”:true, “apower”:81.4, “voltage”:226.1, “current”:0.443, “pf”:-0.84, “aenergy”:{“total”:31447.986,“by_minute”:[918.314,1394.876,1368.474],“minute_ts”:1646853160},“temperature”:{“tC”:47.9, “tF”:118.3}},“switch:3”:{“id”:3, “source”:“init”, “output”:true, “apower”:15.1, “voltage”:226.2, “current”:0.136, “pf”:-0.49, “aenergy”:{“total”:330214.844,“by_minute”:[172.471,262.451,258.641],“minute_ts”:1646853160},“temperature”:{“tC”:47.9, “tF”:118.3}},“sys”:{“mac”:“083AF2BF37D4”,“restart_required”:false,“time”:“20:12”,“unixtime”:1646853161,“uptime”:82554,“ram_size”:252880,“ram_free”:112580,“fs_size”:524288,“fs_free”:282624,“cfg_rev”:37,“available_updates”:{}},“ui”:{},“wifi”:{“sta_ip”:“192.168.1.147”,“status”:“got ip”,“ssid”:“TMNL-3152B1”,“rssi”:-39}}
Nope, there is nothing strange in there. My guess it’s related to the bad gateway error. You could try and install the test version which is linked some posts above just to trigger a app restart.
If the error occurs again after installing the test version please send another diagnostic report.
Sorry, but what do you mean by this event? Certain IF cards? Which ones then?
Then I can determine the impact and therefor reserve some time for updating… 
Flows that have the generic action event trigger card which triggers based on events like single push, long push, double push etc… But this only affects Shelly Pro and Plus devices.
Unfortunately, the test version didn’t help. Installing did trigger a restart and the channels were read out momentarily, but not more than a few seconds.
Diagnostics report: 7a51d30a-ce01-4817-8de9-83d8e13fb17e
Update: reinstalling the test version again has restored two out of the four channels. Diagnostics report of this state here: 73cc3ea1-7413-45eb-a083-cd350aeaee10
That’s even weirder. There is absolutely nothing in the log which is weird as well. As it should as least show something about the initialization of the app. So the log might be broken. I’ll ask around.
Do you only have a Shelly Pro 4 out also other Shelly devices connected?
@Phuturist do you have any clue why the newly added trv does not appear in Alexa as a new device? I created some virtual switches for testing purposes in homey, too. They appear but the trv not…
Nope, perhaps the heater device class is not supported.
other shelly trv from the homey pro are in Alexa… only the newly added is still missing…
I currently only have one 4pm, but would like to get several more at a later stage.
After restarting Homey cloud via the developer tools, the two channels that were read out ok stopped working again.
I have no clue, is this the same one that was not being auto-discovered by Homey? Perhaps that is related? I have read some people where having issues when their device was connected to a different access point thatn the one Homey was connected to. You can try this if it is indeed connected to a different access point.
I wish I could help. At least I know why the log is empty. The log level on Homey Cloud is set to error log only. I will make adjustments to the app that hopefully results in more logging helping me to troubleshoot. You would have to submit another diagnostic report on version 3.9.1.
1 Like
Some powering off and on and other restarts later (nothing that hasnt been tried before), the 4pm works like normal again ! Still a mystery to me why it didn’t work in the first place though.
Are you still on the test channel? I pushed version 3.9.1 to the test channel that may have fixed this issue.
v3.9.1 - 2022-03-11
- Breaking change: action events for Plus/Pro devices have been updated to be able to add double push event. Due to this change you will need to update all flows using the generic action event trigger for Plus/Pro devices.
- Fixed action events of the Shelly i4
- Fixed manual pairing where auto discovery is not available
3 Likes
@Phuturist may I ask you, if you changed the “device class” in the shelly homey app for the shelly trv and if yes, to which type? because my homematic thermostat (connected via homey) works fine in alexa
I’m using a Shelly 2.5 to open and close a sliding sunscreen. I have a flow to close it at sunset
and one to open it (triggered by other flows)
But while setting status (THEN) works, the AND rule based on status does not work; when I test the step it says false, while the screen is closed a.t.m.
So: When I close the screen and test “AND status is Omlaag” (closed) testing results in “no”
However, when I open the screen and revert the test to “AND status is Omhoog” (open) then it works; testing results in “yes”
Am I using it wrong?
Also: when I use a trigger “Input 2 aangezet” it only works when I press the physical (toggle) button longer than normal, is that intended? When I do a “normal” press the screen closes (Selly 2.5 receives the signal), but the trigger does not fire unless I hold the button a bit longer.
