maxnorth

My recollection is that the IP for the M1xep is set in the Elk settings. I use ElkRP software for that. It is located in the Account Details tab.

# Store in /usr/home/admin/ # No SSH required, Command to copy file FROM cd current directory (e.g., Mac desktop) to eisy # Replace with your own IP and user name and dev file name scp 2025-10-10-devfile.yaml admin@10.20.30.xxx:/usr/home/admin/

I believe the best approach is to create a scene including your relay. Then use programs to have the scene turned on and off (including by the KPL). For the light on the KPL button, that is another story. Create another scene including the KPL button. In the program controlling the relay, add an entry to turn off the KPL button scene when the relay is turned off.

I, too, would like to know if there is anything in process to fix the Elk problems related to the upgrade. I am holding off on the upgrade to 6/7 until this is more stable. I am unclear if this is a node server issue or something else. Clarification on that would be helpful.

I don't live in an area affected by lightening, but we do have periodic power outages during the winter months. I had several Insteon devices fried during outages like this. After installing a single whole house suppressor, I have not had any.

I have used darwin.kenyonralph.com successfully.

Ah, yes, "TelePeriod 20" does in fact set this to 20 seconds. Nice to be able to set this on a per-device basis! Thank you!

I am wanting to work with the power readings thrown off by the S31POW. I notice that polyglot seems to retrieve these readings using some sort of polling. They only update every three minutes (per the log). Not very helpful when you have an application needing more frequent readings. The Sonoff itself updates immediately, it's just that Polyglot does not get the updates promptly. Is there a setting somewhere that this can be changed?

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"

I always use a program to control the LED status, and I have the button set to non-toggle off. Pressing the button turns everything off.

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.