John Vickers

This has happened to every switch I have tried so far. I was just working along these lines of exploring the link tables. It looks like somewhere along the way of updating the PLM, my ISY tables lost the address of the PLM. This may be from before I knew my previous PLM was toast, I tried restoring it, which may have zero'ed out the addresses. The ISY and Device table were matching on the fan that was not responding correctly, but the first 4/5 address were all 0. After deleting and re-linking the fan, the address for the new PLM showed up in the first 4 links. Is there a way I can edit the full ISY link table as an XML? I should be able to do a find/replace on the 4 address types for switches and dimmers to replace the 0 address with my new PLM address? Then I should be able to do a Restore devices to push the ISY table out to the devices themselves correct?

Second restore PLM made no difference.

I would have to go through and count, but it is around 34 devices. I don't really want to upgrade until I figure this out. This version was working for me quite well before, and none of the fixes listed since then really apply to my network. It really seems like the issue is the switch not knowing which device to send it's update messages too since they are not showing up in the diag event viewer, but the switch is responding when it receives commands from ISY. What I don't understand is why just relinking the switch without removing it from ISY isn't working.

My old PLM died, thankfully Insteon just started shipping their new upgraded PLMs with better caps for supposed better longevity. So this is a brandy new PLM hot off the presses! PLM table has 75 entries. Firmware and UI are both V 5.3.0 LED is solid green. Rebooting the system (PLM then ISY) didn't help either.

Same behavior, no change.

The red light no longer blinks when the switch is changed locally, but the status is still not coming back to the ISY994i. I also checked the event log this time set to level 3, when the switch is pressed, nothing is coming up in the event log. Another switch right beside it that I did delete and re-link does have a lot of traffic in the log when switched locally.

I just replaced my PLM modem with my ISY994i. I did the File / Restore PLM sequence, and it completed successfully. Here are the symptoms: If I tell a switch to change status from the ISY, it does change and the status of the switch updates to the commanded state. If I change the switch locally (IE press the switch directly), it will change, but there is a red flashing light and the ISY994i status doesn't update. If I re-link with any of the linking options, there is no change. If I delete the switch and re-link, it will work properly. I don't want to rebuild my network from the ground up as that would be very tedious. Any ideas on how I can repair the links to get all the devices to report to the new PLM properly? Thanks! John Vickers

ISY is controlling the Insteon devices directly. I am using Home Assistant with the ISY integration, and then using the HomeKit bridge to allow Siri to control lights as well. So even the first bridge when I use the ISY interface from my computer to send any of the on commands (on, fast on, fade on, brighten) when the dimmer is already in the 100% state, the program doesn't fire. John Vickers

OK, what the hay.... I had a test program very similar to this except I was turning off the fan switch right beside the dimmer instead of changing a variable so I could immediately see if it was being triggered. It was not at that time, but is now. I can only assume I didn't save the program or something stupid like that.... One note with the "Control is on" option, it does not fire when another controller in the scene turns on. IE if the Master is on, and one of the slaves turns on, it will not detect that if you only have the Master is On programmed. If you have all the switches with an "control is on" and all of them with Ors, that will work as MrBill stated. New Program - [ID 0029][Parent 0038] If 'Hallway / Hallway Dimmer' is switched On Or 'Hallway / Hallway Dimmer Slave 1' is switched On Or 'Hallway / Hallway Dimmer Slave 2' is switched On Or 'Hallway / Hallway Dimmer Slave 3' is switched On Or 'Hallway / Hallway Dimmer Slave 4' is switched On Then $GarageLightLastLevel += 1 Set 'Bedroom 2 / Bedroom 2 Fan' Off Else - No Actions - (To add one, press 'Action') I had misunderstood the logic of the programs first read through. I missed that the overrides are disabled until one of the doors is opened. My thought before was also predicated on not thinking the "control is on"s would fire if the light was already on. The last piece of the puzzle that doesn't seem to be working is remote control triggering this program. If the dimmer is already at 100%, none of the options you can send from ISY will trigger the program (on, fast on, dim up, fade up). If the dimmer is off when a remote command is sent, that will trigger the program, just not when it is already at 100%. Any thoughts on that piece? John Vickers

