Global Moderators group | Smart Home

toggledbits

In the version you are using, it is still required; that's the docs leading the released code by a step (sorry). The version you are using also doesn't enforce limits well, so it allows values that could produce no result, or store more data than needed.

For example, given your retention of 60 and interval of 5, there would be r/i+1 = 13 samples in the series. But if you specify depth of 2, then only the most recent 2d-1 = 3 samples are considered... the other 10 samples don't contribute to the result value. A depth of 7 would be the best match for the given interval and retention (just mathematically, ignoring your semantic goals).

toggledbits

The previous post shows depth as null or not provided. Please specify both depth and retention, restart and wait at least one full interval, then copy-paste the attributes if a value hasn't been calculated.

toggledbits

@tunnus OK. Let's start here: copy-paste the device attributes for that VEC entity (remember to use fenced code block formatting when pasting in reply).

CatmanV2

Just popping this in here in case it's helpful to anyone else later. I've got several Tuya Wifi sockets that I'm getting rid of / replacing. Looking at which ones, if any, can be flashed to Tasmota:

SURFOU Smart Plug Wi-Fi Timer Socket with Energy Monitoring, Mini Remote Control Plug Works with Alexa, Google Home and SmartThings, Light Timers For Home Security, App Smart Life/Tuya, 13A : Amazon.co.uk: DIY & Tools

Are NOT flashable

C

CatmanV2

The migration has started. Pulling Z-wave devices and replacing them with Zigbee. Really successful so far. Much much snappier response. No range issues as each socket I'm adding acts as a router. Gonna have a play later see if I can flash the Tuya cloud plugs I bought to Tasmota....

C

toggledbits

You have to wait for the time series to fill before acceleration can be computed. depth is used in the calculation, as well as retention... that's a peculiarity of this aggregate (accel). There need to be at least 2*depth-1 samples collected before the calculation can occur.

I have updated the documentation in the online version just yesterday, so check here.

CatmanV2

That is very helpful, thanks. I'll enable some logging tomorrow and have a dig!

C

CatmanV2

Morning folks! More Zigbee fun today

Just bought me one of these to replace one of my Remotec ZRC-90s and try and speed things up

Although it's immediately visible in Zigbee2mqtt with Battery, Action and Link Quality:

And immediately pops up in HASS, HASS only exposes Battery and Link Quality:

This strikes me as a bit perverse given that HASS can (pretty obviously) react to the keypresses.

Can I use a modified (for example) Scene controller template from @therealdb to integrate direct into Reactor, or would it need to be re-written from scratch? The first may be just within my meagre talents, but I suspect not. The latter not a chance.

I can make a hack by making automations in HASS update entities in Openluup (or create virtual switches in HASS) but would like to keep my automations in one place.

Thoughts?

TIA as ever

C

CatmanV2

Thanks both! Busy day today but shall look tomorrow. Love this place

<edit> Just looks. That makes perfect sense!

C

toggledbits

@gwp1 said in Reset a delay:

This is where @toggledbits says "wow, that's over-complicated --- try this instead" because he usually does and is usually right LOL. (I tend to overthink/overcomplicate my automations....)

ROFL! Actually, your response is dead-nuts right for both the consequence of @CatmanV2 's approach and what he needs to do to get what he wants. The only critique I have is that the first image is a bit daunting to look at, with all the extra conditions. But overall, as they say: This is the way...

Global Moderators

Posts

Member List