Flows being disabled due to running too many times

Hello,
I have quite huge setup running in my home (about 200 devices, and several advanced flows).

Unfortunately one or more devices misbehaves and start to report huge amount of changes is short period of time, which then lunches my advanced flows too often. Homey protective mechanism disables those flows and fortunately due to flow checker I got notified if this happens.

Problem is that I’m not able to find misbehaving device (or more devices - as it seems that those might be some window sensors repeatly reporting open/close).

Is there a way to get some logs from Homey to trace what happened prior my flows got disabled?

Each device has an option to show recent events for that device. You could quickly check your window sensors to see if there are a large number in a short time period.

Would confirm/disprove your suspicion.

Thanks for quick answer Andy,
unfortunately no all devices has this history tab - example Shelly TRV doesn’t have them.
secondly going over 200 devices and checking manually is not really efficient way.

But if there is no other option - I’ll do it.

There’s another check:
when a flow is started 60 times whilst not finished, it gets disabled.
Maybe that’s what’s happening in some cases.

Unfortunately not my case Peter - it’s straight forward flow just checks all windows sensors and sets few variables.

Anyway - thanks for help.

Still my question - is there any way to enable debug logging of messages processed by all devices?

Closest you can get, is installing the Audit app.
It logs very very much by itself, and you can set log levels incl debug.
When added to Betterstack, you can tail (liveview) the incoming logs.

It’s still beta / w.i.p., but on one of my Pro 19’s it works great

Thanks for help Peter - that Audit app is amazing - including betterstack integration (saves space on homey).

1 Like

Typing this just if someone is interested. Audit app helped little bit - because I was able to find out, that my problem is not a issue of one faulty device, but might be somewhere else. The issue happening randomly on several thermostats (even with from different vendors / com channel) - it happens for zwave device but also with Shelly-wifi devce.

Unfortunately detail level of debug logs cannot reveal what triggered this issue. Currently I’m trying to investigate further - possible suspects:

  • Homey / or some flow in it - but I have no possibility to get any logs from the device (and I have no flow which setup target to 23 degrees)
  • Homey heating scheduler - because it’s only app which is setting target temperatures
    - MQTT - there is possibility to set target on thermostat via MQTT - but I checked that in past and I didn’t found any message with ‘/set’ command
    [Edit] - checked MQTT logs and there is no /set message for long period of time, however those switches from 22 to 23 and back are there
  • MQTT hub - some bug in app - I’ll leave this as last option, because it’s less probable.

Attaching my recent behviour - zwave eurotronic thermostat

wifi shelly thermostat

{
    "context": {
        "runtime": {
            "column": 28,
            "file": "lib/watcher/capability.js",
            "function": "trigger",
            "line": 57,
            "method": "trigger",
            "type": "Capability"
        },
        "system": {
            "main_file": "",
            "pid": 147
        }
    },
    "detail": {
        "code": "target_temperature",
        "device": "Oby-ter-02",
        "driver": "spirit_zwave",
        "owner": "org.eurotronic",
        "type": "target",
        "value": "23°C",
        "zone": "3 Obývačka"
    },
    "dt": "2024-10-21T04:30:34.386Z",
    "level": "notice",
    "message": "Oby-ter-02 Target temperature increased from 22°C to 23°C",
    "meta": {
        "action": "update",
        "entity": "capability",
        "fields": [
            "target_temperature"
        ],
        "id": "9920dc40-83b8-411f-9bf1-da4001f69432",
        "name": "Target temperature",
        "reason": "target_temperature",
        "timestamp": 1729485034383
    }
}
{
    "context": {
        "runtime": {
            "column": 28,
            "file": "lib/watcher/capability.js",
            "function": "trigger",
            "line": 57,
            "method": "trigger",
            "type": "Capability"
        },
        "system": {
            "main_file": "",
            "pid": 147
        }
    },
    "detail": {
        "code": "target_temperature",
        "device": "Kuch-Ter-01",
        "driver": "shelly",
        "owner": "cloud.shelly",
        "type": "target",
        "value": "23°C",
        "zone": "4 Kuchyňa"
    },
    "dt": "2024-10-23T04:30:13.634Z",
    "level": "notice",
    "message": "Kuch-Ter-01 Target temperature increased from 22°C to 23°C",
    "meta": {
        "action": "update",
        "entity": "capability",
        "fields": [
            "target_temperature"
        ],
        "id": "60f84fe2-1805-4415-a39b-91adaf3816f1",
        "name": "Target temperature",
        "reason": "target_temperature",
        "timestamp": 1729657813631
    }
}