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

Dead node, neighbour list fails


Question

Posted

I have an issue with dead nodes

 

  1. I have a HCL located downstairs, and a number of Aeotec MultiSensor 6 units spread around the house. All Aeotec Multisensor 6 units are USB powered (no battery devices).
  2. In one room upstairs (approx 8m from the HCL, but through a number of walls), I have an Aeotec MultiSensor 6 and an Aeotec Switch. The Aeotec MultiSensor 6 is meant to read the temperature of the room, be linked to the Aeotec switch, which is connected to a heater. The Aeotec MultiSensor 6 is meant to control the heater. However, the Aeotec Switch regularly dies after turning the heater on, which causes the heater to continually heat the room (30 deg and rising!).
  3. I have tried:
    1. waking up the Aeotec switch node, once it dies. This is not a long-term solution. I can't code the excellent scripts to do this, as I have an HCL (only block scenes). 
    2. using a fibaro multi sensor as a range tester in the upstairs room. The results are strange. They are somewhere between direct connection to the HCL and connected via a repeater.
    3. I have tried an entire remesh. This did not solve the issue.
    4. When I remesh individual devices in the room, strange(r) things happen:
      1. The Aeotec MultiSensor 6 is a master device bundled with 'sub-devices' that provide temperature, humidity, lux, UV, motion information.
      2. On the suggestion of another forum user, I tried remeshing a nearby 'good' device - the Aeotec MultiSensor 6. 
      3. When I remesh the temperature sensor of the Aeotec MS6, I get: [12:52:50] 87: Requesting neighbor list from the node is in progress [12:52:57] 87: New neighbor list received (GOOD)
      4. However, when I remesh the humidity sensor of the Aeotec MS6, I get:  [12:52:50] 87: Requesting neighbor list from the node is in progress [12:52:57] 87: Getting new neighbor list failed  (NOT GOOD. How can a sub-device that is part of the same overall sensor not find neighbours when the other sub-devices do?)
      5. Similarly, when I remesh the Aeotec Switch (the device with the issues, apparently), I get the message 'Getting new neighbor list failed'
      6. However, the  Aeotec Switch also has two sub-devices, an ammeter (current sensor) and volt meter. When I remesh the volt meter, I get 'New neighbor list received' (GOOD), but when I remesh the ammeter, I get 'Getting new neighbor list failed' (BAD). How can a sub-device that is part of the same overall switch not find neighbours when the other sub-devices do? - same issue as above.
  4. I would be grateful for any advice or assistance in trouble shooting the dead node Aeotec Switch, and any suggestions with remeshing.

 

Many thanks in advance 

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