Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,


as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.


As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!



Smart Home Forum by FIBARO Team

  • 0

Configuration and structure



Whenever a new device is included, several features are defined in communication with the hub:

- The master/slave structure with several sub-devices (each with a device name and number) and end-points

- The parameter structure (assuming there is a template) with default values

- The basic associations to the HC2

- The network connections of the new device

When all these are done, a "Configuration complete" is reported


My question is related to the first item on this list, the basic structure. I have experienced that the sub-device (slave) structure is not consistent. As an example, inclusion of the HeatIt Z-Trm2 thermostat may end up with either 8, 10 or 11 sub-devices, "configuration complete" being reported in every case. If a soft reconfigure is done later, some slave units may disappear, while others are added. The sub-device names may end up being duplicated (e.g. "xxx.2.1" for two separate slaves). A full reconfigure avoids this, but may again end up with a variable device structure. I have experienced similar problems with other devices than the Z-Trm2 as well.


This makes me wonder: When a device is set up at inclusion, is there no verification step in the protocol to assure that all sub-devices have been defined correctly? I suspect that jumbled structures may appear when communication between the hub and the new device is noisy or unreliable. But in such cases, error handling and verification should correct any errors and keep working until the basics are correct. 


This question therefore is for anyone who knows something about the basic protocols of the HC2, or maybe the z-wave protocol itself. Any experts out there who can clarify this? For normal users, this is obscure.


PS: I post this in the HC2 forum, as it is a generic question about functionality. I assume the question is also relevant for the HC3, or even to the z-wave protocol.  

Link to comment
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...