Goose66

I received mine on Wednesday (Dec. 13) this week. Ordered on Nov. 6. Came via USPS. No shipping notification. No tracking number. I sent an email last week to the guy and he just said shipping as fast as he can and referred me to the shipping status page at https://paulwieland.github.io/ratgdo/09_faq.html. Flashing with firmware and configuration very easy. Working with my MQTT broker on Polisy. Bug I have Genie GDOs so I am having to do dry contact install paralleled with my limit switches so install a bit trickier. I have lined up somebody with Chamberlain GDOs to do initial testing of ratgdo plugin this weekend but he hasn’t gotten his devices yet. Ordered them same day I did. Hoping he gets them today.

Uh… yeah. Oops.

If your are using the public MQTT broker on Polisy/eISY, it is the local IP address or hostname of your Polisy/eISY and port 1884. i believe the MQTT Plugin has to be configured for the same broker settings, but I don’t use it. The ratgdo plugin will default to the Polisy/eISY public broker but you can set an external broker if you wish (just like Tasmota plugin).

Mine was "NO" as well. Did the Reconfigure, and after about a half an hour or so (the Polisy rebooted), it switched to "YES" and now I am getting events from Ring. It's been a while since this has worked, so the change must have taken place a while back. I wasn't fully understanding the significance of this setting and wasn't aware of the requirement for the Ring node server. But I did look and see that it is in the UD Developer documentation here: https://developer.isy.io/docs/API/pg/Webhooks Looks like not until PG3x, however, which doesn't make a lot of sense. But oh well, it works now so all good. Thanks for the tip!

All that said, my Ring node server is not working - not generating events. It has been messed up for some time. Hopefully you will have better results.

The node “Front Door” should generate a DON command on button press. It shows up in programs as “Ding” command. It is supposed to be able to drop into scenes as a controller.

It’s already there and running in the Polisy. It will be a matter of configuring the connection to it on the ratgdo. Like the Tasmota plugin, I would expect there will be instructions on how to configure ratgdo to work with the plugin.

Looks like both ratgdo and tailwind have push mechanisms for status changes (no polling).

Yes, ratgdo hardwired to GDO, ratgdo connected to Wi-fi, and ratgdo communicating with MQTT broker on Polisy/eISY. I don’t think that the MQTT plugin (node server) supports garage door openers, so we would need a custom plugin to support ratgdo. You could also probably use network resource. I would convert MyQ code. Too bad Tailwind doesn’t do MQTT or we could roll both into one node server.

I get that too. Something in whatever version IoX I have. Hopefully will stop in some future release.

For the node server (plugin) to control the brightness, the Bond bridge has to report a SetBrightness command for the light. This depends on the remote template used to control your fan. Just simple “bright up” and “dim down” commands don’t work for lights without discrete brightness setting, because Bond only supports a start fade and stop fade approach for those lights which doesn’t implement easily or work well with, e.g., Insteon->IoX->plugin->Bond communication.

Same on the Tailwind website: it mentions a local API but there are no details on what it is or how one accesses it.

When I was required to have OpenJDK on my PC, I started the finder like this: java -jar .\downloads\isyfinder-2.0.jar Put it in a "startiox.bat" file. I didn't have too hard of a time finding a copy of isyfinder-x.jar file on the web, but you may have to put in a support ticket to get @Michel Kohanim or @Chris Jahn to post a copy.

Still haven’t gotten mine.

I see a "failed due to bad credentials" in your log four or five times over the course of the day. But it always succeeds a minute later on the next longpoll. I actually got one of these today myself. Based on the timing (the few in your log are exactly one hour apart) it appears to me that the oAuth token is expiring before automatically refreshed, so the pyschlage library just refreshes it on the next call. I will put it in the To-do for the node server to remove the warning message from the PG3 dashboard, but since the node server remains functional (it's just a warning), you can just ignore these errors for now.

My Schlage node server is currently working. Just restarted to verify. Please send a log package.

That’s pretty straightforward. It should restart the BPUP listener thread, however. I believe it does it in the next longpoll? I will look into it when I return to the U.S. in a couple of weeks.

Schlage Encode locks gave a node server but I don’t know if they make a fingerprint version.

Must be a first time upgraded. When you upgrade IoX, you have to clear your Java app cache before restarting IoX Launcher.

Here's something to try: using curl try posting to each thermostat with temperature values in floating point format, i.e. instead of "71", try "71.0". I am wondering if that works for ColorTouch but not Explorer.

Nevermind. I didn’t read thoroughly.

The BPUP_Listener is run on a separate thread and opens the socket to listen for BPUP events. If that thread is dying for some reason, that may be the problem. Mine has been running for months, however, and the thread stays up.

+1 for what @Techman said. Also, can you just turn off the basement light at 9:00 pm? In other words, why check if it is on first?

Two things: 1. This sub-forum is specifically for the Tasmota Node Server. The Tasmota Node Server supports a specific list of devices running Tasmota (primarily from Martin Jerry) that fall into several broad categories: Switch, Plug-in Module, Dimmer, Fan Controller, and Humidity Switch. I hope to add new device support for devices falling into these categories and new categories as we go, but this node server is not intended to support generic Tasmota devices with custom states or properties. For that, I suggest trying the generic MQTT node server that is available in the Node Server Store. 2. For Tasmota community support - particularly rules - I suggest the "Tasmota" server on Discord. There is a specific channel for discussions regarding Rules.

The Bond node server relies on two mechanisms for state updates. The first is polling the Bond Bridge via a REST API every shortPoll interval (the node server also uses the REST API to execute commands). The second is a UDP socket connection over which the Bond Bridge streams events in real-time. Bond refers to the UDP socket connection mechanism as "BPUP." When you execute a command on a device connected to a Bond Bridge, the corresponding change(s) in state for the device should be streamed back to the node server via BPUP and your IoX should update in real-time. If this is not happening for you, then something is wrong with the node server on your platform and we need to debug what's going on. I will need log file package from the node server in DEBUG-level logging and containing a restart of the node server in order to determine why BPUP doesn't seem to be working for you.