SmartThings Community

Hub Firmware 25.x Beta


#142

Yup, my vents are reporting temperature now, thanks!

On a separate note, did anyone notice that the Classic app stopped showing pictures for a Room? All my Rooms have lost the image (png) I was using, except 1.


(Jimmy) #143

mine still work fine


#144

Yeah, figures I’d have weird stuff going on for a Friday. I can easily add mine back.


(www.rboyapps.com - Make your home your butler!) #145

Can you open the IDE Live Logging, unlock using your code copy/paste and PM me your logs


(Chris Baumler) #146

Go ahead and log a bug in Centercode, and I’ll investigate.


#147

Hmmm, something is up. A couple of my Rooms now have names I gave them a long time ago. I made Room name changes a couple months ago, and now they’re back, along with no more Room icons.

I’m sure this can’t be firmware related, so I’ll address this elsewhere because this is a little concerning…


#148

Anyone using Utilitech sirens? If so, do you see this type of battery reporting activity:

Upstairs Siren battery states

Date Name Value Units
2019-02-01 3:31 PM EST - 6 minutes ago battery 100 % %
2019-02-01 3:31 PM EST - 6 minutes ago battery 0 % %
2019-02-01 3:12 AM EST - 12 hours ago battery 100 % %
2019-02-01 3:12 AM EST - 12 hours ago battery 0 % %
2019-01-31 6:30 PM EST - 21 hours ago battery 100 % %
2019-01-31 6:30 PM EST - 21 hours ago battery 0 % %
2019-01-30 2:23 AM EST - 3 days ago battery 100 % %
2019-01-30 2:23 AM EST - 3 days ago battery 0 % %
2019-01-29 4:42 PM EST - 3 days ago battery 100 % %
2019-01-29 4:42 PM EST - 3 days ago battery 0 % %

See how the battery reporting bounces up and down from 0% to the actual value?

Both my Utilitech sirens are doing this, and both are using the stock ST zwave siren DTH.

I submitted BUG-0021, just in case.


(Kianoosh Karami) #149

Responded to you on the centercode, but these are “false” values sent by the device, not sure what the hub can do to circumvent this.


(Kianoosh Karami) #150

This device is a Works With SmartThings certified device, so we will investigate this device internally.


(www.rboyapps.com - Make your home your butler!) #151

Yes I’m seeing the same thing BUT on 24.20 so I’m guessing either the bug has carried over or it’s a platform issue as this started recently. Brand new batteries.


(Bob Kerr) #152

I had a similar issue with 2 Aeon Labs multi sensors. What I did, was go into ide and changed the DTH to some other device, I think I picked Danalock or something like that. Then I clicked update. Waited about a minute or so, then switched back to the appropriate DTH. The devices came back alive within seconds. Give it a try…


#153

@Zach_Varberg @veeceeoh

Both my Xiaomi Aqara Button also stopped working. It reports battery and the “last event” tile changes when I press the button. But no actual button presses. Nothing in the log or recently tab when I press the button

Edit: Turned on debug in the settings. I get this in the livelog:

[1d22074d-4e38-4d76-b4d8-15770aa80d1b](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#1d22074d-4e38-4d76-b4d8-15770aa80d1b) 18:23:13: debug Garasjeport Button Inngang: Parsing 'read attr - raw: 48A4010006100000100000001001, dni: 48A4, endpoint: 01, cluster: 0006, size: 16, attrId: 0000, result: success, encoding: 10, value: 0110000000'


(Zach Varberg) #154

I’ll take a look. If someone who is not in the beta could get me a similar log of the “catchall” or “read attr” message received when a button is pressed it would make my life easier. But I’ll see what if I can track down where the difference is.


(Zach Varberg) #155

Hmm. I see your button has generated some push events in the past day. Is this still a problem, or did it resolve itself. I haven’t been able to find anything that suggests there is a systemic problem with the buttons.


(Chris Baumler) #156

For those of you who are Hub V2 users and have already received the 0.25.15 firmware, we are in the process of releasing the 0.25.16 firmware. We will be rolling the update out to Hub V3 users later this week, barring any unexpected issues that arise.

Note that those beta testers who haven’t yet received the 0.25.x firmware will not be receiving the 0.25.16 firmware. We are still waiting to see if we need to do any additional testing focused on converting to the new Z-Wave framework. We should be ready to roll out to these beta testers within the next few days.

Release Notes

  • Z-Wave: Indicator command class messages were blocked by the hub firmware from being sent to devices. This affected the Dome Sirens (BUG-0012).
  • Z-Wave would not stay in add mode after 15 seconds if you were using SmartThings Classic Android (BUG-0011).
  • Z-Wave: Fixed rare cases where the last value of a dimming switch was not reflected in the SmartThings mobile application.
  • Release version 0x00000220 of the V2 and V3 Zen thermostat FW
  • Release version 0x1F075310 of the Centralite micro door and micro motion sensor FW

(Bob Kerr) #157

Already on .16. Was the Z-Wave garage door bug (for the switch failure meesage) that @prjct92eh2 reported, deployed in this release? I assume, it was not because I am still seeing it.


(Kianoosh Karami) #158

The issue that you mentioned, is actually with the device not responding to the polls sent by the hub.


(Kianoosh Karami) #159

The issue is not a hub firmware issue or a platform issue, it is strictly with the device, as I mentioned, we are now evaluating the status of this device being a Works with SmartThings given the bug found with the device.


(Bob Kerr) #160

Ah, ok, I thought @cbaumler said you guys will update the logging to say “Not responding to polls - since that’s more accurate.” Not a big deal. At least you guys looked at it. :wink:


(Kianoosh Karami) #161

Yes, we updated the exception message to have a better description of the what has gone wrong with the device. Sorry, I just wanted to make sure that users do not think that it was a hub issue.