MrBill, Yes everything is Insteon, sorry I forgot to put that in my first post. You tackled this in a different way than what I was thinking. Your programs are centered around not even starting the timer if the lights were on in the garage when it was first opened. In this scenario if someone was working in the garage and manually turned on the lights from any switch, people could come and go through the garage door without changing the light state. That isn't what I was trying to do, but an interesting thought. I may end up using that. What I was trying to do however was to detect any intervention in the light state when the countdown is active to cancel it. IE if someone is in the garage working on something, they can keep the lights on by hitting any switch in the garage within 5 minutes of both doors being closed. Since my current garage isn't really a work space for anything (just storage) I was prioritizing making sure the lights were not left on accidently since they are power hogs (high bay garage so I have 200W of LED lights just to get semi-decent light in there!). The problem I am having was finding a way to activate a program anytime any switch was pressed, or remotely controlled through the ISY. If you set the IF clause to "Control is ON", that will only respond if it was not ON before. IE if it was ON and you press the up paddle, nothing happens. It also doesn't trigger when the light is controlled remotely. I tried using "Dimmer is Responding" line by itself as I would think that event would fire regardless of what is happening at the switch, but it doesn't. If anyone has any ideas on how to get an ISY program to run anytime something happens to an Insteon dimmer, even if it ends up not changing its state, I would love to hear it! John Vickers

So here is what I am trying to set up. In a garage I have the following currently set up: An overhead light that has 4 dimmers to control it (4 entry ways). All 4 dimmers are in a scene so 3 are slaves and one is the master connected directly to the light. 2 garage doors with state sensors I have some automations that do the following actions: when either door shuts (if they are both shut at that time), a 5 minute timer will start. At the end of the timer the overhead light is turned off. When either door opens, it turns the overhead light on, and stops the turnoff timer The last piece that I want to implement is detect if any manual intervention with the light happens during the 5 minute timer, disable the timer. I am not finding a good way to detect any action on any switch, or any remote command from my home automation stuff. Does anyone know a concise way to do this? Thanks! John Vickers

I have a Zooz Zen15 connected to my ISY, but I need to get the firmware version of the Zen15 device. Is there any way to do this through the ISY interface? Thanks! John Vickers

Thanks dbuss, that did the trick. For others coming across this thread, the piece I was missing is not all devices have the "responding" option. It is a condition under status for a device. In my case the meter device is a sub item under the switch. The switch had the "responding" option, but the meter didn't. The other piece I am still tweaking is the run time alerts. I have one program that keeps track of how long the freezer has been off: Pantry Freezer Last Run Time - [ID 0006][Parent 0010] If 'Pantry / Freezer Switch / Freezer Power Meter' Status <= 5.000 Watts Then $FreezerMinutesSinceLastRun = 0 $FreezerHoursSinceLastRun = 0 Repeat Every 1 minute $FreezerMinutesSinceLastRun += 1 $FreezerHoursSinceLastRun = $FreezerMinutesSinceLastRun $FreezerHoursSinceLastRun /= 60 Else $FreezerMinutesSinceLastRun = 0 $FreezerHoursSinceLastRun = 0 Then I have an alert program that would fire every morning if the freezer has not been on for more than 6 hours (normally it has about a 30-45 minute cycle so it would have had to be off for quite a few cycles at that point): Pantry Freezer Alert - [ID 0007][Parent 0010] If Time is 7:30:00AM And $FreezerHoursSinceLastRun >= 6 Then Send Notification to 'John Only' content 'Freezer Down Time Alert' Else - No Actions - (To add one, press 'Action') Hopefully this helps someone else as well! Thanks again, John Vickers

I know if I query the device when it is not powered I will get a popup saying that the request failed. I am not seeing any way to tie that into a program to send an email if it fails to many times. Can you give some instruction on how to tie this into a program, or point me to a link that has some info? Thanks, John Vickers

How do you check for a response to a query in the programming language of ISY?

I am new to the ISY, so sorry if this has been answered somewhere else! I am looking for a way to have a program detect a loss of connection to a ZWave device. I am setting up a watchdog on a chest freezer and am using the Zooz Zen 15 appliance switch. I have a program set up where I can look for a loss of power draw, but I also need to know if it is still connected to make a robust system. On way I thought of doing it was to update a variable every time it gets a power report, then have something that triggers if that time delta has become to large. I am not sure what the best path to doing something like that would be. Any suggestions from those more familiar with the ISY994? Thanks, John Vickers

I am new to the ISY, so sorry if this has been answered somewhere else! I am looking for a way to have a program detect a loss of connection to a ZWave device. I am setting up a watchdog on a chest freezer and am using the Zooz Zen 15 appliance switch. I have a program set up where I can look for a loss of power draw, but I also need to know if it is still connected to make a robust system. On way I thought of doing it was to update a variable every time it gets a power report, then have something that triggers if that time delta has become to large. I am not sure what the best path to doing something like that would be. Any suggestions from those more familiar with the ISY994? Thanks, John Vickers