larryllix

Hops are not reties! When an Insteon transmission is heard, all capable devices synchronously repeat that transmission. When another device hears this, one hop is completed. This allows Insteon signals to transmit to the Initiating device---->hop---->second device----->hop----->third device----->hop----->PLM or reverse orde,r PLM---->end device This is not counted as a Hop Initiating device ----->PLM On top of all that if an ACK is not heard back or a NAK is received Insteon devices will/may try again with repeats of the whole process. Zero hops left is not a failure. It means it took three intermediate devices to get there. If it failed, ISY wouldn't know about the attempt and you would not likely see any recording of an event.

The 1011 means there is binary code to be written to your device yet. If the device is battery operated it must be put into linking mode first. Then you can right click on it and select "Write Updates" As kclenden posted above, you need good comms first or things get messed up.

Sure. Write a program for each button and put whatever you want in each program. Configure your KPL to non-toggle On mode. If control KPL.Button.A is Switched On Then do whatever Else ----- KPL LEDs can have levels changed with programs in the admin console (all for one setting) but LED On/Off can only be done with scenes. Of course, then use programs to activate the scenes.

Post your program!

I don't think java ever made a 64 bit version. Install is made for a 64 bit O/S but java is 32 bit only. I may be wrong but years ago they announced they would never support 64 bit. Apparently java's install made the decision what to install.

I would use a State variable to control the pump. A simple final program to turn it on and off would be required and this may simplify the look of your programs making it easier to implement complex logic. Another advantage of a variable control is that it can only be turned on once and multiple programs can't keep hitting on it to cancel other timers. If $sPump = $cTRUE Then set pump On Else set pump Off Now using a vacation variable, things can be based on that logic flag If $sVacation is $cTRUE Then Repeat every 72 hours $sPump = $cTRUE Wait 10 minutes $sPump = $cFALSE Else $sPump = $cFALSE <----- vacation might be over while pump is on and then stays on Now you require programs to turn on your vacation mode flag. This flag will be used for many HVAC and other programs . This can be set off HVAC stats and other sources, even manually. I base mine on multiple logics. Mostly 12 MSes with different timeouts from each after seeing motion. If $sVacation is $cFALSE <----- add this to each existing program logic. AND your other time logic similar to what you have shown above etc.. Then $sPump = $cTRUE Else $sPump = $cFALSE To create a cycler after no action something like this could work. If $sVacation is $cFALSE AND $sPump = $cFALSE Then Wait 72 hours $sPump = $cTRUE Wait 10 minutes $sPump = $cFALSE Else $sPump = $cFALSE <--- another just-in-case recovery Now you can add all your shown logic, above, to operate the $sPump variable. This may make it easier for understanding and make program logic shorter, breaking it down into smaller logical blocks. I don't like basing program logic on other programs. I find that method obscure and can bite you down the road because it isn't visible inside programs being edited, that another depends on it's state.

@oberkc That's what I was eluding to, but I was trying not to complicate things just yet, by combining the logics, and I was hurrying to provide an answer. (excuse, excuse) Then the manual lock on / turn off and cancel comes in. The whole thing looks too complicated now and I don't like that, but comfort comes with familiarity. Being more familiar with the light placements would help understand the logic needed to provide better answers and logic. I have found simpler programs for more lights usually works better down the road when I come back and wonder WTF did I do?

You may need a third program for the manual switch operation that cancels the time out and perhaps (for the just-in-case situation) provides a long term timer. Automatic lights get left on a lot when turned on manually. If control 'Exterior Lights / Laundry Room Exterior Light' is switched 'On' <---- control detects the paddle AND control 'Exterior Lights / Laundry Room Exterior Light' is not switched 'Off' <--------- Not runs the else Then set program 'Side Gate On' Stop <----- no interference with this program Set 'BBQ Island' On Set 'Exterior Lights / Laundry Room Exterior Light' On Wait 5 hours Set 'Exterior Lights / Laundry Room Exterior Light' Off Set 'BBQ Island' Off Else set program 'Side Gate On' Stop Set 'Exterior Lights / Laundry Room Exterior Light' Off Set 'BBQ Island' Off

Your first (trigger program) looks good. The second one should work like this. Side Gate On - [ID 0073][Parent 0016] If 'Exterior Lights / Laundry Room Exterior Light' Status is Off Or 'BBQ Island' Status is Off Then Set 'BBQ Island' On Set 'Exterior Lights / Laundry Room Exterior Light' On Wait 5 minutes Set 'Exterior Lights / Laundry Room Exterior Light' Off Set 'BBQ Island' Off Else Set 'Exterior Lights / Laundry Room Exterior Light' Off <------ needed for a change in statuses (2) terminating the Then section Set 'BBQ Island' Off

Why would your lights already be on after 10:00 PM? Manual switch or is there some other way / program that would turn them on?

