auger66

So this topic kept going so I dug out the actual programs I have running in a hangar. The idea is when it's warm and humid, the concrete floor gets wet. So I wanted a program to run when "wet floor" conditions were met and turn on a big floor shop fan. The values that mattered were 60% humidity and 60 degrees. If both of those conditions or above were met, then I wanted the fan on. Otherwise, off. So this is to set the humidity variable Set humidity variable - [ID 000B][Parent 0001][Run At Startup] If 'Thermostat' Humidity >= 60% Then $Thermostat_hum = 60 Else $Thermostat_hum = 59 This is to set the temperature variable Set temp variable - [ID 000A][Parent 0001][Run At Startup] If 'Thermostat' Temperature >= 60.0° Then $Thermostat_temp = 60 Else $Thermostat_temp = 59 And this is to control the fan based on the temperature and humidity conditions. The wait 30 minutes is to keep the fan from cycling on and off too often when the humidity drops. It's not unusual for the humidity to be near 60%. Humidity fan control - [ID 0002][Parent 0001] If $Thermostat_temp is 60 And $Thermostat_hum is 60 Then Wait 30 minutes Set 'Floor fan' On Else Set 'Floor fan' Off

I have something like this I programmed a few years ago with an Insteon thermostat to turn a shop fan on at a remote location. It's still running. Since the humidity changed constantly and restarted the program every few minutes, I made one program to set a variable if the humidity value was 60% or above, and else if below. There is also an above or below temperature value to the variable. The next program just looked at the variable. I also put a one hour wait on the "if" if the humidity cycled between 59 and 60, which it did surprisingly often since the fan would almost immediately drop the humidity. I didn't want the fan cycling on and off rapidly. However, I haven't put near the thought into this that @MrBillhas, nor do I have his ISY ability. The OP just reminded me of what I did to solve a similar problem back then. Works perfectly.

Thank you for this. I have six different ISY/Insteon installations that have been running for awhile now. I've never had a PLM failure, but I just ordered a defensive USB PLM. Cheap insurance. Kind of like if you take an umbrella with you, it will never rain.

I started over with Polisy after Polyglot crashed on a RPi after an upgrade. The Nest node server never worked again. FYI . . .

Well, I can't replicate the issue, either, now. They are all reporting status just fine. Sorry for the bother. It seems like it had more to do with the location rather than Android vs iOS, but I still don't know what the issue was yesterday. Thanks

Javi, thank you for your reply. No errors during sync. Yes, the admin console shows the last status. Not talking about the blue dot--just on or off. I selected status when creating the favorite like the other devices and scenes I added. After I made the previous post, I went out and had a couple of beverages. I then realized I slightly misstated my issue. I realize battery sensors don't state their current status. What I meant to say is the app is not reflecting the last reported status or any status at all. For instance, the admin console will show the last status the leak detector sent--as dry on, or wet off, or heartbeat, etc. The app just shows a couple of -- always. This is the first time I've ever I'm handing off an ISY system to a pending new owner, and I'm trying to simplify the system with favorites and clean up details like this for the wall-mounted iPad I'm leaving. It's a lot to digest for someone that isn't familiar. I won't meet the new buyer until after we close, but I hear she's not "techie." I don't have any favorites on my separate, personal setup, but I just checked the same type of water leak detectors on my Android phone app. They reflect status accurately and immediately so the issue must be specific to the iOS app. Water leaks are a big, big issue in my high-rise building lately. I have programs that alert you to leaks, but it would be nice to see that the leak detector is showing dry on, as in, if the button on the detector was clicked to show it is "armed" again to trigger the program for a new leak. Thanks again for your effort on this native UD app.

I just put UD Mobile on an iPad. Leak sensor status doesn't show. Is there a way to directly show sensor status as a device like other devices do? I'm trying to avoid setting up a variable just look at sensor status. I'm assuming a variable would work. Thanks

I loaded the other five ISYs with only the Portal connections (no local) tonight. I can't believe how fast the app Portal interface is. Well done. One small suggestion . . . Consider making the favorites tab specific to the ISY you selected. I can see arguments either way. I'm all in Android, but the iOS app can't come soon enough for my users. So how's that going? Thanks again.

That's a great idea. Wish I had thought of it when I set up new place. I wanted to do the same thing but didn't know how to do it.

