@Goose66 was talking about developing a Shelly plugin some time back.

 

Try connecting directly to PC and erase all data when loading firmware.

On 9/8/2024 at 10:08 PM, CJVann said:

I'm programming an Insteon keypad to control an Insteon Fanlinc.  The button for "Fan Off" is set to Non-toggle Off, but the LED turns ON if you press it.  It's confusing that "Off" is always lit up whether the fan is on or off, so I prefer it just not light up.

Is it possible to have it stay off without writing a program?   I'm moving and want to take the EISY to my new home, so I'm not able to use programs to force it back "Off" again.  You'd think non-toggle On would stay lit, and non-toggle off would keep the LED Off, but the button stays lit either way.  Thanks...

Make sure the scene that turns the fan on includes the off button with a status of off.

4 hours ago, mdfled said:

I opened a ticket on this error as my YoLink devices aren't working any longer after I did the latest updates.  I've checked all the logs, and the error you posed above is the error I'm seeing in the YoLink node log when I restart the node server.  Can you please tell me how to fix this?

If you have a plugin with the error, delete and reinstall the plugin.

The owner of the plugin has the PG2 version of the code on GitHub. The mappings didn’t change when it was converted to PG3. Also, I believe the A/C normally shows these starting with ST then GVx in numerical order, but there may be exceptions.

ST-ACP-ST-NAME = Alarm Panel Connected

ST-ACP-GV0-NAME = System Alarm State

ST-ACP-GV4-NAME = Bell Trouble
ST-ACP-GV5-NAME = Battery Trouble
ST-ACP-GV6-NAME = AC Trouble
ST-ACP-GV7-NAME = FTC Trouble
ST-ACP-GV8-NAME = Tamper Trouble
ST-ACP-GV9-NAME = Fire Trouble
ST-ACP-GV10-NAME = Zone Fault
ST-ACP-GV11-NAME = Zone Sensor Low Battery

On 6/8/2024 at 7:21 AM, CopyRon said:

trying to set up Kwickset Zwave lock with mini remote so on activates lock and off activates unlock.

I got to on to lock but can't figure out how to make oo unlock

Thank you!

Post your "on" program and "off" if you have one you tried.

I received the following instructions from another member that fixed mine:

1) Z wave compatibility mode on

2) Z wave validation off

3) Z wave rewrite all device links

After this happened the second time to me, I was going to report the problem. This was before there were many others reporting this issue, so I didn’t know if it was just my device or not. Anyway, first I wanted to try to figure out how often this was happening. To do that, I created a program to ‘blink’ the light on the GDO when it detected I was in the garage. I was hoping this would allow me to catch when the control stopped working as I don’t normally use the that feature often. That has been at least several months ago and it has not ‘locked up’ since I did this. It may be very premature to say this, but it seems that if you send control on a regular basis, the problem doesn’t happen.
I would be interested to hear if others that have the problem use their control feature daily?

You might also check the event viewer or program summary tab sorted by last time run to make sure it’s not being turned on/off by a program.

12 hours ago, Goose66 said:

If you are using Security + 2.0, you can try and reinstall the firmware and choose the "Erase" option which will force the generation of a new client ID for communicating with the door.

That is what prompted me to try the re-flash/erase option.

2 minutes ago, hart2hart said:

Do I have to do this from USB port or can I do it with OTA flashing back to the same version it’s already running 2.57?

Don't know.  I have not used OTA flashing.  I think using the erase option is key (not sure) and that is probably only available with USB.  But give it a try.

I see the issue.  The key values used to be tied to variables (and their ids) when the plugin was first created.  They aren't anymore.

As stated each key must be unique, you can't use 78 more than once.  There is no reason to not start with 1, 2, etc.

