ok so heres the thing… it happens at any time of day or night when i hit the switch, also happens with the kitchen 52252 switch. the sensor is not actually sensing any motion, its only being triggered somehow. either from the zwave radio or some sort of voltage drop on the power, or something else… but i dont see why when i turn on the hot water, i have a tankless water heater, that draws up to 80 amps and would definitely cause a voltage change to the system, i dont get an alert of any motion sensed. so im leaning towards some sort of zwave anomoly.
and heres a screenshot from Live Logging, the light switches are not logging anything. i find that odd… but at 11:15:25 i hit the kitchen switch to On and nothing logged but sure enough the FLS100 motion trigger was activated.
Since you have them on Edge drivers you’ll need to download the CLI to see logs.
This would be very difficult to troubleshoot if you’re right. If you just want to jump straight to standard fixes for a z-wave problem, then reboot your hub, include/exclude your devices, and see if that works.
Outdoor motion sensors tend to have a lot of nuisance trips, so I’m hoping you’re completely confident about this. If you’re wrong, any other troubleshooting is wasted effort. Consider that it’s possible that there’s real motion being observed, but some sort of lag in the device-mesh-hub-cloud-app processing/transmission chain is causing the notification to coincide with the light switch push. I’m suggesting cardboard as a way to eliminate real motion events from the equation, which lets you narrow down the possible causes.
Another thing you can try is editing your motion sensor DTH to insert a log line in the parse function so that you can see the raw z-wave message that the hub is getting. That may/may not tell you something.
how do i do this? what is CLI ?
ive rebooted the hub an did not experience any change to this anomoly. not sure how excluding anything would help troubleshoot. if i exclude the switch, then the problem never happens… if i exclude the motion detector, again the problem never happens… not sure how this would help troubleshooting.
i dont know if its a lag in transmission, but if i go outside right now and actually activate the sensor by detecting my motion, i immediately get the motion detected notification and the spotlight turns on. i dont see any lags from detection and notification
this is way beyond my capability. this is the code if anyone would be able to do this > HomeSeer Floodlight Sensor HS-FLS100-G2 (v1.0)
what does this mean >> “install it on your path” from
Live Logging
- Download the most recent release from Releases · SmartThingsCommunity/smartthings-cli · GitHub.
- Open a Command Prompt window and navigate to the directory where the CLI was downloaded.
- The first time you use the CLI, you will be prompted to log into your SmartThings account. Run a list of your devices by typing:
smartthings devices
- After authenticating the CLI, find the Driver ID for this driver by running:
smartthings edge:drivers:installed
- Now start live logging by running the command below, entering the Driver ID found above and the IP address of your ST Hub in place of <DriverID> and <HubIP>:
smartthings edge:drivers:logcat <DriverID> --hub-address <HubIP>
Sorry if I wasn’t clear - I meant to exclude and the re-include the device. This would do a couple of things. Many z-wave devices are factory reset as part of exclusion (if there’s a separate process to factory reset that motion detector, I suggest doing that too). Exclusion also has the benefit of definitively breaking any automations. Essentially, you get back to square one, so if the problem persists then you’ve eliminated a few possible causes.
well… i did it… wow man, im like a brain surgeon right now and the only tool i have is a hammer… but i think the patient will live
C:\Users\Flip>CD \APPDATA
The system cannot find the path specified.
C:\Users\Flip>CD APPDATA
C:\Users\Flip\AppData>CD LOCAL
C:\Users\Flip\AppData\Local>CD TEMP
C:\Users\Flip\AppData\Local\Temp>CD TEMP1_SMARTTHINGS-WIN.ZIP
C:\Users\Flip\AppData\Local\Temp\Temp1_smartthings-win.zip>SMARTTHINGS
SmartThings unified CLI
VERSION
@smartthings/cli/0.0.0-pre.36 win32-x64 node-v12.18.1
USAGE
$ smartthings [COMMAND]
TOPICS
apps get a specific app or a list of apps
capabilities get a specific capability
config list config file entries
devicepreferences list device preferences or get information for a specific
device preference
deviceprofiles list all device profiles available in a user account or
retrieve a single profile
devices list all devices available in a user account or retrieve a
single device
edge list all channels owned by you or retrieve a single channel
generate generate a Java starter app
installedapps get a specific app or a list of apps
installedschema get a specific schema connector instance or a list of
instances
locations list locations or get information for a specific Location
organizations list all organizations the user belongs to
plugins list installed plugins
presentation query device presentation by vid
rules get a specific rule
schema list all ST Schema Apps currently available in a user
account
COMMANDS
apps get a specific app or a list of apps
autocomplete display autocomplete installation instructions
capabilities get a specific capability
config list config file entries
devicepreferences list device preferences or get information for a specific
device preference
deviceprofiles list all device profiles available in a user account or
retrieve a single profile
devices list all devices available in a user account or retrieve a
single device
help display help for smartthings
installedapps get a specific app or a list of apps
installedschema get a specific schema connector instance or a list of
instances
locations list locations or get information for a specific Location
logout
organizations list all organizations the user belongs to
plugins list installed plugins
presentation query device presentation by vid
rules get a specific rule
schema list all ST Schema Apps currently available in a user
account
C:\Users\Flip\AppData\Local\Temp\Temp1_smartthings-win.zip> SMARTTHINGS DEVICES
» Warning: DEVICES is not a smartthings command.
Did you mean apps? [y/n]:
» Error: Run smartthings help for a list of available commands.
C:\Users\Flip\AppData\Local\Temp\Temp1_smartthings-win.zip>smartthings devices
┌───┬────────────────────────────┬────────────────────────────┬────────┬────────
──────────────────────────────┐
│ # │ Label │ Name │ Type │ Device
Id │
├───┼────────────────────────────┼────────────────────────────┼────────┼────────
──────────────────────────────┤
│ 1 │ Bathroom Dimmer 52252 │ ge-dimmer-scene │ ZWAVE │ 9baa103
1-dc20-49e0-b36e-cc7fce3b313d │
│ 2 │ Dining Dimmer 52252 │ ge-dimmer-scene │ ZWAVE │ cf2459b
2-c7ee-438f-8e89-32b671066534 │
│ 3 │ Driveway Floodlight Sensor │ HomeSeer Floodlight Sensor │ DTH │ ddb0264
8-d206-4770-9eee-0b7cf90995be │
│ 4 │ Hub │ SmartThings v3 Hub │ HUB │ adab044
8-2522-4fc0-bf91-6838f1f3c0cc │
│ 5 │ Kitchen Dimmer 52252 │ ge-dimmer-scene │ ZWAVE │ 6e84553
f-5860-46aa-920d-31a7b5fd303c │
│ 6 │ Note20 Ultra │ Note20 Ultra │ MOBILE │ 71355d7
2-80f3-48cc-9e1b-08a4644f8e66 │
│ 7 │ Samsung 7 Series (65) │ [TV] Samsung 7 Series (65) │ OCF │ d34b8a4
4-1487-4290-a27f-2616472134f8 │
└───┴────────────────────────────┴────────────────────────────┴────────┴────────
──────────────────────────────┘
C:\Users\Flip\AppData\Local\Temp\Temp1_smartthings-win.zip>smartthings edge:driv
ers:installed
┌───┬───────┬────────────────────┬──────────────────────────────────────┐
│ # │ Label │ Name │ Device Id │
├───┼───────┼────────────────────┼──────────────────────────────────────┤
│ 1 │ Hub │ SmartThings v3 Hub │ adab0448-2522-4fc0-bf91-6838f1f3c0cc │
└───┴───────┴────────────────────┴──────────────────────────────────────┘
? Select a hub. 1
┌───┬──────────────────────────────────────┬────────────────────────────────────
┬─────────────┬────────────────────────────┬────────────────────────────────────
──┬──────────────────────────────────────┬────────────────────────────┐
│ # │ Driver Id │ Name
│ Description │ Version │ Channel Id
│ Developer │ Vendor Summary Information │
├───┼──────────────────────────────────────┼────────────────────────────────────
┼─────────────┼────────────────────────────┼────────────────────────────────────
──┼──────────────────────────────────────┼────────────────────────────┤
│ 1 │ e120daf2-8000-4a9d-93fa-653214ce70d1 │ GE Z-Wave Motion Switch/Dimmer
│ │ 2022-01-15T14:11:39.76481 │ 479886db-f6f5-41dd-979c-9c5f9366f07
0 │ ea3129b7-51bc-f893-7cb5-1a79ba85f2b1 │ │
│ 2 │ 5ad2cc83-5503-4040-a98b-b0fc9931b9fe │ GE Z-Wave Switch/Dimmer/Fan/Outlet
│ │ 2022-02-03T19:19:39.701624 │ 479886db-f6f5-41dd-979c-9c5f9366f07
0 │ ea3129b7-51bc-f893-7cb5-1a79ba85f2b1 │ │
│ 3 │ 6a90f7a0-e275-4366-bbf2-2e8a502efc5d │ GE Zigbee Switch
│ │ 2022-02-01T21:35:33.624882 │ 479886db-f6f5-41dd-979c-9c5f9366f07
0 │ ea3129b7-51bc-f893-7cb5-1a79ba85f2b1 │ │
└───┴──────────────────────────────────────┴────────────────────────────────────
┴─────────────┴────────────────────────────┴────────────────────────────────────
──┴──────────────────────────────────────┴────────────────────────────┘
C:\Users\Flip\AppData\Local\Temp\Temp1_smartthings-win.zip>smartthings edge:driv
ers:logcat 2
? Enter hub IP address with optionally appended port number: 192.168.xxx.26
2022-02-04T20:40:54.767169153+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet Re
ceived event with handler unnamed
2022-02-04T20:40:54.855811819+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet <Zw
aveDevice: 6e84553f-5860-46aa-920d-31a7b5fd303c [06] (Kitchen Dimmer 52252)> rec
eived Z-Wave command: {args={key_attributes=“KEY_PRESSED_1_TIME”, scene_number=2
, sequence_number=208, slow_refresh=true}, cmd_class=“CENTRAL_SCENE”, cmd_id=“NO
TIFICATION”, dst_channels={}, encap=“S2_AUTH”, payload="\xD0\x80\x02", src_chann
el=0, version=3}
2022-02-04T20:40:55.019880153+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet Fo
und ZwaveDispatcher handler in ge-zwave-switch
2022-02-04T20:40:55.097309153+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet <Zw
aveDevice: 6e84553f-5860-46aa-920d-31a7b5fd303c [06] (Kitchen Dimmer 52252)> emi
tting event: {“state”:{“value”:“pushed”},“component_id”:“main”,“state_change”:tr
ue,“attribute_id”:“button”,“capability_id”:“button”}
2022-02-04T20:40:55.316174486+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet <Zw
aveDevice: 6e84553f-5860-46aa-920d-31a7b5fd303c [06] (Kitchen Dimmer 52252)> emi
tting event: {“state”:{“value”:“down”},“component_id”:“main”,“state_change”:true
,“attribute_id”:“button”,“capability_id”:“button”}
2022-02-04T20:40:55.445150153+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet Ki
tchen Dimmer 52252 device thread event handled
2022-02-04T20:40:55.454492486+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet Re
ceived event with handler unnamed
2022-02-04T20:40:55.545385153+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet <Zw
aveDevice: 6e84553f-5860-46aa-920d-31a7b5fd303c [06] (Kitchen Dimmer 52252)> rec
eived Z-Wave command: {args={indicator_0_value=“OFF_DISABLE”, indicator_objects=
{{indicator_id=“NODE_IDENTIFY”, property_id=“ON_OFF_PERIOD”, value=0}, {indicato
r_id=“NODE_IDENTIFY”, property_id=“ON_OFF_CYCLES”, value=0}, {indicator_id=“NODE
_IDENTIFY”, property_id=“ONE_TIME_ON_OFF_PERIOD”, value=0}}, value=“OFF_DISABLE”
}, cmd_class=“INDICATOR”, cmd_id=“REPORT”, dst_channels={}, encap=“S2_AUTH”, pay
load="\x00\x03\x50\x03\x00\x50\x04\x00\x50\x05\x00", src_channel=0, version=2}
2022-02-04T20:40:55.576928153+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet Ki
tchen Dimmer 52252 device thread event handled
2022-02-04T20:42:38.044096916+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet Re
ceived event with handler unnamed
2022-02-04T20:42:38.058082916+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet <Zw
aveDevice: 9baa1031-dc20-49e0-b36e-cc7fce3b313d [0C] (Bathroom Dimmer 52252)> re
ceived Z-Wave command: {args={indicator_0_value=“OFF_DISABLE”, indicator_objects
={{indicator_id=“NODE_IDENTIFY”, property_id=“ON_OFF_PERIOD”, value=0}, {indicat
or_id=“NODE_IDENTIFY”, property_id=“ON_OFF_CYCLES”, value=0}, {indicator_id=“NOD
E_IDENTIFY”, property_id=“ONE_TIME_ON_OFF_PERIOD”, value=0}}, value=“OFF_DISABLE
“}, cmd_class=“INDICATOR”, cmd_id=“REPORT”, dst_channels={}, encap=“S2_AUTH”, pa
yload=”\x00\x03\x50\x03\x00\x50\x04\x00\x50\x05\x00”, src_channel=0, version=2}
2022-02-04T20:42:38.067494916+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet Ba
throom Dimmer 52252 device thread event handled
2022-02-04T20:42:38.231476916+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet Re
ceived event with handler unnamed
2022-02-04T20:42:38.240880249+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet <Zw
aveDevice: 9baa1031-dc20-49e0-b36e-cc7fce3b313d [0C] (Bathroom Dimmer 52252)> re
ceived Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_MULTILEVEL
“, cmd_id=“REPORT”, dst_channels={}, encap=“S2_AUTH”, payload=”\x00”, src_channe
l=0, version=1}
2022-02-04T20:42:38.251246583+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet Fo
und ZwaveDispatcher handler in ge-zwave-switch
2022-02-04T20:42:38.257856583+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet <Zw
aveDevice: 9baa1031-dc20-49e0-b36e-cc7fce3b313d [0C] (Bathroom Dimmer 52252)> em
itting event: {“state”:{“value”:“off”},“component_id”:“main”,“attribute_id”:“swi
tch”,“capability_id”:“switch”}
2022-02-04T20:42:38.277838583+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet Fo
und ZwaveDispatcher handler in ge-zwave-switch
2022-02-04T20:42:38.285602583+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet Ba
throom Dimmer 52252 device thread event handled
so the above logs are simply turning on and off all 3 switches to see if the logs were going to be created. and they were… looks like chinese to me. 
also @philh30 is there a way i can buy ya lunch? for the work youre doing for me here? i appreciate ya.
I don’t see anything wrong in those logs. BTW, if you put three of these quotes ``` on a separate line before and after the hub logs, they’ll be formatted in a more readable format (and in a way that allows those using assistive technology to more easily skip them).
This line is interesting. I haven’t seen Jasco use the Indicator command class. I have to wonder what’s possible with it.
I think that best case with the logs from the switches will be that if there really is a causal relationship that the time stamps will line up between these logs and those from the motion sensor. They won’t line up perfectly though since they’re coming out of two different systems.
The second to last line of code in the motion sensor DTH is below. Delete the // at the beginning of the line, save, and publish. You should then start getting more logs.
// log.trace(msg)
The thing you’re looking for here will be the z-wave command (it should be a Notification Report) preceding the “motion is active” line. Ideally grab both a legitimate motion event and one that you think is false.
I appreciate the sentiment, but I’m not a starving programmer. Consider donating to a charity instead.
understood. will check it. oddly enough, i havent noticed the anomoly in days now… its almost as if something was changed, not from me, i havent done anything, but its not occuring at all in the past few days, not even once.
done, will monitor and see
you da man. ty for your work and help here. on a side note. the corporation i work for has me running this log4j scan tool on our Windows 7 and 10 machines that our customers use, i had no idea what the fuss was about unitl i researched log4j… considering that smartthings uses java, is there a something to be worried about here? i found some dead end threads of others asking about log4j and smartthings. whats your take on this ?
‘’’
ddb02648-d206-4770-9eee-0b7cf90995be 5:34:56 PM: debug Driveway Floodlight Sensor: motion is active (i went outside and danced around to activate the motion sensor, however due to the settings for lux, the light will not come on until its darker)
ddb02648-d206-4770-9eee-0b7cf90995be 5:34:56 PM: trace NotificationReport(eventParametersLength: 0, eventParameter: , zensorNetSourceNodeId: 0, v1AlarmType: 0, reserved61: 0, notificationStatus: 255, sequence: false, event: 8, notificationType: 7, v1AlarmLevel: 0)
ddb02648-d206-4770-9eee-0b7cf90995be 5:32:49 PM: debug Driveway Floodlight Sensor: temperature is 78.7F
ddb02648-d206-4770-9eee-0b7cf90995be 5:32:49 PM: trace SensorMultilevelReport(scale: 1, sensorValue: [3, 19], precision: 1, sensorType: 1, scaledSensorValue: 78.7, size: 2)
ddb02648-d206-4770-9eee-0b7cf90995be 5:32:48 PM: trace Driveway Floodlight Sensor: illuminance is 900lux
ddb02648-d206-4770-9eee-0b7cf90995be 5:32:48 PM: trace SensorMultilevelReport(scale: 1, sensorValue: [3, 132], precision: 0, sensorType: 3, scaledSensorValue: 900, size: 2)
ddb02648-d206-4770-9eee-0b7cf90995be 5:27:48 PM: debug Driveway Floodlight Sensor: temperature is 79.0F
ddb02648-d206-4770-9eee-0b7cf90995be 5:27:48 PM: trace SensorMultilevelReport(scale: 1, sensorValue: [3, 22], precision: 1, sensorType: 1, scaledSensorValue: 79.0, size: 2)
ddb02648-d206-4770-9eee-0b7cf90995be 5:27:47 PM: trace Driveway Floodlight Sensor: illuminance is 900lux
ddb02648-d206-4770-9eee-0b7cf90995be 5:27:47 PM: trace SensorMultilevelReport(scale: 1, sensorValue: [3, 132], precision: 0, sensorType: 3, scaledSensorValue: 900, size: 2)
ddb02648-d206-4770-9eee-0b7cf90995be 5:24:21 PM: debug Driveway Floodlight Sensor: switch is off
ddb02648-d206-4770-9eee-0b7cf90995be 5:24:21 PM: trace SwitchBinaryReport(value: 0)
ddb02648-d206-4770-9eee-0b7cf90995be 5:24:18 PM: debug off()… (manually turned off the light via the ST app)
ddb02648-d206-4770-9eee-0b7cf90995be 5:24:11 PM: debug Driveway Floodlight Sensor: switch is on
ddb02648-d206-4770-9eee-0b7cf90995be 5:24:11 PM: trace SwitchBinaryReport(value: 255)
ddb02648-d206-4770-9eee-0b7cf90995be 5:24:08 PM: debug on()…’’’ (manually turned on the light via the ST app)
When you get a false one, this is the line to pay attention to. It’s possible that the device is reporting something unexpected with a NotificationReport that the DTH is interpreting as a motion event. If the false reports look exactly the same, then it’s really getting down to something with the device.
No clue. But a big part of my decision to keep my smart home with Samsung is that I expect them to have the resources to quickly respond to a vulnerability like that.
hey @philh30 hope all is well. so last night there was a cloud outage, and i decided to refresh everything. So concerning this Edge driver, one thing that always annoyed me was, when turning off the light, the light slowly dims to off… i see there is Switched Mode or Dimmer Mode in the settings which allows a quick off, when you hit the off switch. is there any chance you could update the driver so that when the setting is in Dimmer Mode, that a “quicker” dim rate is achievable? the problem with push switches is sometimes you just dont actuate the switch intuitively, and ive found myself walking out of the bathroom, tapped the switch, but didnt actually turn off the light… and having a slow dim has always led me to not really look back to see if the light went out… but if it quickly went out, like it does is Switch Mode, it would be more intuitive.
The options in the settings menu are all of the configuration options that the device supports in its firmware. Your model should have an option to dim quickly or slowly, though I don’t know whether that effects the dim speed on a physical toggle of the switch or if it’s just for z-wave commands.
Another thing you can look at is whether your bulbs use the full 0-100% range of the dimmer. If your bulbs hit full strength at 70%, then a good portion of the time when your bulbs are turning off is spent dimming in a range where you don’t see a difference. Your model should have a max brightness setting, and you can try setting that to match when your bulbs hit max brightness.
There are other things that could be done to change ramp rate when the change is being sent by the hub in a z-wave command, but control at the switch is completely governed by the device firmware and the few settings Jasco built in for us to play with.
the dim rate changes nothing when tapping/toggling down.
if i set a zwave command (routine) to turn off the light with a toggle down, still, the light slowly dims to off over the course of 1.5 seconds. also changing the dim rate to slow or quick, did nothing. still a 1.5 sec dim.
in switched mode, the light has the capability to turn off immediately. why this cannot be a thing in dimmer mode is silly.