I would just like to say thank you for this. I put it on my Pixel 4. I haven't customized it yet; but it works, including the RPi. ? I support five ISYs for people that all have iPhones. I look forward to the iOS version for them. Thanks again . . .

Thanks for the input. I'll be putting my commands in programs so I should be able to control the overlapping commands. Plus, there are only two. That condo is small, and the motors are in separate rooms but pretty close together. Hopefully, close enough. I have seven Somfy roller shades and curtains in my condo. The roller shade motors have better range. I'm running Polyglot on a RPi in my place. It's not nearly reliable enough to put in someone else's place. I have to go in and restart the Hue nodeserver often. Same thing with DarkSky, but I removed DarkSky as I don't need it anymore. I put a RPi restart command to run every day at 4am, but I still have to restart the Hue nodeserver once a week or so. The Sonos nodeserver seems to always work. We'll see what happens when S2 comes out in a week. The ISY is rock solid so I'll be sending the Somfy tcp commands from the ISY directly. We'll see how it works out. I was going to buy a Zwave module for the ISY and use the Somfy Zwave interface, but many here didn't think that would work.

Many thanks. I'm looking for the best super robust way forward for some new Somfy roller shades in a rental unit. All of the Somfy solutions get poor reviews (myLink, ZRTSi, URTSi II, etc.,) mostly due to range issues. I'll try myLink and network resources first and cross my fingers. And how 'bout Elon yesterday?!!! ? Well done!

Would you mind sharing the MyLink tcp commands you use for network resources? Thanks

Well, this is probably the best thing I've learned all week. I tried it, and you're right. I wish I had known this a year ago.

Yes

I have a variable to control an Alexa routine. It still works; however, . . . It has always had variable timing on the execution. It can be anywhere from 1 second, 3-6 seconds, or occasionally not at all. It's not the ISY. The variable changes instantaneously.

I've never tried that, but I assume the A key and light are part of a scene; and you are trying to adjust both the light and key. Have you tried having Alexa turn the scene on/off instead?

I set mine up a year or two ago with a Somfy URTSI II and an Autelis Shade Control for Somfy RTS. I don't have any Zwave. The Autelis is reliable and easy to integrate into the ISY with network resources. I've found the URTSI range isn't the best, but I've gotten it to work. For some reason, the roller shades have better range than the curtains. Autelis may be out of business, though. They still have a website, but all of their products are showing "out of stock." They may be still making them by request. You would have to contact them if you're interested. If you're using Zwave with your ISY, I would definitely go with the ZRTSI. It would give you a lot more placement flexibility and one less component to buy assuming no range problems.

My mistake--I misread your post. I thought you had a Samsung and had already gotten this to work. I played with this but didn't get anywhere without knowing how to populate the various fields in network resources. Above my level. Thanks, though . . .

I'm looking to send just a couple of commands (stop, off) to a Samsung commercial display (ML55E) with network resources. The display was released in 2016 so it probably would be the same as a 2017 Samsung tv. What is the protocol information in the network resources editor you used? Thanks.

I would like to know what you think. I have a fixed iPad in a rental unit that I would love to put something on as long as it's solid and not too much work. Universal Devices still features eKeyPad on their homepage, but the forum is dead on it. So I don't know what to think about eKeyPad's status or future. I've already been down the iRule road . . .

Or maybe putting the switch in a program and have Alexa run the program.

I know this doesn't help with the problems y'all are experiencing, but I just wanted to add my two cents on fanlincs. I have recently put in three Modern Fan Torsion fans with a light kit with fanlincs, keypadlincs, and an ISY. It all works perfectly. There's no hum at all and the led light dims unbelievably well. A long time ago, I put in a similar setup for an old Hunter Douglas fan when the fanlincs first came out. It worked great, too. I did have to RMA two version 2 fanlincs when a nearby substation blew up, but they were working great before that. The latest version is 3.1, I believe.

I'll be glad to help, but I just got off an all night flight from Africa. I plan on sleeping the rest of the day. If you pm me your number and/or email address, I'll see what I can do. Gary

You're right; the program was never triggered. But the "if" was so simple, I didn't know why. Plus, it wasn't even running with a "run then" yesterday. It was enabled. I went down today to put 5.12 on and noticed the last run time was correct so I looked at the variables. They were correct today. I poked at it yesterday but didn't change anything. So I don't know why it wasn't running yesterday but is fine today.