Yes. That bit changes for some internal flag. I heard an explanation once and it happens all the time. When I see it I do a restore and correct it but, unlike my usual behaviour, I haven't bothered to study the Insteon protocol bit mapping. It is not likely to be a problem like yours. You need to factory rest your devices. Every one of them and I haven't heard any reports from you doing that. We still haven't seen what the following line from your post was either. Oberkc asked about your program timing report. That information will be buried now. I had an OnOff plug-in module sending out a scene on erroneously instead of an ACK, in response to just turning it on, once. Drove me nuts for months but I finally resolved it wasn't my programs as I recognised the multi-light pattern as one of my scenes. I simple unplug/plug back in resolved it and it hasn't done it for the last two years again. These devices contain CPU and firmware programs running and just get messed up every so often from grid spikes and who knows what-else. You'll get there.

These two lines included, indicate your ISY sent an off command to the device and then ISY logged the status change sent back from it. Something is missing in the troubleshooting/search. Either there is an inclusion in some program or the device was operated manually from ISY. The last status update seems to indicate local activation since no report of ISY sending the On was above the 100% status line. Home Theater Lighting Off Thu 2019/01/10 09:23:01 PM Web Log Home Theater Lighting Status 0% Thu 2019/01/10 09:23:01 PM System Log

I wondered about that also. Do you have any scene links to it? All Insteon devices from the factory need to be factory reset before linking to ISY.They can contain X10 links and firmware that does crazy things. It's easy and after factory reseting the device you just click "restore" in the admin console to put all the links back into it. Takes about -2 minutes.

@iannecj In the admin console under the Program Detail tb you can right click on any program in the tree and select a find and replace tool. Using the name of your device, you can find every program that references this device.

Control is a signal generated by the pushbutton of a SwitchLinc (and other devices), while Status is the current level of the dimming electronics. Control can detect an operation repeatedly while status can only detect an On or Off once until the status changes and then back again. If control of X is switched 'On' Then Turn on YYY device Wait 10 minutes Turn Off YYY device Every time X is switched On (paddle tapped) the Wait 10 minutes will trigger when Then start over. With status... If status of X is 'On' Then Turn on YYY device Wait 10 minutes Turn Off YYY device The trigger can never retrigger the Wait 10 minutes timer unless the status changes Off (or 0-99%) and then to On again. But if the status changes, the If section will re-evaluate and run the Else (it isn't 'On') , cancelling the Wait 10 minutes. BTW: If you right click on a program in admin console, you can copy to clipboard and then paste it here.

GH's assumption level makes it a poor voice recognition device for HA. Most ISY HA systems and ideas have to be modified to make it work properly. With ISY and GH, it's like two automation systems trying to get their own way at the same time, but GH is not going to disclose what it will do, at setup time. If GH disclosed their secrets it wouldn't seem so magic to the lay crowd. Amazon has some of that too, but not quite so interfering with HA, yet, and likely jealous of GH too. Alexa performs with much less conceptual change.

I found the same AI BS with GH as anrdewm above. GH artificial intelligence is not wanted in the case of HA usage. Perhaps if GH only knew about individual devices it could work, as it wants to auto-create all the groups, scenes, and rooms, by itself and there isn't enough room for two smart devices (ISY and GH). I avoid GH for my ISY control and just use Alexa. It's dumber actions are so much smarter, when it comes to HA. GH is much better for information look up and playing games.

That would likely be your work system blocking access to certain URLs/IP address ranges. No port forwarding is required for ISY Portal. ISY Portal is a DDNS type service and they already know who you are so no other setup is required.

If your battery devices don't support that (my 12 MSes don't) you will end up with an ISY with a flooded to do list, that will bog down your system so badly that a simple MS to light scene will take over 30 seconds to get a simple light on. These features can be a dangerous ones and the explanations are not good in the admin console.

For economy I would try to put dual band devices near the centre of the house (assuming PLM is in centre also) and the single band units on the perimeter uses.

Welcome to the UDI forums!! If the device's status page does not show it's status changing from On to Off with the light then the switch and yur ISY PLM are not communicating. You could have interference on your power lines, too much distance (wiring and air distance) betwen the device and your PLM, or a missing link between your device and ISY. How many Insteon devices do you have in your system? I assume the switch is an Insteon module.

X10 used to make a device Rex-10 you hang on your door which pounds the door and barks in a loud volume.

The ISY Portal has a way of initiating many speech texts out of an Amazon speaker but they are all in Alexa's voice from straight text. I started developing an mp3 file player into my Alexa speakers, triggered from ISY via Rest but I could never get the Alexa speakers to interact with my RPi Bluetooth. Connects OK but refuses to accept input.

Did you do the factory reset and ISY restore (as Paul suggested but no response or acknowledgement was seen.)? I wouldn't give up so easily yet. Try it again as they can be tricky to not let the tab slip back into the connected position before depressing for the long hold, and the factory reset will not happen, then. As you said these things are expensive, a PITA to replace and patch all your programs to work again, without mistakes that crop up later.

I hear that but I don;t consider those setting menus as device status fields. You cannot use them for programs either. They don't exist in the falldown menus.