SmartThings Community

Hub Firmware Release Notes - 17.12/17.13/17.14

Removing cloud and making everything local with the update? Didn’t think so. :slight_smile: its not a hard concept, st cloud=unreliable and slow. Perks of a corporate owned automation system I suppose.

@nastevens this issue isn’t limited to Locks but other devices also. Today I excluded a perfectly working Z-Wave Switch and then paired it again. It paired up with all 0000 for MSR and more missing information (see below)

Original Raw Description

Raw Description zw:L type:1001 mfr:027A prod:0003 model:0087 ver:3.81 zwv:4.05 lib:03 cc:5E,72,86,85,59,5A,73,70,25,27,71,32,20 role:05 ff:8700 ui:8700

Re-Paired Raw Description

Raw Description zw:L type:1001 mfr:0000 prod:0000 model:0000 ver:0.00 zwv:0.00 lib:00 cc:5E,72,86,85,59,5A,73,70,25,27,71,32,20

We’re getting reports from users across the board about this issue, it’s also messing up with the platform picking the right device handler. It’s also causing other random communication issues with the device according to some users.

Apparently ST support is telling users that it’s a device issue or the locks/devices aren’t supported.

I think it may warrant an investigation, this issue started only after the October firmware update.

3 Likes

@nastevens I think part of the issue is with the pairing process, after a device pairs (say the switch completed pairing) it took almost 50 seconds for it to recognize that it had completed pairing and display in the screen that the device had been found.

Some folks (me too) keep putting the device back into pairing mode and do this multiple times, i.e. the devices ends up pairing multiple times but the ST app still doesn’t show a confirmation until almost a minute later.

While the exclusion is almost instant (within a second), the pairing confirmation takes almost a minute. I don’t know if that part of the issue.

I even tried pairing it just once, the pairing itlsef took about 3 seconds, it took a solid 50 seconds to show up on the screen as a device was found.

I’m just wondering between the pairing completing (3 seconds) and the next 50 seconds what’s the hub doing and is that where the issue lies with not detecting the device data correctly?

I can consistently replicate this issue. Guidance would be much appreciated.

4 Likes

@nastevens - I’ve got to stop these multi posts!!

So when this issue happens about RAW description missing information and all 0000 etc.

The next thing that starts is communication issues with the hub, now this Z-Wave switch that was working PERFECTLY before I excluded and re paired, is now getting these errors in the event log:

2017-06-06 9:10:32.084 PM EDT
moments ago HUB Z-Wave Relay [3E]: Not respon… Z-Wave Relay [3E]: Not responding

First of all it’s identified it as a Z-Wave Relay and I’m guessing that because of the missing information, but the more concerning issue is the not responding messages. Let me know if I can help in any way.

EDIT: When it doesn’t pair properly it refuses to communicate with the device, simple on / off command don’t work.

2 Likes

@nastevens Promise last post for now…

So the was I was finally able to get it to correctly and complete pair and identify the device was by doing the following steps: (I can replicate the successful pairing consistently with these steps and consistently unsuccessful pairing if I don’t follow these steps)

  1. Reboot Hub
  2. Exclude device
  3. Reboot Hub
  4. Wait for 5 minutes
  5. Start “Add New Device” on ST app
  6. Wait for 5-10 seconds and then starting the pairing steps on the device
  7. Pairing completed within 5 seconds and identified correctly with all parameters and even correct device handler

Here are the logs of when it does NOT properly include a device and waits for 50 seconds before the pairing completes with missing/incorrect data. Hope these logs help. See the timelines, starts a search at 9:04:04 and finishes the join at 9:04:51 (almost 45 seconds).

