Brian H

I have seen the same thing LeeG. Looking at the Device Link Table results. They count from FF back by 1 for each entry. I have seen this with some of my I2CS devices when I was using an older version of the ISY firmware. I believe it kept peeking and poking until it hit the 00 in the link record. I have also seen this with my Beta I2CS I/OLinc. I2CS does not like peeks and pokes. Maybe possible when the 2476S was added. The device was not identified as I2CS and the I2 or I1 protocol was used to add it.

The ISY99i does not know any links you manually added. Alway do all the adding, linking and scenes through the ISY99i.

I don't believe the 2856D2 Icon dimmer ever supported being a controller to any other Insteon devices. My later 2456D3 LampLinc does. I looked at the online manuals. The 2457D2 Dual Band and 2457D2X both indicate they can be a controller also.

I would also recommend you remove the button assembly and make sure something is not rubbing or not seated properly. The details on removing it is in the Full Users Manual under how to change button colors or how to change six and eight button sets.

Lee G; Thanks for the added information on new device actions.

In the configuration tab is Catch Up Schedules at restart checked?

Thank you for the full model number. I found it in the FCC web site and it does look like a welcome addition to the Insteon Line. I found the Users Manual and will give it a better look later. Since it steals power through the load. I would guess incandescent bulbs only.

If you are talking about the 2477S {SBP2477S} that I found in the FCC web site and it is not on sale yet from Smarthome. The manual says "Neutral wire is required"!

Are you saying this new module does NOT require a neutral power connection? Every AC powered Insteon module I have seen. Requires a Neutral Power feed for its internal electronics.

One thing to think about. If you have any later revision ApplianceLincs or Icon On/Off modules. They revert to Off after a power failure even if they where On at the time the power failed. Unlike most Insteon and Icon devices that revet to the state they where in at the time the power failed.

There where some email issues addressed in the new beta 3.2.0 released yesterday. You may want to read the post on what was fixed. viewtopic.php?f=25&t=8309

Tested a few I2CS Modules from the Developers Kit and they seemed to add correctly. Some models are probably not shipping yet. 2450 2486DWH6 2475D 2421 2477D

3.1.17 is the latest released firmware for the ISY99i. viewtopic.php?f=25&t=7966 The beta 3.2.0 was just released also. Until some early issues are fixed. 3.1.17 looks good unless you have a FanLinc or one of the very new I2CS Insteon protocol devices.

All of my programs also went away except two with one X10 command only in it. I also went back to 3.1.17 and all is better now. ISY99i Pro 4GB SD Card replacing original 128K one. A10/X10 Module Network Module Weather Information Module. Internet access disabled. When I reinstalled Firmware 3.1.17. I also did not have to restore the programs from a backup. They just showed up.

3.2.0 soon to be released. Address some email issues. I am not sure if it effects yours but you may want to look at the information post on it. viewtopic.php?f=25&t=8309

I have spares. Mostly from updating to a later PLM. The older firmware ones could get me by until a new replacement could be obtained.

No you don't have to request betas anymore. There will be an announcement post with links and instructions. I have a few I2CS modules from the developers group offer and will give it a try when avilable.

I am using my ISY26's power supply for my ISY99i. The unit is not too fussy on input voltage. viewtopic.php?t=3593 Maybe more steps now but the wiki has this. http://www.universal-devices.com/mwiki/ ... ur_ISY-99i

Are you running any Firewall or Antivirus programs? If you are. What software is it?

What does PLM Info/Status show in the tools diagnostics tests?

Thanks LeeG for the findings. Like when I2 was released and implemented all or part of the protocol. Not all I2CS features are in all model I2CS devices. A different model may not even add to My Lighting.

Since each manufacturer usually uses a different RF frequency and data encoding. I would doubt anything but e Dakota 3000 series device will work with it. I know the Simplehomenet sensors tab seems to say many RF devices but the exact page for the unit specifies Dakota 3000.

I believe it is any Dakota Series 3000 Transmitters for the EZSnsRF. Included in their line of series 3000 devices.

I also was under the impression there was going to be an announcement. Here is what my Beta I2CS 2420M gives when I click on Options. FD NAK is the big clue. At least I could add it to My Lighting as you know other models you can't even add. PLM:19.70.1A Motion Sensor: 14.96.56 I2CS Firmware Clicking Set Options Tab in Administration Console. Event Viewer #3 Communications Events. Sat 03/10/2012 06:53:15 AM : [14 96 56 1 ] Using engine version i2 for 'MS1-Sensor' Sat 03/10/2012 06:53:15 AM : [iNST-ACK ] 02 62 14.96.56 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 03/10/2012 06:53:15 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A 2B 2F 00 (00) Sat 03/10/2012 06:53:15 AM : [standard-Direct Ack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:15 AM : [iNST-ERX ] 02 51 14 96 56 19 70 1A 11 2F 00 00 01 00 07 01 50 10 01 8F 0E 64 01 80 E5 Sat 03/10/2012 06:53:15 AM : [Extended-Direct][14.96.56-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 03/10/2012 06:53:15 AM : [All ] Writing 0 bytes to devices Sat 03/10/2012 06:53:32 AM : [14 96 56 1 ] Using engine version i2 for 'MS1-Sensor' Sat 03/10/2012 06:53:32 AM : [iNST-ACK ] 02 62 14.96.56 1F 2F 00 00 02 00 07 08 50 10 01 8F 0E 64 03 80 00 06 (00) Sat 03/10/2012 06:53:33 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD) Sat 03/10/2012 06:53:33 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:33 AM : [All ] Writing 0 bytes to devices Sat 03/10/2012 06:53:34 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD) Sat 03/10/2012 06:53:34 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:34 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD) Sat 03/10/2012 06:53:34 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:34 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD): Process Message: Ignored Sat 03/10/2012 06:53:34 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:35 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD) Sat 03/10/2012 06:53:35 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:36 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD) Sat 03/10/2012 06:53:36 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:36 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD): Process Message: Ignored Sat 03/10/2012 06:53:36 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

The developers Group was told. Before I2CS was in shipping products. An announcement would be made. That said. A NAK of FD looks like a I2CS reply.