paulbates

Pick one switch that's not working, right-click on it and select "Restore Device". Does that switch work after doing that?

Good point and it's gotten worse... Went through this recently with the center octet of the insteon address was 8B.. those 2 are very close looking and I had to really put my face in it to see where I got it wrong

Thanks Like any technical solution, I have to adjust to their way of doing things and support model. I followed the directions for getting on discord so I could follow along, but that didn't happen. I was told to contact their tech support when I needed help. It's great, they answer quickly. But in asking local api questions relative to hub 3.. I didn't get an answer other than that capability is targeted for sometime this year.

The below thread covers this topic. The USB PLM will generally be preferrable if you are starting over with a new PLM and it's less than 15 feet from your eisy Its much less work to migrate the existing one, if its working

Link management, "Start Linking" at the top. Press set button. If/when it shows up on the list, finish linking

I'm with you in that I decided a few months ago to go with the current hub. I'm not interested in the battery or network backup... also the TTS capability of the current hub does not exist on the new one. Its for a specific market I'm sure yolink has. There were those here interested in it so I thought I would post for them. But now @dwengrovitz pointed out that the store content hasn't changed to available even though the email went out. I'm having a little regret over having posted this....

I added myself to the email alert for product availability, and got this earlier today. Maybe the notification email beat the content update on their store

Some questions, to try in this order: Does it behave as a switch other than not connecting? Backlight and keys light up, beeps appropriately when pressed? Controls the intended load locally, if it has one? There are 2 ways to link, 1 is typing in the switches Insteon address, the other it pressing the set button and letting the PLM discover it... did you try both of those? Do you have a way to try it somewhere else than intended location to eliminate problems there? I've used a utility plug from the hardware store with screw terminals. Screw hot and neutral carefully to that, cap the other leads and plug it in somewhere convenient to physically support it, also where a plug in module also works so you know Insteon traffic makes it there.

Ordering a new one is best. The short recovery from a reset/restore is Insteon end-of-life behavior in my experience.

Yolink has released the Hub 3 in their store. The new features include battery backup and cellular network backup, which is what they stated to me in a message a couple months ago. At that time they commented that it would also have an ET network port... the product description on the site is pretty bare right now.

O Ok thanks

Similar issue. My programs are all running ok. I have a notification that says when my optical dusk sensor turns on my premise lights and it compares it to eISY's published sunset time... sunset time is off one hour ahead... should have been ~7:30 but says ~8:30

X10 is a core feature of the eisy.. There isn't a pg3x for it as it shouldn't; be needed. Given the difficulties with this upgrade, I suggest submitting a ticket

Too much "on time" or bad links could explain some of this. Just to clarify, the UDM app gets different results than the iox console and programs? There's limited things that can be done: You might have done this, but pull the air gap out, count to 10 and push back in to restart it If that doesn't do it, factory resetting the kpl and restore device which will replace the links table. I don't have any KPLs at this house but had them for a long time at my prior house and either air-gapping or occasionally factory resetting and restoring helped.

I have a program that resets values for reporting at the end of month day 1, so I can evaluate highs and lows in future days. The last few lines curiously don't seem to work. However, after 2 months of testing, its clear the last few lines aren't executing. I'm thinking its taking longer than the 5 seconds I gave it, the day value changes and program dies before completing: Assumption: that the variable assignments and inits don't take very long. Sump Pump Monthly Values Reset PM - [ID 0047][Parent 001A] If 'TimeData' Day of Month is 1 days And Time is 11:59:55PM Then $Sump_Pump_Maximum_daily_Gallons = $Sump_Pump_Gallons_Daily $Sump_Pump_Maximum_daily_Gallons Init To $Sump_Pump_Maximum_daily_Gallons $Sump_Pump_Minimum_daily_gallons = $Sump_Pump_Gallons_Daily $Sump_Pump_Minimum_daily_gallons Init To $Sump_Pump_Minimum_daily_gallons $Sump_Pump_Minimum_daily_cycles = $Sump_Pump_Cycles $Sump_Pump_Minimum_daily_cycles Init To $Sump_Pump_Minimum_daily_cycles $Sump_Pump_Maximum_daily_cycles = $Sump_Pump_Cycles $Sump_Pump_Maximum_daily_cycles Init To $Sump_Pump_Maximum_daily_cycles $Sump_Pump_Monthly_Gallons = $Sump_Pump_Gallons_Daily $Sump_Pump_Monthly_Gallons Init To $Sump_Pump_Monthly_Gallons Else - No Actions - (To add one, press 'Action') I just updated it to 11:59:45 and will look next month The question, approximately how long should assign or init take? Paul

