[APP][Pro&Cloud] Shelly

I tried changing parameter 71, “Shutter mode” to “Manual time set” and back, also restart the app, but not helped :frowning: . Removing and adding all my shutter is the last thing what I want to try, I have 11 shutter which are parts of several automated flows, so it can be a huge work :frowning: . Any other idea before that, what to try?

This is now the default as dimmers are pretty much always lights.

What device did you re-pair and could you explain your issue based on a screenshot. I dont use Homey and the whole Energy functionality from Homey is a blackbox to me. It’s unclear what you are expecting to see.

I’ll have a look this evening but since I cant test myself I depend on Allterco Robotics and users to test this. Could you at least try to re-pair one of those devices to see if that fixes it. It would help in troubleshooting.

Shelly EM (1st gen). The device (Named “Elektriciteit”) is coming perfectly under Smart Meters in the Energy card/overview (when adding through the web interface, adding it through the app just placed it under the devices list indeed).
As you can see in the screenshot the “Total” value is 10.2W, this is the sum of the values of all Devices that are showing energy values. Normally, because of the smart meter, this value should be 143W (difference between Solar and EM). It was good with the old driver, not sure if it has anything to do with the new driver. Anybody else experiencing the same with Shelly EM?

I looked at the code and I cant explain why. The updating of the capability is in the same code block as triggering the flow card. The only thing I noticed is that the triggering of the flow occurs before updating the capability. That could result in the flow triggering the wrong action block but wouldnt explain why the flow does not trigger at all.

A possible workaround is that you need to break the flow in two flows and use the input is on and input is off triggercard.

I have pushed a change to the test channel of the app store. Could you check if this fixes the issue.

I don’t know what you did, but it’s working again :slight_smile: , thank you. I will watch the shutters in the next few days and let you know if I face any issue. Thank you again :slight_smile:

Hello,
Maybe someone experienced similar problems and can give me some advice.
Thanks in advance.

I am using the Shelly Plug S and connected it by Wifi to my Homey Pro.
In the Shelly my TV is plugged in.
Now i have the problem that my homematic ccu3 next to the Shelly is not working proberly.
My curtins are not shutting down. As soon as i disconned the Shelly, everything is working.

Greetings,
Martin

@Martin_Ochsenfeld They are using both a fixed ip adres?
Maybe you gave them the same ip adres?

Thanks for the fast reply.
No but i gave them now a fixed adress other than homematic.
At the moment i have no issue.

I checked to see if there are differences in the old driver and the new driver but there isnt. Both have the same pairing config and are use the same code for updating the capabilities. This is either something in the config, setting in Homey or a bug in Homey SDK.

I can imagine though that if a smart meter reports a negative value it is considered as power being returned to the grid and thus adding it up to the value of the solar panels (which seems to match the number). Question is why it is showing as a negative value. The Shelly app for Homey just reports the values reported by the device.

The values are okay, that’s not a problem. It’s reporting the same as it was before. I just thought of something, the solarpanel values are also measured through the same EM device on another clamp and I forgot to remove/re-pair that device/tile so maybe that caused a conflict. So I now removed and re-paired “both” devices/tiles. The first thing I notice is that the settings-icon for my solarpanel-EM-device is missing in the Energy screen which was there before.

I know from last time it wasn’t showing correct values in the Energy screen anyway until there was some measurement from the solarpanel EM so I’ll wait until tomorrow now and see if anything changes.

Update: no improvement. And now the EM device/clamp for the solarpanels is both in the smart devices section and in the solarpanels section :sweat_smile:. I’ll get back to Athom support…

I tried to pair a Shelly, but I got this error. The device seems to be working in the native Shelly app though, and has the latest firmware.

Any suggestions?

Having to use the manual pairing wizard usually already indicates there is something up with your network and Homey cant reach the device. You should first look into that. If you are a network expert and are using the manual pairing wizard because you know the reason for it, it could be because you are trying to pair a Gen2/3 device while you have selected the Gen1 option.

I’m using the manual pairing wizard because I’m pairing remotely. That had been working fine with the previous Shellys but apparently this one (The same Dimmer 2, first gen device) seems to be faulty?

N.B. The native app works flawlessly with this Dimmer.

I rebooted the router and that seemed to do the trick!

Thax again Jilger, I changed in two flows, Thanx again for this! What you write could explain why sometimes it works and sometimes not. Thanx again! Love it so much!

{
    "ble": {},
    "cloud": {
        "connected": true
    },
    "input:0": {
        "id": 0,
        "state": false
    },
    "mqtt": {
        "connected": false
    },
    "switch:0": {
        "id": 0,
        "source": "init",
        "output": false,
        "apower": 0,
        "voltage": 224.9,
        "current": 0,
        "aenergy": {
            "total": 0,
            "by_minute": [
                0,
                0,
                0
            ],
            "minute_ts": 1713524460
        },
        "temperature": {
            "tC": 14.2,
            "tF": 57.6
        }
    },
    "sys": {
        "mac": "E86BEAE76630",
        "restart_required": false,
        "time": "13:01",
        "unixtime": 1713524467,
        "uptime": 66,
        "ram_size": 245412,
        "ram_free": 136632,
        "fs_size": 458752,
        "fs_free": 139264,
        "cfg_rev": 28,
        "kvs_rev": 0,
        "schedule_rev": 1,
        "webhook_rev": 0,
        "available_updates": {
            "beta": {
                "version": "1.3.0-beta1"
            }
        },
        "reset_reason": 1
    },
    "temperature:100": {
        "id": 100,
        "tC": 11.9,
        "tF": 53.5
    },
    "temperature:102": {
        "id": 102,
        "tC": 12.1,
        "tF": 53.8
    },
    "wifi": {
        "sta_ip": "172.17.202.240",
        "status": "got ip",
        "ssid": "Wiedemann-2-4",
        "rssi": -77
    },
    "ws": {
        "connected": true
    }
}

For some reason the external temperatures seems reports null values according to the log you send me. This isnt visible in this specific status report though. Did you change any of the hardware after having paried the device to Homey, perhaps that messes things up. A reboot of the app should fix that though.

I’ll add an extra check in the app to ignore null values but there is not much more I can do.

Thanks for the clarification regarding the Plus Addon device vs the z-wave peoducts.

Do you have any insights regarding a possible future Addon module for the z-wave devices? Given that the connector for an addon module is present on the devices, and documented in Shelly’s knowledge base, one could hope that a similar addon device will become available :crossed_fingers:t3:

Nope, no insights on this whatsoever