Hub Firmware Beta 19.16

[tpmanley (Tom Manley)]

We are going to be rolling 19.16 out to all the enrolled beta hubs shortly. This includes the following changes since 19.14:

• BUG-42: Hue devices events are generated even when the state is not changing
• Allow a temperature offset of -99° to 99° for all locally running Zigbee DTHs that support temperature offsets (previously the SmartSense Multi Sensor offset wasn’t working correctly)
• Z-Wave reliability improvements
• Z-Wave Switch Generic and Z-Wave Dimmer Switch Generic DTHs now run locally. Note that if you use Smart Lighting with these devices you’ll need to manually update the installed apps to force them to reevaluate where they can run and move to the hub if possible.

[SteveWhite]

It’s still too early to tell, the frequency of the errors does seem to have dropped. I’m still seeing multiple Z-Wave power cycle events. They do not seem to be tied to or happen around the control of any specific device.

2017-11-09 10:04:16.619 PM EST
15 minutes ago	HUB		zw device: 2B, command: 3202, payload: 21 74 00 24 9F 38 00 00 00 00 00 00	zw device: 2B, command: 3202,...		zw device: 2B, command: 3202, payload: 21 74 00 24 9F 38 00 00 00 00 00 00
2017-11-09 10:02:50.573 PM EST
17 minutes ago	HUB		index:05, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:05, mac:4C72B9F8B735, h...		index:05, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-11-09 10:00:21.025 PM EST
19 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-11-09 10:00:18.477 PM EST
19 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-11-09 10:00:16.589 PM EST
19 minutes ago	HUB		ping	ping		ping
2017-11-09 9:55:36.464 PM EST
24 minutes ago	HUB		index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:01, mac:4C72B9F8B735, h...		index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...



2017-11-09 8:47:00.725 PM EST
2 hours ago	HUB		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:51c36ab8-06bb-4662-9f98-158e79683404,	index:16, mac:000420F3C826, i...		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:51c36ab8-06bb-4662-9f98-158e79683404, headers:SFRUUC8xLjEgMjAwIE...
2017-11-09 8:46:56.706 PM EST
2 hours ago	HUB		index:05, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:05, mac:4C72B9F8B735, h...		index:05, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-11-09 8:46:11.110 PM EST
2 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-11-09 8:46:08.629 PM EST
2 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-11-09 8:45:43.253 PM EST
2 hours ago	HUB		index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:6e679fbb-ad26-43aa-bacd-3c18fd08dedd,	index:15, mac:000420F3C826, i...		index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:6e679fbb-ad26-43aa-bacd-3c18fd08dedd, headers:SFRUUC8xLjEgMjAwIE...
2017-11-09 8:45:06.683 PM EST
2 hours ago	HUB		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:034a86c2-b11d-431b-9acd-5c911ca738b5,	index:16, mac:000420F3C826, i...		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:034a86c2-b11d-431b-9acd-5c911ca738b5, headers:SFRUUC8xLjEgMjAwIE...
2017-11-09 8:44:46.625 PM EST
2 hours ago	HUB		ping	ping		ping
2017-11-09 8:44:38.700 PM EST
2 hours ago	HUB		index:16, ip:7F000001, port:0BB8, requestId:a40bd53b-ba81-4e95-bc96-b6a12a7d5062, headers:SFRUUC8xLj	index:16, ip:7F000001, port:0...		index:16, ip:7F000001, port:0BB8, requestId:a40bd53b-ba81-4e95-bc96-b6a12a7d5062, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...

[mtuckman (Mike)]

19.16 was loaded, looks like all of my z-wave switches are running locally!

Only thing is the uptime seems to be stuck at 31 seconds! Not sure it matters but thought it was interesting…

[jkp]

the Uptime issue has been around for quite sometime, it is not related to the beta firmware

Hub Firmware Release Notes - 18.18

Yeah, ignore the uptime shown in the IDE. That is basically the uptime at the time that one of the messages to the cloud containing information that changes infrequently changed, not the current uptime. We’ll probably hide this in a future cloud release as it is confusing. The number is stuck at ~30 as the last time that message was sent the device had just booted. In previous versions this number used to be bigger on startup because startup was significantly slower. #feature

