[FIX] Enhance Button status reporting with ‘UNKNOWN’

[johannrichard]

How does the ALIVE check for the MyStrom buttons work?

They're undead. ☺️ Right now, the call to getDeviceStateUpdate() always resolves the promise and thus they're ALIVE. I have plans to change that to UNKNOWN at some point as we just don't know their state, but it was not highest priority anyway (since it's merely a heartbeat and status indicator in the logs).

Good observation though. ☺️😊

Originally posted by @qx54 @johannrichard in #139 (comment)

[qx54]

Didn't want to open a new issue, so I'm putting it here:

MyStrom buttons are now super slow, from the time of the press until the execution of the action it takes several seconds. This must have been introduced recently. Short press already used to be very slow compared to double press and long press, but now everthing is even way slower.

@johannrichard, do you think this could be because of something introduced in your recent code changes?

If I remember correctly the firmware of the buttons got recently updated, so there's two possible causes for this.

[johannrichard]

If I remember correctly the firmware of the buttons got recently updated, so there's two possible causes for this.

I'm still investigating. Got myself an new button which still has an older firmware. Had the same feeling lately. What I can see from my initial investigations with the newest firmware (and also considering that dingz and PIR trigger motion quickly), there are quite quickly requests made to the myStrom Cloud servers (which also must happen). Only then I think are the local requests made.

Still needs some investigations, however considering that the firmware update contains "faster network connections", it might well be that the sequence of requests was changed with the newest firmware.

I will try to figure that out between the old and new.