gzahar

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

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

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

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.

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

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.

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.