FBoucher

I suppose your HA on Pi also runs on your UPS. For now, my HA is a VM on my Media server that is not running on UPS. I can probably move it to my File server that is running on UPS but running low on RAM. I'll give it some thought. Would you know of other solutions?

My Polisy is currently powered by a CyberPower UPS and I'm exploring ways to get notified when my Polisy is on battery and have a few hours or less of operation. The use case is rather simple. In case of being away for a weeks/months, I would have to alert a close friend that I need home surveillance. So: 1. Is it possible for my Polisy to communicate directly with the UPS? On the UPS, there are RS232 and USB connectors. There is also a software provided by CyberPower that allows status feedback to a computer. Any way to integrate? 2. For my Insteon devices, I have a PLM 2413S connected to my Polisy via the DB9 port. The PLM is directly connected to my house electrical grid. During a power outage, the PLM will stop communicating with the Polisy. It looks like the PLM is not listed as part of the nodes. Is there a way to monitor the PLM status in programs? 3. If I can't use the PLM status, is it possible to monitor another Insteon device for an "unknown" status? 4. Other ideas?

I never thought that my simple evening kitchen light program would bring so much passion. I started with a simple 2 states program to get the hang of it. But there is a random variable (no pun intended) I didn't mention ... my wife. Once she realises the capabilities of the ISY, I'm sure she'll have new ideas about how to structure the lights throughout the evening/late night. The kitchen light program will definitively need more states to cover it all. So, for now, I'll continue with a state variable. Thank you all your inputs. You all made valid points and arguments.

To asbril: the problem is that I don't want to issue two requests (one at 6PM and one at sunset-30) to turn the lights on because some of the lights will be turned off manually at some point during the period. For example, today's sunset is at 8:20PM. According to my initial program (first post), the IF is triggered TRUE at 6PM and at 7:50PM. So, the Insteon devices linked in the scene (there are 5 light responders) receive a request to turn the lights on at 6PM and at 7:50PM. Around 7PM, I generally turn some of the light responders off manually (end of dinner). But because of the IF logic firing twice, the lights I turned off manually will be turned on again at 7:50PM. I don't want that. I concur that there are different ways to code this. Before reading your replies, I decided to have 2 programs, one for logic and one for the lights. So it looks like this: Program KitchenEvening - Control If From 6:00:00PM To 11:00:00PM (same day) Or From Sunset - 30 minutes To 11:00:00PM (same day) Then $sKitchenEvening = 1 Else $sKitchenEvening = 0 Program KitchenEvening If $sKitchenEvening is 1 Then Set 'Kitchen RGBW + puck' On Else Set 'Kitchen RGBW + puck' Off larryllix in his first reply suggested to simplify the first IF like this: If From 6:00:00PM To 11:00:00PM (same day) Or Time is Sunset - 30 minutes I considered it. But then I asked myself, what if the ISY is turned off and restarted before and after the sunset-30 trigger. That would mean the program would only be triggered at 6PM (if the sunset is before 6PM), thus missing the intended period for that time of year. Wouldn't it be safer to keep both periods in the IF?

Thank you both for the replies. I wrongly thought that a IF statement would turn true only once, i.e. when either of the conditions would turn true, instead of twice, i.e. when each condition would turn true. apostolakisl, you are right. Some of the lights that turns on automatically with the program will eventually be turned off manually and, depending on the sunset time, they could be turned on again, which I don't want to happen. Thanks larryllix, using a control variable is the way to go, because I want the program to trigger true only once and false only once. Also, I want the lights turn on at 6PM or earlier, if (sunset-30 minutes) is earlier than 6PM. Thank you both.

Well ... I guess I qualify for old enough. My first taste of remote access was Kermit over a regular phone handset inserted in a modem interface ... Thanks for the tip. I'll keep it in mind if I need to adjust the programs.

You're probably right. Thanks again.

Thanks again MrBill. It is as I expected. Sending two requests to the same Insteon device in a short time is unreliable (it may or may not work). So I increased the delay to 10 seconds and it seems to work. I'll let the program run for a few nights and see if it's consistent.

