www.homeseer.com    
 

Go Back   HomeSeer Message Board > Lighting & Primary Technology Plug-ins > Lighting & Primary Technology Discussion > Insteon Plug-in (Mark Sandler)

Insteon Plug-in (Mark Sandler) Discussions related to Mark Sandler's 3rd parth plug-in for controlling Insteon devices via Smarthome's PLM interfaces (the 2412 & 2413 series controllers)

Reply
 
Thread Tools Display Modes
  #41  
Old April 11th, 2017, 08:34 PM
mnsandler's Avatar
mnsandler mnsandler is offline
Insteon Overlord
 
Join Date: Apr 2005
Location: Virginia
Posts: 10,694
Quote:
Originally Posted by codemonkey View Post
Set LED Brightness to Zero. No effect. Still blinks on motion.
ok. thanks for testing. I'll ask SH how to disable the LED, I think I have exhausted all the options I see in the docs
__________________
Mark

HS3 Pro 3.0.0.368
Hardware: Insteon Serial PLM | Vista Alarm 20P with AD2USB | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory
Reply With Quote
  #42  
Old April 11th, 2017, 08:44 PM
mnsandler's Avatar
mnsandler mnsandler is offline
Insteon Overlord
 
Join Date: Apr 2005
Location: Virginia
Posts: 10,694
Quote:
Originally Posted by codemonkey View Post
I'll try the brightness and report back.

I got it calibrated perfectly by using the settings shown. Do you happen to know what the actual math is there? You said it was a fraction. So logic would have it be a tenth of a degree. So for 3 degrees up, you would pick +30. But that got me 133F when I was shooting for 73F. +11 got me 71.1 and +15 got me 73.3. So...
i get the raw temperature byte from the heartbeat msg and convert it based on the power source according to one of the following:

Quote:
for hardwired operation: temp in fahrenheit = 0.73 * decimal value - 20.53
for battery powered operation: temp in fahrenheit = 0.72 * decimal value - 24.61
my understanding is the calibration value affects the temperature byte in the heartbeat msg

suggestions welcome for revising the calibration values.
Reply With Quote
  #43  
Old April 11th, 2017, 09:40 PM
codemonkey's Avatar
codemonkey codemonkey is offline
Seer Master
 
Join Date: Feb 2005
Location: Northern California
Posts: 599
If possible, I would LOVE to have the calibration be in .1 degree increments.
__________________
HomeSeer Version: HS3 Pro Edition
Operating System: Microsoft Windows 10 Pro
Processor Type and Speed: i7 - 3.26 GHz
Total Physical Memory: 16Gig

Plugins: BlBackup | EasyTrigger | FitbitSeer | HSTouchServer | Insteon | WeatherXML
Reply With Quote
  #44  
Old April 11th, 2017, 09:43 PM
codemonkey's Avatar
codemonkey codemonkey is offline
Seer Master
 
Join Date: Feb 2005
Location: Northern California
Posts: 599
I have a couple more devices on order. I plan to calibrate them all identically and see how consistent they are. Once we have a baseline then you might be able to set a better base calibration. We may find that they are all over the place. In that case it will be a little more challenging. I can tell you that my current test device is now stable within +/- .3 degrees.
Reply With Quote
  #45  
Old April 11th, 2017, 09:53 PM
mnsandler's Avatar
mnsandler mnsandler is offline
Insteon Overlord
 
Join Date: Apr 2005
Location: Virginia
Posts: 10,694
Quote:
Originally Posted by codemonkey View Post
If possible, I would LOVE to have the calibration be in .1 degree increments.
I don't have control over the increment

the calibration is a whole number adjustment to the "decimal value" in the formulas above. based on the formula, the adjust would be approximately 0.72
Reply With Quote
  #46  
Old April 11th, 2017, 10:41 PM
codemonkey's Avatar
codemonkey codemonkey is offline
Seer Master
 
Join Date: Feb 2005
Location: Northern California
Posts: 599
Ok I think I think I understand. Math challenged.
Assuming battery:
0.00°F adjusted by +1 would be 0.72°F
0.00°F adjusted by +2 would be 1.44°F...

They don't make it easy do they. :/

Thanks!
Reply With Quote
  #47  
Old April 12th, 2017, 08:30 AM
mnsandler's Avatar
mnsandler mnsandler is offline
Insteon Overlord
 
Join Date: Apr 2005
Location: Virginia
Posts: 10,694
Quote:
Originally Posted by codemonkey View Post
Ok I think I think I understand. Math challenged.
Assuming battery:
0.00°F adjusted by +1 would be 0.72°F
0.00°F adjusted by +2 would be 1.44°F...

They don't make it easy do they. :/

Thanks!
No they don't make it easy. not sure why the fw doesn't report the actual temp as opposed to the raw reading.

I really wish I had these dev notes at the beginning of the development of this unit so I could have provided some feedback on the fw.
Reply With Quote
  #48  
Old April 13th, 2017, 03:21 PM
mnsandler's Avatar
mnsandler mnsandler is offline
Insteon Overlord
 