read recently that ST is considering removing that field or changing it.

[mtuckman (Mike)]

Makes sense - Thanks for the heads up!

[wiseman68 (Bob Wise)]

I’m not up on what should be Cloud and Local, but in checking mine more than 50% devices are Cloud including Yale ZigBee Locks, SmartThings Arrival Sensors, ZigBee Bulbs. I understand Arlo Cameras, Lutron Dimmers (Zwave) are cloud

Is this still normal

Bob

[SteveWhite]

Yes that’s normal. This beta is all about pushing device control out to the edge and have it run locally. I am seeing about 85% of my devices running locally now. Thats a good thing as far as I’m concerned.

[wiseman68 (Bob Wise)]

yes but shouldn’t the ZigBee devices be Local Yale, SmartThings Arrival (ZigBee), ZigBee Bulbs?

Bob

[jkp]

Depends on which device handlers you are using for those devices. If you are using any custom device handlers on those devices, then the answer is they will not be running local. Custom device handlers only run in the cloud.

[wiseman68 (Bob Wise)]

JKP
Thanks that answer the Yale and maybe bulbs but SmartThings Arrival Sensors should be Local no?

[tpmanley (Tom Manley)]

@wiseman68

yes but shouldn’t the ZigBee devices be Local Yale, SmartThings Arrival (ZigBee), ZigBee Bulbs?

The ZigBee Lock, Cree Bulb and Arrival Sensor HA DTHs currently do not run locally. We hope to enable these to run locally in the future. Other ones like ZigBee RGBW Bulb, ZigBee Switch, ZigBee Dimmer, etc… do run locally. Keep in mind also that self published DTHs won’t run locally even if you self publish a variant of one of the ones that normally would run locally. I took a quick look at your hub and everything looks correct.

[wiseman68 (Bob Wise)]

Thanks

tpmanley

Bob

[Behold81 (Antony Pugh)]

Ihave not been around much but my Bug with the Plug and Sensor might be resolved with this.

I got my first notification of possible freezing temps outside even though I have had a many days over the last month it should have triggered the warning.

I will monitor it.

[Terk]

Saterday I had an OSRAM bulb that turned on and off multiple times on its own, when I looked in the recent tab for the light all I saw where Amazon Alexa refreshes however I saw those same refreshes many times before that without ever noticing the light acting weird. When I first added the light I had issues with it coming on by itself but then there wouldn’t be anything in the logs showing that it cam on so I hooked it up to an OSRAM hub and flashed the firmware which fixed it going forward.

The issue seems to have stopped on its own sometime Sunday morning.

No one was awake at this time to trigger this:

[RudiP (Rudi Prunzel)]

Since 19.16 my Hub v2 is acting weird. The feeling is that it’s not sending commands to the devices (LAN, ZigBee or Z-Wave) but I’ve noticed that the commands are taking a long time to come from the Cloud to the Hub to the Device.

One example is when running a Routine (like Good Night) using the ST App on Android. The Mode changes right away in the ST App, the Notifications (and Logs) on the ST App and IDE shows that the commands were sent to the devices and everything occurs at max in 16 seconds. But I’m looking at the devices and they turn off after 1 minute or more sometimes.
Some of the devices are currently set to Local execution but others are set to Cloud.

I was hoping that over the weekend and after several reboots (and physical disconnect from Power) that the issue would go away but it is still happening. Just reporting here to see if someone else had the same issue

[posborne (Paul Osborne)]

@jkp

the Uptime issue has been around for quite sometime, it is not related to the beta firmware
…
read recently that ST is considering removing that field or changing it.

Change should be coming in the next few weeks that displays “Last Boot Time” (e.g. 10/2/2017 08:14:34 CDT) instead of the useless uptime field. This should be good enough to determine if the hub might have rebooted or been power cycled recently.

This is based on the same info from the hub but actually makes it usable.

[Terk]

Tom, since the Arrival Sensor does not work locally and there is no keypad that I’m aware of that will work locally how do we go about disarming the system if we arrive home and the internet is down? Will the app be able to connect to the system via our internal network in that case? I just thought about this and am not at home to test.

Thanks.