bcutter

FYI, back on-topic: still happens from time to time, but rather rarely. Every few months, which is okay for many devices. Power cycling the duoFERN devices immediately restores status update...

Not it wasn't. Your assumption is right: the log entry signals the initiated action (closing/opening). It is shown instantly once the action is started. It's just that this message (and...

> I think I'll have to disable the "opening" and "closing" states again. To bad as it basically is a nice feature - if it works as intended and does...

I will test v0.4.1 asap. What about > Add a low-key auto update by letting the devices schedule an update themselves every five minutes when duofern asks for their state...

> I can also disable that again. 50/50. While it sounds in theory it should solve a few missing states problems (and therefore I definitely want and will test this),...

Coming back to the original core of this issue: irritatingly set states since the `opening` and `closing` states have been introduces (which I basically don't want to miss anymore, they...

I didn't check it (yet), but you are probably/very likely right. The question is: how can we adjust that behavior. Cause it's quite irritating that an opened shutter is opened...

> I didn't check it (yet), but you are probably/very likely right. The question is: how can we adjust that behavior. Cause it's quite irritating that an opened shutter is...

Noticed the same behavior when restarting HA. All (cover) entities set to `open` first. > So by design HA has no memory of what the state was before the reload...

No idea if that's an actual issue (what's VBA32? never heard about them). Maybe the maintainer of the fork can explain. But using an outdated, unmaintained and malfunctioning/broken FOSS is...