Author |
|
Ktulu Newbie
Joined: March 14 2007 Location: United States
Online Status: Offline Posts: 25
|
Posted: September 12 2011 at 21:22 | IP Logged
|
|
|
Lee, thanks for posting this. It solved my motion sensor occupancy mode problem. Many thanks.
__________________ Jeff
"Assiduus usus uni rei deditus et ingenium et artem saepe vincit" - Cicero
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: January 19 2012 at 17:41 | IP Logged
|
|
|
I would like to create a macro that warns me when battery voltage is low on the motion sensors using the extended commands with jumper 5 on. If I follow the post, the macro will generate a report (a text file??) that shows all of the settings of the 2420M. I created the trigger, but I am confused (inexperienced) how to make the macro. I copied the text file from your post, but I am not sure what to do with it. I tried to paste it into the formula editor, but it was too long. What drop down command do I use in the command column, and what do I do with a copied text to create the macro? How will the results be displayed? Can I accomplish what I am trying to do with respect to a warning flag generated by low battery voltage?
Lee/Dave, thank you for time in sleuthing out the motion sensor settings last year.
OK . . . fumbling around a bit here, but maybe I should use the Multi-editor in SQL mode? I pasted the text and let it execute and got the following response:
SQLSTATE = 23000
[Sybase][ODBC Driver][Adaptive Server Anywhere]Integrity constraint violation: Primary key for table 'macroheader' is not unique
Am I on the right track here? When I try to save the script I am not even sure what to save it as.
Edited by Handman - January 19 2012 at 20:55
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: January 19 2012 at 21:07 | IP Logged
|
|
|
Usually you get that message when you have not deleted the previous version of the macro.
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: January 19 2012 at 21:13 | IP Logged
|
|
|
I just tried again with a clean paste and new editor and got it again. I am supposed to be pasting the entire text file (all 172 lines) into the multi-editor, right?
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: January 19 2012 at 21:20 | IP Logged
|
|
|
When in the Multi-Editor make sure you are in Sql Shift + F5.
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: January 19 2012 at 21:27 | IP Logged
|
|
|
A little better clarity… 1st make sure you do NOT have a macro by that name. Then bring up the text with notepad and select all. Copy and paste it onto the MultiEditor. Check that you are in Sql if not F5. Then execute. Should work…
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: January 19 2012 at 21:32 | IP Logged
|
|
|
The macro is not saved, the SQL statements are executed. The first line is the macro header which establishes the name of the macro. It can be renamed to anything after the macro has been created.
Note that the macro is used to configure the motion sensor. You do not need it for Low Battery. The motion sensor sends a single Group 3 On when the battery is low. Link the motion sensor Group 3 as Controller to the PH PLM as Responder. This is necessary for the motion sensor to know what device to send the Group 3 On message to. Then create a trigger that fires on the Group 3 On.
__________________ Lee G
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: January 19 2012 at 21:34 | IP Logged
|
|
|
BTW to trigger a battery low setup a trigger with ID Number 3 Trigger Value On Trigger Type Insteon Group In and you will be good to go with whatever you want to do with it.
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: January 19 2012 at 21:37 | IP Logged
|
|
|
Opps.. No time no see Lee. Good to hear from you.
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: January 19 2012 at 22:30 | IP Logged
|
|
|
The problem, as you noted Pete, was that I had already saved a macro by the same name and so the script was trying to duplicate the same name. OK. The macro is saved correctly and now I see that I just need to set Trigger ID 3 for the low battery. Thank you, I'll do that.
I ran the macro and Lee's motion sensor setting page came up. THANK YOU!
Edited by Handman - January 19 2012 at 22:45
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: January 19 2012 at 22:42 | IP Logged
|
|
|
I personally found it to be informative and self-explanatory when you ran it. It is basically a development tool to assist one in understanding the extended capability of the motion sensor. Lee did a good job of developing it to assist in understanding what the device was up to. Just follow his instructions and your questions will be answered.
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: January 19 2012 at 22:49 | IP Logged
|
|
|
Thank you yet again Lee and Pete. It all works flawlessly (at least as flawlessly as the 2420M works). I can't tell you how tickled I am to send an Insteon command to the MS! Thanks!
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: February 02 2012 at 12:21 | IP Logged
|
|
|
OK, well, that didn't last long. I set the MS to occupancy mode and within 24 hours I was getting low battery warnings. I figured this was a battery drain so I ran Lee's macro to change the settings. A few days later with a new battery, I noticed my MS started misbehaving. I activated Lee's macro again to see what was up and noticed that all the settings I had redone were now at some new settings - some I'd set, some I hadn't. I reran the macro and the script always tells me that the new settings are in place, but if I run the script again, the old (incorrect) settings are there! So, I have a few questions: (1)Does the pop-up which reports that the new settings are programmed just report what was supposed to have happened, or does it actually receive some sort of Insteon confirmation from the motion sensor that the settings were actually changed? (2) Does it matter if jumper 5 (read/write) is left on, or should it be "unjumped" after making the changes, assuming the changes have happened? (3) How many outgoing commands does PH send to change the variables in the motion sensor? My event log shows several Insteon Out commands with Ext DATA, but I never see an Insteon In received with Ext DATA. Maybe my motion sensor is being read, but not written by the script? Any thoughts? Screen shots of event log included.
Edited by Handman - February 02 2012 at 13:41
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: February 02 2012 at 12:37 | IP Logged
|
|
|
There is a bug in 2.1.4 that is not returning Extended data. That is why you do not see the motion sensor configuration being retrieved with Extended commands.
The final popup reflects what was changed. It does not reflect an additional retrieval of configuration data after the changes are applied. Invoking the macro again without changing anything should show the new values.
Leave Jumper 5 On.
For the battery to drain in a few days it sounds like I have a bug in the macro. There is a command that prevents the motion sensor from turning off the RF circuitry. There should be a follow-up command at the end to allow the motion sensor to go back to normal mode of turning the RF off. I'll check the macro and post back.
__________________ Lee G
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: February 02 2012 at 13:18 | IP Logged
|
|
|
OK, so what seems to be happening is that the popup says the values were changed, but if I run the script again, the values haven't changed. How many times will the Insteon Out command be sent by PH? There are usually a half dozen . . . is that due to the bug in PH or is that because no Insteon In command is received by PH even though it is received? Is it possible that the global variable for MSWRITE changes from a Y back to an N before the changed values are actually received by the motion sensor? Finally, what I see in my motion sensor is actually different than what is showing when the script is first run. E.g., options 2,4,6 and 8 are starred (***), but these are not accurate. My MS is sending OFF commands, the LED is ON, and it seems to be working in daylight conditions. Furthermore, the LED light level shows "0," but I can see it plainly (I try to set it at 50); the current ambient light level shows "0", but it is in a room with daylight; the battery level also shows "0," but this is a one day old battery and the unit appears to trigger with motion most of the time. Also, the jumper status shows OFF for 2-5, but the jumper is ON for #5. As for whether there may be a bug in the macro keeping the RF alive, keep in mind that this is the battery that came with the motion sensor, although it was received from Smarthome a week ago. I never checked the voltage before installing it. When I pulled it two days ago though, the voltage was still decent at 8.5V with no load on it. More screenshots of script attached with a before and after . . . note that the after is the original popup after supposedly changing the settings.
Edited by Handman - February 02 2012 at 13:40
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: February 02 2012 at 13:47 | IP Logged
|
|
|
Post the Insteon Raw Log file from first MS On that triggers the macro and displays the current MS configuration through the second MS On that writes the updates. I do not see a missing command to restore normal RF operation that I initially assumed was the bug. The trace will document what commands are being issued and whether they are successful.
__________________ Lee G
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: February 02 2012 at 14:38 | IP Logged
|
|
|
2012-02-02 11:34:34.149 RX &nbs p; RECEIVEX10RAW=5E 00
2012-02-02 11:34:34.602 RX &nbs p; RECEIVEX10RAW=52 80
2012-02-02 11:34:37.696 RX &nbs p; RECEIVEINSTEONRAW=14 7C E2 00 00 01 C3 11 01
2012-02-02 11:34:37.883 TX &nbs p; 02 62 14 7C E2 1F 2E 00 00 00 00 &nbs p;
2012-02-02 11:34:37.915 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:34:41.930 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:34:41.930 TX &nbs p; 02 62 14 7C E2 1F 2E 00 00 00 00 &nbs p;
2012-02-02 11:34:42.618 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:34:46.633 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:34:46.680 TX &nbs p; 02 62 14 7C E2 1F 2E 00 00 00 00 &nbs p;
2012-02-02 11:34:47.321 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:34:51.352 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:34:51.368 TX &nbs p; 02 62 14 7C E2 1F 2F 00 00 00 00 07 01
2012-02-02 11:34:51.946 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:34:55.962 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:34:55.962 TX &nbs p; 02 62 14 7C E2 1F 2F 00 00 00 00 07 01
2012-02-02 11:34:56.399 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:35:00.415 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:35:00.462 TX &nbs p; 02 62 14 7C E2 1F 2F 00 00 00 00 07 01
2012-02-02 11:35:00.899 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:35:04.930 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:35:21.227 RX &nbs p; RECEIVEX10RAW=5E 00
2012-02-02 11:35:21.696 RX &nbs p; RECEIVEX10RAW=52 80
2012-02-02 11:35:25.024 RX &nbs p; RECEIVEINSTEONRAW=14 7C E2 0F 44 B1 42 11 01
2012-02-02 11:35:25.368 RX &nbs p; RECEIVEINSTEONRAW=14 7C E2 0F 44 B1 43 11 01
2012-02-02 11:35:36.696 RX &nbs p; RECEIVEX10RAW=5E 00
2012-02-02 11:35:37.165 RX &nbs p; RECEIVEX10RAW=52 80
2012-02-02 11:35:54.071 RX &nbs p; RECEIVEX10RAW=5E 00
2012-02-02 11:35:54.555 RX &nbs p; RECEIVEX10RAW=52 80
2012-02-02 11:35:59.227 RX &nbs p; RECEIVEINSTEONRAW=0F 46 22 FB 44 B1 43 13 01
2012-02-02 11:36:00.008 RX &nbs p; RECEIVEINSTEONRAW=0F 44 B1 17 44 B1 43 13 01
2012-02-02 11:36:02.555 RX &nbs p; RECEIVEINSTEONRAW=14 7C E2 00 00 01 C3 11 01
2012-02-02 11:36:02.774 TX &nbs p; 02 62 14 7C E2 1F 2E 00 00 00 00 &nbs p;
2012-02-02 11:36:03.508 RX &nbs p; RECEIVEINSTEONRAW=14 7C E2 00 00 01 C3 11 01
2012-02-02 11:36:03.618 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:36:03.665 RX &nbs p; RECEIVEINSTEONRAW=14 7C E2 0F 44 B1 27 2E 00
2012-02-02 11:36:03.758 TX &nbs p; 02 62 14 7C E2 1F 2F 00 00 00 00 07 01
2012-02-02 11:36:03.821 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:36:03.852 RX &nbs p; RECEIVEINSTEONEXT=14 7C E2 0F 44 B1 13 2E 00 00 01 32 00 80 0E 00 00 0E 01 10 5B 00 00
2012-02-02 11:36:06.071 RX &nbs p; RECEIVEINSTEONRAW=14 7C E2 0F 44 B1 27 2F 00
2012-02-02 11:36:07.852 RX &nbs p; INSTEON EXT TIMEOUT=
2012-02-02 11:36:07.852 TX &nbs p; 02 62 14 7C E2 1F 2F 00 00 00 00 07 01
2012-02-02 11:36:08.165 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:36:12.180 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:36:12.227 TX &nbs p; 02 62 14 7C E2 1F 2F 00 00 00 00 07 01
2012-02-02 11:36:12.962 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:36:16.993 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:36:17.024 TX &nbs p; 02 62 14 7C E2 1F 2E 00 00 05 0E &nbs p;
2012-02-02 11:36:17.571 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2E 00 00 05 0E 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:36:21.602 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:36:21.602 TX &nbs p; 02 62 14 7C E2 1F 2E 00 00 05 0E &nbs p;
2012-02-02 11:36:22.337 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2E 00 00 05 0E 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:36:26.368 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:36:26.415 TX &nbs p; 02 62 14 7C E2 1F 2E 00 00 05 0E &nbs p;
2012-02-02 11:36:27.102 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2E 00 00 05 0E 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:36:31.118 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:36:31.133 TX &nbs p; 02 62 14 7C E2 1F 2E 00 00 02 32 &nbs p;
2012-02-02 11:36:31.837 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2E 00 00 02 32 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:36:35.915 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:36:35.915 TX &nbs p; 02 62 14 7C E2 1F 2E 00 00 02 32 &nbs p;
2012-02-02 11:36:36.477 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2E 00 00 02 32 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:36:40.493 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
2012-02-02 11:36:40.540 TX &nbs p; 02 62 14 7C E2 1F 2E 00 00 02 32 &nbs p;
2012-02-02 11:36:41.024 RX &nbs p; SENTINSTEONEXT=0F 44 B1 14 7C E2 1F 2E 00 00 02 32 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 11:36:45.055 RX &nbs p; INSTEON EXT TIMEOUT=14 7C E2
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: February 02 2012 at 15:01 | IP Logged
|
|
|
The motion sensor is not responding to commands.
Is this a V1 or V2 motion sensor?
What is the PLM firmware level?
__________________ Lee G
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: February 02 2012 at 15:28 | IP Logged
|
|
|
Motion sensor is V 2.0 according to the sticker. I got is a few weeks ago. It was exchanged by Smarthome because the other one - less than a year old failed.
PLM is a 2412S ver 2.95 according to the sticker on the exterior. I am not sure it can be flashed, or if I have done that at some point. The PLM is several years old, 2008 according to the sticker I think.
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: February 02 2012 at 16:07 | IP Logged
|
|
|
The PH Help | About | Controllers shows the PLM firmware level.
This is what the Insteon Raw Log should look like. No timeouts and the Extended commands get a response even though PH does not pass the data to the macro.
2012-02-02 15:59:18.015 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 00 00 01 C7 11 01
2012-02-02 15:59:18.625 TX &nbs p; 02 62 13 F2 57 1F 2E 00 00 00 00 &nbs p;
2012-02-02 15:59:19.140 RX &nbs p; SENTINSTEONEXT=0F 44 DC 13 F2 57 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 15:59:19.437 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 0F 44 DC 23 2E 00
2012-02-02 15:59:19.656 RX &nbs p; RECEIVEINSTEONEXT=13 F2 57 0F 44 DC 13 2E 00 00 01 64 00 80 0A 00 86 0E 01 01 53 00 00
2012-02-02 15:59:20.562 TX &nbs p; 02 62 13 F2 57 1F 2F 00 00 00 00 07 01
2012-02-02 15:59:21.296 RX &nbs p; SENTINSTEONEXT=0F 44 DC 13 F2 57 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06
2012-02-02 15:59:22.656 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 0F 44 DC 27 2F 00
2012-02-02 15:59:22.953 RX &nbs p; RECEIVEINSTEONEXT=13 F2 57 0F 44 DC 11 2F 00 00 01 00 07 01 50 10 01 34 0A 64 00 80 00
2012-02-02 16:00:07.343 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 00 00 01 C7 11 01
2012-02-02 16:00:07.890 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 00 00 01 C7 11 01
2012-02-02 16:00:08.250 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 0F 44 DC 41 11 01
2012-02-02 16:00:08.421 TX &nbs p; 02 62 13 F2 57 1F 2E 00 00 00 00 &nbs p;
2012-02-02 16:00:08.484 RX &nbs p; SENTINSTEONEXT=0F 44 DC 13 F2 57 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 16:00:09.046 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 0F 44 DC 27 2E 00
2012-02-02 16:00:09.343 RX &nbs p; RECEIVEINSTEONEXT=13 F2 57 0F 44 DC 17 2E 00 00 01 64 00 80 0A 00 86 0E 01 00 53 00 00
2012-02-02 16:00:10.156 TX &nbs p; 02 62 13 F2 57 1F 2F 00 00 00 00 07 01
2012-02-02 16:00:10.890 RX &nbs p; SENTINSTEONEXT=0F 44 DC 13 F2 57 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06
2012-02-02 16:00:10.906 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 0F 44 DC 27 2F 00
2012-02-02 16:00:11.125 RX &nbs p; RECEIVEINSTEONEXT=13 F2 57 0F 44 DC 11 2F 00 00 01 00 07 01 50 10 01 34 0A 64 00 80 00
2012-02-02 16:00:11.187 TX &nbs p; 02 62 13 F2 57 0F 20 18
2012-02-02 16:00:11.234 RX &nbs p; SENTINSTEON=0F 44 DC 13 F2 57 0F 20 18 06
2012-02-02 16:00:11.828 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 0F 44 DC 27 20 18
2012-02-02 16:00:12.078 TX &nbs p; 02 62 13 F2 57 1F 2E 00 00 05 0E &nbs p;
2012-02-02 16:00:12.125 RX &nbs p; SENTINSTEONEXT=0F 44 DC 13 F2 57 1F 2E 00 00 05 0E 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 16:00:12.703 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 0F 44 DC 27 2E 00
2012-02-02 16:00:12.812 TX &nbs p; 02 62 13 F2 57 1F 2E 00 00 02 20 &nbs p;
2012-02-02 16:00:12.968 RX &nbs p; SENTINSTEONEXT=0F 44 DC 13 F2 57 1F 2E 00 00 02 20 00 00 00 00 00 00 00 00 00 00 00 06
2012-02-02 16:00:13.890 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 0F 44 DC 27 2E 00
2012-02-02 16:00:14.000 TX &nbs p; 02 62 13 F2 57 0F 20 19
2012-02-02 16:00:14.140 RX &nbs p; SENTINSTEON=0F 44 DC 13 F2 57 0F 20 19 06
2012-02-02 16:00:14.421 RX &nbs p; RECEIVEINSTEONRAW=13 F2 57 0F 44 DC 27 20 19
Perhaps moving the motion sensor and access point closer to the PLM.
Smarthome does not flash the PLM.
Edited by grif091 - February 02 2012 at 16:08
__________________ Lee G
|
Back to Top |
|
|