evilpete

Are there any Zigbee buttons that work or "supported" ??

Please include: Manufacturer Name : ONENUO / IHSENO Model # : 22WYZ Link to sales/availability site(s): https://www.amazon.com/IHSENO-ZigBee3-0-Remote-Button-Zigbee/dp/B0CCCKKH27/?th=1 https://www.aliexpress.com/i/3256809496235355.html Key/desired function support Report DON/OFF events described in NodeDef but missing in NodeInfo NodeInfo: <nodeInfo> <node flag="128" nodeDefId="ZB05836_001_1"> <address>ZB05836_001_1</address> <name>ZB 5836.1 On-Off W Button</name> <family>14</family> <hint>39.0.0.13</hint> <parent type="3">26264</parent> <type>255.1.255.255</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZB05836_001_1</pnode> <rpnode>ZB05836_001_1</rpnode> <sgid>1</sgid> <typeInfo> <t val="103" id="ioxType"/> <t val="4742" id="mfgCode"/> <t val="SNZB-01" id="model"/> </typeInfo> </node> <properties/> </nodeInfo>NodeDef <nodeDefs> <nodedef nls="103" id="ZB05836_001_1"> <sts> <st hide="T" editor="ZB_ERR" id="ERR"/> </sts> <cmds> <sends> <cmd id="DON"/> <cmd id="DOF"/> </sends> <accepts> <cmd id="IDENTIFY"> <p optional="T" editor="ZB_IDENTIFY" id=""/> </cmd> <cmd id="QUERY"/> </accepts> </cmds> </nodedef> </nodeDefs>

I'm familiar with the hints described in hint.yaml file on GitHub, but is there a more complete list available somewhere? For example, I have a Zwave switch, which was assigned hint "4.16.0.0" a value not described in the document.. Other hints: Zwave switch :0.0.0.48 Zwave plug : 10.0.0.0 Zigbee plug: 10.0.0.0 Zwave : 48.32.50.53 37.45.61.165 Zigbee On-Off Switch: 48.32.50.53 Zigbee button: 39.0.0.13

Q: should we put together a list on the wiki of functional and nonfunctional zig devices?

THIRDREALITY ZigBee Smart Button Model # 3RSB22BZ https://www.amazon.com/dp/B0BJDWR3BC?th=1 Receive process button event. IoX v6.0.0 I am willing send capture log and/or buy/donate a unit if it will help

Can you give a pros/cons review? This is something I've been thinking about recently

I was able to link my Gen 4 Nest thermostat using the pairing code I got the pairing code though Google's "Home" App (Google Home App -> Thermostat -> Gear Icon -> Device Information -> Linked Matter Apps & Services -> Link Apps and Services -> Use pairing code) then added it using the UD Mobile app (Settings -> Matter -> Add Matter with Setup code) After a minute or so, the device was added, unfortunately only as a 'On-Off Switch' (the thermostat does respond to the On-Off commands) According to sources temperature and fan control are available <nodeDefs> <nodedef nls="103" id="ZM00002_001_1"> <sts> <st editor="ZM_OFF_ON_UNKNOWN" id="ST"/> <st hide="T" editor="ZM_ERR" id="ERR"/> </sts> <cmds> <sends/> <accepts> <cmd id="DON"> <p optional="T" editor="ZM_0_100_PERCENT" init="ST" id=""/> </cmd> <cmd id="DOF"/> <cmd id="TOGGLE"/> <cmd id="QUERY"/> </accepts> </cmds> </nodedef> </nodeDefs> <nodeInfo> <node flag="128" nodeDefId="ZM00002_001_1"> <address>ZM00002_001_1</address> <name>ZM 002.1 On-Off Switch</name> <family>15</family> <hint>48.32.50.53</hint> <type>255.1.255.255</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZM00002_001_1</pnode> <rpnode>ZM00002_001_1</rpnode> <typeInfo> <t val="103" id="ioxType"/> <t val="0" id="mfgCode"/> <t val="" id="model"/> </typeInfo> <property name="" uom="78" formatted="On" value="100" id="ST"/> </node> <properties> <property name="" uom="78" formatted="On" value="100" id="ST"/> </properties> </nodeInfo>

