I have the Hampton Bays Fan Controler (King of Fans Zigbee Fan Controller). They stopped responding although both appear online in both google home and smartthings. I see several requests for an edge driver, but couldn’t find that it has been handled. Sorry if this is a duplicate request for something resolved, but I would appreciate being pointed in the right direction. Thanks!
2 Likes
I was looking to see if someone with experience can update this groovy app for twinkly smart Christmas lights to the new edge drivers. Attached is the link to the form , and one of the last entries was a GitHub update for the current work. I did a message on that form but have not received any updates since October, and it’s finally Christmas time, and I wanted to see if I could get it updated. Thanks in advance for the help. Twinkly Christmas Lights
2 Likes
Will your driver also work with “Asus Z-Wave Smoke Detector SHRM10000”?
It’s AFAIK a rebranded “Heiman HS1SA-Z Smoke Sensor”.
Works in ST Hub with “Z-Wave Smoke Alarm” generic driver (had to choose manually in IDE).
Raw description is:
zw:Ss2 type:0701 mfr:0403 prod:0002 model:0003 ver:3.01 zwv:5.03 lib:06 cc:5E,6C,55,9F sec:86,85,8E,59,72,5A,73,80,71,84
Hi @LLinke
Added to this driver version
Try if it works
───────────────────────────────────────────────────
Name Z-Wave Smoke Alarm-Mc
Version 2022-11-26T15:55:09.731420425
───────────────────────────────────────────────────
- id: 0403/0002/0003
deviceLabel: Asus Smoke SHRM10000
manufacturerId: 0x0403
productType: 0x0002
productId: 0x0003
deviceProfileName: smoke-battery
1 Like
I have a Fibaro FGK-101 (product type 0x0700), which I use with an external temperature probe (I don’t use the open/close function). I have tried the various edge drivers, and can’t seem to find any that work correctly for the temperature function of the probe. Maybe I’m missing somethings?
thanks
1 Like
Hi @makrisn
If you install this driver it could works
Z-Wave Sensor and Child Thermostat Mc
Hi @Mariano_Colmenarejo
thank you for the suggestion!
sadly, it doesn’t seem to work either (no temperature reading, and the contact sensor doesn’t register on/off status, also getting connecting error). When I then immediately switch back to the z-wave sensor (ST beta), the contact sensor is again functional, but obviously there is no option of a temperature reading, and no connecting error
I did try to take a picture of the error message, maybe that could provide a clue, hoping it’s a bug that can be fixed?
thanks again
I don’t know how the device was paired with the driver.
If it was done with a driver change from the stock driver it is normal that it does not work.
To get it to work with the temperature profile you have to drop and re-pair directly with this driver.
In Zwave drivers, the configuration is not sent when changing from one driver to another driver to respect the custom configuration that could have been done with another driver. (zwave device config Mc, for example)
This has its advantages and disadvantages.
Try to exclude it and make it pair directly with this driver, there are other users who use it and it worked for them, that’s why there is this temperature option in the driver.
You may need to remove the stock driver from your hub.
These are things to polish in the new edge architecture.
Hi @5spot
Added preference and profile to show temperature in the tile in this driver version. Default option is open/close sensor
You need clear app memory cache the first time you change the profile
───────────────────────────────────────────────────
Name Z-Wave Sensor Mc
Version 2022-10-29T19:03:15.341030072
───────────────────────────────────────────────────
@makrisn You can try this driver that Mariano created. I use this with my Fibaro FGK-101 sensors with external temperature probes. I believe he has added prod code 0700 and 0701 to the driver.
Hi @Mariano_Colmenarejo : first, I really appreciate all the good work !
I was able to exclude it (and also did a reset of the fibaro FGK-101 to clean the EPROM memory for good measure.
It repaired to the Z -Wave Sensor and Child Thermostat Mc directly, but… no luck, same issue
I see it has worked for some users. When reading thru the community posts, my issues seem very similar to what @alefavara experienced. maybe it’s tied to product 0700?
thanks again
JD and friends first of all thx for the great work you are doing in this community. I also have a request and that is for an edge driver for the EVR_AD1472 which is also known as the nexa AD147-2 dimmer switch. I know this has been sold widely so a lot of people will be looking for an edge driver. Up to know I have been using the DTH: [ smartthings : Dimmer Switch Nexa
https://graph-eu01-euwest1.api.smartthings.com/ide/device/editor/453d20e9-e0f0-4869-990f-c9fa1f9c57ed
fingerprint mfr: “0060”, prod: “0003”, model: “0003”, deviceJoinName: “Nexa Dimmer Switch”
Could anyone tell me if there is a matching device driver or could it be added to an existing one?
Thx in advance
Fred
Hi @makrisn
The firmware version may be older and the parameters are different.
I made some changes in this version if you want to try
────────────────────────────────────────────────────
Name Z-Wave Sensor and Child Thermostat Mc
Version 2022-11-27T18:02:33.964999331
────────────────────────────────────────────────────
1 Like
thanks @Mariano_Colmenarejo. It seems we are moving in the right direction with this version… however, still no temperature readings or contact readings.
On the flip side, the connection problem message is now gone, and the settings are starting to work a bit better (I can create the virtual thermostat device for example, which never worked before)
Let me know if I should just give up on this older hardware; like you said, it’s probably on older firmware.
thanks again
cheers
Hi @makrisn
I have made a version that manages the temperature manually for fibaro open/close devices.
It would be necessary to obtain the pairing logs of the device with the driver, to see what response it sends to the configuration parameters sent.
This is a tutorial on how to install the CLI and get the logs in windows.
────────────────────────────────────────────────────
Name Z-Wave Sensor and Child Thermostat Mc
Version 2022-11-29T11:56:36.797070423
────────────────────────────────────────────────────
Hi @makrisn
In these logs it can be seen that the sensor is interrogated to send the temperature and there is no response from the device.
It would be necessary to uninstall the device.
Open a window with the CLI ready to capture the driver logs
Install device and capture device pairing logs
I have a a tuya ZigBee mmwave presence sensor I’d like to get working. Let me know if any other info is needed to get driver’s for it. Thanks!
1 Like
@Mariano_Colmenarejo … part 2
2022-11-30T17:47:06.739713274+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={scale=0, sensor_type=“TEMPERATURE”}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x01\x00”, src_channel=0, version=5}
2022-11-30T17:47:06.746774233+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(ddeb919b) queued for radio transmission: CC:Sensor Multi-level, CID:0x04
2022-11-30T17:47:06.752374858+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={}, cmd_class=“BATTERY”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2022-11-30T17:47:06.759324524+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(58e0f85f) queued for radio transmission: CC:Battery, CID:0x02
2022-11-30T17:47:06.766674399+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(0e4536da) transmit status: TRANSMIT_COMPLETE_OK
2022-11-30T17:47:06.768162691+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={sensor_type=“DOOR_WINDOW”}, cmd_class=“SENSOR_BINARY”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x0A”, src_channel=0, version=2}
2022-11-30T17:47:06.774874566+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(ead99faf) queued for radio transmission: CC:Sensor Binary, CID:0x02
2022-11-30T17:47:06.778807108+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={sensor_type=“GENERAL_PURPOSE_ALARM”}, cmd_class=“SENSOR_ALARM”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x00”, src_channel=0, version=1}
2022-11-30T17:47:06.786955399+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(a8dbc0fa) queued for radio transmission: CC:Sensor Alarm, CID:0x01
2022-11-30T17:47:06.790985524+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={sensor_type=“TAMPER”}, cmd_class=“SENSOR_BINARY”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x08”, src_channel=0, version=2}
2022-11-30T17:47:06.798097608+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(6bcf4ce5) queued for radio transmission: CC:Sensor Binary, CID:0x02
2022-11-30T17:47:06.801772983+00:00 ERROR Z-Wave Sensor and Child Thermostat Mc Fibaro Open/Closed Sensor thread encountered error: [string “st/dispatcher.lua”]:233: Error encountered while processing event for <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)>:
arg1: doConfigure
arg2: table: 0xc29e80
[string “st/dispatcher.lua”]:233: Error encountered while processing event for <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)>:
arg1: doConfigure
arg2: table: 0xc29e80
[string “fibaro-door-window-sensor/init.lua”]:108: attempt to index a nil value (global ‘self’)
2022-11-30T17:47:06.811194108+00:00 DEBUG Z-Wave Sensor and Child Thermostat Mc Fibaro Open/Closed Sensor device thread event handled
2022-11-30T17:47:06.826496524+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(4a83c0ee) transmit status: TRANSMIT_COMPLETE_OK
2022-11-30T17:47:06.860944691+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Received event with handler unnamed
2022-11-30T17:47:06.867536399+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> received Z-Wave command: {args={battery_level=98}, cmd_class=“BATTERY”, cmd_id=“REPORT”, dst_channels={}, encap=“CRC16”, payload=“b”, src_channel=0, version=1}
2022-11-30T17:47:06.875464524+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:06.879162191+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:98}}
2022-11-30T17:47:06.888938691+00:00 DEBUG Z-Wave Sensor and Child Thermostat Mc Fibaro Open/Closed Sensor device thread event handled
2022-11-30T17:47:06.956617733+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(f7cb2ee4) transmit status: TRANSMIT_COMPLETE_OK
2022-11-30T17:47:06.964087691+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Received event with handler unnamed
2022-11-30T17:47:06.969005358+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> received Z-Wave command: {args={sensor_value=“IDLE”}, cmd_class=“SENSOR_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“CRC16”, payload=“\x00”, src_channel=0, version=1}
2022-11-30T17:47:07.005191358+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.008358441+00:00 WARN Z-Wave Sensor and Child Thermostat Mc Attempted to generate event for a9710043-7434-4115-876e-568f8f43255a.main but it does not support capability Water Sensor
2022-11-30T17:47:07.011494483+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.014857191+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> emitting event: {“attribute_id”:“contact”,“capability_id”:“contactSensor”,“component_id”:“main”,“state”:{“value”:“closed”}}
2022-11-30T17:47:07.024190024+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.027962399+00:00 WARN Z-Wave Sensor and Child Thermostat Mc Attempted to generate event for a9710043-7434-4115-876e-568f8f43255a.main but it does not support capability Motion Sensor
2022-11-30T17:47:07.031539233+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.049978691+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.054010191+00:00 WARN Z-Wave Sensor and Child Thermostat Mc Attempted to generate event for a9710043-7434-4115-876e-568f8f43255a.main but it does not support capability Temperature Alarm
2022-11-30T17:47:07.057142774+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.060223358+00:00 WARN Z-Wave Sensor and Child Thermostat Mc Attempted to generate event for a9710043-7434-4115-876e-568f8f43255a.main but it does not support capability Smoke Detector
2022-11-30T17:47:07.063423774+00:00 DEBUG Z-Wave Sensor and Child Thermostat Mc Fibaro Open/Closed Sensor device thread event handled
2022-11-30T17:47:07.086634108+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(db36df4f) transmit status: TRANSMIT_COMPLETE_OK
2022-11-30T17:47:07.094047608+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Received event with handler unnamed
2022-11-30T17:47:07.098261233+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> received Z-Wave command: {args={seconds=0, sensor_state=“NO_ALARM”, sensor_type=“GENERAL_PURPOSE_ALARM”, source_node_id=61}, cmd_class=“SENSOR_ALARM”, cmd_id=“REPORT”, dst_channels={}, encap=“CRC16”, payload=“\x3D\x00\x00\x00\x00”, src_channel=0, version=1}
2022-11-30T17:47:07.147039149+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.150093274+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.153489483+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> emitting event: {“attribute_id”:“contact”,“capability_id”:“contactSensor”,“component_id”:“main”,“state”:{“value”:“closed”}}
2022-11-30T17:47:07.161521066+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.164623566+00:00 WARN Z-Wave Sensor and Child Thermostat Mc Attempted to generate event for a9710043-7434-4115-876e-568f8f43255a.main but it does not support capability Motion Sensor
2022-11-30T17:47:07.167909399+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.170931149+00:00 DEBUG Z-Wave Sensor and Child Thermostat Mc Fibaro Open/Closed Sensor device thread event handled
2022-11-30T17:47:07.174030483+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Received event with handler device_lifecycle
2022-11-30T17:47:07.187998649+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> received lifecycle event: infoChanged
2022-11-30T17:47:07.201340983+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found DeviceLifecycleDispatcher handler in zwave_sensor → fibaro door window sensor
2022-11-30T17:47:07.206926608+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={configuration_value=6, default=false, parameter_number=3, size=1}, cmd_class=“CONFIGURATION”, cmd_id=“SET”, dst_channels={}, encap=“AUTO”, payload=“\x03\x01\x06”, src_channel=0, version=1}
2022-11-30T17:47:07.214350566+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(02dc31d1) queued for radio transmission: CC:Configuration, CID:0x04
2022-11-30T17:47:07.218159441+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={parameter_number=3}, cmd_class=“CONFIGURATION”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x03”, src_channel=0, version=1}
2022-11-30T17:47:07.225304566+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(230f8486) queued for radio transmission: CC:Configuration, CID:0x05
2022-11-30T17:47:07.230011358+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=54, size=1}, cmd_class=“CONFIGURATION”, cmd_id=“SET”, dst_channels={}, encap=“AUTO”, payload=“\x36\x01\x00”, src_channel=0, version=1}
2022-11-30T17:47:07.237023608+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(2462ce53) queued for radio transmission: CC:Configuration, CID:0x04
2022-11-30T17:47:07.241220108+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={parameter_number=54}, cmd_class=“CONFIGURATION”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“6”, src_channel=0, version=1}
2022-11-30T17:47:07.247735066+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(b5644175) queued for radio transmission: CC:Configuration, CID:0x05
2022-11-30T17:47:07.252822233+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=1, size=1}, cmd_class=“CONFIGURATION”, cmd_id=“SET”, dst_channels={}, encap=“AUTO”, payload=“\x01\x01\x00”, src_channel=0, version=1}
2022-11-30T17:47:07.259754649+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(11b1cf58) queued for radio transmission: CC:Configuration, CID:0x04
2022-11-30T17:47:07.263890233+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={parameter_number=1}, cmd_class=“CONFIGURATION”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x01”, src_channel=0, version=1}
2022-11-30T17:47:07.270459441+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(e98e63d6) queued for radio transmission: CC:Configuration, CID:0x05
2022-11-30T17:47:07.278945983+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=2, size=1}, cmd_class=“CONFIGURATION”, cmd_id=“SET”, dst_channels={}, encap=“AUTO”, payload=“\x02\x01\x00”, src_channel=0, version=1}
2022-11-30T17:47:07.287570274+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(8e7b5031) queued for radio transmission: CC:Configuration, CID:0x04
2022-11-30T17:47:07.291600483+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={parameter_number=2}, cmd_class=“CONFIGURATION”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x02”, src_channel=0, version=1}
2022-11-30T17:47:07.297663941+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(fb75184f) transmit status: TRANSMIT_COMPLETE_OK
2022-11-30T17:47:07.302253858+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(9701cd82) queued for radio transmission: CC:Configuration, CID:0x05
2022-11-30T17:47:07.306660524+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={configuration_value=1, default=false, parameter_number=31, size=1}, cmd_class=“CONFIGURATION”, cmd_id=“SET”, dst_channels={}, encap=“AUTO”, payload=“\x1F\x01\x01”, src_channel=0, version=1}
2022-11-30T17:47:07.318613858+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(2624b34b) queued for radio transmission: CC:Configuration, CID:0x04
2022-11-30T17:47:07.322662941+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> sending Z-Wave command: {args={parameter_number=31}, cmd_class=“CONFIGURATION”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x1F”, src_channel=0, version=1}
2022-11-30T17:47:07.329387691+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(ad2dcded) queued for radio transmission: CC:Configuration, CID:0x05
2022-11-30T17:47:07.336506024+00:00 DEBUG Z-Wave Sensor and Child Thermostat Mc Fibaro Open/Closed Sensor device thread event handled
2022-11-30T17:47:07.340889608+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Received event with handler unnamed
2022-11-30T17:47:07.346059899+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> received Z-Wave command: {args={sensor_value=“IDLE”}, cmd_class=“SENSOR_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“CRC16”, payload=“\x00”, src_channel=0, version=1}
2022-11-30T17:47:07.358723483+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.361912858+00:00 WARN Z-Wave Sensor and Child Thermostat Mc Attempted to generate event for a9710043-7434-4115-876e-568f8f43255a.main but it does not support capability Water Sensor
2022-11-30T17:47:07.365215899+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.368590441+00:00 INFO Z-Wave Sensor and Child Thermostat Mc <ZwaveDevice: a9710043-7434-4115-876e-568f8f43255a [3D] (Fibaro Open/Closed Sensor)> emitting event: {“attribute_id”:“contact”,“capability_id”:“contactSensor”,“component_id”:“main”,“state”:{“value”:“closed”}}
2022-11-30T17:47:07.377352941+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.380502733+00:00 WARN Z-Wave Sensor and Child Thermostat Mc Attempted to generate event for a9710043-7434-4115-876e-568f8f43255a.main but it does not support capability Motion Sensor
2022-11-30T17:47:07.384742066+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.388010983+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.391675024+00:00 WARN Z-Wave Sensor and Child Thermostat Mc Attempted to generate event for a9710043-7434-4115-876e-568f8f43255a.main but it does not support capability Temperature Alarm
2022-11-30T17:47:07.395674566+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Found ZwaveDispatcher handler in zwave_sensor
2022-11-30T17:47:07.398760149+00:00 WARN Z-Wave Sensor and Child Thermostat Mc Attempted to generate event for a9710043-7434-4115-876e-568f8f43255a.main but it does not support capability Smoke Detector
2022-11-30T17:47:07.401896941+00:00 DEBUG Z-Wave Sensor and Child Thermostat Mc Fibaro Open/Closed Sensor device thread event handled
2022-11-30T17:47:07.456091149+00:00 TRACE Z-Wave Sensor and Child Thermostat Mc Z-Wave command(26e97085) transmit status: TRANSMIT_COMPLETE_OK
You guys are killing me. 
Please remember that I have to listen to every line of every post in this thread, because I use voice software. This is not a thread for posting logs or diagnosing individual problems with individual edge drivers.
This is just a thread for posting a request and then a response, which has a link to a thread where you can discuss the request in detail if needed.
Please take these diagnostic conversations to a different topic.
From the first post in this thread:
Developers: if you need to ask questions about the device or start a longer conversation, please start an individual topic for it and link to it from a post in this thread. I’d like to keep this thread to a maximum of two posts per device per developer: one requesting a driver, and one responding to that request. (Of course more than one developer might respond, you never know.)
Thank you.
3 Likes
I did not realize that we are in this general Thread
1 Like