paulbates

I recall others doing this in the past. It's not particularly pretty, but can be done... assuming the rest api has not been deprecated. You could push device states and variables back and forth with Network Resources with substitution {,,}. If the shop will not be changing frequently from a device perspective, it might be worth it. Pass variables back and forth for a few devices/functions you want to control or monitor from the main building. https://wiki.universal-devices.com/ISY_Developers:API:REST_Interface Scroll down a bit to devices and variables. I've done the variable setting from my own python programs, it does work well. Here's a related how to for zwave

One option: Is there a keypad nearby with an extra key? Pressing it could change another variable for the "business" at that time and override for x minutes Another option: is "business" at known time windows? Program exceptions for those times

I monitor 2 of 27 Insteon devices, 2450 io modules that monitor my sump pump. This post has examples of how to program it It only runs when I don't hear from one monitoring the motor running after 5 hours, so it rarely runs. Trying to do this for 25 devices will involve 26 - 50 programs, depending how you initiate the query, and will create significant Insteon traffic with messages going out and coming back to 25 devices that could collide with each other Maybe program the critical one like the fridge, scheduled to run a couple times a day(?)

The conversation will be initiated by the eisy and / or UDM app locally, outbound initiated to the portal. NAT firewall rules allow outbound and related inbound traffic, so there shouldn't be an issue. Between enhanced DNSSEC services and Trend Micro, I have network protection too and have not had UDI services blocked for the NAT firewall rule reasoning above. FWIW my router shows eisy keeping an IPV6 address open as well which I assume portal

I've never tried it, but iox has a programming step under Then statements Select System, pick Restart iox from the drop down This is addressing the symptoms but not the problem.. Its probably best to try and find what's happening when things go wrong Look at the iox and plugin logs / error logs after the event occurs Find out the unix command to track memory and process use... ssh in and observe the change in resource use over time. I've not done this with eisy / BSD, but with rpi/raspbian, I don't know these exact steps but someone here will

It was me, not UDI. I was writing a program that resulted in a tight loop with many UDM push notifications. My bad and apologies to UDI and this community Paul

I think there were migration options in the fall. I think your best bet now is to submit a ticket, explain what you have already here and ask what if anything can be done The ticket system is their way of managing work queue https://www.universal-devices.com/my-tickets/

You're welcome. Even in today's world, 1 second sounds skinny to me... lots of links in the chain / moving parts from the weather service, email, and the ISY itself. Time and use may prove this out either way.

The reason it's happening is that you want to know if either is triggering, and they both are at slightly different times. Assuming they're both triggering within 5 minutes of each other, I would do it with a timer and a second program Program freeze warning 1 If Your first weather condition Or Your second weather conditon Then Run program freeze warning 2 else Program freeze warning 2 (no if) Then wait 5 minutes Send notification 'xxx' Resource 'Freeze warning message' else When the second conditions triggers, the second program will restart because it's waiting, and you'll get only one message. Start with 5 minutes and then try reducing the wait time so there's not as much wait, but the program continues to run only once

No, by hub I mean yolink... yolink has a hub you have to use to integrate the sensors Yolink sensors -> Yolink hub -> ISY Yolink Plugin -> ISY You want the yolink hub to have good wifi and be close to your wifi router so it has good communication. The sensors can be further away. I had to send notifications, the cycle could be a very long time if the temp doesn't change, like 40mins to an hour? I haven't found a way with the plugin to access this, but that app does show last update in minutes. An ISY program could be written to track this

Hi, welcome Yes, navigating the forum can be a handful, because the ISY can do a lot. You've posted in the right location in this yolink subforum On to YoLink. I am a recent adopter too, specifically the 8003 basic temp and humidity sensors. The yolink app is an integral part of getting updates timely. I can provide bullets that I think will help: Wi-Fi and yolink radios: Yolink needs good wifi from the yolink controller to the ISY. IMO, its much more important to place the yolink hub in location that lets it get good wifi signal than worry about sensor location Yonlink sensors use a special long range radios to communicate with the hub, not wifi Long range is a relative term, but I suggest setting up as I outlined above Yolink temp/humid sensor update timing The 8003 sensors by default have a long cycle to save battery. You can affect this, using the app Find the sensor in the app, select it Click on the 3 dots on the upper right next to the sensor name pick alerts Set the temp/humidity slide controls to define normal expected temp Once the sensor crosses from normal to alert, it will update more frequently You can also set your own Alert interval at the bottom In the FAQs it discusses this a little more What I did: I have a enclosed 2nd floor laundry room, and a second floor master bath that I want to control humidity venting for Installed an Insteon i3 paddles to control the fans in each location Installed an 8003 near the switches in each location Used the yolink app history graph for each location after laundry and showers Picked alert ranges for each. Temp and humidity have lives of there own, and for the laundry room, temp was a better indicator Wrote really basic ISY programs for each that looks for => alert level I'll probably have to revisit based on seasonal relative humidity. For now, it works as desired Master Bath Fan Control - [ID 003A][Parent 0006] If 'HVAC / Master Bath Temp Humidity Sen' Current Rel Humidity (%) >= 44.0% Then Set 'HVAC / Master Bath Fan' On Else Set 'HVAC / Master Bath Fan' Off

It's a feature that was more important in the early ISY product days. The ISY has a web server in it and can serve up web pages, including web pages to control ISY devices and programs. HTML role has options for how much of that control you want to give a web user of your ISY. I don't believe it has relevance in the era of plugins and mobile apps. It does not affect the Admin Console. FWIW I leave mine on advanced on the outside chance something happens and I have no other way to reach my ISY. From the ISY 26/99 wiki: HTML Role: Read Only - Allows Program status to be read. Basic - Allows Programs to be Run (If), Run Then, Run Else, and Stopped. Advanced - Allows the user to Enable/Disable Programs. Admin - Allows the user to Enable/Disable Run at Startup for Programs.

No. It's not designed to run continuously.

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

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.

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?

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