Global Moderators group | Smart Home

toggledbits

OK. He just posted 11.4.1 and things are looking better on docker.

toggledbits

About 20 hours ago, the author of zwave-js-ui posted build 11.4.0 of that product, and it contains an error and won't start (at all) under docker. The author is aware and working on a fix. In the meanwhile, stick with 11.3.1 or earlier.

Ref: Issue 4401

toggledbits

@Crille said in [Reactor] Variables not updating correctly in latest-25201-2aa18550:

Looking forward to the bare metal release to try this out.

Shouldn't be too long, unless the group here finds something more, but I'm pretty satisfied with how it's working now. As long as a few others are as well, I'll feel better unleashing it on everyone.

toggledbits

@Crille said in [Reactor] Variables not updating correctly in latest-25201-2aa18550:

If I replace interval with alarm(60) would that also start a new timer everytime meter updates or would I achieve the same behavior as now?

No, if you replace interval/getEntity()..reactor_uptime with alarm(60), you won't get a new timer. Next build, you will be able to call alarm(0) before alarm(60) (i.e. alarm(0), alarm(60), ...) and that will cancel any existing timer first, then start a new timer for 60 seconds. In 25278, there's no way to stop the existing timer.

toggledbits

@therealdb said in [Reactor] Variables not updating correctly in latest-25201-2aa18550:

A global variable named christmas_time, that will be updated every hour/day with dateparts()?

Yes. alarm() will do that.

@Crille said in [Reactor] Variables not updating correctly in latest-25201-2aa18550:

My best example is to check if a getEntity() is not updated in X minutes by comparing time() with value.last_modified but if the entity isn't updated the expression will not evaluate because nothing changed.

Clever! One side effect, though... getEntity() creates an entity dependency for the expression, so that when the entity changes, the expression is re-evaluated. When the expression is re-evaluated, the alarm() timer is not restarted if it is already running, the prior still-running timer is allowed to finish at its originally scheduled time. I'm guessing this may interfere with your intent — if you are using it to detect timeout, you probably want to push the clock out — but I can address that in the next build.

therealdb

@toggledbits is alarm() a new thing? What's the best example to understand its use? IE: A global variable named christmas_time, that will be updated every hour/day with dateparts()? Thanks.

toggledbits

Build 25278 now available, again docker 64-bit only, and only for the folks testing variables/expressions in this thread. Please read this for summary of behavior for global and rule-based variables in this build.

therealdb

Thanks! I managed to get the 4 buttons, a nice feature for the wife.

Unfortunately, it's not POE, but it was easy for me to pull a cable. It has a relay, but I'm not using it ATM.

In the coming weeks I'll mount the second one on the second floor. The custom firmware has both MQTT and HTTP APIs, so it's easy to synchronize them.

akbooer

Ooohhh. Nice!

toggledbits

@tunnus already fixed for next build. Thanks for reporting!

Global Moderators

Posts

Member List