paulbates

There is a manual for it, with a 2019 date on it. Guessing this is what they're planning to releasa. It is the same physical package as the newer lamp module. Comments in the manual about the improvements: Expanded operation to 100-240VAC and 50/60Hz. Increased Insteon links storage from ~1000 to ~4,000 links with faster read/writes Uses the same communication protocol and structure to match earlier models Updated all processors with increased memory space and speed Beefed up electronics to reduce failures due to AC-mains electrical spikes, noise and heat from poorly ventilated install locations New and smaller enclosure that matches other Insteon plug-in products Increased powerline transmitting signaling levels and robustness New RF circuit with higher sensitivity components and calibrated antenna circuit Changed USB translator circuit from FDTI to Microchip with built-in Windows support and hassle-free use with Mac OSs 2234222.pdf

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