Firmware update Wednesday

[tslagle13 (Tim Slagle)]

From support:

[beckwith]

Aaron sent me a copy also. Here is a text version:

Update notes for the 13.5 release:

1. Enhanced Cloud Link Security

2. All server communication now uses the binary protocol. This improves efficiency and lowers bandwidth use.

3. Support for generically reading ZigBee client attributes

4. Added real time with timezone, based on the Location so the hub can provide the ZigBee time cluster

5. Fixed bug that continued to poll Z-Wave switches after they were deleted

6. Fixed bug that caused some battery powered devices to be over-polled

7. Fixed bug that interfered with adding Z-Wave devices with long command support lists

8. Added Z-Wave “replace failed device” feature

9. Improved reliability of Z-Wave network repair

[tslagle13 (Tim Slagle)]

My favorite change I think is the “replaced failed device” feature.

Ability to replace a device without removing the devoce completey from STs? No more removing tons of rules and then adding all of them back? I hope so!

[beckwith]

Saw that too and hope that your interpretation is right. I would think it would require more than a firmware update, however, so it might not work until an app or IDE update.

I think #4 allows Orbit water timer pairing.

[tslagle13 (Tim Slagle)]

@beckwith

I think #4 allows Orbit water timer pairing.

I agree.

---

[joelw135 (Joel W)]

