Craigb

I installed 5.0.16C (previously was on 5.0.16B) Upon first login into the AC (using Launcher, and it showed correct version) I received a "Can not communicate with <device> "which is an Insteon ApplianceLink 2456S3 - v.42. This is the only unit of this model in my system - all the rest are of newer vintage. This device was seen properly for status by the ISY/PLM immediately before the upgrade. The Appliance Link still responds to the KPL button it's scene is controlled by. I cannot control device from device page of ISY or from scene page of ISY - however the scene on-off commands do change the state of the KPL button. The device and scene pages show no status for the ApplianceLink. I tried a Write Updates to Device. - it runs a progress box but doesn't write anything to the ApplianceLink I tried a Restore Device - The event viewer shows: But there is no writing of restore data. I've not seen this behavior before. I also have a 2456S3B v.39 ApplianceLink, which continues to work properly with the ISY/PLM. Each restart of AC gives the same "can not communicate with" message, and the device does not respond to AC commands for scene or device. All other powered Insteon devices (Appliance, Dimmer modules, Dimmer switches, KPL's, Fan controllers) appear to be working with AC/ISY/PLM correctly. Not sure if this is due to the Upgrade or something else. Its getting late here, I'll poke at it again tomorrow, as this device isn't scheduled in any programs tonight.

Update since moving to 5.0.16B: The communication between ISY and Schlage BE569 seems to be working better. However, the Admin Console Device UI was not showing current status (lock was LOCKED, status was UNLOCKED User 1 from when I arrived home an hour previously). I used the Query button (more than once) which caused communication with the lock, but did not update UI. I then clicked on Options, and after two tries (System Busy message box - no content, just header), the UI updated, and the Options panel opened. Event viewer snip:

I am also seeing a failure to properly keep status of Schlage BE469 in 5.0.16. When the status stops updating, a query in the UI also does not update status. You can see communication with the device in the Event Viewer, but the UI doesn't update. You also get intermittent "can not communicate" errors for the Schlage BE569 device, then the icon in the device list will change from ! to normal after a few seconds. Interestingly, the other system I have has a Schlage FE599 and a BE369, and these are not having any issue with keeping UI status updated in 5.0.16. This was not an issue in 5.0.15 and 5.0.15A versions. I just moved to 5.0.16B and will see if that helps. I second the kudos for all the progress on 5.0!

Minor UI issue I'm seeing in 5.0.16, and 5.0.16B. This may have first occurred in 5.0.15, but the UI seemed to remember manual placement in 5.0.15 IIRC. The default screen for programs has the dividing line between program sequence and action area much higher than it was in earlier 5.0.x or 4.x.x versions. Here's the default layout attached I need to manually pull the dividing line down to actually see the content of my programs or find the line to edit. Additionally, the location I move the dividing line to is not saved, so next time I use the Programs UI, I must manually adjust the line again. Like I said, not a huge deal, as it does not affect functionality. However it is an annoyance.

Somewhere in the 5.0 chain the UI changed for the linking function. Start linking, and the UI shows the bar as you described. During this time, you can still link Insteon devices by pressing the SET button on the device (or the KPL button on a KPL) When you are done linking devices, click FINISH on the UI and the devices will be added. If the bar reaches full right, the Linking function times out and ends.

Did you try to link using Link Management / Add a ControlLinc and select 07.00 2450 I0Linc ? Fill in the device address and name and then OK it. I've found that some devices do not link correctly using standard linking (Click on start linking and then press button on device) I've always had good results when doing manual linking from Link Management, especially after the "cannot determine Insteon engine" error shows up, or when Automatic discovery in manual linking does not yield the desired result.

On the Hampton Bay controller, the two white wires are internally connected. You can connect the white wire from the fan motor to the Neutral white wire that is also connected to the Fanlinc white wire. (i.e all white wires connect together)