paulbates

It's really wierd, the forum blocks me if I paste all or part of the log entries from the elk plugin... Look at the top 20 or so lines, warnings about pyisy Since you posted this under the plugin, the author will see it, but sometimes they're traveling and it takes a few days.

The ISY report looks clean to me. The only thing that looked out of place in the elk log is the most recent 17 entries (I tried to paste them in here and the forum threw a block at me) Which looks like it happened as the last thing before you pulled the log. The plugin author will need to take a look.

What would be more helpful would be a view of the ISY's log when it does/doesn't happen, or the event viewer. However, since it's a dry contact output it should never change from what you set it to. Inputs will do that

Arrows mean the isy identifies it as a dry contact device. This arrow means it's a contact device that controls something... turning it on from iox will trigger the contact. You'll see that on/off status by clicking one of them and looking at the iox panel for it.

I would contact them directly and see how close the new PLM is to release. You want to replace a PLM on your terms, not when it fails... You'll have to order and wait for a new one when it does fail. I'd also take a back up of your working system now if you haven't in a while. As the PLM fails, a back up of it will back up potentially corrupted link table that gets pushed to the replacement PLM.

There's a small white sticker with a 4 digit number on the back that gives the 2 digit week and year of manufacturing. Post that number back here. A PLM of that age is on the suspect list, especially if there were recent brown/black outs or nearby lightening strikes. They have a design. During Insteon's marketing call earlier this year it was stated that there would be a new PLM with +1,000 link capability this summer, which were running out of. I asked if it would also support i3 protocol but didn't get a direct answer. No idea on it's package size. They did do a component spec upgrade a few years ago to replace the "crapacitors" that usually caused PLM failures. I haven't seen a lot of posts of more recent PLMs failing.

Some questions: How close is the sensor to the PLM when linking? Have you tried linking mode? Go to iox under linking and click start linking. Then put the sensor in linking mode. If the sensor shows up on the list, complete linking How old is you PLM? If you're not sure, there's a white sticker with 4 black digits on it, what are they. The fact that you're having problems linking and the scene problem hints at something going on there

Nope... if you have a recent good one that's fine. I backup like you do.. pretty much any program/config change gets backed up. The PLM gets backed up with the ISY backup. The reason its good to have a recent backup is that the PLM links info can get corrupted as it dies.. and a back up after it dies can backup bad data and then push that to the new PLM.... You will be fine with your backups

15 years with a plm might be a new record... 2 things... Take a backup.. now It's better to replace a failing plm on your terms timewise, than it die on you. Link tables can get corrupted as it fails more. It takes a few days to get shipped after ordering...more if it's backordered

Phillips warm glows have been recommended by Insteon on one of their announcement / marketing calls last year.

I worked my way into formatting NRs using the chrome browser with a plugin called postman. I could send different formats and it showed me the response, helped with put vs get and URL encoding, etc. This helped me with vestar thermostats and rainmachine sprinkler controller. It may not be around any more, but you can google for HTTP plugins for browsers or look in your browser's plugin store. You probably know this but he limitation to NRs is that they are one way from the eisy to the device. I initially did some python programming on an rpi to change ISY state variables. Or look for a plugin author to help As mentioned above I would contact the vendor or their forum if they have one about getting it to work with integration

I have to guess that's what the eisy is running into. Though that security/authentication needs to be figured out, a quick test would be an ISY program that sends the NR, a 2 second wait, and then send again... Just like the browser It might take going to the devices vendor or forum to ask what the initial problem is. I could imagine a couple things

To partially eliminate (or prove) eisy as the culprit, did your initial link work in a browser tab? What happens when you try?

Can you start by posting an image of how you've tried? A link to the API documentation for httpapi.asp is needed as well

Here is the "On" program If Time is Sunset Or Time is 6:00:00PM Then Set 'Lighting Premise / Premise Lights' On Else - No Actions - (To add one, press 'Action') Here is the off program, I use something simila If Time is 9:50:00PM Then Wait 13 minutes (Random) Set 'Lighting Premise / Premise Lights' Off Else - No Actions - (To add one, press 'Action') This one will start running at 9:50pm, and wait a random amount of time for up to 13 minutes and then shut the lights off. You can tweak that however you want. If you're interested, I can dig out the link to a post where I put lamp post light sensor in a project box with an insteon on/off micro module. It's Velcro'd inside on a window facing out and "switches on" around dusk.. this solves the problem of it being cloudy and dark sooner than dusk.

Currently I have just a drip system that I turn the power on and off to the 24vac power supply with an insteon i3 outlet. I have iox programs that take weather data provided by my ecobee thermostat, via its pg3x plugin, to skip waterings based on forecasted rain. I used to have rainmachine at my last house... but it looks like they are not going to make it as a business. Rachio is good choice... while it will operate schedules without the cloud, *it does have cloud dependencies for integration with ha like eisy*. There is a pg3x plugin for it in the store If I choose to install a sprinkler system here, I would go that direction. Scott's bought rachio which gives some confidence. Edit: I'd consider looking for a used rainmachine as its schedule programming and installation are 100% local, and there is a pg3x plugin for it.

The pg3x log specifically under the yolink plugin. Set it do debug level

"Cloud dependent" is probably the way to say it. Rainmachine and Venstar are examples of technologies that can be programmed and used on local APIs without their cloud capabilities that are nice to haves, but not essentials. (Both companies are still around)

The transfer of ISY modules happens at the UDI side, IIRC. Though the 994i is out of support, you could try opening a ticket with UDI. The caveat is, I believe, that even if they will do that, the module is associated with one ISY's UUID.... meaning it cannot be in 2 places at the same time.

The easiest and most straight forward would be to have an iox program, or 2, to "backstop" the button presses. In the 2 program model, there would be one program each to catch the switched on and switched off. The one program version would use the else with if switched on and not switched off at the start. Its a nuanced choice of which you like best. The downside of this approach is a short, several second delay between press and activity due to the serial line speed into and out of the PLM

@larryllix agreed, but they both independently (I believe) affect the ecobees temp behavior and could be what's going on. I would expect Vacation to win between product set features, but not sure. It looks like there was an iox program nudging it out of vacation mode, which would explain it.

It sounds like no, but do you have any programs that touch the ecobee? Based on what's written, these features of the plugin would affect that behavior. How are they set?

Both eisy-ui and HomeKit support are in ongoing development & testing. If you search the main forums page you can find each of those. eisy-ui is in early stages and beta, so many things are not supported yet.

They put dot in the middle of the 0 sometimes. That has caught me up before...

Correct... If the new switch happened to have links in it from the factory (it happens sometimes) that method deletes them. Then, the replace function puts links in the new switch and updates all the other switches with links to the new replacement switch