Xathros

Copy to clipboard is the way to go. Paste them into code blocks using "<>" on the toolbar.

Post your programs. I will see whats going on. Normally, the IOLinc sensor would be a scene controller with the KPL LED(s) as responders. Why not just move your switch to the other end of the track to sense when the cam is in the closed position? At worst all you would need to do is extend the wire. -Xathros

Hi Dave- Assuming a link table problem, try a Restore Device on both the KPL and the IOLinc and test again. If it were me, I would relocate the limit switch to the door closed end of the track to have a positive indication that the door is closed. -Xathros

I would check with Wes and make sure you will no longer be paying for MLC once its disabled. -Xathros

Hi Benoit- Thats Perfect! URL length is not that important. I can edit my resources one more time knowing its a planned change. Thanks again. -Xathros

Just FYI... I don't believe the geofencing requires Mobilinc Connect as I'm using it just fine without. -Xathros

No problem. Happy to help. -Xathros

Thanks stu! That did the trick. -Xathros

I just updated my Java to 1.8.0_65-b17 and now find that I'm unable to connect to my admin console via https. I receive the following error: What needs to be done to resolve this? Thanks in advance. -Xathros

If you don't want to relocate the stat, you might consider placing a shim behind the bottom of the stat to angle the whole unit up a bit. -Xathros

Excellent. Its not a show stopper since there is a usable workaround but it sure would make it easier if we could just paste the token into the URL field and let the console handle the encoding. Maybe there could be a way for the ISY to pick up the token from a field in the portal module or system config tab then use a ${token} in the network resource. -Xathros

If using the unencoded url from the isy information tool in a network resource then instructing the isy to encode the url, the / chars are not encoded by the isy as it treats them as path delimeters rather than part of the token. My workaround is to use the already encoded isy url minus the /desc and then manually encode the device address and leave encode url unchecked. -Xathros Sent from my iPhone using Tapatalk

The problem is that the admin console doesn't encode the / but treats it as a path delimeter. -Xathros Sent from my iPhone using Tapatalk

Thanks Benoit. The URL for both of my ISYs changed sometime in the last 2 weeks. This was the second time I noticed since the URL changed from the uuids. I will be happy if it stays static from here on out. Any thoughts about preventing the "/" in the hash string? -Xathros Sent from my iPhone using Tapatalk

Thanks Michel. -Xathros

Hello Michel- I noticed once again that the portal URLs have changed for both of my ISY's. I had to remove the finder entries and recreate them using the new URLs. In addition, I had to update the network resources that use the portal URLs to control the other ISY. After update they are now erroring again with HTTP 423 (Locked). Last time this was because I needed to unencode the portal URL before using it in the network resource. This time I'm working with the un-encoded URL and still can't seem to get past the 423s. I thought the portal URLs were going to remain static? I will continue to poke at the resources to see if I can't find my problem. -Xathros EDIT: Solved the 423s again. Two issues here. First when I replaced the portal URL with the unencoded portal IURL, I forgot to unencode the device addresses. Then I checked Encode URL which double encoded thed device address portion. Second problem is that my unencoded URL contains 2 "/" characters that the ISY will not encode since it seems to think that they denote a path delimiter. Had to go back to using the pre-encoded URL and manually encoding the device addresses. Not sure if this can be solved. Only way I see would be to prevent the "/" character from being used in a portal URL token.

I suspect a program got inadvertently/unintentionally changed to cause this hence the search since otherwise you would likely know where to look! -Xathros

OK - Do a search with the find in the program tree for the KPL in question and look for any program that uses the notation I provided above to set the backlights on that KPL. -Xathros

I have a program that runs twice daily to enable/disable my KPL backlights in the bedrooms. Don't like the light at night. I would think you would be able to recover from this with a program like: ComeOnBabyLightMyKPL - [ID 0009][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Office / Office KPL / Office KPLA' On 15 / Off 7 (Backlight Level) Else Set 'Office / Office KPL / Office KPLA' On 2 / Off 0 (Backlight Level) Just RunThen to light it up or RunElse to go dark. -Xathros

Excellent news! Looking forward to seeing how this all works! -Xathros

In my opinion, "Izzy" would be much better in term if ease of use. -Xathros Sent from my iPhone using Tapatalk

UDI has written an Alexa skill and submitted it to Amazon for approval. No idea how long this process takes. In addition, there is a community project that already has Echo working with the ISY but it requires another machine in the middle like a Raspberry Pi or full time PC. See this long thread for details:http://forum.universal-devices.com/topic/14525-amazon-echo-and-isy/ -Xathros

Between devices, 1 sec should do. After a scene with many devices in it, 3-5 seconds might be better. I usually go with 1-2 between resource calls. Network resource calls can and do queue up if things are busy. If doing variable substitution within the resource, it is possible to call a resource and have the variable change downstream in the programs before the resource is substituted and sent. Where this is possible, you may want a longer delay. Just beware. -Xathros

Shouldn't need a delay between variable changes unless they will drive insteon activity in other programs when changed. I find it to be a good idea to delay between scene and device actions to allow time for ack/cleanup messages to happen before generating more traffic. -Xathros

Mil- As Stu said, set the buttons to 'Non-Toggle ON' mode. Create scenes as follows: FanLow: Button B - Controller - On level 100% Button C - Responder - On Level 0% Button D - Responder - On level 0% Button E - Responder - On Level 0% FanLinc - Responder - Fan Low FanMed: Button B - Responder - On level 0% Button C - Controller - On Level 100% Button D - Responder - On level 0% Button E - Responder - On Level 0% FanLinc - Responder - Fan Med FanHi: Button B - Responder - On level 0% Button C - Responder - On Level 0% Button D - Controller - On level 100% Button E - Responder - On Level 0% FanLinc - Responder - Fan High FanOff: Button B - Responder - On level 0% Button C - Responder - On Level 0% Button D - Responder - On level 0% Button E - Controller - On Level 0% This makes the Off button go dark after turning off the fan. FanLinc - Responder - Fan Off If you prefer to use only 3 buttons, you can eliminate the FanOff scene and keep all of the buttons in toggle mode. Hope this helps. -Xathros