Z-Wave Issues with Firmware Update 30.3

I haven’t seen anything that would make me think there “should” be instability after the update. I have a mostly z-wave household and through all the versions I never had any major instability. So yes, if you are seeing major instability, open tickets.

1 Like

Just ran another repair - and got my bathroom light back. If it keeps recurring, will do.

Since firmware 3.03 i have been getting these issues. Even after the 3.05 update.

So this a video of what is happening to my smartthings setup with my fibaro single switch 2 devices

@Andremain this looks like an issue with your DTH. Which DTH are you using for this? And the 3.03 firmware is the firmware of the device itself.

@jody.albritton. yes i know. Although according to fibaro that should have been 3.3 as there is not 3.03 firmware for that device. The handler i am using the the official handler provided jnside the new Smartthings app. It is not a custom dht. I have no idea why this is happening as my other 2 single switch 2 devives work find with the same handler!

@Andremain, can you try this handler temporarily?

Update: I have posted a DH for the dimmer, what I have patched a few months ago for a user who had similar issues. I’ve just updated the Single Switch 2 DH with the same solution, allowing sourceEndpoint == 1 in the multi channel encapsulation.

So here is the updated DH for the Single Switch 2.

2 Likes

@jody.albritton, the issue with some Dimmer 2 and Single Switch 2, that they report from sourceEndpoint 1 in a multiChannel encapsulation, but the DH handles only sourceEndpoint 0 in the multiChannel encapsulation part of the code. The fix is just a small addition to the code, as

if (cmd.sourceEndPoint as Integer == 0)

Change to this in line 317

if (cmd.sourceEndPoint as Integer == 0 || cmd.sourceEndPoint as Integer == 1)

@steven.green added the MultiChannel encapsulation part a few months back, as these devices tend to randomly encapsulate messages, but it handles by default only sourceEndpoint 0. He might have better idea what is going on with these devices, but the short fix should work.

@jody.albritton

YES! The fixed handler works like a charm!!! Thank you so much!!!

Please add this fix to the official handler inside the new app.

1 Like

Happy to help! Great that it has worked for you.

You are the best man!

I used your device handler before on my fibaro dimmer 2 when I was having this problem and it worked great the odd thing is recently I’ve been able to go back to using the official device handler :thinking:

There is something weird with those devices. I have no idea why are they reporting from sourceEndpoint 1 with multi channel encapsulation. Generally they shouldn’t as that was the way before, but they do for some unknown reason. Someone from ST might have a better idea.

1 Like

Anybody out there able to take a look at the DTH for the Aeotec HEM v5 power monitor by ClassicGOD? Trying to edit this to respond on a different endpoint is far beyond what I’m capable of. :slight_smile:

Are you guys able to run a Z-Wave repair with the latest firmware? My hub doesn’t seem to do anything, the live log doesn’t even show anything happening.

Where are you looking? In the app or the IDE? If you are looking in the app and on iOS, there is a known issue with the Z-Wave logs showing the wrong timestamp and an incomplete record of the repair.

1 Like

@Brad_ST: both. The iOS apps are definitely off, in both the new 2.0 and old classic version of the app.

But I also don’t see anything happening within the LiveLog on the IDE.

I started the repair at 8:10 AM and it finished at 8:13 AM (per the iOS app):

