paulbates

I've had good luck with the remote sensor that came with my ecobee. Keeps the temps better balanced without resorting to baffles or individual vent control. The 'occupied' feature had the halo effect of it turning off the suite lights off after 30 mins if left on

This is a bit of a long shot, but easy to try; unplug the PLM for 10 seconds and plug back in. If that doesn't do it, post a screen shot of the link table showing the device and indicating which device it is

That's not the log he's asking for. You need to get the log from pg3x and the plugin. Go to the same web page you showed above ... and click log. Set the log level to debug. Recreate the steps for this and other device. Download the log package from the same web page and PM to panda88

Using Alexa requires an active portal subscription. If the subscription expires, this would happen. I don't think a warning is given, I keep track with a calendar entry It could be something else, but I'd start there

Keeping on the program track, you could try putting a notification at the end to see if the program is finishing regardless of what the device does.

Have you tried moving the statements to another program and calling that program from the one you posted? It would not take much to test the hypothesis

You're certain that the program conditions are not changing to false during the 5 minutes? Without seeing the program it sounds very much like that

Pretty sure the 3000 port was either eisy, pg3 or both. I think earlier PG was 8080 Having said that, its not clear to me that eisy will talk to both at the same time (?)

Another thing is that devices can be dragged into scenes, but scenes cannot be dragged into other scenes. However, you can have almost unlimited scenes (in most installations) and can create many similar ones to create the lighting effects you want for different switches, programs, etc

You can add the center switch to the existing scene...but be sure to click the box to make it a controller. If you didn't do that, remove it from the scene and re-add it as a controller

You need to know how to log when you have an plugin issue and developer asks you to send them a log. What's important to know about that is: you go to the dashboard in pg3x go into the individual plugin itself click details Click log Click "debug" from the list Do the steps that recreate the error you are seeing Click download log package Send that zip file in a message to the developer There's a new wrinkle in the Session and Session Verbose options. I'm going to not select those unless instructed to by the developer.

I used iox during the update window, and just started it again now... it's working as expected

Pick one or two key scene participants, right click on them in iox and pick "restore device"

The alarm does work as expected and quickly! Thanks @Panda88!

Having done several controller software jumps on top of insteon, I suggest breaking the migration into functions or rooms. Start simple and migrate a handful of devices in one room that are fairly simple. Get those back to their original functionality on eisy with programs, scenes, etc. Then pick another room/function. Move at a pace that lets you learn while not frustrating the other occupants. As you learn, you can convert more and go faster. Do not try a "big bang" conversion

Can you post one of the programs? Ideally, you'd add an if clause to see if the light is on . Here's a sample idea If Time is xx:xx AND Status my light is 0% Then Turn on the light Unfortunately it would have to be one light at a time using this method

Sure. Include the UUID of your new unit in the ticket text

Do not buy another license. Submit a ticket and it will get fixed.

I'll get the log file to you in a pm. I did think about changing the range to force it to report more frequently like I did with the 8003 Temp/Humid sensors. The "out of the box" alarm range for the plug is as wide as it goes. It's also a little confusing as it reports kWh, but the control for the alarm says it's in watts. I admittedly took a gamble seeing if this would work for this application and it's looking like no. FWIW it does function similarly to Insteon an on off module if wanting to use it that way

@Panda88 I'm implementing my power sensor for my laundry fan, outlined above, and hit a snag. The plug-in eventually shows the operational load 2.286kWh in iox: The problem: I have this program. Even though iox shows the above energy value, the program will not run, including using a "run if" 1- Laundry Fan run Start Copy - [ID 005C][Parent 0063] If 'HVAC / Dryer Monitor' Watt > 2.00 kW Then // Start the laundry fan based on power sensor, shut it off based on temperature returning to normal range Set 'HVAC / Laundry Fan' On $Laundry_Fan_Start_Temperature = 'HVAC / Laundry Temp Humidity Sensor' Sensor Temperature °F // Let laundry area warm up a little Wait 15 minutes $Laundry_Fan_Auto = 1 Else - No Actions - (To add one, press 'Action') I pulled a debug level log where I had the dryer stopped, and then turned it on. Like the temp/humid sensors, it can take a long time for the module to report If I turn the plug on and off with iox or at the plug, the starting kWh come through I tried query and see messages in the log I can use iox and turn the module on/off remotely, so its working, but I plan to leave it on always It's a gas dryer, so the module is only powering the motor, not heating elements

There's a discrepancy between the data eisy has about the device, based on you configuring it, and how it sees the device on zwave network. The green arrows mean eisy tried to write config data to the device, but was unable to.

Not sure if this is in the directions: I had to physically reboot the eisy once or twice on first setup to access is and for it to access the new PLM i added to it

As it's a security device, it may require the device to be set in a mode to allow updates... Usually pressing a set button or something on the device itself to permit network changes

It sounds like java has not been installed on your system from java.com An installed instance of Java would identify itself as the app to run .jnlp links.

Since the isy is receiving the messages, that suggests it's the harmony that's sending them. Was there something done on the harmony side when you first set up the plug-in to authorize the isy to access it? It may be trying to discover the plug-in.