paulbates

A couple of things The root cause it probably Insteon communications itself and its probably best to address that. There's a number of posts on Insteon Communications issues to search under the Insteon communications section of the forums Consider putting these devices in a single scene, and turn that scene on and off Set 'Outside / Malibu-Garage' On Set 'Outside / Malibu-NE Corner' On Set 'Outside / Outdoor Fountain Light' On Set '.Scenes / Malibu Lights' On For the queries and individual devices in the iox programs... put a 3 second wait between each command. Insteon device commands take time to receive and acknowledge and iox doesn't wait. Those sequence of set commands is banging into each other on the Insteon network Set 'Outside / Malibu-Garage' Query wait 3 seconds Set 'Outside / Malibu-NE Corner' Query wait 3 seconds Set 'Outside / Outdoor Fountain Light' Query Tweak the 'retries' on the problem devices. Right click on the device in iox, and pick advanced/PLM communication. Increase the retries. I makes the Wait after that device even longer. This approach is generally frowned upon, but I had a few at my last house where it ultimately worked ok. I would not recommend going beyond 3 retries

So a 2 part answer. How it's done: UDI created the polyglot pg3x environment for creating plugins that provide functionality and equally share access to the polisy / eisy controller. IMO you'll want to be a more advanced developer and plan on a learning curve and time to get there. Why it's done / how individual plugins are decided: UDI's success depends on community developers to create and sell their plugins. Typically developers are advanced and have the need to integrate the specific product(s) in question. They'll create it, usually, because they needed it and doing it as a plugin helps others. If you have a product like the Ultralogs, want a plugin and not a developer, you start by expressing interest - like you just did. Sometimes developers might take it on if a version of the product is shipped to them for development.

My daughter, not an home automation enthusiast, lives in an apartment where there's no over head light or wall switch. She wants to have either bulbs or lamp modules and a remote control switch by the door (as opposed to a 120v switch). She won't have an home automation controller but does have google home which would be ok for her to use for this application. I sent her the links for the Insteon lamp module and mini remote because that's what I know. Works great but not the cheapest. Recommendations for lower cost versions of products you've used that fit those requirements?

When you add a device to a scene, it presents the controller/responder choice there. If you look at devices in a scene in iox, the red ones are controllers. I'd delete the devices in the scene and add them back in one at a time to make sure they are correct. Another thing to kno for Alexa, (or any automation) you need to make sure it's the scene you've added, not the device. Turning the switch itself on and off will yield the results you're seeing

Two suggestions: When using the scenes and devices are not turning back off, either remove the load (unscrew bulb,etc) or pull the bottom tab out on the switch. Keep repeating until everything else functions. Either the load is the culprit or, see 2. Sometimes insteon devices that have run in place for many years need to have their data refreshed. If there are switches that are more likely the culprit to the problem, factory reset them and then right click in iox and restore device. In my experience it's been these devices in this order: keypadlincs, togglincs, any device that's the most remote from the eisy in terms of wire feet. Unrelated info, I grew up in Woodlawn, just south of you!

In addition to @tazman's suggestion, did you migrate your original PLM or buy a new one? If migrated, about how old is it. What are the 4 numbers on the white sticker on the back?

I think we're speculating on something we can't knowt yet. I can't imagine UDI designing a solution that cuts off functioning customers, too many still on 994i. They don't support it, but different than cutting it off at this time. Since they've mentioned creating a replacement for AC/Iox only, the core ISY product in eisy will probably not change much.. and the web interface will be a module running on polisy/eisy, web on one side and interface to v5 of ISY on the other to maintain its local only capability. But that's my speculation. At this point UDI wants us to know that they're actively working on it. And, for January, they're saying they've started laying the groundwork, not to expect web iox then. It was matter and other features to be released in January.

The notification plugin is recommended with 2 ways to go based on how complex your notification needs are: You can start with the free versions and have notifications come through UD Mobile. The UD Mobile template is the first on the list and handles simple messages... simply. If that doesn't fit your need, you can upgrade to the pay for version of the notification plugin and send notifications through notification plugins through the pushover app. You'll have to touch up all of your notification programs, shouldn't be too bad and you can likely use your existing notifications with variable substitution You'll want to read through the notification section of the forums to see some examples

I'd suggest opening a ticket with udi about options. This subject matter is their wheelhouse.

Another thing to consider, after reading between the lines, is that upgrading Freed BSD on our own will not bring eisy capabilities like HomeKit. UDI will release comprehensive updates of their software that requires the underlying OS to be upgraded. It will be an integrated package that only they can provide

As an appliance that info is not available on the surface of the eisy. I believe you'd need to use an SSH client to log in and use FreeBSD command line to see what it is. Pretty sure everyone but developers would be on the same version as eisy is an appliance, and in general it's not important for us to know unless wanting more capability that someone with developer skills would need. I think I read its 12.something but don't remember and never looked. I'm counting on the UDI team to come out with instructions or a link or something for us to follow sometime this month.

