paulbates

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.

Same for me with the temp sensors... in fact after installing them I found my kitchen fridge & freezer temps were way off and both needed to be adjusted with the fridge's controls- i cold make changes and track with the app's graphs. The garage fridge door stays open sometimes when grandkids go to get something and don't close it completely.. a simple ISY program alerts me. The only challenge was my first use of the 8003 temp humidity in my bathroom to operate the vent fan when the humidity rises. Since humidity is relative, I couldn't put a raw value (like 45%) in the program as it moves around. It took more elaborate ISY programming than I anticipated to capture the humidity and compare at every reading so I got the "slope" right... Too low of a delta and just walking in, siting and breathing in the area starts the fan.... Too high a slope and doesn't start after the shower is used. The built in app's graph was really helpful to look at usage of the room over days and figure it out. It works pretty good now.... the dwell between sensor reports makes it come on a little later than I prefer, but does the job. FYI, in my conversations with yolink (scroll to my messages in this yolink forum)... local api is a software feature release slated for later this year, but not specifically associated with unreleased hub 3. Hub 3 brings a physical ET port and mobile data backup connectivity. Hub 3 does not come with Hub 2's text to speech feature, so I bought hub 2 and did not wait.

To be fair to UDM I went in on the iPadOS version and saw that my notification server needed to be updated. It was easier than logging through and going to the pgx page, finding the plugin and finding upgrade. My biggest issue with UDM for this function has been being able to navigate and view on a small phone screen, there is and iPadOS versions and its nicely laid out. I'll keep trying it this way and a see if I get stuck.

Yes, understood and I get that. IIRC the plugins section says ""Beta" in UDM. I tried it out but couldn't do everything I wanted. I too have been "all ports closed" on my router for a long time and will not change that.. your first post confirmed what happens. I don't have many plugins and things have been stable. However I'll be traveling extended trips in Michigan and elsewhere this year and want to be able to deal with plugins if necessary. A RVNC type solution that includes a proxy login like the portal is what its going to take as it stands now.

I asked this same question another way, the answer is UDI mobile is the recommended way to work with plugins remotely. I want access to the management page. My way is remotely connecting to the house pc using realVNC Connect, so I'm using a web capable device on my network

How old is the plm? If it's 6 to 7 years, it was built during the time they were still using crapacitors, and it's likely dieing. Open tools, and look at the plm diagnostics. Also compare the links tables, they should not be a small number or 0 with that many devices. I believe the newer PLMs have better capacitors

I don't think they would remove their Alexa skill too (assuming that's your access method)- that would cause a bigger riot from a larger crowd. Maybe things are partly cloudy. Another possibility and a thing I've noticed when other plugins can't log in to their respective cloud service is adjusting short and/or long poll... they update how frequently they'll accept polling. @Goose66

Was this after an unplug / replug? I think the 4718 is week 47 of 2018.. so its older and in the time period where they were still getting the bad capacitors. Also look at tools/diagnostics/PLM Info status If those are all bad results, I'm guessing the PLM is shot

Sometimes unplugging, waiting 10 seconds and replugging will sometimes fix it. How old is the PLM, what's its version number, date? Take a look at this link, starting at step 4, number 2. If the links tables are out of line. Based on how old the PLM is, eg 4,5+ years there's a good chance its bad

You can try factory resetting it. See page 67 of the manual. https://docs.universal-devices.com/production/ISY User Guide v4.0.5 v2.pdf If that doesn't work, I would submit a ticket

I hadn't thought about that one. I have the ring plugin and use the ring as a front motion sensor for premise lighting. I barely get out the door and the lights are on.

The portal also provides these features integrate assistants like Alexa and Google home for verbally controlling eisy Geofencing Remote access to eisy maintenance features remotely: reboot, upgrade packages Creating other accounts for other users to access eisy features with different access levels

Me too. I don't have the distance requirement, but I have 4 temp / humid sensors buried in metal / stainless fridge/freezers and they work and show strong signals. Like any technology, its been a learning curve to get yolink's way of thinking (like how long between temp/humdity update), but everything's working I'm getting there. It is a great compliment to an Insteon power line solution.. they both do a great job of what the other doesn't Yes... or learning to drive stick shift all over again 🤪😂

I've not used it yet, but planning on it, it's part of the PG3 plugin config. Go to yolink plugin Config Scroll down to custom config parameters Number of TTS, and then each gets a field to type the message in I'm also making the leap that if you've added them in the app, try restarting the yolink plugin, that's when config changes are addressed

Guess I didn't remember that. Occupancy & lighting is the only thing I need to do. The On Only use goes back to my original MS1, that's the only way I'd use it. Since this one is hardwire powered, I was ok with a shorter wait cycle.. but have always kept it a couple minutes or less It does work. After reading your post, my wife was leaving through the garage. I took 4 screen shots of the program.. When she opened the door to the garage She backed her car out I waited 5 minutes and opened the door (had to visit the drinks fridge 😉👍) Waited for 10 minutes after my last garage movement. The second and third time, the program restarted and the 10 minutes started again