paulbates

Is there an If statement? If that logic becomes false the program will stop. Can you share the program? That will help Paul

Hey, great idea... and I just muted it. I'll see what happens Paul

There have been discussions here about how much traffic the Echo/Dot transmits. I've watched mine in the past and it didn't seem like much. I started monitoring it again.. the results aren't alarming, but curious We do very little with it. Lights, TV, Thermostat commands occasionally, questions here and there. No music. Its consistently about 2.5MB a day uploaded, and about 1.5MB download. The use is bursty (see the graphs). It doesn't always map to people being in the room or noise/conversation. It is interesting that its reverse client server... a little more up than down The amount of data transferred in the peaks is minimal, and hard to believe decent audio was sent: 111K in an hour (the biggest peak) is 1800 bytes a minute. Maybe that's too simplistic though Some of the peaks are times that no-one was home or in the middle of the night and no-one was in the room Traffic sent over 24 hours Traffic received over 24 hours Not sure what to do with this, wondering if anyone else has monitored their's. Maybe I'll try and muffle it and see if anything changes Paul

I think something else is wrong. We average a power outage maybe every year and a half. The ISY and PLM come back no problem. Some older devices like togglincs occasionally have heartburn over extended brownouts and need to be factory reset. When you say "manually reboot the PLM", do you mean unplugging and re-plugging it back in? It might be that the PLM is older and also has been affected by the frequent black outs. You might try factory resetting it and then follow that up with a "Restore modem" from the ISY admin console's file menue Paul

To add to Larry's great idea, you can have your programs in various folders, and have a condition like a variable called "stop" (= 1). Add that as a folder condition to each folder, and make sure its prefixed by an "or". Keep your "stop" program at the root level so its not affected. You will want to initialize stop = 1 so your ISY works when rebooted (or check for 0 instead of 1) If (stop condition) Then $Stop = "1" Else $Stop = "0" ( run program A if) ( run program B then) Keep in mind that the ISY is event driven, so turning the "stop" variable to 1 will stop all of the programs... but changing it to 0 not start all of the stopped programs.. when their conditions are met they will start individually, or you might have to manually run the "ifs". Or add statements in the else to run key programs to restart them. I do something similar when my ISY restarts, I kick off certain key programs so values get populated, etc Paul

Glad you figured it out. I've had a bad one as well. Here is the program that's worked for me. The hearbeat doesn't have an on/off state per-say. It sends a message every ~24 hours and is detected "If xx is switched on" I give it 25 hours as its not always exactly 24 hours, 25 proved safely outside the window. The next message, ~24 hours later, restarts the program (until it doesn't, and falls through to the notification) Battery Doorwall Heartbeat If 'Zystem / Battery Alerts / Doorwall Sensor-Heartbeat' is switched On Then Wait 25 hours Resource 'Pushover Doorwall Sensor Battery Low' Else - No Actions - (To add one, press 'Action') Paul

2 things... 1- what's normal Yellow arrow pointing right indicates a sensor input device.. that's as it should be 3 devices Open and Close indicate state, but the responses are opposite of each other There really is no difference other than making a program more readable, looking for a door to open vs close. A heartbeat message is sent ~ every 24 hours as a way to know the battery, or the unit died You can write a program with a 24 hour wait and then a notification. If you get the notification a few times, the battery is probably going Using the sensor 'If control' program statements let you respond to the action of the door being opened or closed. 'If status' program statements let you use the doors state, especially if timing is needed. We have long periods in the spring and fall when its nice out for a while, then its not. I use this for my doorwall is in open state for x minutes (along with month, outside temp and other factors) to shut off HVAC , as well as cancel my HVAC fan cycling programs. 2- what's not The green light on the sensor body should blink once when you pull the magnet out of range and once when its back in range. Did that not happen? Are there dual band devices nearby to carry the sensors signal onto the powerline or PLM? Paul

Assuming you created an ISY program, with no "if" clause, and you associated it with Connectivity, Amazon Alexa in my.isy.io.. there is nothing special about the ISY program statement content... Normal ISY program statements can be used. Example program: TV (added in Alexa) if <nothing> then (when you say "Alexa turn TV on") set TV on set roomlights off else (when you say "Alexa turn tv off") set roomlights on set TV off You will need to discover devices after creating program the program and associating with my.isy.io. Paul

Hi Matt, welcome to the UDI Forums! I found an older post on this. I suggest you try what's suggested, but since its a new setup, it might be best to submit a ticket as called out in the post. UDI is very responsive... I had a support call when I first set mine up. Merry Christmas to you! Paul

Depending on what you're running for PLC. I'm all insteon and have a few devices on io_guy's nodelink and its fine, and I'm into my second year on v5. However there are some anomalies being reported on how decimal variables behave. This recent thread discussed that, I would pose questions there about what you are doing, what version you should load, and if it would affect your requirements. Maybe its ok on 5.10? Not sure. Paul

Based on what I've seen so far, it seems like something is not right with Java, that java is not caching your admin.jnlp I can think of 2 things it could be The java cache is corrupt / damaged and needs to be cleared (which you indicated you did) The java client is configured to not cache apps local: Go to the java control panel, General / first tab Click View next to Temporary Internet Files. Does it look like the attached pic?​ If no, Go to settings under Temporary Internet Files Is Keep temporary files on my computer checked? Check it if not and retry If yes, as a precaution, I would go under Delete files, check all three boxes and delete it all and try again Paul

