Xathros

Are you using Mobilinc Connect? You can continue to use Mobilinc in conjunction with the ISY portal. It's the MobilincConnect portal that is not compatible. If you do need Mobilinc Connect, send an email to sales@universal-devices.com with the UUID of your ISY explaining your mistake. They will take care you you. Hope this helps. -Xathros

Welcome to the forums jackman! Can you generate a scene list from Houselinc? If so, I would reset everything, add the devices fresh to the ISY and rebuild your scenes in the ISY based on your houselinc report. This is an easy process with the ISY and will likely yield a much better result than attempting to crawl and import the existing system. -Xathros

Hi Benoit- Grab a big cup of coffee and prepare for a long read: http://forum.universal-devices.com/topic/14525-amazon-echo-and-isy/ I am currently using this on my test ISY and it works like a champ even running on and old RPi rev 1. The mapper stuff has evolved well beyond what I'm currently using but the overall solution remains about the same as in the beginning of that thread. -Xathros

Sorry, not today... The Alexa ISY interface for connected home and skill have been submitted to Amazon for approval. These are not available for your Echo yet. Once Amazon approves and publishes them, then you will need the ISY portal and will need to link the ISY portal to your Amazon account. Until then, the ISY portal will allow you remote access to your ISY without the need to port forward and know your external IP address much like Mobilinc Connect does but without the extra features that Mobilinc Connect offers. Hope this helps. -Xathros

Yes it does! -Xathros

Yikes! This is gonna take me some time to digest and work out whats happening. Seems overly complex to me. All that should be needed is: KPL Button as a controller of a scene with IOLinc relay as responder. Relay in momentary B mode with 2 second delay. KPL Button in NonToggle-On mode. A scene "GarageStatusLED" with the KPL Button as responder. And a program like: If Status 'IOLinc_Sensor' is On Then Set Scene 'GarageStatusLED' Off Else Set Scene 'GarageStatusLED' On And, if you moved the switch to the other end of the door travel, you wouldn't even need the program! You could just make the IOLinc Sensor a controller of the GarageStatusLED scene. -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