For the value, you need to put in the word switch, dimmer, etc.  This will create a node in the eisy labeled 1 (maybe with a nxxx_ prefix, I don't remember).  You can then rename it (on eisy) whatever you want.

7 minutes ago, Goose66 said:

It looks like from the logs you sent that the door state wasn't changing from the door commands, but the light state was changing correctly based on the light commands. 

This was similar to the response you sent me.  The AC responds that the light turns on, but it doesn't.  It does seem to be the ratgdo not communicating properly with the gdo.  I was not sure if I had a bad device or this was happening to others.  Wanted to get more data if I could (how often, after some particular event, etc.) before opening an issue on github.

Mine has done this twice.  Continues to report status correctly, just won't control.

Unfortunately, only solution to re-flash (with erase option) and re-install.

I have recently tried to put in an automated use of controlling the light so that I notice how often/when it actually happens.

Post a picture of your configuration page.

Yes. I do that. You can use network resources to control A/V equipment. Some devices can be controlled directly over IP network and devices that are IR only can be controlled with the use of IP to IR converters. Look at the Global Cache Flex IR devices for that. There may be cheaper alternatives also, haven’t looked in a while.

Currently sold out…

1 hour ago, paulbates said:

$Sump_Pump_Monthly_Gallons  = $Sump_Pump_Gallons_Daily

This looks suspicious.  Agreed you may be changing the day and rerunning before it completes.  Do the values change right at midnight so that if it reruns, you would get the wrong results the second pass?   Nevermind, if the days changes it would not run again right away.

If it is all Insteon, put the devices in a scene and turn the scene off.

2 hours ago, rg65 said:

I've come across a need for a program and can't figure out how to write the IF statement.

We have a long driveway without a view to the garage door and we ALMOST always close it without thinking about it. I have a tilt sensor on a garage door that is obviously closed most of the time.  I already have a timer that notifies me if it is left open, but I would like to know before we leave the house.  I want to run a program on the transition from open to closed but there is no option in that device for "changes and becomes" to qualify the event.

I'm sure there is a way, but I'm having no luck making it happen.

Ultimately, I am going to flash the driveway lights at the street a couple of times so we have verification the door closed.

Eisy - 5.8.0

IF device = closed

THEN flash lights

This will run whenever the device transitions to closed.  There is no need to qualify it any more.  It will not run [THEN] again until the devices changes to something else and back to closed.  (It will run ELSE statements whenever it leaves the closed state)  You may want to add a several seconds WAIT before the flash lights depending on the device.  This will de-bounce any open/close back and forth states during the transition that may start your flash routine several times.

28 minutes ago, glacier991 said:

As I am working through the final stages of installing my new ISY, I discovered that somehow I inadvertently deleted the Notification Server" item in the AC tree. 

How can I get that back?

 

Restart the plug-in in PG3.  You may also need to restart the AC after that.

Short answer is, it is working now.

I thought I would try to setup control through HA using MQTT and didn't know enough to get it working.  Actually appeared to lock up the device after entering some configuration data incorrectly.  Then I decided to flash it with the firmware meant for HA and that went very smoothly and was able to control door with HA.

So then switched back to MQTT / PG3 setup and that seemed to do the trick.  Only difference that I know of this time around is I check the 'erase all data' box when I flashed the MQTT firmware.  Who knows... Hopefully it continues to operate and I don't have something going on that corrupts the device after some time.

Thanks again for the plugin!

I agree it looks like the ratgdo is the issue.  I guess I haven't played with it for a while until doing the upgrade, so it may have gone unresponsive before then.  I will take it down and reflash to see if that changes things.  I think I hit the lock command as one of my first things, because that status was unknown.  Maybe I locked myself out somehow?  It does report as being unlocked though.

6 hours ago, hart2hart said:

For motion testing with 3.2.5, I created following programs to catch based on motion event and motion status.  I walked past the motion sensors on keypads and they appear to react to me by display and backlight changes.  However, neither program become True.  I didn't delete and re-add the nodes or openers after the NS upgrade, should I? 

Test GDO Motion Event

If
        'Garage / Garage:Paul Garage Door' is switched Motion
 
Then
   - No Actions - (To add one, press 'Action')
 
Else
   - No Actions - (To add one, press 'Action')

 

Test GDO Motion Status

If
        'Garage / Garage:Paul Garage Door' Motion is Detected
 
Then
   - No Actions - (To add one, press 'Action')
 
Else
   - No Actions - (To add one, press 'Action')
 

 

I will PM the log package 

 

I also ran a motion test and it seemed to work just fine.  I did completely delete and reinstall the plugin due to other issues.

Here was the output from the event viewer.  And my test program did trigger (more often than expected; using the switched/DON3 condition).

Wed 01/31/2024 11:39:14 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:39:14 PM : [n001_ratgdo47285]      GV3   1 (uom=25 prec=0)
Wed 01/31/2024 11:39:19 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:39:24 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:39:24 PM : [n001_ratgdo47285]      GV1   1 (uom=25 prec=0)
Wed 01/31/2024 11:39:27 PM : [n001_ratgdo47285]      GV1   0 (uom=25 prec=0)
Wed 01/31/2024 11:39:34 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:39:39 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:39:44 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:40:54 PM : [n001_ratgdo47285]      GV3   0 (uom=25 prec=0)
Wed 01/31/2024 11:49:44 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:49:44 PM : [n001_ratgdo47285]      GV3   1 (uom=25 prec=0)
Wed 01/31/2024 11:49:48 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:49:53 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:50:04 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:50:09 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:50:24 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:50:29 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:50:34 PM : [n001_ratgdo47285]     DON3   0
Wed 01/31/2024 11:51:40 PM : [n001_ratgdo47285]      GV3   0 (uom=25 prec=0)