Goose66

I don’t know. I wasn’t involved in the PG2 warning.

I see the problem. It uses the first 14 characters from the "name" from the ratgdo for the node address. For the light, it lops off 3 trailing characters and adds "_lt". So while that's enough characters to distinguish "housegarage" and "housegarage2," it's not enough to distinguish "housegarage_lt" and "housegarage_lt". Rookie mistake. I will put something in the next release.

I need some info: 1) ratgdo firmware version, 2) control mode (sec+2.0, sec+1.0, dry contact), 3) debug level log file with you sending commands. One note: the plugin doesn’t change status when commands are received. It sends the command on to ratgdo and waits for ratgdo to report a changed status. If you are turning on and off the light and the light status in IoX is responding correctly, then it sounds like the problem may lie in the ratgdo.

First, check the EnvisaLink website to make sure your alarm panel is supported. Also, make sure you have the installer passcode or be prepared to factory reset the unit. If the Evisalink 4 will work with your panel, then the plugin will work as well.

I also hope to be using this plugin soon.

But yes, I will put a note in the plugin to add in the next release a "Stop" command for all blinds. The plugin will just ignore it for blinds that don't support stop, or maybe go ahead and send it and let the Bond bridge deal with the lack of support.

Can you not set the stop position for open in the blinds themselves? E.G., manually control the blinds with your remote to set the "Open" position? Two subsequent opens then open to 100%. That's how my blinds at my last house worked.

There is only one state here, and it reflects the lockout function of the GDO that prevents remote activation by RF controllers. The ratgdo publishes status messages for it with the topic ".../status/lock" and the plugin calls it "Lockout". It can have the values of "locked" and "unlocked".

I will probably change it to paid for new subscribers at some point.

Yes. The MyQ plugin is dead. It’s been removed from the Plugin store. My next step is to physically take down the MyQ hardware and toss it in the garbage.

This is done in new version v3.2.5. You need to delete and re-Discover your nodes to get the hierarchy.

I have published a new version of the ratgdo plugin (v3.2.5). This version adds both a "Motion" command (DON3) on motion detection and a Motion state that goes to "detected" on motion detection, and then "clear" approximately 60 seconds after the last motion. Motion is only supported on GDOs with Security+ 2.0 and control pads with a motion sensor. NOTE: You need to change your shortPoll to a smaller increment (such as 10 seconds) because the shortPoll is where it checks to clear the Motion state, and thus the shortPoll value is the maximum resolution for the 60 second timer for clearing the Motion state.

The Bond plugin doesn't dynamically build the profile of the nodes. Thus the node profiles are designed to support the broadest set of features for each class. In the case of blinds, that's Open and Close. What's the use case for automating a Stop command of a blind?

You don't need Java server. Write a local HTML page with buttons hooked to javacript functions to make the REST calls. The javascript can ignore the reply from the REST calls. Add one bookmark to the local HTML page and just use the buttons on it to control the devices.

Also, to clear up some confusion with the original photo, the black to white connection in box 1 is fine and normal in this type of circuit, except the white wire should have had a piece of black tape wrapped around each end (and particularly in the box 2) to signal to electricians doing after-work that the wire is being used as a hot wire.

Ghost voltage in travelers on long runs in a 3-way circuit is common. Never used to show up in older incandescent lighting, but I have had problems with LED bulbs in 3-way (or 4-way) circuits where the line was at one end and the load at the other with long run travelers in between.

Without logs or any knowledge of your configuration, I would say the problem is most likely with your Lincoln. You probably have your Lincoln set up to connect to your wifi while at home and when you arrive back home there is a period where the Lincoln is unsure if it’s on LTE or WiFi.

Did you restart the plugin after you added the numzones configuration parameter?

Look in the release notes for the plugin. It describes how to use the Custom Configuration Parameters to drive what nodes are created. The EnvisaLink doesn’t provide any indication of the configuration of the DSC panel. It defaults to 1 partition and 8 zones if you don’t set any configuration parameters.

If your motion sensor sends periodic “on” commands during continuous motion (e.g. Insteon MS), you could use one program: If Motion Sensor A is switched on Then Turn Switch B On Wait 5 minutes Turn Switch B off Else Nothing This would turn the light on on motion and turn it off 5 minutes after the LAST motion command was sent.

So what's the use case? Are you looking for robust monitoring of the smoke/CO detector status or just a way for your eISY to respond with additional functionality on an alarm, e.g., lights, door locks, HVAC shutdown, etc.? If the former, then yes, I would recommend a home security system with additional, actively-monitored smokes. If your security system can interface with the eISY (e.g., Elk or DSC/Honeywell with EnvisaLink), then you can get the additional functionality as well. If you are just looking for the additional functionality, then the second question is where is the other end of the three-wire circuit to your hardwired smoke/CO detector and do you have access to it? If yes, then you could get something like this: https://www.amazon.com/First-Alert-RM4-Smart-Relay/dp/B0039PF21U that will let you use a dry contact sensor to interface alarm status into eISY.

Excellent. I just updated the release notes, but I will go back and work in some of your screenshots with the next release.

If you click the link on number 1. in the instructions above, you get the "ratgdo Firmware" page. It says "There are several excellent firmware options available for ratgdo..." and then shows options for "ESPHome" firmware, "Chowmain Software Integrations" firmware for Control4 and Elan, Native HomeKit firmware, and "MQTT" firmware. It is the MQTT firmware you want to install. It appears from the PDF file you posted that you installed the ESPHome firmware, and thus you get that ESPHome status/configuration page when you click "Visit Device."

From the symbol at the top of the attached PDF file, I am guessing you installed the ESPHome firmware. You need the MQTT firmware. Looking at the firmware installation page now, it appears that it has changed substantially since I flashed my first ratgdo and subsequently wrote the plugin directions. I will need to update the release notes to make sure folks are selecting the MQTT firmware option for flashing. Specifically, under the MQTT option on the firmware page, choose "ratgdo v2.57, Security + 1.0, 2.0 & Dry Contact" from the dropdown.

Sounds like you are never accessing or seeing the configuration web page from the device itself. After flashing your device with the MQTT firmware (hopefully what you've selected) and setting the Wi-fi connection parameters, there should be a link on the last page of the firmware flasher to "Access your ratgdo." If it seemed to connect to the Wi-fi successfully and you don't see this link, or if the link doesn't seem to work, then you can access the ratgdo configuration web page directly through your browser at http://<ip address of ratgdo>. You may have to go out to your network router to find the IP address. Look through your connected devices for a newly added "espressif" device (how all ESP32-based devices show up in my router) to get the IP address. On this configuration page, you have to provide a password (don't forget it!) and this is also where you will specify your MQTT broker info. Follow the instructions in the Release Notes and Instructions for the ratgdo Plugin for configuring this (reproduced below for your convenience): Make sure the "Enable MQTT" checkbox is checked. Set the "MQTT server IP" to the IP address of your Polisy or eISY (unless using an alternate MQTT broker). Set the "MQTT server port" to 1884 (unless using an alternate MQTT broker). MQTT server username and password need not be changed if using the default Polisy or eISY broker. Leave the "Home Assistant Discovery Prefix" set to "homeassistant" unless you changed it for your configuration - see discussion of the "discoverytopicprefix" Custom Configuration Parameter in notes below.