Xathros

If you set the ISY for a static address, you can then specify the DNS 8.8.8.8 in the ISY and that should solve the issue until Frontier gets their network sorted out. -Xathros

Several reasons. First the 2412s supplies power to the ISY in the range of 12 to 18 volts. The ISY only needs 5 volts and in some cases last year the higher voltage from the 2412s actually burned up some of the first Zwave dongles for the ISY. Second, the 2412 is an aging device and history has shown that Smarthome's PLMs have a limited lifespan before failure. Any 2412 still in operation has already exceeded the average operational lifespan of a PLM. I would be worried that a PLM of that age is about ready to quit. Third, newer insteon devices use a newer I2CS protocol that the 2412 knows nothing about. The 2413s with current firmware should fully support the newer Insteon products. Lastly, a new 2413 will have the latest firmware with fixes for an untold number of issues since the firmware in your 2412 shipped. Hope the helps. -Xathros Sent from my iPhone using Tapatalk

Yes. However if you still have a 2412S PLM, I would consider getting a new 2413S PLM as well. -Xathros Sent from my iPhone using Tapatalk

Think you need to upgrade the ISY to 4.2.16 and try again. -Xathros

Am I missing something? Wouldn'tl this be TRUE for ALL seasons between Sept 2014 and Dec 2020, not just fall? -Xathros

Either should do the job just fine. I have the older access points. The range extender is a newer version. Not sure what to think about Smarthome refurb products as I have heard mixed reviews. If it were me, I would go with the Range extender. See this user supported/reported device list: http://www.madreporite.com/insteon/Insteon_device_list.htm It may give you what you need in terms of what each device actually does. -Xathros

What platform are you on? Mac/Windows/Linux ? -Xathros

The toggleincs are powerline only and are not sending/receiving rf at all. The Door sensor is apparently able to reach a dual band device at the main house under certain circumstances but not reliably. You need an dual band device in the garage to provide rf coverage for the door sensor. As above, I recommend an access point/range extender be installed in the garage. -Xathros

Keep in mind, a from...to time condition only self triggers at the from and to times. To have it evaluate between those times it needs to be triggered by another trigger, RunIf from another program or manually run from the console. -Xathros

My recommendation would be to plug in an access point/range extender in the garage to provide the wireless Uplink to the powerling for the door sensor and any other wireless devices you decide to add in the garage. I have one in my garage to provide coverage for an open/close sensor, motion sensor and a remotelinc2. -Xathros

Unless they are low voltage Halogen - then the transformer may introduce some noise or cause issues with dimmers. -Xathros

Are these devices dimmers? What kind of load do you have attached to these devices? -Xathros

Beat me to it! -Xath

By this do you mean: You deleted the sensor from the ISY after adding it near the PLM and you are now trying to add the Door Sensor to the ISY with the sensor in proximity of a dual band device with confirmed good communication with the ISY? -Xathros

The info posted above by LeeG is taken from the event viewer running at level 3 (device communications) To get the event viewer select tools / diagnistics / Event Viewer -or- click the empty white toolbar button. Once opened, change the dropdown at the bottom of the event viewer window to: 3 (device communications) With the event viewer open and set to level 3, move in front of your motion sensor. The insteon traffic will be captured by the event viewer. Save and post the event log here for analysis. -Xathros

Are AutoUpdates to battery devices currently disabled on your ISY ? -Xathros

I read the Smarthome ad and found it somewhat misleading in that respect as well. I did make the assumption however that it was one or the other. -Xathros

Why not use: If Control 'Ground Floor / Living Room / Light Switch (Ceiling)' is switched On and Control 'Ground Floor / Living Room / Light Switch (Ceiling)' is not switched Off Then Wait 3 hours and 59 minutes Repeat 2 times Set 'Ground Floor / Living Room / Light Switch (Ceiling)' Fast Off Wait 1 second Set 'Ground Floor / Living Room / Light Switch (Ceiling)' Fast On Wait 1 second Repeat 1 times Wait 1 minute Set 'Ground Floor / Living Room / Light Switch (Ceiling)' Off $i.cnt.LivingroomMainLightOFF += 1 $i.cnt.LivingroomMainLightOFF Init To $i.cnt.LivingroomMainLightOFF Resource 'Pushover_LivingroomMainLightOff' Else - No Actions - (To add one, press 'Action') This should provide the requested functionality AND allow the program to be canceled by manually turning the light off. -Xathros

My contribution was to point out that the data received at 3am was likely due to the 3am query running. This "Qurey All" is built into the ISY that runs by default at 3am. It was LeeG that pointed out that the data is only sent via program query when a value has changed. Now, what need to be done: 1) Open the console, open the event viewer, set to level 3 (Device Communications) 2) Take a hair dryer and blow some warm air at the stat. See if any traffic is recorded in the event viewer from the stat. If not, back to checking link records. I believe there is a specific procedure that needs to be followed when adding a TStat to the ISY. As I recall, the stat needs to be in the "Off" mode when adding for all of the nodes to be correctly added. -Xathros

One thing that may help here is to rename your scenes and devices where similar to include .scn or .dev in the names. This way you can tell them apart more readily. -Xathros

I use one of these for that kind of work. http://www.homedepot.com/p/Klein-Tools-Flexible-Drill-Bit-Kit-3-Piece-53721/203913339 -Xathros

The only comm I see from the stat is at 3am - likely due to the 3am query running. At that time, the temp was 61F, the stat was set to heat and 55F and the humidity was 38%. -Xathros

I have heard someone say that Gmail can issue a special device specific password for those things that do not support 2 factor auth. I'll see if I can google that out for you. -Xath EDIT: And Google says: https://support.google.com/mail/answer/1173270?hl=en The keyword is: Application Specific Password

smtp.gmail.com on port 587 with TLS checked and timeout at 5000ms works for me. Make sure you haven't enabled 2 factor authentication at Gmail, otherwise you will need to get a special device password set to allow the ISY to authenticate without using 2 factor auth. -Xathros

No Problem. Just wanted to make sure I wasn't missing a step somewhere. -Xathros