paulbates

@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

I had the dimmer and relay versions of these at my last house. It's important to know that they are power-line / single band only. If there's a change in powerline nearby, it can "numb" them. I had one at the furthest edge of my powerline. Every year or so it would flake out and I would have to factory reset it and restore device. I had several of the wireless access points and I eventually plugged one in near by and it worked ok after that as well as helping other devices. A dualband device would serve the same purpose.

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.

The behavior is definitely odd. I had a short experience with 2441TH in 2012 for a few weeks. More than once I had to pull the power lead and restart it because of flaky behavior. I know you said you've had no problems previously but I would try the following things: Pull the power lead, wait 10 seconds and repower it, see what happens If that doesn't work: factory reset it, power off, wait 10 seconds and repower, followed by put it in linking mode and restore device

I would put one in linking mode, right click on it in iox (admin console) and pick restore device. Test it again. If it works, do it for the other one

Sounds like some info did not come across in your backup? Do you still have your ISY? You could fire it up, open it with the admin console and see what the settings/configs were previously, screen shoot it or something and update the eisy. If there are no other ideas here, I would submit a ticket.

If you want to test your formatting changes only, right-click on the program name and pick "run then". If the notification is buried in a lot of code or part of multiple programs, create a temporary program with no "if" that sends the notification, and "run then" that program

I didn't think ecobee, venstar or insteon will meet your need. They're wireless in that you can control their functions via Wi-Fi (or insteon) with software, but they all need 24vac wiring to the device to control the HVAC system's functions Venstar and ecobee have wireless sensors you can read independently and possibily make zone decisions and control ducts, but it would be a "roll your own", not a manufacturer's integrated/managed zone control system...I wouldn't do it that way

I've jumped ship on other HA integration solutions in the past 24 years 3 times because it didn't work out, to arrive at UDI/ISY. None of them are perfect, changes happen. Make the choice you need to make. One of the best things UDI offer, not sure any of the competition does to anything close to... and it didn't see it listed as something you tried in your post....is submitting a ticket and getting UDI's high level support.

Perfect, thank you

I have a second-floor laundry with an exhaust fan / vent in addition to the dryer vent. I working to automate the fan operation better when the dryer is running. My questions are: Can I use the plugin to sense power consumption with the "Smart Plug With Power Monitoring" when the dryer is on and use it in iox program "Ifs"? If anyone has used it, how much space of the outlet does it consume? The washer is also powered by the same outlet, standard sized 3 prong plug, but I need it to be plugged in there and not be blocked by the Smart Plug. Maybe the vibration sensor is a better solution? I'm open to alternatives that lead to the same end.

Your best bet is serial. USB is not designed for that kind of distance. Having said that, 50' is a long serial run but I've read stories here and the homeseer forum of that working for a PLM

I'm not sure the programming effort involved to achieve this solution, but the previous incarnation of the Venstar plugin under nodelink put the runtimes in a separate "main node" (not sure of the right term), so when you clicked it in the device tree, runtimes were there, and controls & sensors were in another "main node" which navigated around this issue.

Ticket time https://www.universal-devices.com/my-tickets/

Not a MAC user, can't help there. Here's how to submit a ticket and I suggest that as your next step: https://www.universal-devices.com/my-tickets/

The big manufacturers (Google, Apple, Samsung, Amazon) that are working on creating the matter spec have it working to some degree, but smaller integrators (Homeseer, Insteon, UDI and Home Assistant) are working on their non-beta matter offering of their respective products and across the big manufacturers' product. At this time you are an early adopter of matter. There are numerous posts here on that topic

This post rang a bell to when I set my eisy up about a year ago. The problem seemed to go away after leaving the program sit for a day or 2 and the problem has never returned.

An option, if your programming is really simple, is to replace the isy with an insteon hub. While the isy is flexible and has more possibilities, the insteon hub is relatively easy use and less expensive. You insteon devices should work with it

Right click on Deck Lights and pick "Restore Device". Compare and test again An additional method is to factory reset Deck Lights, that will clear all links, and then "Restore Device".

Take a look at the solution, here

It's possible a link got lost in the shuffle. Put the the sensor in linking mode, right click on it in iox and pick restore device, restest