paulbates

Thanks @IndyMikeand @gzahar It triggers any time after the query fails. The wait and program call above are redundant and I get a second notification, I took those out The summary, what I needed to know: Come up with a program to include the query statements in the "then". It could be based on a couple times of day, or some other logic like I did Create a separate service handling programs that are not called or referred to by the first program. To your points, they trigger when the ISY doesn't hear back. The first program looks like this. My recollection is that iox doesn't pause between back-to-back Insteon commands, so the "wait". If I haven't heard from the sump pump power sensor for X hours, query both iolincs. Sump Pump 2450 Error Check - 1 - [ID 0035][Parent 0033] If $Sump_Pump_Hours_Since_Last_Run >= 5 Then Set 'Sump Pump Monitor / Sump Pump Power - Sensor' Query Wait 4 seconds Set 'Sump Pump Monitor / Sump Depth Alarm-Sensor' Query Else - No Actions - (To add one, press 'Action') These two programs service the query errors, initiated by above. They send me notifications when the query fails Sump Pump 2450 Depth Error - 2 - [ID 000D][Parent 0033] If 'Sump Pump Monitor / Sump Depth Alarm-Sensor' Responding is False Then Set 'Notifications / Service Pushover alerts' Send Sys Custom With Params Sound=Siren Retry=30 Expire=60 Content 25 Notification ID (ID=25) Else - No Actions - (To add one, press 'Action') I tested it by pulling the 2450 out of the wall and running the program. Thanks for the thoughts, Mike. I had pretty good luck with 2450s at my last house over 12 years; garage door, rain sensor and attic fan louvre control. I did look seriously at YoLink as you suggested and recently got it for temp/humid sensors. It's possible these get switched. I'm having to learn YoLink's way of thinking, and more successful with it the more I do. Definitely very impressed and looking at expanding sensors using it. It seems to be designed for DIY and not worried about MYq type changes affecting it.

I didn't have this plugin at the time, but there are other HA use cases in general that helps someone whose health brings mobility challenges. Voice control of lights and thermostat. Remotelincs for things like attic fan motors and attic louvers. Also automated lighting premise and inside for convenience and making the house look actively lived in For me, a 100% traveler at the time, it offered passive support through notifications; did the Simiplisafe alarm get turned off?, implying letting the dog out or leaving the house. Did the garage door go up at the right time to go to known appointments? I wish this one would have existed at that time as audio prompts for medications would have been great. It offers them support, with dignity

I had an idea to run a program 4 times a day, every 6 hours, .. but ideally when it should be when it appears there may be a problem. When I don't hear from the 2450 after 3 hours, I want to make sure Insteon isn't the problem. Sump Runtime 2450 Error 1 - [ID 0035][Parent 0033] If $Sump_Pump_Hours_Since_Last_Run >= 3 Then Set 'Sump Pump Monitor / Sump Pump Power - Sensor' Query Wait 5 seconds Run Program 'Sump Runtime 2450 Error 2' (If) Else - No Actions - (To add one, press 'Action') Not sure if the above program needs to call this one, not sure on the conditions for "Responding" to trigger Sump Runtime 2450 Error 2 - [ID 000D][Parent 0033] If 'Sump Pump Monitor / Sump Pump Power - Sensor' Responding is False Then Set 'Notifications / Service Pushover warnmsg' Send Sys Custom With Params Priority=Normal Sound=Pushover (default) Retry=30 Expire=60 Content 26 Notification ID (ID=26) Else - No Actions - (To add one, press 'Action') I'll let this run, and go down and unplug the 2450 tomorrow and see it works

Thanks Mike No, not worried about missing. I looked at that. I added the equivalent parts for a signalinc to my panel. The log and event viewer show it hitting every time... On and offs line up completely day after day I'm more concerned that the 2450 stops working and I won't know . The e conversation is initiated by the 2450, not the eisy The query part...I don't know / forgot what to do. What steps are needed to do that. How do I structure the program?

I have 2 2450 / iolincs monitoring my sump pump. The programs to do the reporting of the sump pump activity have been working as expected for an over a month. I'm going back and writing alert programs that verify links in the chain like: are the 2450s alive? My concern is that both 2450 are sensor only, the only communication is initiated from contact closure at the sump pump, not the eisy... so If I don't hear back, could the 2450 failed? This is not a case of a program not working, more about how to approach it. I did go back and review posts from the past, and the 994i manual. I didn't find program snippets that show the right way to do it. Here's how I approached it for one of them: The logic is, if 3 hours or more go by without on or off from the 2450, and the 2450 is not responding, send me a notification. Sump Runtime 2450 Error - [ID 0035][Parent 0033] If $Sump_Pump_Hours_Since_Last_Run >= 3 And 'Sump Pump Monitor / Sump Pump Power - Sensor' Responding is False Then Wait 5 seconds Set 'Notifications / Service Pushover warnmsg' Send Sys Custom With Params Priority=Normal Sound=Pushover (default) Retry=30 Expire=60 Content 26 Notification ID (ID=26) Else - No Actions - (To add one, press 'Action') I'm assuming the Query in the If is sending a Insteon messages to the 2450, and the 5 second wait is to let that communication work itself out. Is that how this is supposed to work? if not, suggestions are appreciated

It could be an IP issue. If I'm reading this correctly, the NS restarted which might cause the isy device to ask for new IP info, it finds the new path and goes online. How would the envisalink device know to do that? It was left on and it's previous IP path was pulled out from under it, maybe? Can you access it to see what it thinks its host configuration info is? IP, DNS, subnet mask,etc? I think this will have a lot to do with the router and how failover is managed. Have done simulated failover with this setup?

