apnar

You can even lock the switches so they can't be programmed locally via options in the ISY. I lock all my devices.

If you're interested in trying to work through the issue, it sounds like an problem with your AWS_config.ini file. In particular the "Location", "ISY userid", or "ISY Password" setting in the "[uDI ISY994]" section.

Assuming you can get the Emulator to start and don't have a firewall running, all the rest of the stuff with properly formatting URLs and getting device IDs and such is wonderfully handled by barrygordon's great little configuration app. Were you having issues getting it running or configured?

Yes, I'm aware you can do things on the ISY via URL (or shall we say REST API calls). The issue is on the Echo side and how you get it to listen for a word and call the correct URL. What you're suggesting seems to be exactly number 2 I listed, using IFTTT to map echo commands to URL calls.

This still doesn't make sense though. From my understanding there is no way for the Echo and ISY to talk directly to each other. You are left with one of three options: 1) Use an emulator as a bridge running on another device in your network acting like something the Echo can talk directly to 2) use IFTTT, in which case I don't think you'd need to use different dim level approach 3) use the (hopefully approved soon) ISY skill for the Echo routing commands through ISY Portal, which again I don't think would need this different dim level approach The Hue emulator from BWS is a simple Java app, so you can run it on just about anything you may already have running 24x7 like a Pi, linux box, windows box, Mac, random NAS, etc. And as I previously mentioned you can fire off as many as you need, one per every 40 or so devices or scenes you want to control. Maybe I'm missing a forth approach where this would help.

I'm having trouble understanding why you're trying to do this in the first place? Are you just trying to get around limit on device count in the emulator? If so its much simpler to just run more emulators, you can start up as many as you need and each supports ~40 devices if I remember correctly.

Modified this slightly to add couple other 'x's that need to be adjusted for multiple emulators:

Thanks Barry. If I'm not mistaken the %20 is a space though, not a period. I also meant to say the %20 in the device ID work just fine so you can leave those as is, just need to adjust the one in the intensity byte.

Barry, Just started playing around with this stuff, great little app. I ran into a problem with getting devices to dim which I was able to work through. It appears your program (I'm using 5.0.12) creates on URLs for devices with "${intensity%20byte}". Looking at the emulator documentation (I'm using 1.0.7), it appears that it wants "${intensity.byte}" in the URL, note the period instead of %20. I changed the %20s in the in the URL to dots and it's working great. Thanks for the program!

You can temporarily set a static IP on your computer on the old range and see if you can find it. The ISY may not request new DHCP lease until old one expires, you could try power cycling it.

You can grab their super simple button: https://www.liftmaster.com/For-Homes/Accessories/Control-Panels/model-883LM If you then want something you can short you can solder to the internal button contacts of that button.

Does it require cloud connectivity to work?

I'm planning on putting in a new opener with MyQ system so have been doing a good bit of reading. I think my solution is goign to be to get an extra normal wireless remote and wire an IOlink to "press" the button on it. I also plan to hardwire power to it. Should work smoothly with no ill effects.

I reread your original post, what exactly is it you think is wrong? The only node you really need to be using is the Open node. The Closed node won't do anything in the default config of the sensor. Heartbeat just pings current state every so often so you know battery is still working.

I'd try removing the device from the ISY and adding it back using the New Insteon Device with Auto Discover. See if it adds all the nodes you're expecting.

Thanks for checking. I pulled out my backup laptop, brought it up to same versions, and I can't reproduce it there either. So I guess it's something specific with my setup. I'll see if I can track it down.

I can occasionally get one or two slides in without issue, but can reproduce the issue in a matter of seconds every time by just going to any scene and sliding a ramp rate back and forth with the mouse. Should be pretty easy for someone else with a similar config to see if it's just me or a broader issue.

So you did a hard reset and now it doesn't happen? Or does something you do after make it occur again?

Not sure exactly what you're suggesting but the communication between the ISY and PLM is not Ethernet. You could potentially use a wireless extender to connect your ISY to your home network though.

Not directly related to the above but figured I'd thread jack as title of a new thread would be almost identical. I'm running java 8 update 45 on Yosemite, I've noticed an issue with the UI hanging when trying to use a slider (such as on level or ramp rate for a scene). The little ball will slide initially but then the UI will lock up and I get the spinning beach ball. Menu doesn't respond, only thing you can do is force quit the process. Interestingly enough if you click quickly you can get it highlighted and then adjust with the keyboard arrows no problem at all, so seems to be directly related to mouse control only. Currently seeing it on 5.0 alpha but noticed the same behavior with at least the last 4 branch update or two. Anyone else seeing this issue?

They should just work Make sure the KPL main switch and the FL light are both set to controllers in the scene for the light. Pretty much exactly how you'd setup a normal "3-way" switch setup if you're familiar with that.

How about 2 ISYs each with its own PLM. Leave one as a secondary unconfigured and unlinked to anything, but IP reachable. Should the primary fail, restore the backup from the primary ISY to the secondary ISY.

I picked a 4 pack of switches up from Costco a few weeks ago. Completely normal current dual-band dimmers. Included screwless face plates as well. The thing I found interesting is the shipment came direct from SmartHome

I haven't tried it (I port forward myself) but one nice thing of Mobilinc Connect is it supports iOS push notifications which can be a nice way to get notices from various things in your house. There are of course lots of other ways to get notifications on your phone like using email or email to text gateway direct from ISY.

Not sure I agree here. One of the main reasons to have an ISY is to abstract some of the details and work. If the native values don't make logical sense the GUI should present values that do make sense and translate them. I haven't used it but from above it sounds like HouseLink does this by allowing percentages to be defined. Setting LED values of KPLs is an area that could use some polish or at a minimum more descriptive text in the GUI.