Understanding what the CLI logs are

Apps & Clients
1

So I’ve been watching the CLI scroll by in my command prompt. While no devices are being switched or triggered, it seems quite active. First I’m wondering if this is “normal”, whatever that might be. Second, is there some way to understand what these things mean? INFO | TRACE | DEBUG | WARN |

Example. this shows repeatedly… 2024-12-21T14:13:09.558050246Z TRACE Z-Wave Sensor Found ZwaveDispatcher handler in zwave_sensor
2024-12-21T14:13:09.562264371Z TRACE Z-Wave Sensor Found ZwaveDispatcher handler in zwave_sensor
2024-12-21T14:13:09.580587913Z WARN Z-Wave Sensor Attempted to generate event for ba028686-f4ce-4ae5-b3a8-c312295e19c5.main but it does not support capability Illuminance Measurement

2

Yes, that is normal. The CLI logs are very busy, even if you select a single driver that you are debugging. I typically capture the log to a file, tidy it up a bit, and then search for specific events.
I believe WARN indicates an error detected by SmartThings.
When I enter specific debugging printout statements in my drivers, they come out as INFO.
Hopefully others will supply a more complete answer to you.

3

These are “severity levels” used in various logging systems. A good keyword to use to find out more is ‘syslog’. They form a hierarchy that is something like:

EMERGENCY
ALERT
CRITICAL/FATAL
ERROR
WARNING
NOTICE
INFO
DEBUG
TRACE

It does vary though, as does the circumstances in which each is used. It is usually possible to filter the messages.

You have highlighted four levels that you will commonly see when viewing Edge driver logs, even if nothing particularly remarkable is happening.

Typically a WARN message is used to tell you something is not quite right, but it isn’t actually breaking anything. In your example it would appear that the driver/libraries/hub may have received an illuminance measurement from a device that hasn’t been defined in SmartThings as supporting that capability. So it provides a heads up that maybe the device profile needs looking at. An alternative explanation might be that the developer has just got things wrong.

An INFO might typically be used to report something of broad interest like things starting or stopping or methods being entered. If you are reading the Edge driver logs in the CLI filtering out anything less severe than INFO might be good for giving you a feel for the flow. I don’t tend to use anything less severe than INFO for my own purposes.

A DEBUG message is going to give a bit more detail of what is happening. Still useful and likely to be meaningful to non-developers but they do make the log a bit busy.

A TRACE message is typically more of interest to developers, but even they might filter it out.

2 Likes
4

Thanks Graham and Aidan-
I only know of this CLI because of a severe delay in triggering a couple devices in Smartthings. Smartthings had me try and capture some of the delays that were around 5 minutes. (Time a door sensor opened to actually turning on the light.) They never did figure out the issue and it seemed to work itself out over about a year. It’s now creeping back (randomly about a 20 to 30 second delay, but not all the time) so I took a look at the CLI selecting ALL drivers. It just seems really busy to me, but I really have no idea what it’s doing!!

As an additional note: I only have 3 Zigbee devices, (in addition to about 100 Z Wave devices) 1 door contact sensor and 2 plug in smart plugs. I get a ton of messages about Zigbee. Seems like a lot for only 3 devices that are not even doing anything…

5

I use this smartthings edge:drivers:logcat but is there a list somewhere of commands to filter?

6

So I find this in the CLI stream. I am only assuming this is all related to the “Chandelier” device. It is a wall switch that doesn’t do anything until sunset but it seems quite busy. Is it possible to find out what the event is that seems to generate this below?