Join Date: Apr 2005
Location: Virginia
Posts: 10,694
Quote:
Originally Posted by codemonkey View Post
Ok I don't have any more of the new motions at the moment but I will have replacements coming when they arrive. I'll be sure to give that a go if someone else doesn't beat me to it.

Correct me if I am wrong but I think you are creating the options for events for these devices. I'm wondering if there might be a way to create a range for the light level.

Right now it looks like you can only pick the exact level, but I would like to pick 0-150. That gives you more control than the dusk dawn trigger. (which I realize isn't working yet)
can't you use the default hs trigger 'value less than' or 'value great then' for this like the following?

Quote:
IF Insteon Prod 1 MS II - Light Level was set and has a value that is less than 150
Reply With Quote
  #49  
Old April 13th, 2017, 03:23 PM
mnsandler's Avatar
mnsandler mnsandler is offline
Insteon Overlord
 
Join Date: Apr 2005
Location: Virginia
Posts: 10,694
Status Update. I have resolved the following issues:

1. The led on/off
2. the dawn/dusk sensor
3. added temperature scale
4. revised battery level graphics

working on the low battery warning

i may be able to post the next beta sometime this weekend
Reply With Quote
  #50  
Old April 13th, 2017, 06:50 PM
steveng steveng is offline
Seer Plus
 
Join Date: Feb 2014
Location: Corinth, Texas
Posts: 96
Awesome news


So is fare to say Dusk/Dawn is triggered at a certain light level?
In other words you could use either to tell if room was dark etc...

I have been using Light level for past few days to keep lights from coming on during the day and that has been working.

Also have been noticing double entries in logs:
Apr-13 5:46:51 PM Insteon Received Office Motion Sensor Occupancy Sensor: (41.65.37) Go OFF
Apr-13 5:46:50 PM Insteon Received Office Motion Sensor Occupancy Sensor: (41.65.37) Go OFF
Apr-13 5:46:12 PM Insteon Received Office Motion Sensor Occupancy Sensor: (41.65.37) Go ON
Apr-13 5:46:11 PM Insteon Received Office Motion Sensor Occupancy Sensor: (41.65.37) Go ON

Thanks
Steven Giles

Quote:
Originally Posted by mnsandler View Post
Status Update. I have resolved the following issues:

1. The led on/off
2. the dawn/dusk sensor
3. added temperature scale
4. revised battery level graphics

working on the low battery warning

i may be able to post the next beta sometime this weekend
Reply With Quote
  #51  
Old April 13th, 2017, 07:17 PM
mnsandler's Avatar
mnsandler mnsandler is offline
Insteon Overlord
 
Join Date: Apr 2005
Location: Virginia
Posts: 10,694
Quote:
Originally Posted by steveng View Post
Awesome news


So is fare to say Dusk/Dawn is triggered at a certain light level?
In other words you could use either to tell if room was dark etc...

I have been using Light level for past few days to keep lights from coming on during the day and that has been working.

Also have been noticing double entries in logs:
Apr-13 5:46:51 PM Insteon Received Office Motion Sensor Occupancy Sensor: (41.65.37) Go OFF
Apr-13 5:46:50 PM Insteon Received Office Motion Sensor Occupancy Sensor: (41.65.37) Go OFF
Apr-13 5:46:12 PM Insteon Received Office Motion Sensor Occupancy Sensor: (41.65.37) Go ON
Apr-13 5:46:11 PM Insteon Received Office Motion Sensor Occupancy Sensor: (41.65.37) Go ON

Thanks
Steven Giles
Steven
yes with the dusk/dawn sensor does trigger on at one level and off at another.

you can use the Light level device itself as a trigger condition as well.

as for the double entries, are you seeing events fire twice? the plugin is going to log everything but shouldn't retrigger events if the msgs are within 1 sec of each (this is adjustable via an ini setting)

please post a detailed log snippet similar to the above if you are having trouble
Reply With Quote
  #52  
Old April 14th, 2017, 11:45 AM
Blackbeard Blackbeard is offline
Seer Plus
 
Join Date: Dec 2015
Location: PNW
Posts: 86
Can anyone comment on reliability of the new devices? I have the old version of the motion sensors and door sensors (plunger style). I would say they are about 90% reliable. I've got several other Insteon switches within a few feet of them and I even picked up a range extender. Still miss events more frequently than I would like for security related devices.
Reply With Quote
  #53  
Old April 14th, 2017, 01:38 PM
codemonkey's Avatar
codemonkey codemonkey is offline
Seer Master
 
Join Date: Feb 2005
Location: Northern California
Posts: 599
I have two of them and they are working really well. One is about 20 feet away from the nearest switch and outside. I did some range testing and the new motions have about 20% better range do to an improved antenna. One of my new devices is at 100 percent and the other is at 88% after I believe a week of activity. It is my belief that the range extender really doesn't help because each device has at least a 100' range. The problem is more likely interference from other 2.4 GHz devices or traffic collision on the insteon network.
Reply With Quote
  #54  
Old April 14th, 2017, 01:57 PM
steveng steveng is offline
Seer Plus
 
Join Date: Feb 2014
Location: Corinth, Texas
Posts: 96
I have the old ones as well and between unreliability and battery life (high traffic areas) they were useless. The new ones seem to be perfect so far only been a few days but:


I switched so I could hard wire them in (via USB plug) so they should be more reliable and as a bonus act as a repeater.

Also my reliability issue with the old ones is not a range problem I have dual band switches 5-10 feet from every sensor plus 30+ dual band thru out house so I rarely have issues with Comm Reliability.

Quote:
Originally Posted by Blackbeard View Post
Can anyone comment on reliability of the new devices? I have the old version of the motion sensors and door sensors (plunger style). I would say they are about 90% reliable. I've got several other Insteon switches within a few feet of them and I even picked up a range extender. Still miss events more frequently than I would like for security related devices.
Attached Images
 
Reply With Quote
  #55  
Old April 14th, 2017, 04:30 PM
claude claude is offline
Seer Master
 
Join Date: Mar 2002
Location: Montréal, Qc. Canada
Posts: 1,026
Quote:
Originally Posted by steveng View Post
... Also have been noticing double entries in logs ...
I've seen those double entries since at least November 2016 (oldest log). They occur for both Dusk and Dawn, most of the time, but not always. The time stamps on the entries are consistently 1 second apart.
Reply With Quote
  #56  
Old April 15th, 2017, 10:02 PM
cmomany cmomany is offline
Viewer
 
Join Date: Dec 2016
Location: Watkinsville, GA
Posts: 3
Does the plug-in work with Insteon Motion Sensor II's on the Zee? I have installed the Insteon beta plugin 3.0.6.12, but I cannot get the motion sensor II's to be recognized by the Insteon Hub (Model 2245). I can install the MSIIs via the Insteon I-Phone app just fine (though they are not found by HS3 Insteon plugin). When I try to tap add or manually add the MSII's in HS3, they are not found by the Hub. Is there any additional menu specific for the MSII setup?
I rebooted the computer a few times after the plugin update (from 3.0.6.8). Interestingly, I can see the traffic from the sensors in the log, so the hub sees them and passes messages to HS3. 41.60.ED in the following line is an MSII, but HS3 does not recognize it.

Apr-15 9:34:29 PM Insteon Received STX 0x50 (Raw Insteon Rec):41 60 ED 11 01 01 CF 06 00 Debouncing repeat.
Apr-15 9:34:28 PM Insteon Received STX 0x50 (Raw Insteon Rec):41 60 ED 11 01 01 CF 06 00

Current version is: HS3 ZEE S2 Edition 3.0.0.318
Thanks for any help!
Reply With Quote
  #57  
Old April 16th, 2017, 08:53 AM
mnsandler's Avatar
mnsandler mnsandler is offline
Insteon Overlord
 
Join Date: Apr 2005
Location: Virginia
Posts: 10,694
Quote:
Originally Posted by cmomany View Post
Does the plug-in work with Insteon Motion Sensor II's on the Zee? I have installed the Insteon beta plugin 3.0.6.12, but I cannot get the motion sensor II's to be recognized by the Insteon Hub (Model 2245). I can install the MSIIs via the Insteon I-Phone app just fine (though they are not found by HS3 Insteon plugin). When I try to tap add or manually add the MSII's in HS3, they are not found by the Hub. Is there any additional menu specific for the MSII setup?
I rebooted the computer a few times after the plugin update (from 3.0.6.8). Interestingly, I can see the traffic from the sensors in the log, so the hub sees them and passes messages to HS3. 41.60.ED in the following line is an MSII, but HS3 does not recognize it.

Apr-15 9:34:29 PM Insteon Received STX 0x50 (Raw Insteon Rec):41 60 ED 11 01 01 CF 06 00 Debouncing repeat.
Apr-15 9:34:28 PM Insteon Received STX 0x50 (Raw Insteon Rec):41 60 ED 11 01 01 CF 06 00

Current version is: HS3 ZEE S2 Edition 3.0.0.318
Thanks for any help!
the msii should be supported with your setup. how do you have the msii powered now (battery or usb)? if you haven't tried usb, try that.

otherwise please enable detailed logging in the plugin (config page), and post (copy and paste) a log snippet of the registration transaction. I need to see how the plugin is responding
Reply With Quote
  #58  
Old April 16th, 2017, 09:10 PM
mnsandler's Avatar
mnsandler mnsandler is offline
Insteon Overlord
 
Join Date: Apr 2005
Location: Virginia
Posts: 10,694
I posted 3.0.6.13 with the next beta support for the MS II.

I have resolved and added the following :

1. The led on/off works
2. revised battery level graphics
3. added the dawn/dusk sensor
4. added temperature scale
5. added the low battery warning

a few comments
- still haven't invested the Modes. stick with Occupancy mode for now
- the Low battery level is adjustable but based on my testing the MS stops transmitting at 1.5v so there isn't much adjustment between the default low level of 1.75v.

Please delete the MS II from the plugin, factory reset the device, and register it again as new. This will ensure you are testing the latest setup.
Reply With Quote
  #59  
Old April 16th, 2017, 10:07 PM
cmomany cmomany is offline
Viewer
 
Join Date: Dec 2016
Location: Watkinsville, GA
Posts: 3
Mark,
I was able to manually add three MSII's to HS3 that were powered via USB using their Insteon addresses. I then unplugged them and put the batteries in. They seem fine. I was not able to enter them using the Tap-Add- even plugged in to the USB. One MSII was obstinate and needed a hard reset. I am good now with a working situation. I guess I didn't understand the need for USB power instead of battery from the posts (and I still don't understand why this matters). Here are a bunch of lines from the INSTEON log over the time period where I was trying the Tap-Adds and got the manual to work . The time of the MSII additions was 4/15/2017 in the 8:20-8:30PM-ish range (I hope this is helpful, thanks again!):
Insteon Plug-in Error Log Generated 4/16/2017 8:57:21 PM
-----------*Error Message*----------------
Error: Forced error / log generation -- 4/16/2017 8:57:21 PM
--------*Initialization Log*--------------
4/15/2017 8:49:20 PM - Host System: () 3.0.0.318
4/15/2017 8:49:20 PM - Plugin HSPI_Insteon.exe version: 3.0.6.12
4/15/2017 8:49:20 PM - Insteon Support library (Insteon.dll) version: 1.0.6.12
4/15/2017 8:49:20 PM - RegisterCallback Completed
4/15/2017 8:49:20 PM - Enter InitIO
4/15/2017 8:49:20 PM - Enter InitPlugin
4/15/2017 8:49:20 PM - Global initialization of plug-in required, starting up.
4/15/2017 8:49:20 PM - Initializing Insteon hardware interface...
4/15/2017 8:49:20 PM - In ProcessRawReceiveThread
4/15/2017 8:49:20 PM - Initializing Interface...
4/15/2017 8:49:20 PM - In PLMBuffer_ProcessBufferThread
4/15/2017 8:49:20 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/15/2017 8:49:20 PM - Sending command 02 60 to Interface, (Expecting 6 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
4/15/2017 8:49:20 PM - Sending http://192.168.1.106:25105/3?0260=I=3
4/15/2017 8:49:21 PM - ..My XML buffer begins with: 02603C9BD403339F06
4/15/2017 8:49:21 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/15/2017 8:49:21 PM - ..Got Interface Response 02 60 3C 9B D4 03 33 9F 06
4/15/2017 8:49:21 PM - PLMBuffer_Clean - Cleared 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 to locate next possible STX
4/15/2017 8:49:21 PM - Sending command 02 60 to Interface, (Expecting 6 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
4/15/2017 8:49:21 PM - Sending http://192.168.1.106:25105/3?0260=I=3
4/15/2017 8:49:22 PM - ..My XML buffer begins with: 02603C9BD403339F06
4/15/2017 8:49:22 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/15/2017 8:49:22 PM - PLMBuffer_Clean - Cleared 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 to locate next possible STX
4/15/2017 8:49:22 PM - ..Got Interface Response 02 60 3C 9B D4 03 33 9F 06
4/15/2017 8:49:22 PM - Hub contacted on 192.168.1.106:25105 with an Insteon address of 3C.9B.D4 and firmware version 9F
4/15/2017 8:49:22 PM - ResourceManager::RequestExclusive for Resource 1
4/15/2017 8:49:22 PM - ResourceManager::RequestExclusive acquired for Resource 1
4/15/2017 8:49:22 PM - Sending command 02 6B 48 to Hub, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
4/15/2017 8:49:22 PM - Sending http://192.168.1.106:25105/3?026B48=I=3
4/15/2017 8:49:23 PM - ..My XML buffer begins with: 026B4806
4/15/2017 8:49:23 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/15/2017 8:49:23 PM - PLMBuffer_Clean - Cleared 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 to locate next possible STX
4/15/2017 8:49:23 PM - ..Got Hub Response 02 6B 48 06
4/15/2017 8:49:23 PM - ResourceManager::ReleaseExclusive for Resource 1
4/15/2017 8:49:23 PM - Insteon hardware interface initialized.
4/15/2017 8:49:23 PM - I/O (Insteon Protocol) Interface Initializing...
4/15/2017 8:49:23 PM - In TransmitMessageThread
4/15/2017 8:49:23 PM - Scheduled polling enabled.
4/15/2017 8:49:23 PM - In CreateDevices
4/15/2017 8:49:23 PM - Scheduled polling temporarily stopped.
4/15/2017 8:49:23 PM - Reloading 10 Insteon device information tables...
4/15/2017 8:49:25 PM - 10 Matching HS device records were found and updated for the Insteon device database.
4/15/2017 8:49:25 PM - 0 matching HS device records were found and updated for the Insteon group database.
4/15/2017 8:49:25 PM - Scheduled polling resumed.
4/15/2017 8:49:25 PM - Exit CreateDevices
4/15/2017 8:49:25 PM - I/O(Insteon Protocol) Interface Initialized.
4/15/2017 8:49:25 PM - Exit InitPlugin

-----------*Pre-Error Log*----------------
4/16/2017 8:31:37 PM - ResourceManager::ReleaseExclusive for Resource 1
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 0* 41 60 ED ** ** ** 8* 01 **
4/16/2017 8:31:37 PM - Received STX 0x50 (Raw Insteon Rec):41 60 ED 10 16 46 8F 02 00
4/16/2017 8:31:37 PM - Received a Direct ACK from 41.60.ED: 41 60 ED 3C 9B D4 2A 10 00
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 0* 41 60 ED ** ** ** 8* 02 **
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 0* 41 60 ED ** ** ** 8* 06 **
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 41 60 ED 3C 9B D4 8* 03 00
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 01 41 60 ED 3C 9B D4 1* 03 00
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 01 41 60 ED ** ** ** 8* ** **
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 01 41 60 ED 3C 9B D4 ** 10 FF4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 0* 41 60 ED ** ** ** 8* 01 **
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 0* 41 60 ED ** ** ** 8* 02 **
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 0* 41 60 ED ** ** ** 8* 06 **
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 41 60 ED 3C 9B D4 8* 03 00
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 01 41 60 ED 3C 9B D4 1* 03 00
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 01 41 60 ED ** ** ** 8* ** **
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 01 41 60 ED 3C 9B D4 ** 10 FF
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 0* 41 60 ED ** ** ** 8* 01 **
4/16/2017 8:31:37 PM - Received STX 0x50 (Raw Insteon Rec):41 60 ED 10 16 46 8F 02 00 Debouncing repeat.
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 0* 41 60 ED ** ** ** 8* 02 **
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 0* 41 60 ED ** ** ** 8* 06 **
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 41 60 ED 3C 9B D4 8* 03 00
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 01 41 60 ED 3C 9B D4 1* 03 00
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 01 41 60 ED ** ** ** 8* ** **
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 01 41 60 ED 3C 9B D4 ** 10 FF
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 10 16 46 8F 02 00 against key 0* 41 60 ED ** ** ** 8* 01 **
4/16/2017 8:31:37 PM - CheckRawMessageMatch: 01 41 60 ED 10 16 46 8F 02 00 against key 0* 41 60 ED ** ** ** 8* 02 **
4/16/2017 8:31:37 PM - Wait: Found a matching Insteon raw message: 01 41 60 ED 10 16 46 8F 02 00
4/16/2017 8:31:37 PM - Got controller only type broadcast for Insteon ID 41.60.ED of type 1016, Firmware version 46
4/16/2017 8:31:37 PM - Received a Broadcast message from 41.60.ED: 01 41 60 ED 10 16 46 8F 02 00
4/16/2017 8:31:37 PM - PLMBuffer_Clean - Cleared 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 to locate next possible STX
4/16/2017 8:31:37 PM - PLM_ProcessInBuffer received STX 0x54 (Button Event Report): 00
4/16/2017 8:31:37 PM - WARNING: Attempt to unbuffer more data than available in [PLMBuffer_Consume]. We had 2 and tried to consume 3.
4/16/2017 8:31:37 PM - GetInsteonProtocol for '41.60.ED'
4/16/2017 8:31:37 PM - ResourceManager::RequestExclusive for Resource 1
4/16/2017 8:31:37 PM - ResourceManager::RequestExclusive acquired for Resource 1
4/16/2017 8:31:37 PM - Sending command 02 62 41 60 ED 0A 0D 00 to Hub, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
4/16/2017 8:31:38 PM - Sending http://192.168.1.106:25105/3?02624160ED0A0D00=I=3
4/16/2017 8:31:38 PM - ..My XML buffer begins with: 02624160ED0A0D000602504160ED3C9BD42A0D02
4/16/2017 8:31:38 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/16/2017 8:31:38 PM - ..Got Hub Response 02 62 41 60 ED 0A 0D 00 06
4/16/2017 8:31:38 PM - Received STX 0x50 (Raw Insteon Rec):41 60 ED 3C 9B D4 2A 0D 02

4/16/2017 8:31:38 PM - PLMBuffer_Clean - Cleared 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 28 to locate next possible STX
4/16/2017 8:31:38 PM - Received a Direct ACK from 41.60.ED: 41 60 ED 3C 9B D4 2A 0D 02
4/16/2017 8:31:38 PM - ResourceManager::ReleaseExclusive for Resource 1
4/16/2017 8:31:38 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 01 41 60 ED 3C 9B D4 2* 0D **
4/16/2017 8:31:38 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 01 41 60 ED 3C 9B D4 ** 0D **
4/16/2017 8:31:38 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key 04 41 60 ED 3C 9B D4 2* 0D **
4/16/2017 8:31:38 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 0D 02 against key 01 41 60 ED 3C 9B D4 2* 0D **
4/16/2017 8:31:38 PM - Wait: Found a matching Insteon raw message: 01 41 60 ED 3C 9B D4 2A 0D 02
4/16/2017 8:31:38 PM - Got Insteon Protocol Engine response from Insteon ID 41.60.ED, Protocol i2CS
4/16/2017 8:31:38 PM - Reading Basement Motion Sensor 1 (41.60.ED) Settings...
4/16/2017 8:31:38 PM - ResourceManager::RequestExclusive for Resource 1
4/16/2017 8:31:38 PM - ResourceManager::RequestExclusive acquired for Resource 1
4/16/2017 8:31:38 PM - Sending command 02 62 41 60 ED 1A 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 to Hub, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
4/16/2017 8:31:39 PM - Sending http://192.168.1.106:25105/3?0262416...00000000D2=I=3
4/16/2017 8:31:39 PM - ..My XML buffer begins with: 02624160ED1A2E0000000000000000000000000000D20602504160ED3C9B D42A2E0002514160ED3C9BD41B2E00010100037F
4/16/2017 8:31:39 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/16/2017 8:31:39 PM - ..Got Hub Response 02 62 41 60 ED 1A 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06
4/15/2017 9:32:27 PM - ..My XML buffer begins with: 02623EFFC5050F000602503EFFC53C9BD4250F
4/16/2017 8:31:39 PM - Received STX 0x51 (Raw Insteon Rec):41 60 ED 3C 9B D4 1B 2E 00 01 01 00 03 7F 1E 00 00 00 02 19 B2 20 43
4/16/2017 8:31:39 PM - Received a Direct ACK from 41.60.ED: 41 60 ED 3C 9B D4 2A 2E 00
4/16/2017 8:31:39 PM - ResourceManager::ReleaseExclusive for Resource 1
4/16/2017 8:31:39 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key ** 41 60 ED 3C 9B D4 1* 2E 00
4/16/2017 8:31:39 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 00 against key ** 41 60 ED 3C 9B D4 1* 2E 00
4/16/2017 8:31:39 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key ** 41 60 ED 3C 9B D4 1* 2E 00
4/16/2017 8:31:39 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 00 against key ** 41 60 ED 3C 9B D4 1* 2E 00
4/16/2017 8:31:39 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key ** 41 60 ED 3C 9B D4 1* 2E 00
4/16/2017 8:31:39 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 00 against key ** 41 60 ED 3C 9B D4 1* 2E 00
4/16/2017 8:31:39 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 1B 2E 00 01 01 00 03 7F 1E 00 00 00 02 19 B2 20 43 against key ** 41 60 ED 3C 9B D4 1* 2E 00
4/15/2017 9:32:29 PM - ..My XML buffer begins with: 026242B3F605190206025042B3F63C9BD42119
4/16/2017 8:31:39 PM - Wait: Found a matching Insteon raw message: 01 41 60 ED 3C 9B D4 1B 2E 00 01 01 00 03 7F 1E 00 00 00 02 19 B2 20 43
4/16/2017 8:31:39 PM - Reading Basement Motion Sensor 1 (41.60.ED) Settings...
4/16/2017 8:31:39 PM - ResourceManager::RequestExclusive for Resource 1
4/16/2017 8:31:39 PM - ResourceManager::RequestExclusive acquired for Resource 1
4/16/2017 8:31:39 PM - Sending command 02 62 41 60 ED 1A 2E 01 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 to Hub, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
4/16/2017 8:31:40 PM - Sending http://192.168.1.106:25105/3?0262416...00000000D1=I=3
4/16/2017 8:31:40 PM - ..My XML buffer begins with: 151515151515151515
4/16/2017 8:31:40 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/16/2017 8:31:40 PM - ..Got NAK from the Hub for command
4/16/2017 8:31:40 PM - PLMBuffer_Clean - Cleared 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 to locate next possible STX
4/16/2017 8:31:40 PM - ..Retry #1 required. Pausing 250ms for Hub to clear...
4/16/2017 8:31:41 PM - Sending http://192.168.1.106:25105/3?0262416...00000000D1=I=3
4/16/2017 8:31:41 PM - ..My XML buffer begins with: 02624160ED1A2E0100000000000000000000000000D10602504160ED3C9B D42A2E0102514160ED3C9BD41B2E010101000703
4/16/2017 8:31:41 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/16/2017 8:31:41 PM - Received STX 0x50 (Raw Insteon Rec):41 60 ED 3C 9B D4 2A 2E 01
4/16/2017 8:31:41 PM - ..Got Hub Response 02 62 41 60 ED 1A 2E 01 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 06
4/16/2017 8:31:41 PM - Received STX 0x51 (Raw Insteon Rec):41 60 ED 3C 9B D4 1B 2E 01 01 01 00 07 03 7B 84 80 92 C0 8D 85 3E A4
4/16/2017 8:31:41 PM - ResourceManager::ReleaseExclusive for Resource 1
4/16/2017 8:31:41 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key ** 41 60 ED 3C 9B D4 1* 2E 01
4/16/2017 8:31:41 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 00 against key ** 41 60 ED 3C 9B D4 1* 2E 01
4/16/2017 8:31:41 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 01 against key ** 41 60 ED 3C 9B D4 1* 2E 01
4/16/2017 8:31:41 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key ** 41 60 ED 3C 9B D4 1* 2E 01
4/16/2017 8:31:41 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 00 against key ** 41 60 ED 3C 9B D4 1* 2E 01
4/16/2017 8:31:41 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 01 against key ** 41 60 ED 3C 9B D4 1* 2E 01
4/16/2017 8:31:41 PM - Received a Direct ACK from 41.60.ED: 41 60 ED 3C 9B D4 2A 2E 01
4/16/2017 8:31:41 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 10 00 against key ** 41 60 ED 3C 9B D4 1* 2E 01
4/16/2017 8:31:41 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 00 against key ** 41 60 ED 3C 9B D4 1* 2E 01
4/16/2017 8:31:41 PM - PLMBuffer_Clean - Cleared 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 76 to locate next possible STX
4/16/2017 8:31:41 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 01 against key ** 41 60 ED 3C 9B D4 1* 2E 01
4/16/2017 8:31:41 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 1B 2E 01 01 01 00 07 03 7B 84 80 92 C0 8D 85 3E A4 against key ** 41 60 ED 3C 9B D4 1* 2E 01

4/16/2017 8:31:41 PM - Wait: Found a matching Insteon raw message: 01 41 60 ED 3C 9B D4 1B 2E 01 01 01 00 07 03 7B 84 80 92 C0 8D 85 3E A4
4/16/2017 8:31:41 PM - Reading Basement Motion Sensor 1 (41.60.ED) Settings...
4/16/2017 8:31:41 PM - ResourceManager::RequestExclusive for Resource 1
4/16/2017 8:31:41 PM - ResourceManager::RequestExclusive acquired for Resource 1
4/16/2017 8:31:41 PM - Sending command 02 62 41 60 ED 1A 2E 03 00 00 00 00 00 00 00 00 00 00 00 00 00 CF to Hub, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
4/16/2017 8:31:42 PM - Sending http://192.168.1.106:25105/3?0262416...00000000CF=I=3
4/16/2017 8:31:42 PM - ..My XML buffer begins with: 15151515151515151515
4/16/2017 8:31:42 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/16/2017 8:31:42 PM - PLMBuffer_Clean - Cleared 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14 to locate next possible STX
4/16/2017 8:31:42 PM - ..Got NAK from the Hub for command
4/16/2017 8:31:42 PM - ..Retry #1 required. Pausing 250ms for Hub to clear...
4/16/2017 8:31:43 PM - Sending http://192.168.1.106:25105/3?0262416...00000000CF=I=3
4/16/2017 8:31:43 PM - ..My XML buffer begins with: 02624160ED1A2E0300000000000000000000000000CF0602504160ED3C9B D42A2E0302514160ED3C9BD41B2E030101B21986
4/16/2017 8:31:43 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/16/2017 8:31:43 PM - Received STX 0x50 (Raw Insteon Rec):41 60 ED 3C 9B D4 2A 2E 03
4/16/2017 8:31:43 PM - ..Got Hub Response 02 62 41 60 ED 1A 2E 03 00 00 00 00 00 00 00 00 00 00 00 00 00 CF 06
4/16/2017 8:31:43 PM - Received STX 0x51 (Raw Insteon Rec):41 60 ED 3C 9B D4 1B 2E 03 01 01 B2 19 86 BF 1A 87 00 00 00 00 00 1C
4/16/2017 8:31:43 PM - Received a Direct ACK from 41.60.ED: 41 60 ED 3C 9B D4 2A 2E 03
4/16/2017 8:31:43 PM - ResourceManager::ReleaseExclusive for Resource 1
4/16/2017 8:31:43 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 00 against key ** 41 60 ED 3C 9B D4 1* 2E 03
4/16/2017 8:31:43 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 01 against key ** 41 60 ED 3C 9B D4 1* 2E 03
4/16/2017 8:31:43 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 03 against key ** 41 60 ED 3C 9B D4 1* 2E 03
4/16/2017 8:31:43 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 00 against key ** 41 60 ED 3C 9B D4 1* 2E 03
4/16/2017 8:31:43 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 01 against key ** 41 60 ED 3C 9B D4 1* 2E 03
4/16/2017 8:31:43 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 03 against key ** 41 60 ED 3C 9B D4 1* 2E 03
4/16/2017 8:31:43 PM - PLMBuffer_Clean - Cleared 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 76 to locate next possible STX
4/16/2017 8:31:43 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 00 against key ** 41 60 ED 3C 9B D4 1* 2E 03
4/16/2017 8:31:43 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 01 against key ** 41 60 ED 3C 9B D4 1* 2E 03
4/16/2017 8:31:43 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 03 against key ** 41 60 ED 3C 9B D4 1* 2E 03
4/16/2017 8:31:43 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 1B 2E 03 01 01 B2 19 86 BF 1A 87 00 00 00 00 00 1C against key ** 41 60 ED 3C 9B D4 1* 2E 03
4/16/2017 8:31:43 PM - Wait: Found a matching Insteon raw message: 01 41 60 ED 3C 9B D4 1B 2E 03 01 01 B2 19 86 BF 1A 87 00 00 00 00 00 1C
4/16/2017 8:31:43 PM - Requesting Insteon status (Polling) for device Basement Motion Sensor 1 (41.60.ED)
4/16/2017 8:31:43 PM - ResourceManager::RequestExclusive for Resource 1
4/16/2017 8:31:43 PM - ResourceManager::RequestExclusive acquired for Resource 1
4/16/2017 8:31:43 PM - Sending command 02 62 41 60 ED 0A 19 00 to Hub, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
4/16/2017 8:31:44 PM - Sending http://192.168.1.106:25105/3?02624160ED0A1900=I=3
4/16/2017 8:31:44 PM - ..My XML buffer begins with: 15151515
4/16/2017 8:31:44 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/16/2017 8:31:44 PM - PLMBuffer_Clean - Cleared 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 to locate next possible STX
4/16/2017 8:31:44 PM - ..Got NAK from the Hub for command
4/16/2017 8:31:44 PM - ..Retry #1 required. Pausing 250ms for Hub to clear...
4/16/2017 8:31:45 PM - Sending http://192.168.1.106:25105/3?02624160ED0A1900=I=3
4/16/2017 8:31:45 PM - ..My XML buffer begins with: 02624160ED0A19000602504160ED3C9BD42A19D2
4/16/2017 8:31:45 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/16/2017 8:31:45 PM - Received STX 0x50 (Raw Insteon Rec):41 60 ED 3C 9B D4 2A 19 D2
4/16/2017 8:31:45 PM - ..Got Hub Response 02 62 41 60 ED 0A 19 00 06
4/16/2017 8:31:45 PM - PLMBuffer_Clean - Cleared 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 28 to locate next possible STX
4/16/2017 8:31:45 PM - Received a Direct ACK from 41.60.ED: 41 60 ED 3C 9B D4 2A 19 D2
4/16/2017 8:31:45 PM - ResourceManager::ReleaseExclusive for Resource 1
4/16/2017 8:31:45 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 01 against key ** 41 60 ED 3C 9B D4 2* 19 **
4/16/2017 8:31:45 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 2E 03 against key ** 41 60 ED 3C 9B D4 2* 19 **
4/16/2017 8:31:45 PM - CheckRawMessageMatch: 01 41 60 ED 3C 9B D4 2A 19 D2 against key ** 41 60 ED 3C 9B D4 2* 19 **
4/16/2017 8:31:45 PM - Wait: Found a matching Insteon raw message: 01 41 60 ED 3C 9B D4 2A 19 D2
4/16/2017 8:31:45 PM - Requesting Insteon status (Polling) for device Basement Motion Sensor 1 (41.60.ED)
4/16/2017 8:31:45 PM - ResourceManager::RequestExclusive for Resource 1
4/16/2017 8:31:45 PM - ResourceManager::RequestExclusive acquired for Resource 1
4/16/2017 8:31:45 PM - Sending command 02 62 41 60 ED 0A 19 03 to Hub, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
4/16/2017 8:31:46 PM - Sending http://192.168.1.106:25105/3?02624160ED0A1903=I=3
4/16/2017 8:31:46 PM - ..My XML buffer begins with: 02624160ED0A19030602504160ED3C9BD42A19BF
4/16/2017 8:31:46 PM - Sending http://192.168.1.106:25105/1?XB=M=1
4/16/2017 8:31:46 PM - Received STX 0x50 (Raw Insteon Rec):41 60 ED 3C 9B D4 2A 19 BF
4/16/2017 8:31:46 PM - ..Got Hub Response 02 62 41 60 ED 0A 19 03 06
4/16/2017 8:31:46 PM - ResourceManager::ReleaseExclusive for Resource 1
Reply With Quote
  #60  
Old April 17th, 2017, 06:50 AM
mnsandler's Avatar
mnsandler mnsandler is offline
Insteon Overlord
 
Join Date: Apr 2005
Location: Virginia
Posts: 10,694
Quote:
Originally Posted by cmomany View Post
Mark,
I was able to manually add three MSII's to HS3 that were powered via USB using their Insteon addresses. I then unplugged them and put the batteries in. They seem fine. I was not able to enter them using the Tap-Add- even plugged in to the USB. One MSII was obstinate and needed a hard reset. I am good now with a working situation. I guess I didn't understand the need for USB power instead of battery from the posts (and I still don't understand why this matters). Here are a bunch of lines from the INSTEON log over the time period where I was trying the Tap-Adds and got the manual to work . The time of the MSII additions was 4/15/2017 in the 8:20-8:30PM-ish range (I hope this is helpful, thanks again!):
you should be able to register the MS via the usb or battery. If using the battery, you must put the MS into linking mode first whether you are using the manual or tap add process.

I don't see any issues in the log you posted
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Programming Insteon Motion Sensor JimSpy Insteon Plug-in (Mark Sandler) 1 September 19th, 2016 09:20 PM
Insteon Motion Sensor BIGMACK48 RFXCOM Plug-In (3P) 1 April 23rd, 2010 07:11 AM
Insteon motion sensor compatibility? jdls HomeSeer General Discussion Area 2 November 2nd, 2009 12:08 PM
INSTEON Motion Sensor support? vansluis Insteon Plug-in (Mark Sandler) 56 July 20th, 2009 06:07 PM
Insteon Motion Sensor jamesx0 ISY Plug-in Beta (3P) 5 November 12th, 2008 04:10 PM


All times are GMT -4. The time now is 07:46 AM.


Copyright HomeSeer Technologies, LLC