Ik kan het nog altijd niet verklaren. Ik ga binnenkort kijken of ik de app een versie boost kan geven, door wat andere gewenste feature te implementeren. Dan zal ik ook eens verder inzoomen of ik dit kan verklaren, of hoe we dit verder kunnen debuggen.
Voor nu kan ik je nog wel de tip meegeven om eens te kijken in de instellingen van de app, daar zie je een overzicht van alle lopende timers. Dus ook als de lijst leeg is, en je loopt langs de bewegingssensor, dan zou de timer daar gelijk moeten verschijnen.
@LvanderRee hi Leon. I have only just now discovered your app. It seems quite useful but for a newcomer like me, itās not directly understandable how to use your app.
For example, my son always forgets to switch off his bedroom light after leaving the room. So Iāve installed a motion sensor which should switch off the light after no motion during e.g. 2 minutes, but when motion is detected again, it should rerun the 2-minute period.
Is there a page where you explain how such a basic flow can be created making use of Timer?
(also: is it correct that this can be done with only 1 flow?)
No, but homey can handle a lot of flows. So thats not an issue.
I prefer to split up my flows as much as possible to keep it simple.
If you are interested you can read my post about āhow to structure your flowsā
Here how you can build your flows with the timer.
When motion is detected:
Thanks, I can see the error in de Development Tools area, but didnāt get a notification.
The problem however is somewhat difficult to fix for me, since this stack is only showing HomeyApi traces, without any sign of the Timer-source code that triggered it.
Besides upgrading from SDKv2 to SDKv3 Iāve also upgraded athom-api to homey-api, and I wonder why here I see APIV2 is being used, instead of APIV3 which is also provided by HomeyApi. Iāve created a issue for it on HomeyApi
Can you reproduce it, and tell me what you think is causing this?
Yep, I was wondering the same, why I see V2
It starts crashing every time timer got started, ao I reverted - I will try to reinstall and submit also report after crash, if you will see something, within next 10min
If I can help anyhow with testing, let me know, happy to help. True is that currently thanks to that condition many flows are actually broken for me, just discovering new and new flows (out of 800) while wondering why something in my home doesnāt work Itās great that you kept also non-test version, till itās still OK to use SDK2, itās easy to switch back.