2017-06-06 9:04:58.155 PM EDT
21 minutes ago HUB zwStatus ready Z-Wave device setup finished
2017-06-06 9:04:56.347 PM EDT
21 minutes ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:0005CDA0AC3A, networkAddress:C0A80112, deviceAddress:1F90, stringCount:04, ssdpPath:/description.xml, ssdpU…
2017-06-06 9:04:53.393 PM EDT
21 minutes ago HUB deviceUpdate deviceUpdate Z-Wave Relay updated
2017-06-06 9:04:53.353 PM EDT
21 minutes ago HUB deviceAdd deviceAdd Z-Wave Relay added
2017-06-06 9:04:51.138 PM EDT
21 minutes ago HUB zwjoin 3E zw:L type:1001 mfr:0000 prod:0000 model:0000 ver:0.00 zwv:0.00 lib:00 cc:5E,72,86,85,59,5A,73,70,25,27,71,32,20
2017-06-06 9:04:43.962 PM EDT
21 minutes ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:0005CDA0AC3A, networkAddress:C0A80112, deviceAddress:1F90, stringCount:04, ssdpPath:/description.xml, ssdpU…
2017-06-06 9:04:35.936 PM EDT
21 minutes ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:0005CDA0AC3A, networkAddress:C0A80112, deviceAddress:1F90, stringCount:04, ssdpPath:/description.xml, ssdpU…
2017-06-06 9:04:26.211 PM EDT
21 minutes ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:0005CDA0AC3A, networkAddress:C0A80112, deviceAddress:1F90, stringCount:04, ssdpPath:/description.xml, ssdpU…
2017-06-06 9:04:20.312 PM EDT
22 minutes ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:0005CDA0AC3A, networkAddress:C0A80112, deviceAddress:1F90, stringCount:04, ssdpPath:/description.xml, ssdpU…
2017-06-06 9:04:18.040 PM EDT
22 minutes ago HUB zwStatus device setup Z-Wave device setup started
2017-06-06 9:04:16.527 PM EDT
22 minutes ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:0005CDA0AC3A, networkAddress:C0A80112, deviceAddress:1F90, stringCount:04, ssdpPath:/description.xml, ssdpU…
2017-06-06 9:04:07.092 PM EDT
22 minutes ago HUB zwStatus device inclusion Z-Wave device inclusion started
2017-06-06 9:04:04.107 PM EDT
22 minutes ago HUB zwStatus include search Z-Wave include search started

Here are the logs of the device when it finally paired correctly after rebooting the hub before and after the exclusion as given above. Pairing took place within 20 seconds:

