craigf

Benoit, Thank you for fixing this so quickly. I agree with you on setting the scene so there is no brightness, that is the most logical. For now, I have the device as a light and just use the power setting. It works great. Have a great New Year, Craig

Hi Benoit, I have already tried that and even though it appears as a device (light), it still operates like it did as a scene. There is no option to change the brightness. I have tried every Alexa category in the portal and it still has the same problem. Thanks, Craig

Michel, Adding a device works properly with no problems. I disabled the V3 skill and deleted all of the devices and scenes. I then reinstalled the V2 skill and detected all of the devices. All of my ISY scenes now show up in the Alexa app under "Devices". The name of the device says it is a scene in parenthesis (eg Spa (Scene) ). I am then able to use the scene in a routine with no problems. I can turn it on or off. I reviewed the portal and my routines are correctly listed in the Alexa Category as a Scene. So, something has changed in the V3 that makes the scenes be detected in the Alexa app as a Scene (which makes sense but doesn't work). It did work in V2 since the Alexa app detected the ISY scenes as devices which were then allowed and on or off state. I then disabled the V2 skill and deleted ("Forget") all the devices and scenes. I then added the V3 skill again. (No changes to the portal). I then detected devices. As it did before, it added my ISY scenes to the Alexa app under scenes. It gave me the same issue as before. When I add the scene to a routine, it gives me no options and adds it to the routine as "Spa on at 50% brightness". I then went into the portal and changed the Alexa category to "Switch" for the Spa Scene. It then showed in the portal as a Device/Switch. I then went into the Alexa app and deleted all the devices and scenes. I then did a discover and this time it put the Spa scene into the Device category. I then tried to add it to a routine and it acts just like it did as when it was a scene. It does not give me any options and when I add it, the command is "Spa: Turn on, 50%" So, I can go back to V2 and have it work, but I know you guys are trying to get rid of that version. Please let me know what to try next. Thanks, Craig

Michel, Thank you for the reply. I agree and that is part of my confusion/problem/issue. I have no idea why it says that and also as I recall I could also turn a scene off in the last version. I have checked the portal and is shows Alexa as a "Scene" so it shouldn't be confused at that. It also shows up as a scene under the Alexa app. I have tried deleting the skill, forgetting all the devices and then re added the skill ISY V3 and re-detected the devises. Any time I try and add an ISY scene to a routine, it adds it as "Spa: Turn On, 50%" (substitute "SPA" for any scene I try to add) The items that are controlled by the scene are a Switch (on/off), an IO Linc Relay, and a Keypad button. All of these are On/Off devices. Any suggestions on what else to try or reset? It worked fine in V2. I'm not saying V3 is the problem, but during the upgrade is where things went bad. Thanks Craig

I have just upgraded from V2 to the V3 skill. I followed the instructions per the wiki. In some of my routines I used scenes. When I update my routines (since the scenes were deleted during the upgrade) there is now way for me to control the scene. For example, I add and action, select smart device and choose control a scene. I then choose the scene I want and a big "NEXT" button appears. I click next and it adds the scene to my routine as "Turn on Spa at 50%" I have tried everything and can't figure out how to get it to just turn on the scene or turn it off like it did in V2. Any ideas why the Alexa app is acting this way? Thanks, Craig

Thanks for the update everyone. The new firmware works great, no problems and everything seems to be working!

I rolled back the firmware to 2.8.16 and tried the same thing with the same results so it does not appear to be a firmware issue. I also tried both of the configuration's for 2420M and 2420M-SP. I'm not sure what the difference is, but both behaved that same. Thanks for looking into this. Craig

Lee, I double checked the jumper. I returned the MS and got a new one and I am having the same identical behavior. Craig

Lee, Here is the Log info: Thu 03/08/2012 06:20:26 PM : [14 98 59 2 ] Using engine version i2 for 'Garage Motion Sensor-Dusk/Daw' Thu 03/08/2012 06:20:26 PM : [iNST-ACK ] 02 62 14.98.59 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06 (00) Thu 03/08/2012 06:20:27 PM : [iNST-SRX ] 02 50 14.98.59 14.83.54 2B 2F 00 (00) Thu 03/08/2012 06:20:27 PM : [standard-Direct Ack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 03/08/2012 06:20:27 PM : [iNST-ERX ] 02 51 14 98 59 14 83 54 11 2F 00 00 01 00 07 01 50 10 01 41 0E 64 01 80 33 Thu 03/08/2012 06:20:27 PM : [Extended-Direct][14.98.59-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 03/08/2012 06:20:27 PM : [All ] Writing 0 bytes to devices Thu 03/08/2012 06:20:33 PM : [14 98 59 2 ] Using engine version i2 for 'Garage Motion Sensor-Dusk/Daw' Thu 03/08/2012 06:20:33 PM : [iNST-ACK ] 02 62 14.98.59 1F 2F 00 00 02 00 07 08 50 10 01 41 0E 64 03 80 00 06 (00) Thu 03/08/2012 06:20:33 PM : [iNST-SRX ] 02 50 14.98.59 14.83.54 AB 2F FD (FD) Thu 03/08/2012 06:20:33 PM : [standard-Direct Nack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 03/08/2012 06:20:34 PM : [All ] Writing 0 bytes to devices Thu 03/08/2012 06:20:42 PM : [14 98 59 2 ] Using engine version i2 for 'Garage Motion Sensor-Dusk/Daw' Thu 03/08/2012 06:20:42 PM : [iNST-ACK ] 02 62 14.98.59 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06 (00) Thu 03/08/2012 06:20:42 PM : [iNST-SRX ] 02 50 14.98.59 14.83.54 2B 2F 00 (00) Thu 03/08/2012 06:20:42 PM : [standard-Direct Ack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 03/08/2012 06:20:42 PM : [iNST-ERX ] 02 51 14 98 59 14 83 54 11 2F 00 00 01 00 07 01 50 10 01 41 0E 64 01 80 33 Thu 03/08/2012 06:20:42 PM : [Extended-Direct][14.98.59-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 03/08/2012 06:20:42 PM : [All ] Writing 0 bytes to devices Thu 03/08/2012 06:20:47 PM : [14 98 59 2 ] Using engine version i2 for 'Garage Motion Sensor-Dusk/Daw' Thu 03/08/2012 06:20:47 PM : [iNST-ACK ] 02 62 14.98.59 1F 2F 00 00 02 00 07 08 50 10 01 41 0E 64 01 80 00 06 (00) Thu 03/08/2012 06:20:47 PM : [iNST-SRX ] 02 50 14.98.59 14.83.54 AB 2F FD (FD) Thu 03/08/2012 06:20:47 PM : [standard-Direct Nack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 03/08/2012 06:20:47 PM : [All ] Writing 0 bytes to devices The timeout was originally set to 1 s. I changed it to 3 s. When I went back in the second time, it was still set to 1s. The only jumper installed is jumper 5. Also, it might be noteworthy that the Sensor status is ON, the Bat Low is OFF, and the Dusk/Dawn status is blank. Thanks, Craig

I just purchased a new 2420M motion sensor. It is Rev 2.1. I also updated the ISY to version 3.1.17 before adding the MS. I have put on jumper 5 but I am unable to change the settings from the ISY. I am putting the MS in linking mode and I am not getting any errors but when I change the time or try and change to send on signals only, it writes to the device but the changes don't stick. After it writes the changes, I push the set button, the led double flashes repeatedly. If I push the set button again it goes back to normal mode. The problem is that the settings didn't change. If I put it back in link mode and choose "Set Options", the settings are back to the original settings. Any ideas why they are not sticking? Thanks, Craig

Never said I didn't try it. Also, that is not really the topic of this thread. I am trying to get an understanding of why it works the way it does with the ISY. If we review the manual for the IO link, it states that when the relay is set to Momentary C, the sensor will determine if the relay will respond or not. So, obviously the IOLinc has some internal logic as to whether the relay will energize. This independent of any other device, it is built into the IO Linc. If the IO Linc gets an ON command, it will check the sensor to determine if the relay should respond. If it gets an OFF command, it again evaluates whether the relay should respond based upon the sensor input. It should be noted that the behavior can be programmed to respond to and open or closed sensor with respect to an ON or OFF command. Now that we have that clear, it would appear that we should get this behavior when controlled by the ISY. In other words, I would expect that when I go to "My Lighting" and choose the "Garage - Relay" and send it an ON command, the relay should only respond when the sensor is in the closed status. Accordingly, when sending an OFF command, it should only respond when the sensor is open. It does not do that. The relay always responds to an ON command regardless of the sensor state. When linked to a controller such as the ControLinc, the operation is correct as stated in the manual. When the relay is included in a scene, it also works as expected. (I said it wasn't in a scene, I didn't say that I didn't try it in a scene and it didn't work) I don't plan on using the relay in a scene or with a controller, I plan on using it in a program so I really didn't see a reason to create a scene for it. Getting to the subject of this thread, it would appear that ISY sends a different ON command than an Insteon controller. When an Insteon controller sends an ON, it works as stated. When ISY sends an ON command from "My Lighting", it does not work according to the internal logic of the IO Linc. So, ISY must be sending something other than the same command as an Insteon controller. That is the part we are trying to understand. So far it seems pretty straight forward. I am just curious why sending an ON command to the relay from ISY seems to override the internal logic of the IO Linc. Also, I believe I have the latest version of the firmware since the IO Linc is only a week old and the ISY properly displays both the sensor and relay status independently. So, back to our original question of whether the ISY sends a different command than and Insteon controller. If so, why? If it does, than it will make the programming more difficult. I will admit that I haven't written the program yet and I know I can write the logic to make it work the prescribed way, but it would be nice if I didn't have to write the logic that is already built into the IO Linc.

I have not created any scenes yet that use the sensor or relay. I am still trying to get the basic functionality of the Momentary C relay to work. If us link to a ControLinc, then the relay works with respect to the sensor. For example, if the sensor is open, then the relay only momentarily closes if you press the off button. It does not activate the relay if you hit the on button. The similar case is true if the sensor is closed. Then the relay only cycles when you hit the on button and does nothing when you hit the off button. This is the described operation of the IO Linc when set to the Momentary C relay action. Now, if the sensor is open and I use the ISY to send an ON command, the relay cycles momentarily (wrong operation). If I send an OFF command, the relay does not cycle (wrong operation). If the sensor is closed and I send an ON command, the relay cycles (correct operation), if I send a OFF command, the relay does nothing (correct operation). I get the same operation no matter what the sensor condition is. As for seeing the relay and sensor status, I can see the changes of state for both of them. This really does seem like an ISY issue. It should be easy to test and replicate on other systems.

Has there been a solution to this yet? I am having the same exact behavior with my ioLink. I have upgraded to 2.7.15 with the same results. It works as expected with a controller but not with the ISY99. Any ideas?

Rand, Thanks. I don't know why, but when I unplugged the PLM and then plugged it back in, I found a program that I had deleted had not really been deleted (and was still enabled). I redeleted it and now everything works ok. Thanks. The programs are working well now. Craig

Rand, I have rewrtiten the programs to be like you suggested. I am having an odd problem though. When I hit the on for the first time, the io link turns on. I have written an identical program that turns the io link off with a slow double tap and it works fine. I am convinced the program works properly. I have disabled all of the programs and when I hit the SL on, the io link turns on. If I unplug the ISY, then hitting the SL does not cause the IO link to turn on. So, something in the ISY is turning on the io link in response to the SL switched on, even with all of the programs disabled. I have reset teh io link just to make sure it is not linked to the SL (whcih is obvious since it doesn't turn on when the ISY is disconnected). How can I troubleshoot this and determine what is in the ISY that is causing the SL to trigger the io link? I don't have any scenes that show them linked and when I check the managed by there is no connection. Thanks, Craig