Homematic Bidcos States do not represent real values

[avanc]

Homematic device values (like state) shown with config print within the homegear console might not show the real values of the device.

Background: My HM-LGW didn't worked which I didn't recognized. It took me some time to realize it, as config print showed the expected states. After some time I saw that the corresponding device didn't react as expected.
I would expect, that homegear would not change the states if it cannot communicate to those devices.

[hfedcba]

Hi @avanc,

the problem is, there are a lot of devices, where the value needs to be cached before it can be sent to the device (i. e. all RF devices without wake on radio). So the value needs to be set regardless of the devices reachability (we don't know if it is reachable or not) and this is the expected behavior. The error condition is shown by UNREACH. For all wired devices, setValue() should return an error, when setting is not possible (in Node-BLUE variable-out returns false).

What would you propose, how this should be handled?

Cheers,

Sathya

[avanc]

Still thinking how this can be handled considering the constraints...
Are those error messages printed to the console/log also available somehow within Node-Blue? I was thinking how I can Monitor the whole Homegear chain using some kind of watchdog.

To make sure that communication is working, it seems that I have to physically connect a Homematic actor with a Homematic sensor and check within Homegear, if triggering the actor results in state changes of the sensor. Sounds not very handy :-/

[avanc]

How about setting the state to "unknown" and update I after it was confirmed?

[hfedcba]

Hi @avanc,

sorry for the late reply.

Are those error messages printed to the console/log also available somehow within Node-Blue?

Not really at the moment. But I agree, an error monitoring option in Node-BLUE would be nice. You could however do a tail on the error log file and process the string output in Node-BLUE.

How about setting the state to "unknown" and update I after it was confirmed?

That's not possible (at least right now), because i. e. a boolean or integer variable can't be set to the string "unknown". What would be possible is to add a meta information to every variable when it was updated last. This information then could be read by a RPC method. What do you think?