2017-06-06 9:22:50.039 PM EDT
moments ago HUB zwStatus ready Z-Wave include search ended
2017-06-06 9:22:47.456 PM EDT
moments ago HUB zwStatus include search Z-Wave include search started
2017-06-06 9:22:47.311 PM EDT
moments ago HUB ssdpTerm urn:samsung.com:device:Remote… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_10_, ssdpUSN:uuid:…
2017-06-06 9:22:42.614 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:0005CDA0AC3A, networkAddress:C0A80112, deviceAddress:1F90, stringCount:04, ssdpPath:/description.xml, ssdpU…
2017-06-06 9:22:41.025 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_18_, ssdpUSN:uuid:…
2017-06-06 9:22:40.636 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_18_, ssdpUSN:uuid:…
2017-06-06 9:22:37.998 PM EDT
moments ago HUB ssdpTerm urn:samsung.com:device:Remote… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_10_, ssdpUSN:uuid:…
2017-06-06 9:22:37.567 PM EDT
moments ago HUB ssdpTerm urn:samsung.com:device:Remote… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_10_, ssdpUSN:uuid:…
2017-06-06 9:22:37.327 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:0005CDA0AC3A, networkAddress:C0A80112, deviceAddress:1F90, stringCount:04, ssdpPath:/description.xml, ssdpU…
2017-06-06 9:22:36.436 PM EDT
moments ago HUB ssdpTerm urn:samsung.com:device:Remote… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_10_, ssdpUSN:uuid:…
2017-06-06 9:22:35.373 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_18_, ssdpUSN:uuid:…
2017-06-06 9:22:34.788 PM EDT
moments ago HUB zwStatus ready Z-Wave device setup finished
2017-06-06 9:22:32.389 PM EDT
moments ago HUB ssdpTerm urn:samsung.com:device:Remote… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_10_, ssdpUSN:uuid:…
2017-06-06 9:22:32.075 PM EDT
moments ago HUB deviceUpdate deviceUpdate ZooZ ZEN07 MiniPlug updated
2017-06-06 9:22:29.781 PM EDT
moments ago HUB deviceAdd deviceAdd ZooZ ZEN07 MiniPlug added
2017-06-06 9:22:27.823 PM EDT
moments ago HUB zwjoin 3F zw:L type:1001 mfr:027A prod:0003 model:0087 ver:3.81 zwv:4.05 lib:03 cc:5E,72,86,85,59,5A,73,70,25,27,71,32,20
2017-06-06 9:22:25.870 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:0005CDA0AC3A, networkAddress:C0A80112, deviceAddress:1F90, stringCount:04, ssdpPath:/description.xml, ssdpU…
2017-06-06 9:22:25.410 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_18_, ssdpUSN:uuid:…
2017-06-06 9:22:22.317 PM EDT
moments ago HUB ssdpTerm urn:samsung.com:device:Remote… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_10_, ssdpUSN:uuid:…
2017-06-06 9:22:17.455 PM EDT
moments ago HUB zw device: 3F, command: 8612, payload: 03 04 05 03 51 41 00 zw device: 3F, command: 8612,… zw device: 3F, command: 8612, payload: 03 04 05 03 51 41 00
2017-06-06 9:22:16.914 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:0005CDA0AC3A, networkAddress:C0A80112, deviceAddress:1F90, stringCount:04, ssdpPath:/description.xml, ssdpU…
2017-06-06 9:22:15.383 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_18_, ssdpUSN:uuid:…
2017-06-06 9:22:13.087 PM EDT
moments ago HUB zw device: 3F, command: 7205, payload: 02 7A 00 03 00 87 zw device: 3F, command: 7205,… zw device: 3F, command: 7205, payload: 02 7A 00 03 00 87
2017-06-06 9:22:13.050 PM EDT
moments ago HUB zw device: 3F, command: 7205, payload: 02 7A 00 03 00 87 zw device: 3F, command: 7205,… zw device: 3F, command: 7205, payload: 02 7A 00 03 00 87
2017-06-06 9:22:12.998 PM EDT
moments ago HUB zw device: 3F, command: 7205, payload: 02 7A 00 03 00 87 zw device: 3F, command: 7205,… zw device: 3F, command: 7205, payload: 02 7A 00 03 00 87
2017-06-06 9:22:12.367 PM EDT
moments ago HUB ssdpTerm urn:samsung.com:device:Remote… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_10_, ssdpUSN:uuid:…
2017-06-06 9:22:05.316 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_18_, ssdpUSN:uuid:…
2017-06-06 9:22:02.363 PM EDT
moments ago HUB zwStatus device setup Z-Wave device setup started
2017-06-06 9:22:02.338 PM EDT
moments ago HUB ssdpTerm urn:samsung.com:device:Remote… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_10_, ssdpUSN:uuid:…
2017-06-06 9:22:00.293 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_18_, ssdpUSN:uuid:…
2017-06-06 9:21:58.363 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:0005CDA0AC3A, networkAddress:C0A80112, deviceAddress:1F90, stringCount:04, ssdpPath:/description.xml, ssdpU…
2017-06-06 9:21:57.316 PM EDT
moments ago HUB ssdpTerm urn:samsung.com:device:Remote… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_10_, ssdpUSN:uuid:…
2017-06-06 9:21:55.202 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_18_, ssdpUSN:uuid:…
2017-06-06 9:21:52.208 PM EDT
moments ago HUB ssdpTerm urn:samsung.com:device:Remote… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_10_, ssdpUSN:uuid:…
2017-06-06 9:21:51.678 PM EDT
moments ago HUB zwStatus device inclusion Z-Wave device inclusion started
2017-06-06 9:21:46.132 PM EDT
moments ago HUB zwStatus include search Z-Wave include search started

There is something not right with this new hub firmware while pairing

EDIT: I also see these messages while trying to pair the device and when it “successfully” pairs the device with missing or 0000 data