Third reality zigbee smart plug power monitoring not showing up Third Reality, Inc Model # 3RSP02028BZ https://www.amazon.com/THIRDREALITY-Zigbee-Smart-Plug/dp/B0BPY2KRHH IoX v.5.9.1 The device has no problem pairing, and is functional with on / off capabilities, but the power monitoring feature is not available. Note: under Xray: Device channel database object: ELECTRICAL_MEASUREMENT is listed

on my Ipad when I create a favorite the default note color is #71A6FA, I've noticed that if I change the color and then change it back to the value #71A6FA it's not the same. To reproduce add a new node to favorites, change the default color (eg: #71A6AA) then change it back to #71A6FA

Name: Aqara Water Leak Sensor URL: https://www.amazon.com/dp/B07D39MSZS I'd like this also, I have one and it connects but the note identifies itself as "main" with no attributes

Understood.. On a simular topic, it's already been noted that iOS and android backups are not compatible, but a way to export/import just favorites would be very convenient for copying "consoles" between device devices (and hopefully easier to implement 😀) btw: android should not even be allowed to import an iOS backup, it really fuckers the android app, requiring a purge and then reinstall (and a lesson turned)....

I placed a cheap ($11) usb fan from Amazon on top on the unit have had zero problems With the ambient temperature on my desk is around 71° [admin@eisy ~]$ ./get-temp.sh CPU0 26 C / 78 F CPU1 27 C / 80 F CPU2 26 C / 78 F CPU3 27 C / 80 F TZ0 27 C / 80 F Quiet 90mm Router Fan Cooler $11.99 2Pack Quiet 80mm USB Fan Dual-Ball Bearings $19.99

Is there a way to copy the advanced configuration settings in favorites one object node to another, for example, value based color settings on multiple temperature sensors.

Yeah, now that i understand what is going on more that's what I've thinking about with a few translation table based on protocol number... I was trying to use it as it at first not realizing it was special case mostly for Tasmota integrations