2024-12-22T14:40:27.364365018Z INFO Z-Wave Switch  <ZwaveDevice: 44797c6e-aadc-4a44-8f92-7a8f9cf7159e [07] (Chandelier)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2024-12-22T14:40:27.400963768Z TRACE Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch
2024-12-22T14:40:27.402065851Z TRACE Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch
2024-12-22T14:40:27.403106601Z TRACE Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch
2024-12-22T14:40:27.404132934Z WARN Z-Wave Switch  Attempted to generate event for 44797c6e-aadc-4a44-8f92-7a8f9cf7159e.main but it does not support capability Contact Sensor
2024-12-22T14:40:27.405727351Z TRACE Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch
2024-12-22T14:40:27.406792059Z WARN Z-Wave Switch  Attempted to generate event for 44797c6e-aadc-4a44-8f92-7a8f9cf7159e.main but it does not support capability Motion Sensor
2024-12-22T14:40:27.409208143Z TRACE Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch
2024-12-22T14:40:27.417005018Z WARN Z-Wave Switch  Attempted to generate event for 44797c6e-aadc-4a44-8f92-7a8f9cf7159e.main but it does not support capability Water Sensor
2024-12-22T14:40:27.426912268Z DEBUG Z-Wave Switch  Chandelier device thread event handled```
7

You can use the --log-level argument to set the minimum level that you see. The levels are actually:

	TRACE = 100,
	DEBUG = 200,
	INFO = 300,
	WARN = 400,
	ERROR = 500,
	FATAL = 600,
	PRINT = 1000,

So if you use --log-level=INFO you immediately get rid of the DEBUG and TRACE lines.

All that log does seem to relate to your Chandelier device. If we lose the DEBUG and TRACE it looks a bit cleaner.

2024-12-22T14:40:27.364365018Z INFO Z-Wave Switch <ZwaveDevice: 44797c6e-aadc-4a44-8f92-7a8f9cf7159e [07] (Chandelier)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2024-12-22T14:40:27.404132934Z WARN Z-Wave Switch Attempted to generate event for 44797c6e-aadc-4a44-8f92-7a8f9cf7159e.main but it does not support capability Contact Sensor
2024-12-22T14:40:27.406792059Z WARN Z-Wave Switch Attempted to generate event for 44797c6e-aadc-4a44-8f92-7a8f9cf7159e.main but it does not support capability Motion Sensor
2024-12-22T14:40:27.417005018Z WARN Z-Wave Switch Attempted to generate event for 44797c6e-aadc-4a44-8f92-7a8f9cf7159e.main but it does not support capability Water Sensor

The few seconds of logging just before that might have been interesting. There should certainly have been evidence of Chandelier reporting that the switch is off. If an automation of some sort was involved then there should have been some evidence of a command being sent to the device.

To see what else was going on in SmartThings it is usually easiest to look at Menu > History in the mobile app and looking at what was going on around 14:40 GMT today. If anything rules based (Routines, Scenes, Smart Lighting, Rules) activated it should show and you’ll also see what was happening with other devices.

I don’t know what is going on with the WARN lines there. It suggests that after the driver set the switch status to off it then tried to set the states for the Contact Sensor, Motion Sensor and Water Sensor capabilities but the ‘system’ stopped those because Chandelier doesn’t have those capabilities. So there is something a little odd going on there.

8

Thanks Graham!

This info is from ST Advanced:

DevicesChandelier

is a GE Dimmer Switch using Driver Z-Wave Switch (assuming from Smartthings)

Attributes:

Capture
Capture1710×425 26.1 KB

Commands:

Capture
Capture1673×542 30.7 KB

In use by:

Capture
Capture1689×440 27.1 KB

Events:

Capture
Capture1679×725 72.2 KB

This switch gets used very infrequently. The OFF yesterday was a manual switch press at around 7PM my time. Other than that, it gets turned on at Sunset “EVENING LIGHTING LEVELS” and gets turned off with GOOD NIGHT. While I have zero knowledge of what’s happening at the CLI level, it just seems odd that the switch would be doing anything outside of the times it is triggered.

9

I’ll defer to those more familiar with what is normal behaviour for these devices, but I guess it could be that the device had been asked to report its status for whatever reason. The driver isn’t really going to care why the report has been sent, only that it has, and will act on it accordingly by sending an attribute event. However that event isn’t going to get very far if it isn’t a change of status so you probably won’t even see it in the history.

1 Like
10

So would you think if there are a bunch of these things happening, it would NOT contribute to any kind of delay in the system? They seem to scroll by pretty quickly…

11

Please provide a screenshot from the whole Summary section.

12

bitmap
bitmap1920×4696 315 KB

13

You gave us logs for a Z-Wave device, although the logs for the Zigbee devices would be much more interesting in this case.

(The log for the Z-Wave device doesn’t look sane, though.)

14

Like this?

? Select a driver. all
connecting… connected

2024-12-22T20:02:37.682868852Z DEBUG Zigbee Switch  driver device thread event handled
2024-12-22T20:02:44.856397255Z DEBUG Zigbee Contact  driver device thread event handled
2024-12-22T20:03:07.671801710Z DEBUG Zigbee Switch  driver device thread event handled
2024-12-22T20:03:14.865794253Z INFO Zigbee Contact  Doing health check read for [5312]:0500:0002
2024-12-22T20:03:14.873287836Z INFO Zigbee Contact  <ZigbeeDevice: 5d4e5159-6f23-4aa1-8c9d-5bcc0ffe17b4 [0x5312] (Kailey's Window)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5312, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
2024-12-22T20:03:14.884201378Z DEBUG Zigbee Contact  driver device thread event handled
2024-12-22T20:03:24.050967879Z TRACE Z-Wave Sensor  Received event with handler unnamed
2024-12-22T20:03:24.052654212Z INFO Z-Wave Sensor  <ZwaveDevice: ba028686-f4ce-4ae5-b3a8-c312295e19c5 [7A] (Garage Motion 2)> received Z-Wave command: {args={precision=1, scale="CELSIUS", sensor_type="TEMPERATURE", sensor_value=12.1, size=2}, cmd_class="SENSOR_MULTILEVEL", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x01\x22\x00\x79", src_channel=0, version=1}
2024-12-22T20:03:24.088424837Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:03:24.100439212Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:03:24.106137671Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:03:24.107147087Z WARN Z-Wave Sensor  Attempted to generate event for ba028686-f4ce-4ae5-b3a8-c312295e19c5.main but it does not support capability Temperature Measurement
2024-12-22T20:03:24.114202962Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:03:24.115605837Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:03:24.116639546Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:03:24.117647712Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:03:24.121592546Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:03:24.122707004Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:03:24.123629337Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:03:24.124521504Z DEBUG Z-Wave Sensor  Garage Motion 2 device thread event handled
2024-12-22T20:03:37.690368006Z DEBUG Zigbee Switch  driver device thread event handled
2024-12-22T20:03:44.877189798Z DEBUG Zigbee Contact  driver device thread event handled
2024-12-22T20:04:07.720472509Z DEBUG Zigbee Switch  driver device thread event handled
2024-12-22T20:04:14.888679927Z DEBUG Zigbee Contact  driver device thread event handled
2024-12-22T20:04:37.710365263Z DEBUG Zigbee Switch  driver device thread event handled
2024-12-22T20:04:43.696680180Z TRACE Z-Wave Sensor  Received event with handler unnamed
2024-12-22T20:04:43.769622222Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> received Z-Wave command: {args={}, cmd_class="WAKE_UP", cmd_id="NOTIFICATION", dst_channels={}, encap="NONE", payload="", src_channel=0, version=1}
2024-12-22T20:04:43.931362472Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:43.936360389Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:43.950577055Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:43.978815139Z TRACE Z-Wave Sensor  Found CapabilityCommandDispatcher handler in zwave_sensor
2024-12-22T20:04:44.138703097Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> sending Z-Wave command: {args={sensor_type="DOOR_WINDOW"}, cmd_class="SENSOR_BINARY", cmd_id="GET", dst_channels={}, encap="AUTO", payload="
", src_channel=0, version=2}
2024-12-22T20:04:44.233303639Z TRACE Z-Wave Sensor  Z-Wave command(197c99d7) queued for radio transmission: CC:Sensor Binary, CID:0x02
2024-12-22T20:04:44.240455347Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> sending Z-Wave command: {args={}, cmd_class="BATTERY", cmd_id="GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2024-12-22T20:04:44.297353097Z TRACE Z-Wave Sensor  Z-Wave command(42aeb9c5) queued for radio transmission: CC:Battery, CID:0x02
2024-12-22T20:04:44.305084847Z DEBUG Z-Wave Sensor  Pool Power Status device thread event handled
2024-12-22T20:04:44.405554222Z TRACE Z-Wave Sensor  Z-Wave command(197c99d7) transmit status: TRANSMIT_COMPLETE_OK
2024-12-22T20:04:44.501021222Z TRACE Z-Wave Sensor  Received event with handler unnamed
2024-12-22T20:04:44.510518347Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> received Z-Wave command: {args={sensor_type="FIRST", sensor_value="DETECTED_AN_EVENT"}, cmd_class="SENSOR_BINARY", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\xFF\xFF", src_channel=0, version=2}
2024-12-22T20:04:44.548867514Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:44.551880305Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:44.554503180Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:44.560514764Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:44.561593430Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:44.562524680Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:44.563405222Z DEBUG Z-Wave Sensor  Pool Power Status device thread event handled
2024-12-22T20:04:44.706022430Z TRACE Z-Wave Sensor  Z-Wave command(42aeb9c5) transmit status: TRANSMIT_COMPLETE_OK
2024-12-22T20:04:44.910572180Z DEBUG Zigbee Contact  driver device thread event handled
2024-12-22T20:04:44.920668055Z TRACE Z-Wave Sensor  Received event with handler unnamed
2024-12-22T20:04:44.926439014Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> received Z-Wave command: {args={battery_level=80}, cmd_class="BATTERY", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="P", src_channel=0, version=1}
2024-12-22T20:04:44.958216805Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:44.962300639Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> emitting event: {"attribute_id":"battery","capability_id":"battery","component_id":"main","state":{"value":80}}
2024-12-22T20:04:44.985699055Z DEBUG Z-Wave Sensor  Pool Power Status device thread event handled
2024-12-22T20:04:46.148814056Z TRACE Aeotec AerQ  Received event with handler unnamed
2024-12-22T20:04:46.150632806Z INFO Aeotec AerQ  <ZwaveDevice: 1170280f-41e7-4c7b-9588-8a0413ca56d0 [B1] (Attic Temp-Humidity)> received Z-Wave command: {args={precision=1, scale="FAHRENHEIT", sensor_type="TEMPERATURE", sensor_value=42.8, size=2}, cmd_class="SENSOR_MULTILEVEL", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x01\x2A\x01\xAC", src_channel=0, version=1}
2024-12-22T20:04:46.191710097Z TRACE Aeotec AerQ  Found ZwaveDispatcher handler in aeotec-aerq
2024-12-22T20:04:46.192730014Z INFO Aeotec AerQ  <ZwaveDevice: 1170280f-41e7-4c7b-9588-8a0413ca56d0 [B1] (Attic Temp-Humidity)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"F","value":42.8}}
2024-12-22T20:04:46.259687681Z TRACE Aeotec AerQ  Found ZwaveDispatcher handler in aeotec-aerq
2024-12-22T20:04:46.261660972Z TRACE Aeotec AerQ  Found ZwaveDispatcher handler in aeotec-aerq
2024-12-22T20:04:46.262851056Z DEBUG Aeotec AerQ  Attic Temp-Humidity device thread event handled
2024-12-22T20:04:46.263909264Z TRACE Aeotec AerQ  Received event with handler unnamed
2024-12-22T20:04:46.264841139Z INFO Aeotec AerQ  <ZwaveDevice: 1170280f-41e7-4c7b-9588-8a0413ca56d0 [B1] (Attic Temp-Humidity)> received Z-Wave command: {args={precision=0, scale="PERCENTAGE", sensor_type="RELATIVE_HUMIDITY", sensor_value=85, size=2}, cmd_class="SENSOR_MULTILEVEL", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x05\x02\x00\x55", src_channel=0, version=1}
2024-12-22T20:04:46.285051847Z TRACE Z-Wave Sensor  Received event with handler unnamed
2024-12-22T20:04:46.286836889Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> received Z-Wave command: {args={battery_level=80}, cmd_class="BATTERY", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="P", src_channel=0, version=1}
2024-12-22T20:04:46.303217056Z TRACE Aeotec AerQ  Found ZwaveDispatcher handler in aeotec-aerq
2024-12-22T20:04:46.309104306Z TRACE Aeotec AerQ  Found ZwaveDispatcher handler in aeotec-aerq
2024-12-22T20:04:46.321914056Z INFO Aeotec AerQ  <ZwaveDevice: 1170280f-41e7-4c7b-9588-8a0413ca56d0 [B1] (Attic Temp-Humidity)> emitting event: {"attribute_id":"humidity","capability_id":"relativeHumidityMeasurement","component_id":"main","state":{"value":85}}
2024-12-22T20:04:46.360032056Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:46.361315889Z TRACE Aeotec AerQ  Found ZwaveDispatcher handler in aeotec-aerq
2024-12-22T20:04:46.362388681Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> emitting event: {"attribute_id":"battery","capability_id":"battery","component_id":"main","state":{"value":80}}
2024-12-22T20:04:46.363731806Z DEBUG Aeotec AerQ  Attic Temp-Humidity device thread event handled
2024-12-22T20:04:46.373376847Z TRACE Aeotec AerQ  Received event with handler unnamed
2024-12-22T20:04:46.378499889Z INFO Aeotec AerQ  <ZwaveDevice: 1170280f-41e7-4c7b-9588-8a0413ca56d0 [B1] (Attic Temp-Humidity)> received Z-Wave command: {args={precision=1, scale="FAHRENHEIT", sensor_type="DEW_POINT", sensor_value=38.6, size=2}, cmd_class="SENSOR_MULTILEVEL", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x0B\x2A\x01\x82", src_channel=0, version=1}
2024-12-22T20:04:46.388564222Z DEBUG Z-Wave Sensor  Pool Power Status device thread event handled
2024-12-22T20:04:46.399022056Z TRACE Aeotec AerQ  Found ZwaveDispatcher handler in aeotec-aerq
2024-12-22T20:04:46.400181472Z TRACE Aeotec AerQ  Found ZwaveDispatcher handler in aeotec-aerq
2024-12-22T20:04:46.401209264Z TRACE Aeotec AerQ  Found ZwaveDispatcher handler in aeotec-aerq
2024-12-22T20:04:46.402138056Z INFO Aeotec AerQ  <ZwaveDevice: 1170280f-41e7-4c7b-9588-8a0413ca56d0 [B1] (Attic Temp-Humidity)> emitting event: {"attribute_id":"dewpoint","capability_id":"dewPoint","component_id":"main","state":{"unit":"F","value":38.6}}
2024-12-22T20:04:46.427487472Z DEBUG Aeotec AerQ  Attic Temp-Humidity device thread event handled
2024-12-22T20:04:46.623910847Z TRACE Z-Wave Sensor  Received event with handler unnamed
2024-12-22T20:04:46.635075347Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> received Z-Wave command: {args={battery_level=80}, cmd_class="BATTERY", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="P", src_channel=0, version=1}
2024-12-22T20:04:46.656866097Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:46.660829472Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> emitting event: {"attribute_id":"battery","capability_id":"battery","component_id":"main","state":{"value":80}}
2024-12-22T20:04:46.675776056Z DEBUG Z-Wave Sensor  Pool Power Status device thread event handled
2024-12-22T20:04:46.946700722Z INFO Z-Wave Switch  hub handled command: 40ef1e2f-ff1c-47ae-92e5-16329888e312:main:switch:on []
2024-12-22T20:04:46.947783264Z INFO Z-Wave Switch  hub sending: Z-Wave command (40ef1e2f-ff1c-47ae-92e5-16329888e312): <cmd_class: 0x25, cmd_code: 0x1, dst_channels: [], encap: 0x0, payload: [ff], src_channel: 0x0>
2024-12-22T20:04:46.984088056Z TRACE Z-Wave Switch  Z-Wave command(6446c910) queued for radio transmission: CC:Switch Binary, CID:0x01
2024-12-22T20:04:47.060458556Z TRACE Z-Wave Sensor  Received event with handler unnamed
2024-12-22T20:04:47.062100597Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> received Z-Wave command: {args={battery_level=80}, cmd_class="BATTERY", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="P", src_channel=0, version=1}
2024-12-22T20:04:47.108837681Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:47.110880014Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> emitting event: {"attribute_id":"battery","capability_id":"battery","component_id":"main","state":{"value":80}}
2024-12-22T20:04:47.149371431Z DEBUG Z-Wave Sensor  Pool Power Status device thread event handled
2024-12-22T20:04:47.205305472Z TRACE Z-Wave Switch  Z-Wave command(6446c910) transmit status: TRANSMIT_COMPLETE_OK
2024-12-22T20:04:47.251280139Z TRACE Z-Wave Switch  Received event with handler unnamed
2024-12-22T20:04:47.252913389Z INFO Z-Wave Switch  <ZwaveDevice: 40ef1e2f-ff1c-47ae-92e5-16329888e312 [C1] (Attic Fan)> received Z-Wave command: {args={value="ON_ENABLE"}, cmd_class="SWITCH_BINARY", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\xFF", src_channel=0, version=1}
2024-12-22T20:04:47.281491764Z TRACE Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch
2024-12-22T20:04:47.285232556Z INFO Z-Wave Switch  <ZwaveDevice: 40ef1e2f-ff1c-47ae-92e5-16329888e312 [C1] (Attic Fan)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-22T20:04:47.308370014Z TRACE Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch
2024-12-22T20:04:47.309315972Z DEBUG Z-Wave Switch  Attic Fan device thread event handled
2024-12-22T20:04:47.611468889Z TRACE Z-Wave Sensor  Received event with handler unnamed
2024-12-22T20:04:47.623775514Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> received Z-Wave command: {args={battery_level=80}, cmd_class="BATTERY", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="P", src_channel=0, version=1}
2024-12-22T20:04:47.644720472Z TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2024-12-22T20:04:47.658316389Z INFO Z-Wave Sensor  <ZwaveDevice: ccd274ad-20ad-43db-be3f-2fb5fa3fae5a [AF] (Pool Power Status)> emitting event: {"attribute_id":"battery","capability_id":"battery","component_id":"main","state":{"value":80}}
2024-12-22T20:04:47.733723306Z DEBUG Z-Wave Sensor  Pool Power Status device thread event handled
2024-12-22T20:04:47.986304722Z INFO Z-Wave Switch  hub sending: Z-Wave command (40ef1e2f-ff1c-47ae-92e5-16329888e312): <cmd_class: 0x25, cmd_code: 0x2, dst_channels: [], encap: 0x0, payload: [], src_channel: 0x0>
2024-12-22T20:04:48.364008681Z TRACE Z-Wave Switch  Z-Wave command(202a6e78) queued for radio transmission: CC:Switch Binary, CID:0x02
2024-12-22T20:04:48.743974389Z TRACE Z-Wave Switch  Z-Wave command(202a6e78) transmit status: TRANSMIT_COMPLETE_OK
2024-12-22T20:04:49.000953889Z TRACE Z-Wave Switch  Received event with handler unnamed
2024-12-22T20:04:49.005790556Z INFO Z-Wave Switch  <ZwaveDevice: 40ef1e2f-ff1c-47ae-92e5-16329888e312 [C1] (Attic Fan)> received Z-Wave command: {args={current_value="ON_ENABLE", duration=0, target_value="ON_ENABLE", value="ON_ENABLE"}, cmd_class="SWITCH_BINARY", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\xFF\xFF\x00", src_channel=0, version=2}
2024-12-22T20:04:49.116903556Z TRACE Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch
2024-12-22T20:04:49.122352056Z INFO Z-Wave Switch  <ZwaveDevice: 40ef1e2f-ff1c-47ae-92e5-16329888e312 [C1] (Attic Fan)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-22T20:04:49.144236306Z TRACE Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch
2024-12-22T20:04:49.145154473Z DEBUG Z-Wave Switch  Attic Fan device thread event handled```
15

I mean… The whole Z-Wave switch driver is odd:

Screenshot_20241222_210617_Samsung Internet
Screenshot_20241222_210617_Samsung Internet1200×1777 418 KB

Screenshot_20241222_210817_Samsung Internet
Screenshot_20241222_210817_Samsung Internet1200×898 220 KB

16

Almost.

Please edit your post and add ``` before and after the log. Like this:

```
Log
Log
Log
```

Edit: way better now!

Not busy at all, if you ignore all the TRACE and DEBUG entries.

17

How’s that?

18

Not busy at all, if you ignore all the TRACE and DEBUG entries. Quite normal for 100 devices.

19

Okie Dokie!

I have 108 devices, and 19 are virtual devices. I appreciate the look! I guess I just don’t know why things that only are in use 2 or 3 times a day are scrolling by in the CLI logs all day. If that is normal, I’m good with it.

20

Should I look for another Driver for this GE Dimmer?