paulbates

The journey that got you to this point is not clear. What steps did you take to get to that point?

First, do you have Lutron's serial command spec, is publicly available, not proprietary? If yes, it will require some digging, but it's plausible. There are products that can accept REST calls and communicate serially. eISY Network Resources can generate REST calls: iox program statement > Network Resource > Your network > Network/Serial controller > Homeworks. Here are some Network/Serial controllers to look at: Lantronix XPort or UDS: These are industrial serial-to-Ethernet device servers that allow serial devices to connect to a network and be controlled via IP. Lantronix also offers some models with built-in web interfaces. USR-TCP232: A series of low-cost serial-to-Ethernet converters, with REST API support. Moxa NPort: A widely-used serial-to-Ethernet gateway with various models that support different protocols, including HTTP/REST API for controlling serial devices over the network. Raspberry Pi. Petty sure it has a serial UART on it. There'll be tons of examples to search for but you're likely looking a python coding to receive the eisy's Network Resource call and turn it into RS232 commands Also, figuring out the RS-232 pin out will be required for any solution. It's going to be a bit of technical exercise

Has any one tried with this with insteon i3 paddles? I only have those as switches which have not flickered, but 2 micro dimmer modules in scenes with the i3s that occasionally do. It's not all the time but I can recreate it sometimes getting the modules to flicker when generating insteon traffic. It usually takes actions that are not normal, eg turning the same switch on/off several times back to back. It's all the same brand/model of recessed led lights. They're all older, ~5 years old. If the comment level gets high enough, I'll try swapping the problem locations with newer recessed leds. I believe the i3s are triacs too which probably makes this a long shot, but alternatives to the are being discussed here.

The hub question should be posted here To @Guy Lavoie's point, Amazon echo is supported through the UDI portal, not the 994 specifically. Even though the 994 is at end of life, Amazon echo through the portal should work

I use http://<ISY local ip address>:3000 ( not https: ) as the pg3x server is located there. It will give security warnings but I move through them as it's a local only connection. Try that in a browser window. I don't know why iox sent you where it did.

Not sure exactly what you're looking to do. You can right click on the scene name and see the options. You can also "click and drag" devices in to scenes as well as scene members.

Can you post the scene in question?

The portal can support multiple devices. Add the eisy and maintain both as long as you need to.

I've had Samsung and LG tvs.. I think you have to enable something on the tv to allow it to use local network discovery, something in the tv's menu

Take this as something to try. I've been giving ChatGPT more of a chance on technical solutions. It took a couple of iterations, but I asked it specifically about LG TVs and ISY network resources. Here's what it said. Based on my use of network resources, it looks close to try easily: Name: Turn Off LG TV Protocol: HTTP URL: http://192.168.x.x:3000/ir/remote_control Method: POST Body: {"type":"KEY_POWER"} I'll be curious how close it got. I think LG TVs are toggle, meaning the "off" command will also be the "on" command. This was the whole answer where it was close:

Yes, that's discussed in the posts.

Take a look at these threads where the plugin author explains what's going on and is working on fixes that are available in the beta as things get resolved. Have you tried the beta version described there?

Try picking a device that's not working and perform a restore device, retest

It's hard to know as @Techman points out. When you launch iox from the launcher, do you pick the "Cloud" option from the finder? This would refresh iox itself if something happened to it due to adding dev packages. If that doesn't work, do the "generic" clear cache, reinstall java and iox.

Do you think the iox console was popping up on that second monitor all along. Not 100% sure from the posts if freezing means you could see it, but it wouldn't respond... or you never saw it.

How old is the plm? Insteon devices, especially the plm can be affected, damaged by power blips and age doesn't help. There's a sticker on the back with 4 digits, what are those digits?

6 nines? That's ~30 seconds of total downtime a YEAR on a product that costs $24. The reality is we don't experience that much downtime, most of it planned and announced. Let's let the team fix and they'll let us know.

Around 7am et my Alexa said she couldn't reach the hub, something like that. UDM said it couldn't connect. Rebooted eisy. I think that's a first for me, having to reboot my ISY to get it to respond. But everything else appeared to be working locally Everything works now

This sounds pretty specific yet unusual. I would open a ticket with a link to this post

I left mine in the house I sold in 2023. That was after a number of years of nothing new added or changed, it just worked.

When you're in iox, look at insteon devices that are out in the open where you can visibly see the LED and review them. Depending on which insteon product or revision of it you have, There could either be button on the buttons on the bottom of iox, or .. There's be an options button, look under there The label for what you're looking for can vary, it can say: LED on TX - which can mean only when the device transmitts Error Blink Blink on Traffic You might have to look around and experiment to see what results you get.

We're guessing a little based on what you said. If you log into the ISY Portal, and access Connectivity / Amazon Echo, you'll get a list of things to control with their spoken. Are the things in question listed as "device" or "scene"? If they are on the list as devices, it's one explanation for the results you're getting; delete and recreate with the scene that controls the lights

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.

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