@sjenkins thanks I'll probably have to write a plug-in that interprets the output of rtl-433. it's written in C and the code focuses on SDR protocol decoding thus the input format is not gonna change (I contributed to code base a few years ago) after looking around they have some example code that does something similar for another product. Side Note: once done it will be trivial to incorporate pre-existing devices as input sensors Tire pressure: {"time" : "2025-08-04 18:22:45", "protocol" : 186, "model" : "Hyundai-VDO", "type" : "TPMS", "id" : "5173f60b", "state" : 48, "flags" : 8, "repeat" : 1, "pressure_kPa" : 248.875, "temperature_C" : 25.000, "maybe_battery" : 1, "mic" : "CRC"} Home security sensors (admittedly the neighbors') {"time" : "2025-06-30 22:14:47", "model" : "Interlogix-Security", "subtype" : "unknown", "id" : "51a4c2", "battery_ok" : 0, "switch1" : "CLOSED", "switch2" : "CLOSED", "switch3" : "OPEN", "switch4" : "CLOSED", "switch5" : "CLOSED", "raw_message" : "d24000"} Efergy home energy meter (also the neighbors', but hey, it's good for development input data) {"time" : "2025-07-31 19:01:36", "protocol" : 100, "model" : "Efergy-e2CT", "id" : 16386, "battery_ok" : 0, "current" : 18.781, "interval" : 6} Rolling code Keyfobs {"time" : "@0.843604s", "protocol" : 164, "model" : "Secplus-v2", "id" : 1959100928, "button_id" : 16, "remote_id" : 1959100928, "fixed" : "70678577664", "rolling" : "240124739"} Motion sensors {time" : "2024-09-27 19:28:26", "model" : "Skylink motion sensor", "motion" : "true", "id" : "1e3e8", "raw" : "be3e8"}

Thanks I'll do more studying.. I found a few filters that grok the json and publish the filtered results.

I am trying to feed data from my outdoor temperature sensor (LaCrosse-TX141Bv3). I'm receiving the data using an SDR dongle and passing it via mqtt. The data I'm sending to MQTT: {"time" : "2025-08-07 13:39:10", "protocol" : 73, "model" : "LaCrosse-TX141Bv3", "id" : 237, "channel" : 1, "battery_ok" : 1, "temperature_C" : 20.800, "test" : "No"} This is the json output from rtl_433 My devfile: devices: - id: "TX141Bv1" sensor_id: "temperature_C" type: "Temp" name: "Temperature" status_topic: "rtl_433/LaCrosse-TX141Bv3/temperature_C" cmd_topic: "rtl_433/LaCrosse-TX141Bv3/power" - id: "TX141Bv2" sensor_id: "battery_ok" type: "raw" name: "Battery" status_topic: "rtl_433/LaCrosse-TX141Bv3/battery_ok" cmd_topic: "rtl_433/LaCrosse-TX141Bv3/power" - id: "TX141Bv4" sensor_id: "test" type: "flag" name: "testFlag" status_topic: "rtl_433/LaCrosse-TX141Bv3/test" cmd_topic: "rtl_433/LaCrosse-TX141Bv3/power" MQTT Explorer reports: . But Im seeing . any suggestions? I'm guessing I am misinterpreting fieldnames?

that was exactly what I was thinking, there is plenty of room. as I said above, I have had zero failures of insteon devices ( not counting the PLM) ever since I installed a main surge protector in my main panel 8 years ago.

@bpwwer in rtl_433/examples there are some example python scripts that take the json messages and publish MQTT messages, is that what you are doing? The only issue i've had with receiving that you need to increase the sample rate to around 1500k or better, or sometimes (depending on the signal) use the other FSK pulse detector ( -Y classic or -Y minmax ). i have found it useful for occasional debugging by looking at the hops count field and / or packet duplication, If I do not see at least one duplicate I can assume there are connectivity issues as insteon has no routing thus you should see multiple packets via different paths I'm cleaning up my insteonrf stuff to use rtl_443 instead of my sucky home brew FSK demodulator as well as cleaning up the python. There is already code to transmit and receive Insteon packets with the CC1111 platform using the rfcat library with a Yardstick One or cc1111emk868 usb dongle. (I can also do it with a hackrf but that is more complicated)

I agree I'm better off with a new one (Amazon promises delivery by next week. by the 17th) II may install a MOV for surge protection in the new unit, I figure i can attach it via the screws on the inside in the plug (no soldering)

the Insteon 2448A7 Portable USB Adapter may be a good work around.. As for discontinued PLMs maybe their plan is to force people to use SmartHome branded Hubs? how fast is the Insteon market shrinking ?

@Michel Kohanim They stopped making PLMs?? interesting... with the rtl_433 program, I only contributed the protocol decoding part, the maintainers did all the heaving lifting implementing the demodulators. As for legality, I never signed a non-disclosure and thus was free to reverse engineer it. (https://github.com/merbanan/rtl_433/blob/master/src/devices/insteon.c) regarding making a product, if someone was to do this, i'd suggest building on the CC1111 chip instead of the RTL2832U chipset. With SDR dongles you'll have to do the demodulating of the raw I/Q data (aka the raw RF wave info) in software along with the accompanying CPU overhead (receive only) Where as if you use TI's CC1111 chipset family, the demodulation is done by in the chip, and you and can most likely get it done with cheap aarduino cpu at the a controller ( + you can transmit just as easily ) The or cc1111emk868 or Yardstick One are both based on CC1111 platform and allows simple transmit and receiving on the sub-1 GHz ISM radio bands. ( https://greatscottgadgets.com/yardstickone/ http://www.ti.com/tool/cc1111emk868-915 )

the. rtl_sdr app will do that with the -M level option rtl_433 -f 915M -s 1500k -M level _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ time : 2020-11-12 10:04:58 model : Insteon From_Addr : 34F837 To_Addr : 132580 Message_Type: 2 Message_Str: Group Cleanup Direct Message Extended : 0 Hops_Max : 3 Hops_Left : 3 Packet : 4F : 132580 : 34F837 : 13 04 65 Integrity : CRC Payload : 4F80251337F834130465 CMD_Data : 19, 4 Modulation: FSK Freq1 : 914.9 MHz Freq2 : 915.1 MHz RSSI : -0.2 dB SNR : 33.4 dB Noise : -33.7 dB _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ time : 2020-11-12 10:05:00 brand : LaCrosse model : LaCrosse-TX35DTHIT id : 8 Battery : 1 NewBattery: 0 Temperature: 11.2 C Integrity : CRC Modulation: FSK Freq1 : 914.9 MHz Freq2 : 915.1 MHz RSSI : -12.1 dB SNR : 17.7 dB Noise : -29.8 dB (I also picked up my 915MHz LaCrosse outdoor temperature sensor )

the c7 is a 10uF 35v cap with another 10uF 35v cap soldered to it's leg and a 1mH soldered to the other leg. honestly I am tempted to just order a new one given the corrosion (with fingerprint) on the back and the shit-show of hanging parts on the front. I'll try to replace what I can without touching the hanging parts crap. but the corrosion is another story ------------------ Update: the repair worked (I hope), although corrosion was bad enough that soldering was difficult enough that I didn't expect it to work I'll do a burn in overnight, if it fails, I'll just buy a new one.. BTW: I have had practically zero failures of insteon devices ever since I installed a home surge protector in my main panel 8 years ago (Intermatic IG3240RC3 Surge Protective Device https://www.amazon.com/gp/product/B003A3MUJI/ )

If anyone is interested, a few months ago I added the Insteon wireless protocol to the SDR application rtl_433 ( https://github.com/merbanan/rtl_433 ) . For those not familiar, rtl_433 is a Software Defined Radio (SDR) program that supports decoding of hundreds of protocols including wireless weather station sensors, and power meters. X10 (just to name a few) The program compiles on Linux, Mac and windows, and requires a rtl_sdr dongle ( ~$30 on amazon: https://www.amazon.com/s?k=RTL-SDR ). Terminal output using the command : rtl_433 -f 915M -s 1500k time : 2020-11-11 14:33:17 model : Insteon From_Addr : 110103 To_Addr : 34F837 Message_Type: 6 Message_Str: Group Broadcast Message Extended : 0 Hops_Max : 3 Hops_Left : 3 Packet: CF : 34F837 : 110103 : 06 01 E0 Integrity : CRC Payload : CF37F8340301110601E0 CMD_Data : 6, 1 Json Output from the command rtl_433 -f 915M -s 1500k -R 159 -F json {"time" : "2020-11-11 14:36:11", "model" : "Insteon", "from_id" : "34F837", "to_id" : "132580", "msg_type" : 2, "msg_str" : "Group Cleanup Direct Message", "extended" : 0, "hopsmax" : 3, "hopsleft" : 3, "formatted" : "4F : 132580 : 34F837 : 11 02 C1", "mic" : "CRC", "payload" : "4F80251337F8341102C1", "cmd_dat" : [17, 2]} {"time" : "2020-11-11 14:36:12", "model" : "Insteon", "from_id" : "110102", "to_id" : "34F837", "msg_type" : 6, "msg_str" : "Group Broadcast Message", "extended" : 0, "hopsmax" : 3, "hopsleft" : 3, "formatted" : "CF : 34F837 : 110102 : 06 01 D1", "mic" : "CRC", "payload" : "CF37F8340201110601D1", "cmd_dat" : [6, 1]}