[eda628cc-b05c-47bd-ba3a-9c1fd32c2f27](https://graph-na04-useast2.api.smartthings.com/ide/logs#eda628cc-b05c-47bd-ba3a-9c1fd32c2f27) 8:13:30 AM: debug Parsed SwitchBinaryReport(value: 0) to ['name':'switch', 'value':'off', 'type':'digital', 'linkText':'Front Door Light Switch', 'descriptionText':Front Door Light Switch switch is off, 'isStateChange':false, 'displayed':false]

[eda628cc-b05c-47bd-ba3a-9c1fd32c2f27](https://graph-na04-useast2.api.smartthings.com/ide/logs#eda628cc-b05c-47bd-ba3a-9c1fd32c2f27) 8:13:30 AM: debug ---BINARY SWITCH REPORT V1--- Front Door Light Switch sent SwitchBinaryReport(value: 0)

[eda628cc-b05c-47bd-ba3a-9c1fd32c2f27](https://graph-na04-useast2.api.smartthings.com/ide/logs#eda628cc-b05c-47bd-ba3a-9c1fd32c2f27) 8:13:30 AM: debug description: zw device: 0F, command: 2503, payload: 00

[eda628cc-b05c-47bd-ba3a-9c1fd32c2f27](https://graph-na04-useast2.api.smartthings.com/ide/logs#eda628cc-b05c-47bd-ba3a-9c1fd32c2f27) 8:13:30 AM: debug ---BINARY SWITCH REPORT V1--- Front Door Light Switch sent SwitchBinaryReport(value: 0)

[eda628cc-b05c-47bd-ba3a-9c1fd32c2f27](https://graph-na04-useast2.api.smartthings.com/ide/logs#eda628cc-b05c-47bd-ba3a-9c1fd32c2f27) 8:13:30 AM: debug description: zw device: 0F, command: 2503, payload: 00

[5345dfb6-2675-411c-9343-d0aa78376489](https://graph-na04-useast2.api.smartthings.com/ide/logs#5345dfb6-2675-411c-9343-d0aa78376489) 8:13:27 AM: debug Parsed SwitchBinaryReport(value: 0) to ['name':'switch', 'value':'off', 'type':'digital', 'linkText':'Kitchen Sink Light Switch', 'descriptionText':Kitchen Sink Light Switch switch is off, 'isStateChange':false, 'displayed':false]

[5345dfb6-2675-411c-9343-d0aa78376489](https://graph-na04-useast2.api.smartthings.com/ide/logs#5345dfb6-2675-411c-9343-d0aa78376489) 8:13:27 AM: debug ---BINARY SWITCH REPORT V1--- Kitchen Sink Light Switch sent SwitchBinaryReport(value: 0)

[5345dfb6-2675-411c-9343-d0aa78376489](https://graph-na04-useast2.api.smartthings.com/ide/logs#5345dfb6-2675-411c-9343-d0aa78376489) 8:13:27 AM: debug description: zw device: 07, command: 2503, payload: 00

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: debug Front Door Lock user 10 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: debug Front Door Lock user 9 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: debug Front Door Lock user 8 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: debug Front Door Lock user 7 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: debug Front Door Lock user 6 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: debug Front Door Lock user 5 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: debug Front Door Lock user 4 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: debug Front Door Lock user 3 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: debug Front Door Lock user 2 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: debug Front Door Lock User 1 Everyone is a permanent code and is already active

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: trace The date/time on the hub now is Thu Jun 04 2020 08:13 CDT

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:13:13 AM: warn READ THIS BEFORE PROCCEDING: IT IS NORMAL TO SEE DEBUG MESSAGES EVERY MINUTE, IT CONFIRMS THAT THE APP IS HEALTHY AND RUNNING IN THE CLOUD. IT DOES NOT COMMUNICATE WITH THE LOCK UNLESS YOU SEE A MESSAGE BOX SAYING 'REQUESTED LOCK TO XXXXX'.

[5654e0c2-45fd-453b-a91b-ad0970de274b](https://graph-na04-useast2.api.smartthings.com/ide/logs#5654e0c2-45fd-453b-a91b-ad0970de274b) 8:13:08 AM: debug Parsed BasicReport(value: 0) to [['name':'switch', 'value':'off', 'type':'physical', 'linkText':'Family Room Light Dimmer', 'descriptionText':Family Room Light Dimmer switch is off, 'isStateChange':false, 'displayed':false]]

[5654e0c2-45fd-453b-a91b-ad0970de274b](https://graph-na04-useast2.api.smartthings.com/ide/logs#5654e0c2-45fd-453b-a91b-ad0970de274b) 8:13:08 AM: debug description: zw device: 18, command: 2003, payload: 00

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: debug Front Door Lock user 10 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: debug Front Door Lock user 9 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: debug Front Door Lock user 8 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: debug Front Door Lock user 7 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: debug Front Door Lock user 6 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: debug Front Door Lock user 5 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: debug Front Door Lock user 4 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: debug Front Door Lock user 3 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: debug Front Door Lock user 2 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: debug Front Door Lock User 1 Everyone is a permanent code and is already active

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: trace The date/time on the hub now is Thu Jun 04 2020 08:12 CDT

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:12:13 AM: warn READ THIS BEFORE PROCCEDING: IT IS NORMAL TO SEE DEBUG MESSAGES EVERY MINUTE, IT CONFIRMS THAT THE APP IS HEALTHY AND RUNNING IN THE CLOUD. IT DOES NOT COMMUNICATE WITH THE LOCK UNLESS YOU SEE A MESSAGE BOX SAYING 'REQUESTED LOCK TO XXXXX'.

[23773d8e-8ab7-4c95-b7fe-f1020b20a0a8](https://graph-na04-useast2.api.smartthings.com/ide/logs#23773d8e-8ab7-4c95-b7fe-f1020b20a0a8) 8:12:07 AM: info Updated 22 objects (172ms)

[cc96fb46-cee4-4f78-8eb8-72e967c18af0](https://graph-na04-useast2.api.smartthings.com/ide/logs#cc96fb46-cee4-4f78-8eb8-72e967c18af0) 8:12:07 AM: trace No updates

[cc96fb46-cee4-4f78-8eb8-72e967c18af0](https://graph-na04-useast2.api.smartthings.com/ide/logs#cc96fb46-cee4-4f78-8eb8-72e967c18af0) 8:12:07 AM: info Checking: Auth_token refreshed

[cc96fb46-cee4-4f78-8eb8-72e967c18af0](https://graph-na04-useast2.api.smartthings.com/ide/logs#cc96fb46-cee4-4f78-8eb8-72e967c18af0) 8:12:07 AM: info Requesting ( equipmentStatus runtime extendedRuntime ) for thermostat Garage Thermostat (411987711061)

[cc96fb46-cee4-4f78-8eb8-72e967c18af0](https://graph-na04-useast2.api.smartthings.com/ide/logs#cc96fb46-cee4-4f78-8eb8-72e967c18af0) 8:12:07 AM: info Polling 411987711061

[cc96fb46-cee4-4f78-8eb8-72e967c18af0](https://graph-na04-useast2.api.smartthings.com/ide/logs#cc96fb46-cee4-4f78-8eb8-72e967c18af0) 8:12:06 AM: trace Checking for updates...

[cc96fb46-cee4-4f78-8eb8-72e967c18af0](https://graph-na04-useast2.api.smartthings.com/ide/logs#cc96fb46-cee4-4f78-8eb8-72e967c18af0) 8:12:06 AM: info refreshAuthToken() - Success! Token expires in 59.98 minutes

[cc96fb46-cee4-4f78-8eb8-72e967c18af0](https://graph-na04-useast2.api.smartthings.com/ide/logs#cc96fb46-cee4-4f78-8eb8-72e967c18af0) 8:12:06 AM: info checkThermostatSummary() - HttpResponseException occurred: Auth_token has expired

[cc96fb46-cee4-4f78-8eb8-72e967c18af0](https://graph-na04-useast2.api.smartthings.com/ide/logs#cc96fb46-cee4-4f78-8eb8-72e967c18af0) 8:12:06 AM: trace Checking for updates...

[101bd9b5-5ab2-4b69-b18c-52a0bc88b071](https://graph-na04-useast2.api.smartthings.com/ide/logs#101bd9b5-5ab2-4b69-b18c-52a0bc88b071) 8:11:46 AM: info ╔ Event processed successfully (91ms)

[101bd9b5-5ab2-4b69-b18c-52a0bc88b071](https://graph-na04-useast2.api.smartthings.com/ide/logs#101bd9b5-5ab2-4b69-b18c-52a0bc88b071) 8:11:46 AM: trace ║╔ Execution stage complete. (1ms)

[101bd9b5-5ab2-4b69-b18c-52a0bc88b071](https://graph-na04-useast2.api.smartthings.com/ide/logs#101bd9b5-5ab2-4b69-b18c-52a0bc88b071) 8:11:46 AM: trace ║╚ Execution stage started

[101bd9b5-5ab2-4b69-b18c-52a0bc88b071](https://graph-na04-useast2.api.smartthings.com/ide/logs#101bd9b5-5ab2-4b69-b18c-52a0bc88b071) 8:11:46 AM: trace ║ Runtime (36995 bytes) successfully initialized in 8ms (v0.3.110.20191009) (87ms)

[101bd9b5-5ab2-4b69-b18c-52a0bc88b071](https://graph-na04-useast2.api.smartthings.com/ide/logs#101bd9b5-5ab2-4b69-b18c-52a0bc88b071) 8:11:46 AM: debug ║ RunTime Analysis CS > 30ms > PS > 8ms > PE > 48ms > CE

[101bd9b5-5ab2-4b69-b18c-52a0bc88b071](https://graph-na04-useast2.api.smartthings.com/ide/logs#101bd9b5-5ab2-4b69-b18c-52a0bc88b071) 8:11:46 AM: info ╚ Received event [Moja Holpa].time = 1591276307402 with a delay of -1307ms

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: debug Front Door Lock user 10 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: debug Front Door Lock user 9 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: debug Front Door Lock user 8 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: debug Front Door Lock user 7 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: debug Front Door Lock user 6 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: debug Front Door Lock user 5 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: debug Front Door Lock user 4 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: debug Front Door Lock user 3 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: debug Front Door Lock user 2 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: debug Front Door Lock User 1 Everyone is a permanent code and is already active

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: trace The date/time on the hub now is Thu Jun 04 2020 08:11 CDT

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:11:13 AM: warn READ THIS BEFORE PROCCEDING: IT IS NORMAL TO SEE DEBUG MESSAGES EVERY MINUTE, IT CONFIRMS THAT THE APP IS HEALTHY AND RUNNING IN THE CLOUD. IT DOES NOT COMMUNICATE WITH THE LOCK UNLESS YOU SEE A MESSAGE BOX SAYING 'REQUESTED LOCK TO XXXXX'.

[b26e60b3-5132-472f-b547-49d6f01ef3ce](https://graph-na04-useast2.api.smartthings.com/ide/logs#b26e60b3-5132-472f-b547-49d6f01ef3ce) 8:10:30 AM: error java.util.concurrent.TimeoutException: Execution time exceeded 20 app execution seconds: 75734505025270 @line -1 (traceEvent)

[b26e60b3-5132-472f-b547-49d6f01ef3ce](https://graph-na04-useast2.api.smartthings.com/ide/logs#b26e60b3-5132-472f-b547-49d6f01ef3ce) 8:10:24 AM: debug getChildDevices(false), children=7

[b26e60b3-5132-472f-b547-49d6f01ef3ce](https://graph-na04-useast2.api.smartthings.com/ide/logs#b26e60b3-5132-472f-b547-49d6f01ef3ce) 8:10:20 AM: debug getChildDevices(false), children=7

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:14 AM: trace Checking for next app update after Thu Jun 04 2020 16:03 CDT

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:14 AM: trace Last code check was done 1.898 seconds ago

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:14 AM: trace Heartbeat monitor called

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: debug Front Door Lock user 10 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: debug Front Door Lock user 9 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: debug Front Door Lock user 8 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: debug Front Door Lock user 7 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: debug Front Door Lock user 6 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: debug Front Door Lock user 5 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: debug Front Door Lock user 4 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: debug Front Door Lock user 3 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: debug Front Door Lock user 2 is empty, code already deleted

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: debug Front Door Lock User 1 Everyone is a permanent code and is already active

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: trace The date/time on the hub now is Thu Jun 04 2020 08:10 CDT

[a4a8c471-ac4e-4ad5-9a85-fc314582853b](https://graph-na04-useast2.api.smartthings.com/ide/logs#a4a8c471-ac4e-4ad5-9a85-fc314582853b) 8:10:13 AM: warn READ THIS BEFORE PROCCEDING: IT IS NORMAL TO SEE DEBUG MESSAGES EVERY MINUTE, IT CONFIRMS THAT THE APP IS HEALTHY AND RUNNING IN THE CLOUD. IT DOES NOT COMMUNICATE WITH THE LOCK UNLESS YOU SEE A MESSAGE BOX SAYING 'REQUESTED LOCK TO XXXXX'.

You need to look in the hub events log, not live logging.

1 Like

Your absolutely correct, my bad. It displays on the Hub Events.

Now I am just getting random results, example 4 - Z-Wave switches literally next to each other in a gang box and they aren’t linking with one another, they all are actually connecting to different devices for the next hop before the hub.

Devices side by side might will not choose each other. It is like people standing next each other and shouting.

2 Likes

Is there an updated DH for the ZW5 Double Switch available as well? Mine suddenly stopped working on the child channel for some reason with the regular device handler, but does report online and everything. Just odd.

Thanks in avance,
–Zax