Erik Baauw
Erik Baauw
Now on v2.05.72, still seeing some issues with rule triggering for time-based conditions: - `ddx` rules seem to be triggered twice, a second apart, looking at the deCONZ log and...
> - `ddx` rules seem to be triggered twice, a second apart, looking at the deCONZ log and at the `timestriggered` attribute. No big deal for me, as the actions...
@manup, sorry to bug you. Could you please have a look at the update of `/config/localtime`? I'd like to fix this asap, but I'm not sure what approach to take.
> I added an info message for the case when `e.id().isEmpty()`, i.e. when `handleRuleEvent()` is called for `/config/localtime`. It would seem that it is not always called every second for...
In v2.05.73.
Damn. My 23:00:00 alarm didn't go off this evening. Looking at the log, deCONZ skipped two seconds, during database save. Note the times between the last SQL statement and the...
Next idea: keep track when previous trigger for `RConfigLocalTime` happened, and check whether time for conditions falls between last trigger and current trigger time. Resource already keeps track of previous...
This is unrelated, but a very interesting use case. Both the `ddx` and `in` conditions are evaluated as trigger (rather than as regular condition) on the clock event. The `in`...
> On a Hue bridge all works fine > Could you reconsider this is a bug? Yes, I think the deCONZ API still strives to be backwards compatible with the...