3.97 RC connection issues

  • 81 Views
  • Last Post 26 March 2014
Axial-User posted this 25 March 2014

Hey Ryan.

Just upgraded to the latest pre-release and there seem to be some connection issues. I have at least 4 devices that claim "command Expired" quite often see image below for details:

http://cd.jct.ca/incontrol/deviceerror01.jpg

I also tried to "Auto Configure" the lock and received the following error each time:

http://cd.jct.ca/incontrol/autoconfig.jpg

No way to add images in this forum?

Carl.

Order By: Standard | Newest | Votes
Ryan-Scott posted this 25 March 2014

[quote=carltaylor@jct.ca]Hey Ryan.

Just upgraded to the latest pre-release and there seem to be some connection issues. I have at least 4 devices that claim "command Expired" quite often see image below for details:

http://cd.jct.ca/incontrol/deviceerror01.jpg

I also tried to "Auto Configure" the lock and received the following error each time:

http://cd.jct.ca/incontrol/autoconfig.jpg

No way to add images in this forum?

Carl.[/quote]

If you just upgraded from a prior RC version, then these "expired" messages are new. They weren't shown to you before but they were probably still happening. If your lights work fine, then you probably don't need to worry about them. In some cases though, if you see them often, it might be a clue that you have a failing device or that your network is too spread out.

In the image you posted, it's saying that InControl wasn't able to send a battery level command to the node 17. Is that your lock? Could you lock have been dropped from the network or are the batteries low/dead?

Axial-User posted this 25 March 2014

Unfortunately I have yet to receive any battery level indicators from the lock in HA Server. I will have to pull the batteries manually and check them later today.

since the new update all of the connections that used to be instant are very sluggish to turn lights on / off via the software like 20 - 40 seconds and sometimes not working at all.

Carl.

Axial-User posted this 25 March 2014

I think there is something screwy with this yale lock. I decided to remove it from the network and then reconnect it in order to get it working again. but no matter how many times I try to remove it using the keypad codes the only option I get from it is "Exit The Wireless Netword" (option7, # then 3, then #). The lights flash as if it accepted the command and then when I go back in it again only offers the "3" and "Exit The Wireless Network" option.

I have pulled the batteries & Network module and put them back in again with the same results.

Carl.

Axial-User posted this 25 March 2014

Tried to perform and "Auto-config" on my Aeon-Labs" usb controller and it fails with the below error:

"Auto-configuration Node 15 Associating device with Main controller... Fail! Unable to retrieve manufacturer info from device, Performing basic configuration"

See image here: http://support.jct.ca/incontrol/autoconfigfail.jpg

Carl.

Axial-User posted this 26 March 2014

Any more suggestions on what is going on here? is my lock defective?

Carl.

Ryan-Scott posted this 26 March 2014

Unfortunately I have yet to receive any battery level indicators from the lock in HA Server. I will have to pull the batteries manually and check them later today.

since the new update all of the connections that used to be instant are very sluggish to turn lights on / off via the software like 20 - 40 seconds and sometimes not working at all.

Carl.


3.97 introduced a fix for battery powered devices; in previous versions, any polls to them would have 'queued' up the command. In 3.97, InControl will attempt to send the command and then fail. If this is happening in your scenario, it could explain the 40 second delay. You should make sure you are not polling any battery powered devices unless you know it's a device that will still respond (like locks and some thermostats -- though you should still only poll them on an infrequent basis).

Do you have any red warning messages on your devices saying that they've got expired commands? This could be an indicator of a device gone bad or out of range - that may also cause delays in your network.

As for the lock itself...does it respond to lock/unlock commands?

Close