Thanks MrBill. My home is in an urban vicinity with a pretty reliable internet access. I configured Pushover "the old method" and I also have email configured in parallel. I'll use it like this for a while and see how it goes. For Locative, as I said a few post back, it worked when I got far away from my house. My house boundary is set at 50 meters. When I did the initial testing, I walked away up to 70-80 meters from the house and Locative didn't trigger. But when I drove away more than 150 meters from the house, Locative triggered. So it works, but not quite as I expected. I thought geo fencing would be more precise.

Ok, the title is probably not great, but I wasn't sure how to describe my problem. I have an Insteon On/Off Outlet (2663-222) that is linked with two seperate scenes dedicated to outdoor lights. The top part is with scene A and bottom part with scene B. I've created two programs (one for scene A and one for scene B ) where the scenes are turned on 30 minutes before sunset and turned off at midnight. So, both scenes operate at the same time, except for scene B that can be triggered manually via an Insteon Keypad button. During my tests, I sucessfully turned on and off the scenes via the admin console nodes. If I use the keypad, scene B turns on and off like clockwork. The problem is when the programs run, only one of the node gets turned on. The status of the nodes show that both are turned on, but when I issue a query, the status of the off node is reset to off. I thought that the Insteon device was not able to handle both requests at the same time, so I introduced a 2 seconds wait time for scene B. It doesn't seem to be enough. Should I increase the delay or is there another solution? Thanks,

Hello all, I created a simple program to turn on the lights (via a scene) in the kitchen. I want the lights to turn on at 6PM or before if sunset is earlier than 6PM. So I created this: If From 6:00:00PM To 11:00:00PM (same day) Or From Sunset - 30 minutes To 11:00:00PM (same day) Then Set 'Kitchen RGBW + puck' On Else Set 'Kitchen RGBW + puck' Off Tonight, at 6PM, the lights turned on, but a new requests to turn the lights on was made 30 minutes before sunset. So it means that each part of the IF would trigger an event separately regardless of the status of the other. I could create a first program that determines if the sunset is before or after 6PM and have actions in Then and Else to execute programs for each condition. But is there a simpler way to code this?

I'm looking at Pushover. To install on my ISY, do I have to follow this wiki? If yes, when I click on https://pushover.net/apps, I get to a page where there is a list of apps, including one for Universal Devices by Jim Searle. Should I use this one or create my own?

I tried Locative and you were right. It detected that I left the zone when I was way outside the home zone (like 3 times). Now, I was driving my car, so there is maybe a time hysteresis that would trigger closer to the zone if I was walking. I'm a bit concerned with the battery drain of geofencing. I guess that to make this work, I would have to let Locative use the location service all the time. How have you configured your system to limit battery drain?

Thanks, I'll try this. I see that you use Pushover. How does it compare to Pushsafer?

I see in admin console the portal server nodes I created (like your Home and Bill iPhone). From Locative, if I long press the location and manually trigger an enter event, I receive a notification from Locative, I see a status of Entered in Locative and the portal server nodes are set to true. If I long press the location and manually trigger an exit event, I receive a notification from Locative, I see a status of Left in Locative and the portal server nodes are set to false. The problem is the events don't get triggered when I cross the geofence boundary which is actually set to 50 m around my house.

Hi to all, I need some pointers regarding Geo Fencing and Push Notification. After reading the wiki pages on the subject, I'm rather confused. Following the wiki for Occupancy & Locative (for IOS), I managed to create the location and geofence nodes. The wiki was written for a previous version of Locative (now at 5.11.0), so I tried my best to configure it for my location. After many tries, it just doesn't seem to work. I used MrBill Locative reset procedure from another post, and if I force an entry or an exit with the long press, I see the status change in ISY admin console. So I guess the configuration is OK and there is something wrong with Locative on IOS 15.4.1. I opened a ticket with Locative. So I continued reading and found this wiki where it is recommended to use IFTTT and Locative. Is it only true for MobiLinc users or for everyone? I downloaded IFTTT and found that it could be triggered by location on its own. So I created a simple location based notification, but I can't seem to make it work either. In the end, I'm looking for a way to get notified of water leaks (Insteon leak detectors), movements (Insteon motion sensors) and entry doors being opened (Insteon open/close sensors) on my phone while I'm away (a function that was available with the defunct Insteon Cloud). I also have an old alarm system (wired motion detectors and wired windows switches) connected to an Insteon I/O Linc that gets triggered when the alarm sounds. What would you recommend? Occupancy - Locative? IFTTT - Locative? IFTTT alone? For the notification app, I'm considering Pushsafer.