If you go to your windows download folder, do you find admin.jnlp there? If its not there, you can open file explorer, click on Drive C: and type in admin.jnlp in the search box. (it might take a minute or so) Move it when you find it to your desktop If that doesn't help, can you post a screen shot of what you're clicking? Paul

IndyMike is right, I forgot that that the ISY does not do group clean ups. Having a controller like the ISY getting dozen or more cleanups back from a very large scene potentially creates a lot of traffic.. around the same time. Paul

Were these "disabled" for the winter and subsequently re-enabled now? I disable the older lamplincs I put away with the Christmas decorations till the next year. Maybe factory reset one and re-test to see if that helps. Paul

There is one other thing to try, if the device supports it: 'Communication to the PLM'. Its found by right clicking on a device and picking 'Advanced'. If the device supports it, there will be a drop down to pick the number of retries. I have a few devices on the edge of my network that were problems I tried this on. For keypads, you set it by the key which was handy for me. I started with 2 retries and that seemed to solve it. I'm not really sure of the scope of this feature, and the problem was very intermittent... but the problem has gone away. Its easy to try. Paul

To follow up on Stu's comment, what you've listed is 1/2 of the necessary steps.. .the ISY admin console part. You need to go to my.isy.io, set up and account and associate your ISY's UUID with that portal account. Maybe you've done that but I didn't see it mentioned. Paul

Cool...the rainmachine has the Alexa skill built in... turn in on the RM's web page, use the Alexa discover, nothing to install. I used it once to herd a squirrel from one part of the yard to another . Paul

Jack Ok.. Hope you figure out. Part of me wonders if its the PLM. My experience is that they can fall apart a little bit at a time. Its probably worth looking at the ISY, PLM and Device links. The hydreon has been great! Just had a forum chat about it the last couple of days. My water usage / bills have been way down, which is good because our water is expensive. I've had no problems with it. Other than inspecting and wiping it down at the start of the season in march, it gets ignored. I switched out the ezfloras for a rainmachine a 2 seasons ago. The RM does the bulk of active watering, and cuts back zone time based on WX / forecast data. I push a 48 hour "sleep" to it when the hydreon senses enough water, and also determine if my in-the-sun hot zones... also if its rained enough during an active watering cycle. Paul

Hey Jack, good to hear from you. These things stand out The light is on, switch (a 2876SB Icon Relay Switch) is on (i.e the pilot light is off In admin console, the last run status is correct In admin console, the status of the light shows OFF, until queried In Mobilinc pro, the status of the light is OFF until the actual control page is brought up. Given that its a scene, it can make sense that the admin console (and downstream things that refer to the AC), show things as the ISY believes them to be. This suggests that either the scene command / group cleanup aren't making it to the switch, or, the switch is ignoring it. Any other programs running at the same time? Have you factory reset the switch and restored it? Any chance the settings in the scene or the switch itself have changed Paul

Nothing wrong either way, it depends what you like and work with: Waits The only way to do it if you have hundreds of devices and are low on Insteon links Downside is that it creates a lot of traffic at that time Each scene goes off one at a time, rather than one single "off" (Personally don't like the effect of this) You need to add a bunch of wait statements to one or more programs One Scene Uses a lot of additional links.. ok if you have lots open (I do) Less insteon traffic Ons and offs are coordinated.. everything on or off at one time (My preference) You need to use the Admin Console to drag a bunch of devices and build a big scene Paul

Leon I believe this feature was designed into insteon and in the Insteon whitepaper. This is "working as designed". The messages generated by insteon switches that are associated with "if xxx is switched on/off" are transmitted only when locally and physically tap/double tap/holding the switch. Remotely activating the switch does not send the messages back out, ISY programs won't respond. This applies to linked devices too.. turning on a switch via admin console or ISY program does not turn on linked devices it activates when switching it on locally. What should work in programs is status on/off, no matter how the switch is activated, its status should be detected. Paul

Leon, If you open your ISY Admin Console, find the on/off device and click on it, look at the options at the bottom. Fast On / Off should be there. This is what was recommended to the OP I have several on/offs that I detect being switched locally fast on / off. Attached is a pic of one of my oldest togglincs in the if part of an ISY program. The fast on / off buttons are there and work in the Admin console. Also a sample If statement where the ISY is allow me to detect fast on/off from in a program Its the same double tap speed as any other switch. Paul

Agreed with Stu. "Group Cleanup" messages from a previous Set command are colliding with other Set commands as the program runs. Another way to do this is to create another scene, a master scene that contains all of the devices, and turn only that scene off. This is possible only if you have enough links available in the links table. If you have hundreds of devices my suggestion may not work. Paul

Only dimmers can make functional use of fast on / fast off on their loads -- it overrides a slow dim up or down rate. However, insteon on/off switches support the ability to be locally double tapped fast on/off, and ISY programs can detect that. On/Off switches also send dimming commands to dimmable devices linked scenes when when using "press and hold" of the paddle or keypadkey. ISY programs do not see this and not able to respond to it Paul

Insteon scenes can't be specified by double tap. However, you can get the same results with this: Create a scene where all 3 are Responders only Create 2 programs If switchA is switched fast on or switchB is switched fast on or switchC is switched fast on Then Set SceneAllThree on Create as similar program for off There will be a second or two delay Paul