paulbates

I have an eisy, a portal account and a <1 year old Samsung smart tv. I also have an ecobee t stat that can serve as an Alexa. I have some basic things I want to do, looking for comments from those who have integrated a Samsung tv, Alex and the portal. Trying to keep it as simple as possible. What I want to do: Turn the tv on and off, navigate hdmi inputs I believe this all Alexa and Samsung; the portal and iox programming not required(?) I'd really like to avoid smart things, but doubt I'll get away with that. Is smart things necessary or can Alexa discover the tv on its own? For eisy and portal, I'd like to do the old school theater effects; dim room lights and lamps and bring them up based on on/off spokens to alexa Can Alexa routines be written that detect spokens from Alexa->samsung for on/off and update a variable, run a. Program, etc? My recollection of doing this a few years ago was the other way around.. having an ISY program command something on the Alexa side. If someone's done this and can comment I'd appreciate their experience before wandering through this.

Is the same devices though, or a a number of them in multiple scenes and the ones that don't fire?

I had a V572 in my last house and had coax from the attic antenna to the basement equipment shelf. It did work pretty well to catch the Hawkeye/eagleeye triggering (whichever MS was for outdoors)

One way is to go to each device, factory reset it, and then "restore device" from the admin console, one at a time. I know that can be difficult for some devices, but do the ones you can If I was uncertain as to the devices' link table content, I would do that. (I still have some original lamplics in use for indoor Christmas lights)

Do you have a portal account? If yes, my suggestion is to try the UDM app and see what you think. I still use the console a lot, but I'm implementing a lot too *** having said that, not sure if the portal supports the 99i

I forgot to mention that I use the UDM app also for the basic things I need like adding new insteon devices and basic edits. It works well on the iPad

I do most of my admin console work on an iPad Air Gen 5. I use the secure real vnc app as a remote console, about $3.50 / month

Thanks, I just purchased and installed it

This gave me "flashbacks" to isy_data 🤪😂 Thanks!

That's a good suggestion. When I looked in the store, and went to get hub to see an image of what iox would present, it was sunrise and sunset data only. Sounds like you're saying it also presents month / day info like io_guy's ISY_Data node server used to?

I have programs that report out daily data for a sensor. They calculate and give monthly highs and lows. What I need to do is reset the monthly value variables at the end of the first day of the month. It's been a while since I've done this. I found a post that reminded me that I used io_guy's ISY data plugin at my last house.. but I now don't have/want a pi to run nodelink. From what I can see, I'll have to create program that runs at the start of the day and assign day of the month to a variable from system data If time = 12:00:01am then day_of_month = system data / day of month from the drop down I'll have a second program do what I want If time = 11:59:50pm and day_of_month = 1 then (Reset the variables) Is there a way to do it directly with an if in one program, I feel like I'm forgetting something?

The technology provided by UDI, the company this forum represents, can do those things. There is an ecobee plugin for the eisy controller. It provides numerous data points and programmable controls for the ecobee family of thermostats. I use simple point and click ISY programs to automate it. I have it and have 3 important ecobee integrations for my home programmed with it, so my point is you might want to consider something like the UDI eisy controller and spend more time automating and less time integrating.

+1 I'm a recent yolink convert as well, two 8003 temp humid sensors controlling indoor vent fans For isy programs I had to adjust to their way of thinking in terms of how often they update, but they work consistently once I did. I'm planning my next project for smoke/CO sensors backed with virtualarm monitoring.

Yes.. it's how Insteon is designed.. the ISY programs the links into the switches, then the switches talk to each other and the ISY's role is passive.

That's done through the scene and it has to be edited.. I don't know of another way

In addition to providing Insteon programming, the ISY manages Insteon configuration including scene management If you haven't removed the old switch, open the scene you are talking about under Main in the admin console. Right-click on the old switches entry in the scene and pick delete. (There will probably be an error due to the old switch not responding, just move through the errors) You can then right click on the old switch in the ISY and pick delete Install and add the new switch to the ISY Under main, click on the switch and drag it to the scene name and drop it. Make sure to click "controller" in the window that appears and then complete That should do it.

So do the following: Box 1 Upper right black/white wire pair. White to white bundle Black to Insteon switches red lead, cap together Upper middle red - cap off separately black to black bundle White to white bundle Insteon switch Red to upper right black as noted above Black to black bundle White to white bundle Turn on breaker and test... do the lights come on? If yes, add the switch to ISY Configure as dimmer if its an i3 and you want a dimmer Box 2 Cap red from box separately on its own cap red from Insteon switch separately on its own Black to Insteon switch black White to Insteon switch white turn on breaker, does switch show it has power, leds light up? If yes add switch to isy make it a dimmer if i3 and needed create a scene and put both switches in, setting them each as controller Test everything from both sides Push wires in, mount switch, etc,

Insteon makes a noise filter that the UPS could be plugged into so you can keep everything there. It is bulky like PLM so maybe a short extension cable too... or I use a one outlet to three outlets horizontal adapters to fit my PLM in with lamp module

If it happens again, I would unplug the UPS temporarily, and unplug/replug the PLM... and wait to see if it reoccurs. UPS's can be a powerline noise problem and affect Insteon devices.

Seems odd that a 6 month old PLM would need this. Have there been any eletrical system anomalies; brown outs, low voltage, etc? Is the PLM plugged in electrically near something like a washer/dryer, window air conditioner etc.. something that uses a lot of power?

It appears that light fixture is coming into the first picture, down on the top right with the black and white wire. The left box is the j box that inteon switch controlling the load with its red wire will go.. red on the switch connecting to the black on the upper right. But.... I'm confused too, why black is connected to white on left wire nut. You're sure about that? The Insteon switch in the other box will not be happy, and likely not under warranty, if the black and white are backwards.

Before giving the PLM an "all clear", how old is it. To complete your list of things, I would unplug it, wait 10 seconds and replug in, re-run your tests.

I asked recently on the Insteon Forum, and "Insteon John" provided the schematic for the signalinc with the parts listed. I made my own. Follow this link to the Insteon forum, and scroll down to the bottom, I provide the parts list from mouser.com there. It's 2 very small parts that can go in a single gang work box on the side of the panel. An electrician can do it if you don't want to. If you have one meter then I'm guessing only 2 legs feed the house and only need to add one of these. You could try with one and see what happens. But if you choose to try, buy 2 sets of parts... the shipping is more than the parts.

From a recent discussion with yolink support about local API: " 2. We understand the importance of local API capabilities, and I'm pleased to inform you that a Local API is expected to be released by the end of this year. Waiting for the local API could indeed be a beneficial decision for your application, providing a more streamlined and responsive solution.'

No, sorry I may have said it to wrong. I was in support of your comment, and agreeing that they respond to their user base... we're all good. 👍👍