I can say only for thermostat, but I think the issue applies to other ZigBee things as well.
When I bind a new thing into the ZigBee network, some initial values are stored in its properties. Some of those initial values are also logged in some logs, others are not, it seems.
These are the details for a freshly bound thermostat:
A dashboard showing graphs for most of those properties looks like this:
Therefore, any diagram showing whether that thing is connected will show its connection status as unavailable when it is, in fact, connected; similarly for other properties.
This makes debugging issues with a nymea installation more difficult, when I can not rely on the diagrams showing their corresponding data.
In addition, it's not so elegant when the prompter which constructs a diagram includes properties that are not currently being logged, such as the signal strength, but this would be another issue.
I can say only for thermostat, but I think the issue applies to other ZigBee things as well. When I bind a new thing into the ZigBee network, some initial values are stored in its properties. Some of those initial values are also logged in some logs, others are not, it seems.
These are the details for a freshly bound thermostat:
A dashboard showing graphs for most of those properties looks like this:
Therefore, any diagram showing whether that thing is connected will show its connection status as unavailable when it is, in fact, connected; similarly for other properties.
This makes debugging issues with a nymea installation more difficult, when I can not rely on the diagrams showing their corresponding data.
In addition, it's not so elegant when the prompter which constructs a diagram includes properties that are not currently being logged, such as the signal strength, but this would be another issue.