This is the process: https://wiki.universal-devices.com/ISY_Portal_Admin_Console

It's a climate type, and uses status:

It's very likely not an Insteon device sending X10 as the messages are all Housecode "J", which is the X10 Housecode where all signal bits are set to "on" on the powerline. In that case its one of two things: An appliance or some electrical device is emitting noise on a continuing basis that looks like all bits on all the time, that the PLM interprets as X10 house code "J" The PLM is losing its marbles and creating these messages in error. I've seen this one myself. I don't have the forum links handy, but it's not the first time I've seen a post about PLMs producing a flood of "J" messages

This. If not, put a couple of seconds between each command as the "back to back" Insteon commands are crashing into each other.

I use the 8003 in my bathroom. I do save to variables and compare when it changes to the previous reading to determine a delta rise to turn on the fan. It's a bathroom that's open to the master suite so it doesn't always peg at a high value, like my laundry room does. Works fine for when the shower is used. However some of the sensor updates can be a long time, and when the 8003 decides it's time to update, the Delta is that same 3% - 4% and the fan comes on at unexpected times, eg middle of the night. (I've based the values on looking at days of yolink logs) It's related to my thermostat letting the house cool down at 10pm, and then the first cycle after that happens in the middle of the night. I've updated the program so it doesn't run then and will see what happens

I don't think I saw this in write up, did you compare the links table between PLM and iox, and also look at your link table count? One of the reasons that some things like Motion sensors and light switches may be working is that they can be device-device programmed scenes and the PLM&eisy have no role in their operation. Is the MS you mention setup to trigger the associated light(s) directly? This could explain some of what you're reporting.

I use the ring pg3 plugin for using the ring doorbell as a motion sensor. There are some prerequisites, and the plugin doesn't mention the mailbox specifically. Look at the forum pg3 ring plugin section and ask there if the mailbox is or could be supported and if you have / want the prerequisites. It works really well is the reason I bring it up.

Put one of them in linking mode, right click on it in AC and pick restore device. It's possible things got confused in the upgrade. If that works, continue on to the others that aren't workinkg

@hart2hart That's nice! There is a reference in iox 5.8.0 in January to a SQLite database being added for node values, but IIFC it was more a future feature and no details provided. If that were available I would love to store / access values in it, using a client on my pc.

@Ross...The "set it high" method does work for my upstairs laundry room fan which was the first project. The fan didn't always get used manually and a couple times the comment "the dryer smells funny". If the fan is used consistently it's not a problem. The dryer's operation will "punch through" upper temp and humidity values fairly quickly and it works. I tried this approach also in the bathroom and it doesn't work. the shower never makes it to a level that is consistently very high, or where it doesn't take a long time to do so. Empirical is a place where yolink shines. I looked at the yolink graph and downloaded the yolink data into a sheet and cacled a delta of 3.5% between readings based on when the shower was actually used. If current reading >3.5% of last reading, the shower was used. It works well now. They only comment for this application with the 8003 is there is dwell in the time that the sensor gets a reading, and when it decides to send it through the hub to the cloud... I can see the readings jump up on the sensor it self, but it can be a few minutes before it makes it back to the plugin to turn the switch on.