Xathros

Glad I could help. -Xathros

Just to clarify and put it all in one place... The 4 Tap beacon test is not linking the range extenders. It's simply running a test to help you determine if their placement and circuit choices are correct to allow them to bridge the legs of your electrical feed. These are simply dual band devices with no load control or sensors built in. Since they have no controller or responder functionality, they have no need to be added to the ISY or linked to themselves or anything else. Basically just plug and play as long as they are within range of each other (or another dual band device) and on opposite legs of the electrical feed. Some folks (Teken) recommend DualBand LampLinc modules instead of range extenders as they perform double duty (same bridging function as range extender plus can control loads). -Xathros

Should be able to call a script to get the status from the python module, evaluate the response and set an ISY var with a /rest call based on the response. No? -Xathros

Does DSCLink have io_guy's Relay server built in? If so, then you have everything you need to make this work with the ISY already. A few simple bash scripts is all it would take to complete the interface between this python module and the ISY. Use the Relay server to run the scripts via the ISY's network module. If not, then look at ISYLink or NodeLink both of which offer the Relay server. -Xathros

Just curious, what was the resolution? -Xathros

Excellent. Factory reset of all new or devices being repurposed is the best route for sure. -Xathros

Stu- Understood and I have many such offsets in my programs. Just didn't expect that in this case and since the times here are less trigger and more of a limit of operations, +/- minutes makes more sense to me. Thats why I called it out. Just trying to read between the LoC. -Xath

Howdy smokegrub, Your sensor is likely configured to send On commands only. This is why you never see the status in the console change to Off. You can change that by changing the "On Commands Only" option in the sensor. You don't NEED to however. The simeplest and, in my opinion, best solution here would be to change your program to use Control rather than status: If From Sunset - 30 seconds To Sunrise - 30 seconds (next day) And Control 'Motion Sensors / Deck Motion Sensor / Deck Motion Detector-Sensor' is Switched On Then Set 'Deck Light (TL)' On Wait 10 minutes Set 'Deck Light (TL)' Off Else Set 'Deck Light (TL)' Off This solution has the added benefit of restarting the 10 minute wait with each additional motion detected and will only turn the light off after 10 minutes of no motion detected and/or at 30 seconds before sunrise. Also, did you really mean 30 seconds before sunset/sunrise or was that supposed to be minutes? Not that there is anything wrong with this, just seemed odd to me. -Xathros

In my case, because the HTTPS connection is quite noticeably slower and with a complex Mobilinc profile it becomes to slow for regular use around the house. When away, having to wait 10-15 seconds to check the status once in a while is fine. -Xathros

Because the credentials are different when using the portal and Mobilinc only allows one set of credentials per profile. -Xathros

Hi Chuck, I don't have an answer for you but I can sympathize. Mine crashes during the "Parsing Address ..." phase rather than hanging. I have gone back to regular HTTPS and HTTP for remote/local operation as I use mine both in and out of the house regularly and switching profiles would be too much of a hassle. -Xathros

Barry- I believe Lee's point was that this is an Insteon protocol limitation, not an ISY specific limitation. -Xathros

I believe so but the timing may be such that the ISY is capable of detecting the dupes. As apostolakisl mentioned above, there have been some releases where the ISY would see and act on both receives. My motion counters would double up in these instances. What I am referring to above is single broadcast messages from a device like a dual band switchlinc dimmer taking different paths and arriving at the PLM spaced far enough apart for them to appear as separate messages rather than duplicates to be ignored. -Xathros

I still see this on occasion but have chalked it up to multiple paths of communication resulting in duplicate messages received by the ISY/PLM. An Off received over the power line that turns off my bedroom light then the same Off received moments later via RF after making a few hops and crossing the phase bridge triggering my "Off when Off" trap. Only solution would be for the ISY to wait longer (continue to reject duplicates for a longer period) but then we might miss real commands in higher frequency applications (have to wait longer between paddle presses to use the double off or double on as opposed to fast off/on). -Xathros

It does work as you describe with the emulator. Initially it wasn't clear that you were referring to the mic on the remote. -Xathros

Doesn't seem to work that way for me. I always need to say "Alexa, turn on the..." -Xathros EDIT: As Jon pointed out above, you can issue the commands without the wake word if waking the echo with her remote button. I suspect this is what Stu meant.

Well, it saved me the worst of the work I though I would need to do! Not only did I not need to pull the fan down to deal with this, I was able to accomplish the whole procedure remotely! -Xathros

All set. Removed and re-added. Had to add the Fan and Light back to the various scenes they were previously members of. Did NOT have to fix the programs as after adding the devices back with exactly the same names they had, the programs all continued to show the devices after adding them back. Thanks Lee, Michel and the rest that chimed in on this. -Xathros

Duh. Thanks Lee. Guess I've spent too much time recently dealing with wireless devices... Now all I need to do is search out what scenes and programs will need to be adjusted after the delete and add. -Xathros

Thanks Michel, Turns out, this is the one device that is the hardest to deal with in my entire installation. Its the fanlinc in my MBR fan. I had a hell of a time stuffing that into the box as the fan has a very small canopy and the bracket fills most of it. Funny thing is, this device appears to be working just fine. Guess I have another project for this weekend. Hope I can get to the set button without having to pull the fanlinc out of the box. -Xathros

Hi Paul- I more suspect just a corrupted file than an actual problem with the SD card. Its not that old and I doubt I'm anywhere near is max number of writes at this point. -Xathros

Hello, I am seeing a lot of this: Mon 2015/11/16 11:42:28 PM System -110014 /CONF/149DAC.REC in my error log lately. It is always with this one file. What is this file? I'm thinking it may be a network resource rule but I'm not sure. If it is, is there any way to tell what rule ID it belongs to? Is it safe to delete? Thanks in advance. -Xathros

That is excellent news and a far cry from the days when Amazon wouldn't even acknowledge UDI's existence. Lets hope this is the beginnings of a good working relationship between UDI and Amazon. -Xathros

Well, you can use the portal for remote access to your ISY without the need for port forwarding in your router. -Xathros

You most certainly can, however, that doesn't solve the problem here. He is using a single Lamplink with multiple scenes each using a different OnLevel to control MANY activities. Off only has a single OnLevel of 0% How to know which activity the single Off is directed at? There are 100 (or 255 depending on how you get there) flavors of "on" but only 1 flavor of "Off" -Xathros