maxnorth

You don't really send commands to sensors. Here is a screenshot from a Tasmota device console for a switch. If you have a more specific question, let us know. In this case my "status topic" configured in Polyglot is "stat/sSlamphC/POWER"

To answer my own question, the correct type to use is "TempHumid." This is working now. It might be helpful to update the configuration help to list the SI7201 sensor as an acceptable sensor for TempHumid.

I believe that if you then want to set up the S31 as a switch, you would create a second device for that, using "switch" type.

I can't figure out what node server yaml entry to use for this setup. I tried the types "analog" and "Temp", but the resulting node device does not show any temps. My tasmota config identifies the Sonoff THS01 temp/humid sensor as a SI7021, and that config is working fine in the Tasmota web setup. It show readings. I am using "SI7021" in the node server as the sensor ID. From the Tasmota web console: "18:08:48.992 MQT: tele/sSonoff_THR316/SENSOR = {"Time":"2025-05-18T18:08:48","SI7021":{"Temperature":68.7,"Humidity":51.3,"DewPoint":50.0},"TempUnit":"F"} I also have a "switch" device for the TH Origin. It is working fine in the node server and the switch device appears in order after the sensor device. Below is an example: - id: "sSonoff_THR316Sens" type: "Temp" name: "AtticSwTemp_145" sensor_id: "SI7021" status_topic: "tele/sSonoff_THR316/SENSOR" cmd_topic: "cmnd/sSonoff_THR316/power" - id: "sSonoff_THR316" type: "switch" name: "AtticSw_145" status_topic: "stat/sSonoff_THR316/POWER" cmd_topic: "cmnd/sSonoff_THR316/power"

I seem to recall there was a problem in not being able to see the config help screen for the plugin unless you enter some data first. Not sure if that was fixed. In any case: https://github.com/Trilife/udi-mqtt-pg3x/blob/0.40/POLYGLOT_CONFIG.md

Install the MQTT nodeserver from the plugins store on the PG3 home page, by trilife. Note that they do not necessarily appear in alphabetical order in the store.

I finally installed my RatGDO and faced a similar problem. Here is my experience. If you just want your KPL light to come on when the door is open and off when closed, simply create a scene with the RatGDO and the KPLs involved, and it should just work. If your KPL is set to "toggle" mode, when the toggle sends an "on" the door will open and the KPL light will come on. When it sends an "off" the door will close and the light will go off. In this scenario, you should not use a separate scene to control the LED, because your door will no longer work properly if the off/on status of the KPL gets out of sync with the actual door status. In my case (previous IO Linc user), I have always had my LED set to be on when the door is closed. That provides me positive confirmation that the door is actually closed, whereas no light does not. I have three KPLs with garage door buttons. So, how to do this? I do not put the RatGDO and KPLs in a scene together. The method I used was to set my KPL buttons to non-toggle (on). So, every press sends an "on". I created a program that says anytime a button "on" is received, "toggle" the RatGDO. This program is dumb -- it does not care about door status. Then, to control the LEDs I created a scene containing only my KPL buttons. I created two programs. When RatGDO door status is closed, turn the scene on (the LEDs turn on but no command is sent to the RatGDO). When door status is open, turn the scene off. This seems to work perfectly fine. This is not needed if you are content with having the LED on when the door is open.

This happened to me with the Tasmota node server at one point, and the developer fixed the node server.

I currently have a contact sensor to detect the garage door position, with the IO Linc. Is it true that with Security + 2.0, I no longer need that? The door position is signaled by the control board on the opener?

I am considering switching to the ratdgo from Insteon IO Linc for reliability reasons. I am tired of having my garage door open by itself, due to "all on" events or other reasons. I currently have a lock out on my IO Linc that I activate when out of town, but that is not enough. My question is whether users have been satisfied with the reliability of the ratdgo from a security perspective. I have an eisy, Home Assistant/ESPHome, and HomeKit integration. I could just use HA with the ratdgo if introducing the node server would increase security concerns. But using the node server in addition would make program development easier. Are people using electronic lockouts with the ratdgo? Thoughts?

If you can use the Home Assistant to ISY integration and ESP Home, Apollo MSR-2 presence sensor. Uses a LD2410B mmWave board. Radar. Very sensitive and very configurable. It completely solves all of my presence issues. Also has an issue with false positives, so it is best used for "off" programs only, not "on." You can also build your own using a C3Mini ESP-32 board.

Same behavior here, although I am on 5.8.4.

You have a choice on Synology (depending on your model) of using Docker or the Synology Virtual Machine Manager (VMM). The former is quicker and easier to install, but more laborious to update over time. The latter is harder to install but will give you access to all the features of the Home Assistant Operating System over time. (HA is improving its own voice control capability, by the way).

I believe the basic approach for controlling KPL LEDs is to create another scene with only the LED in it. Then create a program that will turn that scene on or off. When the garage door is open, run the program to turn the LED on. When closed, off. (fwiw, I have mine set to turn the light on when the door is closed. It's sort of a failsafe so I know it is working properly.)

Thanks. On my Mac, it does not remember the path.