I've recently purchased and installed it on the version prior to 5.8 and it installed as it should and working. So I'm going literally by the steps you listed, I don't see that you did the install step? That would explain the outcome. Install and reboot If that's not it, I would go to the pg3x log, set for debug and look at the entries near the bottom for errors related to yolink.

There was an FreeBSD OS upgrade behind the most recent IoX update. The steps are a little different for eisy for using the power button - one click. I did it and it seemed to take a little longer

Some log info is needed to help the developer, @firstone, help you. After attempting to launch the plugin, go to the log tab of pg3 select "Debug" on the right Click download pg3x log Mention firstone here when you've done that

Edit.. Forgot about the else, I think my suggestion will also toggle back and forth I would try adding/testing to the if: And $Blizzard_warning not equal 1 I'm assuming that it stays 1 during the blizzard and doesn't toggle back and forth

Isn't that the the version of matter that comes in a box, and you make out of parts and a stick figure diagram?

Jimboautomates has an IFTTT plugin, and IFTTT supports the Nest. I haven't done this, but you could start with setting up IFTTT, connecting it to your nests and experiment, see where it leads, then try the eval period for Jimboautomates plugin.

My recollection is that User 1 - 10 supported the earliest version of node server. Since moving on to polyglot, I don't believe this feature has relevance / purpose any longer.

DIdn't versions of ISY AC/FW maybe 10 years ago have an ALL ON button? If yes and you have a "dev" ISY you could load old firmware to do your testing. I don't remember exactly, but maybe a version in this timeframs

Understood, thank you, that helps. The updates to humidity are referred to in the FAQs "At least 0.9°F (0.5°C) change over a period longer than 1 minute. At least 3.6°F (2°C) change within 1 minute. At least 5% change over a period longer than 1 minute. Device alert level reached or restored to normal range. The data will be refreshed automatically once an hour." I'm pretty sure they're referring to humidity with "%"

I've installed 2 yolink 8003 temp/humidity sensors on a hub 2. I've had the sensors sitting in their locations prior to install to understand their behavior. After looking at the FAQs, I found the refresh rules. My application is to control 2 vent fans when humidity peaks. Normally the documented behavior will be fine, but once its peaked I'll probably call for an update every 5 minutes or so it doesn't change. There's 2 commands that can be sent with ISY programs, "Update Status" and "Query". Pressing either in iox has not yielded results but that likely because there's been no change. Curious how the 2 commands are meant to work, how they are different. Any related experience from others?

My suggestion is make this a ticket and point it to this thread. It needs to get on list to be evaluated and worked.

I've performed 3 "platform" upgrades over the years and one thing helped me out: If you have a second PLM or can afford it, get one. This allows you to not try to do it "big bang". Instead set up the eisy with a new PLM, and migrate devices in groups; like rooms or things that function together. Do this a little at a time. Work at a pace that doesn't wear you out and/or heavily impact/frustrate you and the occupants. The other thing is reviewing how involved your setup is. For me, even after 4 months into a new setup in a new-to-me house, programs and variables are a biggie. How many programs, how big are they, how many variables,? Any independencies? Example of how to migrate a function or room: Start with a room with a couple of 3 way switch setups and lamps If you have programs, print them and the variable list out, or copy/paste into google docs Have everything you need in hand. I'm not big on printouts usually, but if the computer is being used with iox, flipping back and forth between iox and docs can be difficult Factory reset devices for a specific function like a 3 way. Add them into eisy Add scenes add the programs and variables test / debug delete them from the ISY Go on to the next function or room

I felt you all leering at the myq ad on the national championship game. That is all 🤪😂

I don't see 20' as a problem.

Brian, I think maybe what is going on here is the X10 powerline interfaces were RJ13 / phone connectors.. and X10 is being used here.

There's a lot of moving parts here: 1. I don't have zwave, but if I did i would eventually go with the one UDI provides / recommends. I think what types if devices you have, their age influence this decision and other zwave users can comment further 2. & 3. This is where to be careful and "divide and conquer": If the upgrade didn't work, I'd be wary of the post upgrade backup. The unknowns here included what version of FW was the pre-upgrade and can it be used in the eisy migration. Need to look at the ISY docs and curated answers Having said that, what are the implications of adding a new zwave controller to the uncertain mix of events? I'd think about moving the current zwave dongle, if it works with the pre upgrade backup and move to the new dongle later as a separate step. Again, zwave users who have migrated to eisy can provide more guidance here. Document which slots plugins are currently installed in on the pi, for the sake of your programs you'll want to install them back where they started from once on eisy What PLM do you already have, how old is it and is it working? I would defer changing PLMs and adding the XTB until you get the eisy on its feet and your existing devices working... then make those 2 changes - one at a time. Changing PLMs takes time, can/will have hiccups that have to be manually fixed. This is especially true if you have a lot of Insteon wireless devices Do you have a lot of programs? I believe you can print them out or paste them in a google doc / word as reference. I'd do that and organize them by folder / function (rooms, indoor vs outdoor lighting, etc) I think if you get organized and have a plan you can avoid an entire rebuild, but be prepared for unexpected things that take longer and try to do it at a minimally disruptive time

I submitted a UDI ticket about this topic. I got a response from Chris that they have the specs and should be able to implement this. They will add support in the future.

I guess it's time to write the chuchaqui program, eh? 🤪😂 Happy new year to you

If you select on the device, right click and pick "restore device". That should do it. For really stubborn devices, follow the devices factory reset steps first before restoring