[quote="@ beckwith

• I think this is the first “official” firmware update since 11.00603.
  Otherwise, support would load 000.011.00705 to fix known issues upon
  request.
  [/quote]

So are you saying that I don’t need the update and will not get it?

[Tyler]

Yikes! That’s my fault. Forgot to include the time zone in the email blast for today.

It’s EST.

[beckwith]

@joelw135

Everyone is getting this firmware update from what I can tell. It just will be rolled out over time.

[Tyler]

Correct. Staged roll out. Everyone will get the update.

[beckwith]

Looks like my firmware update has already started but failed. I happened to be checking the logs for a different reason and this came across:

62d0734c-e095-491b-91b5-dc6071812a0d 10:07:24 AM: trace cp desc: firmware update started
62d0734c-e095-491b-91b5-dc6071812a0d 10:07:10 AM: trace cp desc: Firmware update failed
62d0734c-e095-491b-91b5-dc6071812a0d 10:07:10 AM: trace cp desc: hub has disconnected
62d0734c-e095-491b-91b5-dc6071812a0d 10:06:59 AM: trace cp desc: hardwareID:0001, version:02, {deleted…}, zigbeeFWMajor:1, zigbeeFWMinor:5, zigbeeFWBuild:4, zigbeePanID:BA9A, zigbeeNodeID:0000, zigbeePowerLevel:254, zigbeeChannel:14, zwaveVersion:0, zwaveSerialVersion:0, zwaveHomeID:D7111F34, zwaveNodeID:01, zwavePowerLevel:00, zwaveRegion:255, bootloaderVersion:4
62d0734c-e095-491b-91b5-dc6071812a0d 10:06:54 AM: trace cp desc: Firmware download started

[tslagle13 (Tim Slagle)]

Interesting… I got it too. But mine completed and I am on the following

000.013.00005
zigbeeFirmware: 1.5.4
zwaveVersion: 809

2015-01-14 9:39:21.488 AM CST
36 minutes ago HUB firmwareSuccess 1.0 Firmware update complete
2015-01-14 9:38:26.683 AM CST
37 minutes ago HUB firmwareRebooting 0.0 Firmware downloaded completed and rebooting hub
2015-01-14 9:38:26.666 AM CST
37 minutes ago HUB firmwareDownloading 1.0 Firmware download in progress

[brianlees (Brian Smith)]

@beckwith

Added Z-Wave “replace failed device” feature

My feature request finally made it in! Nice… Of course, it was really needed to be able to swap to a new hub…since I’m guessing the code base to replace a failed device is similar to what will do the migration?

Feature Request - "Swap/Replace a Device Wizard"

I’m looking towards the future when I have to swap out / replace one of my devices. If I have a device that has multiple smartapps associated with to it, the process of replacing it seems like it could be a bit painful. Having an option on each device page allowing you to “swap” it out with another would make the process painless for the end user. As we all know, devices die. Have a good process to replace them in the app would benefit everyone!

[tslagle13 (Tim Slagle)]

@brianlees

Of course, it was really needed to be able to swap to a new hub…since I’m guessing the code base to replace a failed device is similar to what will do the migration?

yep. i would also assume the same thing

[smart (Ron S)]

@beckwith

Added real time with timezone, based on the Location so the hub can provide the ZigBee time cluster

Can somebody explain this part to me, please? Willing to learn. Is it like providing the current time so that other devices on the network can synchronize to a common time value???

[dfairbro1 (Dawn Fairbro)]

Eric, I have the same

[beckwith]

It is explained here:

Orbit Sprinkler Timer (Iris)

Update! Ok so there is a part of the ZigBee spec where a device needs to know the time of day it is. We don’t support this in the base spec like other controllers would right now. When the valve pairs it keeps on asking for the time until it gets it. Since the hub isn’t telling it the time, it keeps on asking and asking. I’m going to either try hacking it in, or see if I can somehow get it to stop asking. If I can’t then it will take a new firmware version which could take a while.

[beckwith]

OK, so I couldn’t wait for a response from support why my firmware failed so I tried recycling the power on my hub in hopes that it would try again. Now I get the following:

e8af73f1-3d38-4e00-b3a2-f52fdaca0edf 11:28:00 AM: trace cp desc: firmware update ember version: 01.05.0004
e8af73f1-3d38-4e00-b3a2-f52fdaca0edf 11:27:59 AM: trace cp desc: register
e8af73f1-3d38-4e00-b3a2-f52fdaca0edf 11:27:59 AM: trace cp desc: stack status: 90
e8af73f1-3d38-4e00-b3a2-f52fdaca0edf 11:26:22 AM: trace cp desc: firmware update main failed
e8af73f1-3d38-4e00-b3a2-f52fdaca0edf 11:26:22 AM: trace cp desc: hub has disconnected

So it looks like it is failed and isn’t going to try again until something gives it a push.

Others see a firmware attempt succeed or fail?

[greg]

Mine was successful 1

[tslagle13 (Tim Slagle)]

@beckwith

OK, so I couldn’t wait for a response from support why my firmware failed so I tried recycling the power on my hub in hopes that it would try again. Now I get the following:

e8af73f1-3d38-4e00-b3a2-f52fdaca0edf 11:28:00 AM: trace cp desc: firmware update ember version: 01.05.0004e8af73f1-3d38-4e00-b3a2-f52fdaca0edf 11:27:59 AM: trace cp desc: registere8af73f1-3d38-4e00-b3a2-f52fdaca0edf 11:27:59 AM: trace cp desc: stack status: 90e8af73f1-3d38-4e00-b3a2-f52fdaca0edf 11:26:22 AM: trace cp desc: firmware update main failede8af73f1-3d38-4e00-b3a2-f52fdaca0edf 11:26:22 AM: trace cp desc: hub has disconnected

So it looks like it is failed and isn’t going to try again until something gives it a push.

Others see a firmware attempt succeed or fail?

@tslagle13

Interesting… I got it too. But mine completed and I am on the following

000.013.00005zigbeeFirmware: 1.5.4zwaveVersion: 809

2015-01-14 9:39:21.488 AM CST36 minutes ago HUB firmwareSuccess 1.0 Firmware update complete2015-01-14 9:38:26.683 AM CST37 minutes ago HUB firmwareRebooting 0.0 Firmware downloaded completed and rebooting hub2015-01-14 9:38:26.666 AM CST37 minutes ago HUB firmwareDownloading 1.0 Firmware download in progress

---

[beckwith]

2 success and 1 failure so far.