xjsimon Posted November 9, 2015 Posted November 9, 2015 Hello. I'm fairly new to Home Automation and I've already made the switch from the Hub to the ISY994i. I've been adding all my devices back (deleting all prior links and scenes). I have created scenes for my home theater which uses a micro module to open and close the curtains on the stage. These scenes require the curtains to be either in an open or closed position. On the hub, everything worked perfectly. On the ISY, I'm having trouble getting the module to behave. I had no problem adding the device and then adding the device to various scenes. The module itself is completely functionally. It accepts the open and close (on/off) commands with no issues when those are sent outside a scene. By default each scene has the curtain in an closed position (or ON). Inside the scene, when I switch it to an open position (or OFF), it appears to try to write that change to the controller and/or device, but for some reason it just doesn't take. Being new the system, I don't know every troubleshooting technique, but I did try removing the device from the scene, restoring the device, and most recently I factory reset the device and added it back. None of these seems to have helped. I'm running the 5.02 firmware and the micro module is new. There are many dual band devices in close proximity to the module. Here is the level 3 log from the change in the scene (switching it to a closed position). Mon 11/09/2015 09:09:28 AM : [iNST-TX-I1 ] 02 62 2C 96 A0 0F 13 00 Mon 11/09/2015 09:09:28 AM : [iNST-ACK ] 02 62 2C.96.A0 0F 13 00 06 LTOFFRR(00) Mon 11/09/2015 09:09:28 AM : [All ] Writing 0 bytes to devices Mon 11/09/2015 09:09:29 AM : [iNST-SRX ] 02 50 2C.96.A0 2F.BB.92 2B 13 00 LTOFFRR(00) Mon 11/09/2015 09:09:29 AM : [std-Direct Ack] 2C.96.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 11/09/2015 09:09:29 AM : [iNST-DUP ] Previous message ignored. Any other ideas on troubleshooting?
LeeG Posted November 9, 2015 Posted November 9, 2015 This looks like a glitch in 5.0.2. The command being issued is a Direct command, not a Scene command. Here are a scene On and Scene Off for scene ID 0x33. Mon 11/09/2015 12:15:08 PM : [iNST-TX-I1 ] 02 62 00 00 33 CF 11 00 Mon 11/09/2015 12:15:08 PM : [iNST-ACK ] 02 62 00.00.33 CF 11 00 06 LTONRR (00) Mon 11/09/2015 12:15:08 PM : [D2D EVENT ] Event [1C FD D5 2] [sT] [255] uom=0 prec=-1 Mon 11/09/2015 12:15:08 PM : [ 1C FD D5 2] ST 255 Mon 11/09/2015 12:15:16 PM : [iNST-TX-I1 ] 02 62 00 00 33 CF 13 00 Mon 11/09/2015 12:15:16 PM : [iNST-ACK ] 02 62 00.00.33 CF 13 00 06 LTOFFRR(00) Mon 11/09/2015 12:15:16 PM : [D2D EVENT ] Event [1C FD D5 2] [sT] [0] uom=0 prec=-1 Mon 11/09/2015 12:15:16 PM : [ 1C FD D5 2] ST 0 The issued command has the address of the device (making it a Direct command) rather than a Scene command Mon 11/09/2015 09:09:28 AM : [iNST-TX-I1 ] 02 62 2C 96 A0 0F 13 00 Mon 11/09/2015 09:09:29 AM : [iNST-SRX ] 02 50 2C.96.A0 2F.BB.92 2B 13 00 LTOFFRR(00) Mon 11/09/2015 09:09:29 AM : [std-Direct Ack] 2C.96.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 11/09/2015 09:09:29 AM : [iNST-DUP ] Previous message ignored. Unless there is a strong need to use 5.0.2, 4.3.26 Official release is a better choice. 5.0.2 is an early beta.
xjsimon Posted November 9, 2015 Author Posted November 9, 2015 This looks like a glitch in 5.0.2. The command being issued is a Direct command, not a Scene command. Here are a scene On and Scene Off for scene ID 0x33. Mon 11/09/2015 12:15:08 PM : [iNST-TX-I1 ] 02 62 00 00 33 CF 11 00 Mon 11/09/2015 12:15:08 PM : [iNST-ACK ] 02 62 00.00.33 CF 11 00 06 LTONRR (00) Mon 11/09/2015 12:15:08 PM : [D2D EVENT ] Event [1C FD D5 2] [sT] [255] uom=0 prec=-1 Mon 11/09/2015 12:15:08 PM : [ 1C FD D5 2] ST 255 Mon 11/09/2015 12:15:16 PM : [iNST-TX-I1 ] 02 62 00 00 33 CF 13 00 Mon 11/09/2015 12:15:16 PM : [iNST-ACK ] 02 62 00.00.33 CF 13 00 06 LTOFFRR(00) Mon 11/09/2015 12:15:16 PM : [D2D EVENT ] Event [1C FD D5 2] [sT] [0] uom=0 prec=-1 Mon 11/09/2015 12:15:16 PM : [ 1C FD D5 2] ST 0 The issued command has the address of the device (making it a Direct command) rather than a Scene command Mon 11/09/2015 09:09:28 AM : [iNST-TX-I1 ] 02 62 2C 96 A0 0F 13 00 Mon 11/09/2015 09:09:29 AM : [iNST-SRX ] 02 50 2C.96.A0 2F.BB.92 2B 13 00 LTOFFRR(00) Mon 11/09/2015 09:09:29 AM : [std-Direct Ack] 2C.96.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 11/09/2015 09:09:29 AM : [iNST-DUP ] Previous message ignored. Unless there is a strong need to use 5.0.2, 4.3.26 Official release is a better choice. 5.0.2 is an early beta. Wow, thank you so much for checking. Any known issues in reverting back to the official release?
LeeG Posted November 9, 2015 Posted November 9, 2015 Sorry, I have not moved to 5.0.2 so no experience moving back. Hopefully someone with 5.0.2 experience can jump in.
Teken Posted November 9, 2015 Posted November 9, 2015 Just some context for you the 4.3.X firmware platform is field tested and over all proven to operate very well with little bugs / issues. The newly release 5.XX platform is UDI's first pass in introducing more advanced features and capabilites to the 994 Series Controller. As it is in early Beta release I would second LeeG's suggestion in down grading to the 4.3 X level.
xjsimon Posted November 9, 2015 Author Posted November 9, 2015 Thanks guys for the guidance. Thanks Teken for helping me on different issues on two boards! So I downgraded back to the 4.3.26 firmware and UI and had absolutely no issues in doing so. However, my issue persists. Getting the same exact behavior and the log is the same as above. Appears that the scene modification is still sending a direct command. Ugh.
LeeG Posted November 9, 2015 Posted November 9, 2015 What are you doing to issue Scene command. The Scene On/Off examples I posted came from 4.3.26.
Teken Posted November 9, 2015 Posted November 9, 2015 Thanks guys for the guidance. Thanks Teken for helping me on different issues on two boards! So I downgraded back to the 4.3.26 firmware and UI and had absolutely no issues in doing so. However, my issue persists. Getting the same exact behavior and the log is the same as above. Appears that the scene modification is still sending a direct command. Ugh. When you down graded please ensure the Java Cache is cleared and all box's are checked. Once that is done you need to ensure that the correct Admin Console Java application is being used. Failure to do these two basic things will lead to odd things to happen and to be seen. Lastly, delete the device and add it back and report back success / failure. I don' recall if you hard reset this lone device but that is something I would do first since it came from a HUB II install. Sometimes deleting a device and adding it back does not resolve the issue hence why a hard reset is done then the device is added back.
xjsimon Posted November 9, 2015 Author Posted November 9, 2015 What are you doing to issue Scene command. The Scene On/Off examples I posted came from 4.3.26. So I removed the device from the scene entirely just to start fresh. After dragging the device back to the scene, I click on that scene and simply adjust the slider to the closed (off) position for that device (that's the specific point that I logged). Is that the correct way to do it?
LeeG Posted November 9, 2015 Posted November 9, 2015 Confirm Help | About shows 4.3.26 for both Firmware and UI. Is there a pending update Icon for the micro module? How are you invoking the Scene?
Teken Posted November 9, 2015 Posted November 9, 2015 So I removed the device from the scene entirely just to start fresh. After dragging the device back to the scene, I click on that scene and simply adjust the slider to the closed (off) position for that device (that's the specific point that I logged). Is that the correct way to do it? Just informational feedback: The ISY should not offer a slider since the Open/Close module can only (literally) open-close. There is no method (natively) to make the device open/close a curtain part way with out the aid of another device / program. Ideally, you should create a scene add the device to the scene, and then press the Open-Close. Some Insteond devices in the past did not like being controlled by the direct link in the device tree and had to be operated with in a scene folder etc.
xjsimon Posted November 9, 2015 Author Posted November 9, 2015 Confirm Help | About shows 4.3.26 for both Firmware and UI. Is there a pending update Icon for the micro module? How are you invoking the Scene? Correct. Both the firmware and UI show 4.3.26. No pending updates/writes for the micro module. I plan to invoke the scene through the web interface and will also program a keypad, but I haven't done that yet, as I'm trying to get the scene built first.
xjsimon Posted November 9, 2015 Author Posted November 9, 2015 Just informational feedback: The ISY should not offer a slider since the Open/Close module can only (literally) open-close. There is no method (natively) to make the device open/close a curtain part way with out the aid of another device / program. Ideally, you should create a scene add the device to the scene, and then press the Open-Close. Some Insteond devices in the past did not like being controlled by the direct link in the device tree and had to be operated with in a scene folder etc. Right. I don't know why it shows a slider, but the software only allows me to set it at the on or off (open/close) positions. It displays an error when you try to put the slider anywhere in between. It seems the device is fully functional from the device tree. I can open and close it directly from there without any problem. I did experience the control via the direct link vs scene on my garage IO devices. I have no option to open or close the relay on those unless I add them to a scene. I can live with that, but I did find that odd.
xjsimon Posted November 9, 2015 Author Posted November 9, 2015 FYI - I did delete the link from the controller and factory reset the device, then re-added. This was before the downgrade back to 4.3. I guess I can try that again.
Teken Posted November 9, 2015 Posted November 9, 2015 Right. I don't know why it shows a slider, but the software only allows me to set it at the on or off (open/close) positions. It displays an error when you try to put the slider anywhere in between. It seems the device is fully functional from the device tree. I can open and close it directly from there without any problem. I did experience the control via the direct link vs scene on my garage IO devices. I have no option to open or close the relay on those unless I add them to a scene. I can live with that, but I did find that odd. Just to summarize though the issue: If you (literally) press the device the shades will in fact open-close with out issue, correct? Next, if you are in the Admin Console (IF) you press either Open-Close in the scene and not use the slider the shades open-close, correct?
xjsimon Posted November 9, 2015 Author Posted November 9, 2015 Just to summarize though the issue: If you (literally) press the device the shades will in fact open-close with out issue, correct? Next, if you are in the Admin Console (IF) you press either Open-Close in the scene and not use the slider the shades open-close, correct? Yes, I can open/close the curtains directly from the device. Also yes, I can open/close when directly select the device in Admin Console. And yes, I can open/close when I'm setting the scene (I only see a slider, no on/off or open/close buttons). The problem is that after I set the device to the off position in the scene, it does not seem save that position to the scene. When I leave the scene and come back to view it, it shows the device in the On position again.
Teken Posted November 9, 2015 Posted November 9, 2015 Yes, I can open/close the curtains directly from the device. Also yes, I can open/close when directly select the device in Admin Console. And yes, I can open/close when I'm setting the scene (I only see a slider, no on/off or open/close buttons). The problem is that after I set the device to the off position in the scene, it does not seem save that position to the scene. When I leave the scene and come back to view it, it shows the device in the On position again. Interesting, perhaps this is a bug that UDI is unaware of. Moving forward to get the fastest solution to this issue please submit a service request to UDI following this link: http://www.universal-devices.com/contact-support/ Please ensure you reference this thread so the history and back ground can be obtained.
xjsimon Posted November 9, 2015 Author Posted November 9, 2015 Interesting, perhaps this is a bug that UDI is unaware of. Moving forward to get the fastest solution to this issue please submit a service request to UDI following this link: http://www.universal-devices.com/contact-support/ Please ensure you reference this thread so the history and back ground can be obtained. Done. Thanks for your help Teken!
Teken Posted November 9, 2015 Posted November 9, 2015 Done. Thanks for your help Teken! No worries, but for completeness could you please affirm the module shows up as a 2444-222, and not something else in the Admin Console.
xjsimon Posted November 9, 2015 Author Posted November 9, 2015 No worries, but for completeness could you please affirm the module shows up as a 2444-222, and not something else in the Admin Console. Correct. It does show up as the 2444-222 Micro Module Open/Close v. 43. And that matches up with the module's model number.
LeeG Posted November 9, 2015 Posted November 9, 2015 The Micro Module Open/Close is relay based so only slider positions full On or Off are appropriate. Cannot set a Relay device to anything else. Can you post an event trace LEVEL 3, turning the Micro Module Scene On and Off. The ISY Scene name should be selected and On and Off buttons clicked.
xjsimon Posted November 9, 2015 Author Posted November 9, 2015 So I decided to create a new scene to keep the log on this simple. This is the log from creating the new scene and then adding the micro module to the scene: Mon 11/09/2015 02:47:56 PM : [Temp Curtain] Start : Adding scene to ISY Mon 11/09/2015 02:47:56 PM : [Temp Curtain] Finish : Adding scene to ISY was Successful Mon 11/09/2015 02:47:56 PM : [All ] Writing 0 bytes to devices Mon 11/09/2015 02:48:10 PM : [Theater Stage Curtains] Start : Adding to scene 'Temp Curtain Scene' Mon 11/09/2015 02:48:10 PM : [Theater Stage Curtains] Making 'Temp Curtain Scene' a Controller Mon 11/09/2015 02:48:10 PM : [MNG-LNK-RSP ] 02 6F 40 E2 1F 2C 96 A0 0E 01 43 06 Mon 11/09/2015 02:48:10 PM : [2C 96 A0 1 ] Link 2 : 0FE8 [A21F2FBB92FF1F01] Saving [A21F2FBB92FF1F01] Mon 11/09/2015 02:48:10 PM : [Theater Stage Curtains] Finish : Adding to scene 'Temp Curtain Scene' was Successful Mon 11/09/2015 02:48:11 PM : [All ] Writing 8 bytes to devices Mon 11/09/2015 02:48:11 PM : [iNST-TX-I2CS] 02 62 2C 96 A0 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Mon 11/09/2015 02:48:11 PM : [iNST-ACK ] 02 62 2C.96.A0 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Mon 11/09/2015 02:48:11 PM : [iNST-SRX ] 02 50 2C.96.A0 2F.BB.92 2B 2F 00 (00) Mon 11/09/2015 02:48:11 PM : [std-Direct Ack] 2C.96.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 11/09/2015 02:48:12 PM : [iNST-ERX ] 02 51 2C 96 A0 2F BB 92 11 2F 00 00 01 0F FF 00 A2 00 2F BB 92 FF 1F 01 85 Mon 11/09/2015 02:48:12 PM : [Ext-Direct ] 2C.96.A0-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Mon 11/09/2015 02:48:12 PM : [2C 96 A0 1 ] Link 2 : 0FE8 [A21F2FBB92FF1F01] Writing [A21F2FBB92FF1F01] Mon 11/09/2015 02:48:12 PM : [iNST-TX-I2CS] 02 62 2C 96 A0 1F 2F 00 00 02 0F EF 08 A2 1F 2F BB 92 FF 1F 01 6D Mon 11/09/2015 02:48:12 PM : [iNST-ACK ] 02 62 2C.96.A0 1F 2F 00 00 02 0F EF 08 A2 1F 2F BB 92 FF 1F 01 6D 06 (00) Mon 11/09/2015 02:48:12 PM : [iNST-SRX ] 02 50 2C.96.A0 2F.BB.92 2B 2F 00 (00) Mon 11/09/2015 02:48:12 PM : [std-Direct Ack] 2C.96.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 11/09/2015 02:48:12 PM : [MNG-LNK-RSP ] 02 6F 40 E2 1F 2C 96 A0 0E 01 43 15 Mon 11/09/2015 02:48:12 PM : [PLM ] Group 31 : Writing Controller Link matching [2C 96 A0 1 ] Link 2 : 0FE8 [A21F2FBB92FF1F01] This is the log from trying to setting the micro module to the off position in the scene: Mon 11/09/2015 02:50:46 PM : [iNST-TX-I1 ] 02 62 2C 96 A0 0F 13 00 Mon 11/09/2015 02:50:46 PM : [iNST-ACK ] 02 62 2C.96.A0 0F 13 00 06 LTOFFRR(00) Mon 11/09/2015 02:50:47 PM : [All ] Writing 0 bytes to devices Mon 11/09/2015 02:50:47 PM : [iNST-SRX ] 02 50 2C.96.A0 2F.BB.92 2B 13 00 LTOFFRR(00) Mon 11/09/2015 02:50:47 PM : [std-Direct Ack] 2C.96.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 11/09/2015 02:50:47 PM : [iNST-DUP ] Previous message ignored. As reported before, this does not seem to write this to the scene and the position reverts back to the on position after jumping away from it then coming back to the scene. This is the log from turning the entire scene to "On": Mon 11/09/2015 02:52:26 PM : [iNST-TX-I1 ] 02 62 00 00 1F CF 11 00 Mon 11/09/2015 02:52:26 PM : [iNST-ACK ] 02 62 00.00.1F CF 11 00 06 LTONRR (00) Mon 11/09/2015 02:52:26 PM : [D2D EVENT ] Event [2C 96 A0 1] [sT] [255] uom=0 prec=-1 Mon 11/09/2015 02:52:26 PM : [ 2C 96 A0 1] ST 255 This is the log from turning the scene "off": Mon 11/09/2015 02:53:43 PM : [iNST-TX-I1 ] 02 62 00 00 1F CF 13 00 Mon 11/09/2015 02:53:43 PM : [iNST-ACK ] 02 62 00.00.1F CF 13 00 06 LTOFFRR(00) Mon 11/09/2015 02:53:43 PM : [D2D EVENT ] Event [2C 96 A0 1] [sT] [0] uom=0 prec=-1 Mon 11/09/2015 02:53:43 PM : [ 2C 96 A0 1] ST 0
LeeG Posted November 9, 2015 Posted November 9, 2015 I had to install the Micro Open/Close before seeing the problem. Moving the Micro Open/Close slider turns the Micro On or Off. It does not "reverse" Open/Close. This is done with the Set button. Reverse Motor Direction For some applications, such as a projector screen, you want the connected motor to lower or close your connected screen or blinds when you press the up button or send an on command. Or you may have accidentally wired Micro module into the motor wrong. However, you don’t have to rewire Micro module to fix it. Follow these steps to reverse the motor direction in response to commands (i.e., an on command will close/lower while an off command will open/raise). 1) Press and hold Set button until it beeps LED will start blinking green 2) Press and hold Set button until it beeps again LED will start blinking red 3) Press and hold Set button until it beeps a third time LED will start blinking green 4) Press and hold Set button until it beeps a fourth time LED will start blinking red 5) Slowly tap Set button three times LED will continue blinking red 6) Press and hold Set button until it double-beeps 7) Test by tapping connected switch up and down Motor will now operate in the reverse direction There is no software control to reverse direction.
xjsimon Posted November 10, 2015 Author Posted November 10, 2015 I had to install the Micro Open/Close before seeing the problem. Moving the Micro Open/Close slider turns the Micro On or Off. It does not "reverse" Open/Close. This is done with the Set button. Reverse Motor Direction For some applications, such as a projector screen, you want the connected motor to lower or close your connected screen or blinds when you press the up button or send an on command. Or you may have accidentally wired Micro module into the motor wrong. However, you don’t have to rewire Micro module to fix it. Follow these steps to reverse the motor direction in response to commands (i.e., an on command will close/lower while an off command will open/raise). 1) Press and hold Set button until it beeps LED will start blinking green 2) Press and hold Set button until it beeps again LED will start blinking red 3) Press and hold Set button until it beeps a third time LED will start blinking green 4) Press and hold Set button until it beeps a fourth time LED will start blinking red 5) Slowly tap Set button three times LED will continue blinking red 6) Press and hold Set button until it double-beeps 7) Test by tapping connected switch up and down Motor will now operate in the reverse direction There is no software control to reverse direction. I'm sorry to report that this did not resolve the problem. It switched the direction of the curtain when the on/off commands are sent, but the scene will still not remember the off command. I switched it back so because my default position is open/off and that's a little easier for me to remember. I'm no expert, but this really seems like a bug. In a scene, when you change the on/off position of any other device, that change is written to the controller/device. This is what it looks like when I change another device to the off position in the scene: Mon 11/09/2015 05:13:47 PM : [iNST-TX-I1 ] 02 62 30 A8 56 0F 13 00 Mon 11/09/2015 05:13:47 PM : [iNST-ACK ] 02 62 30.A8.56 0F 13 00 06 LTOFFRR(00) Mon 11/09/2015 05:13:47 PM : [30 A8 56 1 ] Link 5 : 0FD0 [A2142FBB92001701] Saving [..........00....] Mon 11/09/2015 05:13:47 PM : [All ] Writing 1 bytes to devices Mon 11/09/2015 05:13:47 PM : [iNST-SRX ] 02 50 30.A8.56 2F.BB.92 2B 13 00 LTOFFRR(00) Mon 11/09/2015 05:13:47 PM : [std-Direct Ack] 30.A8.56-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 11/09/2015 05:13:47 PM : [D2D EVENT ] Event [30 A8 56 1] [sT] [0] uom=0 prec=-1 Mon 11/09/2015 05:13:47 PM : [ 30 A8 56 1] ST 0 Mon 11/09/2015 05:13:48 PM : [30 A8 56 1 ] Link 5 : 0FD0 [A2142FBB92001701] Writing [..........00....] Mon 11/09/2015 05:13:48 PM : [iNST-TX-I2CS] 02 62 30 A8 56 1F 2F 00 00 02 0F D7 08 A2 14 2F BB 92 00 17 01 97 Mon 11/09/2015 05:13:48 PM : [iNST-ACK ] 02 62 30.A8.56 1F 2F 00 00 02 0F D7 08 A2 14 2F BB 92 00 17 01 97 06 (00) Mon 11/09/2015 05:13:48 PM : [iNST-SRX ] 02 50 30.A8.56 2F.BB.92 2B 2F 00 (00) Mon 11/09/2015 05:13:48 PM : [std-Direct Ack] 30.A8.56-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 And when I change the micro module to the off position in a scene, all I get is this: Mon 11/09/2015 05:15:06 PM : [iNST-TX-I1 ] 02 62 2C 96 A0 0F 13 00 Mon 11/09/2015 05:15:06 PM : [iNST-ACK ] 02 62 2C.96.A0 0F 13 00 06 LTOFFRR(00) Mon 11/09/2015 05:15:06 PM : [All ] Writing 0 bytes to devices Mon 11/09/2015 05:15:06 PM : [iNST-SRX ] 02 50 2C.96.A0 2F.BB.92 2B 13 00 LTOFFRR(00) Mon 11/09/2015 05:15:06 PM : [std-Direct Ack] 2C.96.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 11/09/2015 05:15:06 PM : [iNST-DUP ] Previous message ignored.
LeeG Posted November 10, 2015 Posted November 10, 2015 According to the message the Micro module returned the Off command did turn the device Off. And when I change the micro module to the off position in a scene, all I get is this: Mon 11/09/2015 05:15:06 PM : [iNST-TX-I1 ] 02 62 2C 96 A0 0F 13 00 Mon 11/09/2015 05:15:06 PM : [iNST-ACK ] 02 62 2C.96.A0 0F 13 00 06 LTOFFRR(00) Mon 11/09/2015 05:15:06 PM : [All ] Writing 0 bytes to devices Mon 11/09/2015 05:15:06 PM : [iNST-SRX ] 02 50 2C.96.A0 2F.BB.92 2B 13 00 LTOFFRR(00) Mon 11/09/2015 05:15:06 PM : [std-Direct Ack] 2C.96.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 11/09/2015 05:15:06 PM : [iNST-DUP ] Previous message ignored. From an earlier post the Scene On and Scene Off did not change the color of the Micro Module LED? This is the log from turning the entire scene to "On": Mon 11/09/2015 02:52:26 PM : [iNST-TX-I1 ] 02 62 00 00 1F CF 11 00 Mon 11/09/2015 02:52:26 PM : [iNST-ACK ] 02 62 00.00.1F CF 11 00 06 LTONRR (00) Mon 11/09/2015 02:52:26 PM : [D2D EVENT ] Event [2C 96 A0 1] [sT] [255] uom=0 prec=-1 Mon 11/09/2015 02:52:26 PM : [ 2C 96 A0 1] ST 255 This is the log from turning the scene "off": Mon 11/09/2015 02:53:43 PM : [iNST-TX-I1 ] 02 62 00 00 1F CF 13 00 Mon 11/09/2015 02:53:43 PM : [iNST-ACK ] 02 62 00.00.1F CF 13 00 06 LTOFFRR(00) Mon 11/09/2015 02:53:43 PM : [D2D EVENT ] Event [2C 96 A0 1] [sT] [0] uom=0 prec=-1 Mon 11/09/2015 02:53:43 PM : [ 2C 96 A0 1] ST 0
Recommended Posts
Archived
This topic is now archived and is closed to further replies.