It's the version of OS that all of the UDI Eisy software runs on, and it doesn't get upgraded frequently. Its usually upgraded around new capabilities to be launched. IMO that's one of advantages of the Eisy vs other server based Home Automation systems is that it's not an owner responsibility to regularly keep it running and the system software upgraded. The eisy is more of an appliance and I came from server based home automation to UDI. I've not had to worry about random reboots or restarting it because it crashed. The reason you don't see instructions is that they haven't been provided yet. What you read was an announcement of what's to come. The other factor is UDI releases things when they deem them ready and not before.

Funny you mention that. I first noticed around 1:30ET when wanting to shut off downstairs lights after the guests left. I worked for IBM services at the time. What Y2K did was provide an incredible revenue stream for consulting. Ironically it was mostly IBM's fault for creating the system clock that they did in in the original PC... just 2 more bytes of rom and it wouldn't have happened.

I can say this having retired from a career in IT: It always picks a whopper of a time to fall down and break. Happy New Year, Benoit and UDI team!

There are different approaches, do any of these sound close? I use the paid for notifications plugin to write notifications to the pushover notification app. The notifications are from iox programs based on certain events or sensor limits. The pushover interface lets me filter down to what I'm looking for which has allowed me to learn what I need. It also allows export to a excel compatible csv file. It's important to have the end in mind when naming the notifications and arranging the data points so you can easily pull out what you want with the app. Another approach: It has been very helpful for tuning my iox programs to use yolink brand sensors and the plugin. The yolink app has graphs and data points built in so it's not been necessary to do the hard work of writing iox programs to capture data points and make graphs. I can just look at the graphs in the app. For temperature, I use the 8003 temp/humidity sensor which could be installed in a plenum or at a register. It can be used up to ~120 F so in range for home heating applications. Not sure what voltage you're looking for, but I use a yolink smartplug to monitor my dryer's on off. The dryer is plugged into it. I tuned it to the extremes of it running or not running, but the yolink plugin will return discrete runtime power consumption values that would be in their app. I've seen posts in the forum where there was a way to use network resources to write to a google sheet. I experimented with it but found it hard for me to do for the results I wanted.

There is an older post here on this device. Looks like there are hints to what you're looking for

This is from yolink docs: The sensor updates the app each hour, minimum, but also updates if any of the following occur: - At least 0.9 F degree change over a period longer than 1 minute - At least 3.6 F degree change within 1 minute - At least 5% humidity changes over a period longer than 1 minute I use a number of the 8003s and it took me a while to figure this out. I've seen it as fast as 10 minutes, but also as long many hours. This is most likely to extend battery life, which is impressive. A way to see for yourself is to open one of the sensors in the yolink app, and touch and slide along the graph lines. As you swipe, the different update datapoints, with their update time, will show up. You can also click on the history icon to see it in a table.

log in to your Ecobee account on the website, navigate to the "Home IQ" section, then select "System Monitor" where you can choose a date range and download your data as a CSV file; this will provide you with a detailed record of your temperature and humidity readings from your thermostat.

Correct it's on it's way to dieing. I think it was mentioned above. It will fade away in and out until it dies for good. Now is your chance to replace it in your terms

For creating notifications after you get each phone configured, you'll create one one program for each person: if geofence1 is true then Set 'Notification / UDM' Send message content X Notification ID (ID=X) else Set 'Notification / UDM' Send message content X Notification ID (ID=X) Let's assume you have no notifications defined today. In the case X=1 for you in geo fency, X=2 for you being out of geofence. X=3 for your wife in geo fency, X=4 for her being out of geofence. But X should be what the custom notification # in. You create those custom messages under the iox configuration tab - Emails/Notifications/Customizations

I've had an ecobee for year. I came from Venstar Colortouchs that had tons of settings and adjustments you can make. I also had a lot of iox programming to keep things adjusted. The ecobee is the opposite of that... it takes care of just about everything on its own. You'll want to get used to letting it do its thing and also looking at the app for settings and features. For the occupied sensors, they change to occupied immediately when something crosses their path. I use the remote sensor on our master bedroom to turn off the suite lights when not occupied.. its exactly 30 minutes to the second after the last motion sensed The eco+ is an install time decision, or later with the app. You can look in the app, or here The value I get from the plugin is some notifications for reporting, turning lights off when leaving an area also to activate the HVAC fan to follow up outdoor vent fan automation for our master bath and upstairs laundry. Edit: What causes the ecobee to go into these Eco+ states? Mine normally uses 0, 6 and 7 not 1. EN_ECOHCS-0 = Idle EN_ECOHCS-1 = Heat EN_ECOHCS-6 = AuxHeat EN_ECOHCS-7 = AuxHeat2 EN_ECOHCS-8 = AuxHeat3 I'm not sure this is right. Do you have a heat pump? Can indicate which wires from your system go to which wiring spot on the ecobee?

Why to be sure I understand: if any one of the three leaves or comes home, all three people should get a notification?

It's true of most forums; do a Google search and add udi isy.

Give this post a read:

If you have programs it will help if you paste the text of them here