New User - having problems once devices are paired

Community Playground General Discussions
1

I’m a new user from a different HA platform, and having issues. I’ve reached out to tech support over the phone, but had to leave after an hour to get back to work.

My problem is that I’ve got 3 different devices I’ve paired with my Vera Plus, but despite pairing, nothing else works.

Example 1:
Aeotec Smart Switch 6 - I can get it to pair, but then the device errors in the controller with “Device failed to configure” shortly after pairing

Example 2:
Ecolink Motion Sensor - Again, I can pair it, but then the device errors in the controller with “Timed out waiting for the node to reply…”

Same thing with a Fibaro Open Close sensor.

So, three different sensors, all failing. The only common denominator is they’re all ZWave+, but I feel like this shouldn’t be an issue.

Sending a stress test command fails, etc…

2

I’d recommend checking the officially supported devices list on Vera’s main website. If these aren’t listed, they may never work, Zwave or not. Do see if support can get them going, though.

Sent from my LGUS992 using Tapatalk

3

Are these also, by chance, all battery-powered devices?

4

Just had a similar issue and called support. He said he turned auto configure to NO and then ran the stress test. Fixed my devices that were throwing similar errors. None were battery powered if that makes a difference.

5

Not sure if it matters for the solution you were provided, but in general battery operated devices behave different way than the others due to some settings introduced to lower their power consumption and save battery.
The “power supply” devices (AC or DC) react immediately to commands sent from controller, while battery operated ones communicate with the controller based on a schedule, which can be configured through so called “wakeup” parameter. If you device wakeup time is set i.e. to 30 minutes that means that it turns on the radio every 30 minutes to check if there are no new commands from the controller, and then turns it down for the rest of the time. The other case when device is turning the radio on is when it is triggered (i.e. motion sensor detects a motion) as this information has to be passed immediately.

Due to the wakeup setting if you send configuration commands to the device during it “sleep” time, they won’t be proceeded and you may receive an error message. This means that if you want to change some device’s settings or configure it, you have to wake it up (i.e. by triggering it) to make it able to receive and process changes.