Goose66

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.

I had a friend that had this same issue. He tried everything: Mac, PC, drivers, different cables. Then I took my laptop and cable that I used to configure mine over to his house and tried and got the same thing. Just a bad device, I presume.

That makes sense. I’ll have to think about how we should be handling that, but I will log a change for the next version.

But… thinking about this, when it comes online it won’t repost its state values (the ratgdo uses retained messages) and there is no periodic query of state, so if it does go offline and the states are set to unknown, they will remain unknown until they change (assuming the ratgdo is back online when the change occurs).

Should only happen if the ratgdo devices go offline.

I've had put in a note to fix it in next release. But as I mentioned, it is a non-fatal connection error very infrequently returned from the Schlage API the plugin uses, and the data is updated on the next poll. But it adds the notification when the error occurs. So even though it's logged as a warning and the plugin recovers on the next poll, the notification just hangs out until you clear it. Shouldn't cause any issues in the operation of the plugin.

If it is “built upon … ratgdo software libraries” like it claims, it may be easy to work it into the ratgdo plugin.

If we could get the query to work in the ratgdo firmware, that would help too.

Resetting the status values to “Unknown” when the device goes off line is something I’m doing. I don’t really use it in programming though, so if it’s hanging other people up, I can remove it.

No worries. And I did take away your vote for option 2 (sans the separate node 😜). But now that I think about it, there's absolutely no reason not to do both option 1 and option 2 at the same time, so that's probably what I'll go with.

I addressed the idea of the “motion” node in the text above. Would just be an extra node that always said “online” but otherwise never generated a node event for the majority of users.

Selecting "Chat with a specialist" at the bottom of this page: https://www.resideo.com/us/en/support/

I chatted with Resideo support. They can see my thermostats and the "ISY Node server HomeAutomation" app or integration. This particular support rep doesn't seem to think anything has changed on their end. I wonder if the current problem lies with the authorization step. It asks you to specify "https://udi-honeywellhome-auth.azurewebsites.net/auth" as the authorization callback. This appears to be a website created by the original developer dbarentine 5 years ago. I wonder if it still functions? Sounds like this plugin needs to be brought up to newer standards and more tightly integrated with UD's oAuth and websocket infrastructures. Still doesn't explain why resideo support is not responding to password reset requests, however.

I believe this plugin was ported from PG2 by @bpwwer several years ago. I don't believe the original developer is involved at this point.

So you can no longer log into https://developer.honeywellhome.com/?