Q0: Does this app work on my Homey? A1: Homey Pro: YES A2: Homey (Early 2016): YES A3: Homey (Early 2018): YES A4: Homey (Early 2019): YES A5: Homey Cloud (Bridge): NO (Status: checking with Athom)
A6.1: All old Homey’s are Pro now. (The white ball) Only with less cpu and memory. A6.2: HOMEY is now a cloud service you can run free or with subscription and a Bridge as a local antenna.
Q1: How to disable notifications A1: Go to the app settings and un-tick the notification settings
Q2: I got a rate_limit error A1: In this case you got too many flows which are reporting a status. This happens only on the first load of the app. After that the app only report single flow issues. Once the list with flows is made. To get rid of the rate_limit issue you have to restart your Homey or wait for a couple of Hours. This is limitation in the Homey codebase
Is it OK to report bugs / strange phenomenons here, Martijn?
This flow got disabled by Homey, after I disabled and enabled ONE random picked flow. Note: on beforehand I was getting lots of messages of flows being set to inactive or active. It should only report the flow I disabled and enabled again, I suppose)
Apps looks like it’s working correct. But the flows broke after too many tries with triggering flows.
I’m not sure if I create a delay if that will fix the too many tries. With the rate_limited issue. That’s really a Homey limitation
About the duplicate tries I can see that. On startup it started processing every single flow but while doing that the interval check already kicked in causing it to process everything again. This is fixed in the new testversion.