2017-06-06 9:42:25.496 PM EDT
moments ago HUB zwStatus include search Z-Wave include search started
2017-06-06 9:42:25.493 PM EDT
moments ago HUB zwStatus ready Z-Wave is ready
2017-06-06 9:42:25.305 PM EDT
moments ago HUB ssdpTerm urn:schemas-upnp-org:device:M… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_18_, ssdpUSN:uuid:…
2017-06-06 9:42:22.342 PM EDT
moments ago HUB ssdpTerm urn:samsung.com:device:Remote… devicetype:04, mac:508569F6EB5A, networkAddress:C0A8014E, deviceAddress:1DFC, stringCount:04, ssdpPath:/smp_10_, ssdpUSN:uuid:…
2017-06-06 9:42:20.709 PM EDT
moments ago HUB zwStatus starting up Z-Wave starting up
2017-06-06 9:42:20.689 PM EDT
moments ago HUB Err 103: Z-Wave include failed Err 103: Z-Wave include failed
2017-06-06 9:42:19.792 PM EDT
moments ago HUB zwStatus device inclusion Z-Wave device inclusion started

4 Likes

The mfr:0000… and association issue for Schlage locks will be fixed in the next update.

8 Likes

Thanks Duncan! Hope to see the patch soon, this is make a lot of a folks very very happy. BTW if you can share what was the issue?

1 Like

Thanks Duncan. I have the same problem with my lock and hope to see the patch soon.

Can you give a timeframe for the next update? This is far more disruptive (in my case) than you might imagine. THANK YOU for identifying and pursuing this bug!

3 Likes

The issue was that the hub is automatically secure-encapsulating commands to securely-included devices. It’s now required that devices support everything securely that they support normally, but the first generation of Schlage locks predates that requirement so they were ignoring the secure-encapsulated AssociationSet and ManufacturerSpecificGet commands.

5 Likes

I am disappointed to receive the following in email this morning.
Is the decision final?


_Leo F. (SmartThings)
Jun 11, 8:44 AM MST

Hello,

I was taking a look at the article that you had sent me and from what I had gathered was as Duncan had mentioned “The issue was that the hub is automatically secure-encapsulating commands to securely-included devices. It’s now required that devices support everything securely that they support normally, but the first generation of Schlage locks predates that requirement so they were ignoring the secure-encapsulated AssociationSet and ManufacturerSpecificGet commands.”

So, from what I can tell the older locks seem to fail the Z-Wave standards put in place by the protocol which explains why that lock is no longer supported. No firmware update would be able to correct this as it is a protocol standard and not one set by our firmware.

If you have any other questions or need assistance with anything else please let me know.

Thank you,
Leo


The Z wave standard requires backwards compatibility. The device is not “failing” because it predates the new requirement. As a certified zwave controller, it is the SmartThings hub which has to support backwards compatibility. This is why, I’m sure, Duncan said in post 386 above that it will be fixed in a future release. :sunglasses:

The mfr:0000… and association issue for Schlage locks will be fixed in the next update.

So I’m not sure what you mean by “the decision is final” as Duncan has already said a patch will be released that fixes the problem. But the support response you received was somewhat confused as the older devices are not “failing” the third-party protocol in any way.

From the official Zwave Alliance site:

Z-Wave certification ensures that all Z-Wave products work together with each other regardless of brand, including backward-compatibility between versions.

Fortunately, since there will be a patch the problem should be fixed in the future regardless of the confusion. :sunglasses:

2 Likes

I’ll leave the final confirmation to @duncan, but I am looking at the commit that should fix the Schlage association info. I think there was just some miscommunication there, sorry for the confusion.

7 Likes

Yeah, it was a misunderstanding. The issue is a bug with our hub, not the lock, and it’s going to be fixed. The release should be sometime in the next couple weeks.

6 Likes

Thank you Duncan. I look forward to the fix.

One of my hubs is still running version 000.016.00014. Is there a delay in the complete roll out of 17.x or is there something I can do to manually trigger the update?

1 Like

I’m still on 14. I asked the same question a month or two ago. I was told the rollout was still slowly happening. But I’m interested in any answer you get.

:open_mouth: and this is a V2 hub?

yes it is :hourglass_flowing_sand:

Did you try rebooting (warm and cold and using the reset button)?

1 Like