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!

 

Regards,

Smart Home Forum by FIBARO Team


  • 0

FGS223 association group 2 sending messages to wrong endpoint


Christian Schnidrig

Question

I’ve got an Aeotec ZW075 Switch which I would like to be switched when I press S1 on a Fibaro FGS223 Switch.

 

If I add the zw075 node to the 4th association group of the fgs223 everything is working as expected. When I press S2 on the fibaro, the zw075 is switched accordingly.

 

However when I add the zw075 node to association group 2 of the FGS223 then the zw075  switch does not change state when I press the corresponding switch S1.

I tried several zw075s and several fgs223s. All show the same behaviour. S2 is working fine, S1 is not.

 

Hoping to shed a bid more light on this, I did the following. (I'm using openhab2, the logs are from there)

- Lifeline -> removed controller
- group2 & group4 set to controller: “node_1_0”

This way I should see on the controller, what the fgs223 is sending to devices added to the association groups 2 & 4. Here are the results:

 

When pressing S1:

 

    2017-08-17 20:43:34.785 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Application Command Request (ALIVE:DONE)
    2017-08-17 20:43:34.785 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Starting initialisation from DONE
    2017-08-17 20:43:34.787 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Incoming command class MULTI_INSTANCE
    2017-08-17 20:43:34.788 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 18: Received MULTI_INSTANCE command V2
    2017-08-17 20:43:34.789 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 18: Requested Command Class = BASIC (0x20)
    2017-08-17 20:43:34.790 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 18: Endpoint = 1, calling handleApplicationCommandRequest.
    2017-08-17 20:43:34.790 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Received Basic Request
    2017-08-17 20:43:34.791 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Basic Set sent to the controller will be processed as Basic Report
    2017-08-17 20:43:34.792 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Basic report, value = 0x00
    2017-08-17 20:43:34.794 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
    2017-08-17 20:43:34.795 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got a value event from Z-Wave network, endpoint = 1, command class = BASIC, value = 0
    2017-08-17 20:43:34.796 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Updating channel state zwave:device:0001:node18:switch_binary1 to OFF [OnOffType]
    2017-08-17 20:43:34.815 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Application Command Request (ALIVE:DONE)
    2017-08-17 20:43:34.816 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Starting initialisation from DONE
    2017-08-17 20:43:34.818 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Incoming command class MULTI_INSTANCE
    2017-08-17 20:43:34.818 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 18: Received MULTI_INSTANCE command V2
    2017-08-17 20:43:34.819 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 18: Requested Command Class = BASIC (0x20)
    2017-08-17 20:43:34.820 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 18: Endpoint = 1, calling handleApplicationCommandRequest.
    2017-08-17 20:43:34.821 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Received Basic Request
    2017-08-17 20:43:34.822 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Basic Set sent to the controller will be processed as Basic Report
    2017-08-17 20:43:34.823 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Basic report, value = 0x00
    2017-08-17 20:43:34.825 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
    2017-08-17 20:43:34.826 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got a value event from Z-Wave network, endpoint = 1, command class = BASIC, value = 0
    2017-08-17 20:43:34.827 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Updating channel state zwave:device:0001:node18:switch_binary1 to OFF [OnOffType]

 

When pressing S2:
 

 

    2017-08-17 20:43:38.988 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Application Command Request (ALIVE:DONE)
    2017-08-17 20:43:38.989 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Starting initialisation from DONE
    2017-08-17 20:43:38.991 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Incoming command class BASIC
    2017-08-17 20:43:38.992 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Received Basic Request
    2017-08-17 20:43:38.993 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Basic Set sent to the controller will be processed as Basic Report
    2017-08-17 20:43:38.994 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Basic report, value = 0xFF
    2017-08-17 20:43:38.997 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
    2017-08-17 20:43:38.998 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
    2017-08-17 20:43:39.000 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Updating channel state zwave:device:0001:node18:switch_binary to ON [OnOffType]
    2017-08-17 20:43:39.024 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Application Command Request (ALIVE:DONE)
    2017-08-17 20:43:39.025 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Starting initialisation from DONE
    2017-08-17 20:43:39.027 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Incoming command class BASIC
    2017-08-17 20:43:39.028 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Received Basic Request
    2017-08-17 20:43:39.030 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Basic Set sent to the controller will be processed as Basic Report
    2017-08-17 20:43:39.031 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Basic report, value = 0xFF
    2017-08-17 20:43:39.033 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
    2017-08-17 20:43:39.034 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
    2017-08-17 20:43:39.036 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Updating channel state zwave:device:0001:node18:switch_binary to ON [OnOffType]
 

 

One can see, that S1 is generating messages for endpoint 1 instead of 0.
The question now would be why and can this be fixed?

 

 

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.

Guest
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...