Devices show as disconnected even though they are communicating

citywok · February 16, 2015, 5:50am

I have two devices that show as disconnected:

A door/window sensor, even though when I open/close the door it triggers and the vera knows the new state of the door, so it’s obviously talking
My Onkyo Receiver, (using the Onkyo App). It says the Onkyo Receiver is disconnected even though I can control the receiver through the app

Any thoughts?

integlikewhoa · February 17, 2015, 3:19am

[quote=“citywok, post:1, topic:186003”]I have two devices that show as disconnected:

A door/window sensor, even though when I open/close the door it triggers and the vera knows the new state of the door, so it’s obviously talking
My Onkyo Receiver, (using the Onkyo App). It says the Onkyo Receiver is disconnected even though I can control the receiver through the app

Any thoughts?[/quote]

UI7 issue.

BOFH · February 17, 2015, 4:35am

Out of 3 PIR sensors and 3 door sensors on the UI7 Vera, the back door on is the only one that seems to go into disconnected mode on a regular basis. Not sure if it is the sensor or UI7. It’s the Schlage RS100HC same as the other 2.

citywok · February 23, 2015, 4:39am

Sooooo they’re fixing it?

konradwalsh · February 23, 2015, 9:53am

A temporary fix I used for some plugins that did this is add

luup.set_failure(false)

to the startup function in the implementation file…

I cant say this is best practice but I can say it works

citywok · March 16, 2015, 5:46am

Unfortunately the issue persists after the last couple firmware updates.

Is there a solution that doesn’t involve ghetto hacking this thing, or is owning a vera just this obnoxious?

Inzax · March 16, 2015, 11:54am

I had four 4-1 sensors that worked perfectly for a week. Which for Vera seems to be epic (my experience). Then Saturday morning one showed up as disconnected. The rest of my day was spent tweaking, troubleshooting, deleting, re-adding. During the week when everything worked I made no changes to Vera (U17.) The only change has been the request to upgrade every time I log in.

At this point I have set the devices so they are NEVER polled. That seems to help for today…who knows what tomorrow will bring. I have not tried the “luup.set_failure(false)” option.

Very frustrating.

hmspain · March 16, 2015, 7:53pm

In the Advanced area, I’ve changed CommFailure from “1” to “0”.

I’ve also set the Configured parameter from “-1” to “1” at times to get the thing to understand I don’t want to re-configure.

integlikewhoa · March 17, 2015, 3:06am

[quote=“hmspain, post:8, topic:186003”]In the Advanced area, I’ve changed CommFailure from “1” to “0”.

I’ve also set the Configured parameter from “-1” to “1” at times to get the thing to understand I don’t want to re-configure.[/quote]

This will work for a short time but in a day or 3 it returns.

citywok · March 18, 2015, 3:15am

So does vera plan to fix this issue?

Inzax · March 19, 2015, 11:44pm

Reference Aeon 4 in 1 sensor.

I was getting disconnects and thought I found solution only to be disappointed when the various tweaks on the board did not work.

For what it is worth, I am at 26 hours and no disconnected device notice for the Aeon 4 in 1 sensor. I set polling to default (leave blank) and went with the default wake interval (1680 seconds).

I realize this doesn’t help everyone but wanted to get it out there since I know how frustrating the disconnected sensor notice is.