There is nothing like keeping it simple for the novices, is there
Some open questions...
* I'm confused why then is an always-on Vera unit not an SUC by default/design?
* If not, any idea what the rational was for why it was 'stripped' out in the latest version now used?
* How is this different to the routing (nearest node) and the heal options that are in Vera today?Floris mentioned the following in one of his posts, any ideas where this SUC setting/value can be found?
I was looking in to this SUC and found that it is set to 0. Would that change any thing (i own a Vera lite)?
Finally, in regards to hkmod25 comment
To make sure that all other nodes and particularly other controllers are
aware of the presence of a SUC in the network, the Node ID of an
activated SUC is communicated within the network periodically."
2. "The nodeID set in the WAKE_UP_INTERVAL_SET command must be for a permanently listening device which reponds to the commands sent from living connect®.
Does this tie in Floris comment in that the NodeID value therefore theZwave ID of Vera itself, you know, the value you see in the neighbours info on Zwave devices? so '1'
Although living connect® supports single commands, multi commands must always be used to ensure two years battery lifetime.
If multiple thermostats are installed in the same room it is important that the controller ensures that they all have the same schedule and the same setpoint."
Finally, how do you do a 'multi command'?