Thanks Geddy, support already replied asking me to click again on Manage Modules and the Portal Module Install started. Now everything seems to be back to normal. I guess some parameter needed to be reset on UD side to allow the module to become available, as if I was a new user again. Other matter, 24h time format. I selected 24h format in configuration, but the Schedule in Programs still shows hours in the AM/PM format. Is it possible to have 24h time format in Programs?

OK, I tried again and I have a red X ... No portal module installed. I'll wait for support to reply.

Thanks Geddy, I did that, but I can try again. I also opened a ticket.

Hello again, Also, I selected 24h format in configuration, but the Schedule in Programs still shows hours in the AM/PM format. Is it possible to have 24h time format in Programs?

Thank you very much Geddy and MrBill for taking the time to answer my questions. I just need to learn this programming language. I followed lilyoyo1 suggestion to factory reset all my Insteon devices. It took me a little while because some of these devices are not easy to reach. I also factory reset My Polisy and PLM. Now I've added all the Insteon devices back, created basic scenes and basic programs. I'll play with them to get a better sense of the interactions while referring to the wiki and cookbook. However, in the process of resetting everything, I no longer have the "Portal" tab in the "Configuration" tab. Before the reset, I succeeded in linking to UD Mobile and ISY Portal. Now ISY Portal list the Polisy, but says it's offline. What should I do to get it back? Thanks

Thanks for the tip lilyoyo1, If not mistaken, factory reset requires a physical access to the set button on the device, right?

Hi again, I should have read the cookbook further before posting ... sorry. The answer is a bit more complicated. From the cookbook page 183 section 9.5.4, I understand that the IF condition is re-evaluated when there is a WAIT or REPEAT action in the THEN (or ELSE) section. So, if I understand correctly, for a simple program like the one you posted: if from sunset to sunrise then turn light on else turn light off the THEN and ELSE actions will only be executed once because the IF condition will only be evaluated twice, at sunset and at sunrise. I'll keep reading before posting ... Many thanks, FBO

Thanks Geddy for the reply. This ISY cookbook is really good. That's what I was looking for. I didn't venture in the ISY994 wiki thinking that it no longer applied to Polisy. From the cookbook on page 145, section 9.2.4, reproduced here: IF – has the condition that must be met to for the program to run. This condition is the trigger for the program to take action. THEN – is the primary action when the condition is met. The program here stays running as long as the condition is met or True. ELSE – is the secondary action when the condition is no longer met or False and only after the primary action was taken. So, as you stated, the program gets triggered when the IF condition is met. Other times the program is not running. Once met, the actions under THEN are executed while the condition is TRUE. When the condition goes from TRUE to FALSE, the ELSE actions are executed once. If the condition is a period (like sunset to sunrise) does "The program here stays running" mean that the actions under THEN are repeatedly executed? Or the THEN actions are executed only once when the IF condition is met and keeping the program running serves as some sort of timer to get the ELSE actions executed at the end of the period?

Hi to all, I just received my Polisy (running v5.4.3) and Insteon PLM 2413S. So I'm on a learning curve and this is my first post. I managed to build my own RJ45 to DB9 interface with an ethernet cable and an inexpensive DB9 to RJ45 Modular Adapter like this. I also managed to add my 25 devices using the "remove links" option. So, I think I'm all set to start programming. I searched for a programming primer, but couldn't find one to answer my questions. My questions regarding programs are: Do programs run 24/7 like a service or they only run when the condition is true like a scheduled task? If they run 24/7 like a service, then everything under the "then" is executed at every cycle when the condition is true and everything under the "else" is executed the rest of the time when the condition is false. For example, if my program turn on a scene (then action) at 18h00 for 1 hour (if condition) and turn off the scene otherwise (else condition), does it mean that if I turn on the scene manually at 20h00 the program will automatically turn it off because it's in the else condition? If they run like a scheduled task, why is there an "else" option since the task is only executed when the condition is true which means that at other times the task would not run. Plese help me understand, Many thanks to the community, FBO