Hub Firmware Beta 0.30.5

Version: 0.30.5

Hub Targets:

  • Samsung SmartThings Hub 2015 (Hub V2)
  • Samsung SmartThings Hub 2018 (Hub V3)

Release Date:

  • May 11, 2020

Release Notes:

Bug Fixes

  • Z-Wave will accept all incoming Multi-Channel encapsulated messages regardless of the Destination Endpoint value.
10 Likes

Does this affect all devices using multi channel encapsulation including those which are already paired or only devices that freshly paired? (need to know to be able to test it effectively). I have a variety of devices using 1 to 13 multi channel endpoints.

1 Like

This change accepts all endpoints like the behavior from the previous z-wave firmware. A longer more detailed post is forthcoming.

3 Likes

Why this change of mind (in 30.4 you said it wasn’t ok for certification…)

Thanka

1 Like

I’ll take it as a gift… :grin:

I will post a longer detailed post shortly.

1 Like

Well, I know when the update occurs because I have two mirrored hue lights that turn on after the update. This has been happening for the past few updates :slight_smile:

@jkp, has it turned on yet? Mine just have been updated.

Yes, a couple of minutes before I posted

0.30.5 is now rolled out, just a few finishing the download. Please test especially if you have Z-Wave devices that were not functioning as expected in 0.30.4 which may have been using endpoints not in the set {0, 1}.

Temp reporting for a few of my Fibaro FGK contact sensors just came back online, still testing

Mine are all back to normal.

My Fibaro RGBW controllers are now working correctly again. FYI, here are the logs relating to the messages that were getting blocked:

11:24:23 PM: info Kitchen LED Low: Channel 3 is on.
11:24:23 PM: info Kitchen LED Low: Channel 3 level is 51%.
11:24:23 PM: trace Kitchen LED Low: zwaveEndPointEvent(): EndPoint 4 has value: 129
11:24:23 PM: trace Kitchen LED Low: zwaveEvent(): SwitchMultilevelReport received from endPoint 4: SwitchMultilevelReport(value: 50)
11:24:23 PM: trace Kitchen LED Low: zwaveEvent(): MultiChannelCmdEncap received: MultiChannelCmdEncap(destinationEndPoint: 4, parameter: [50], sourceEndPoint: 4, command: 3, commandClass: 38, bitAddress: false)
11:24:23 PM: trace Kitchen LED Low: parse(): Parsing raw message: zw device: 0C, command: 600D, payload: 04 04 26 03 32
11:24:22 PM: info Kitchen LED Low: onX(): Setting channel 3 switch to on.

11:23:03 PM: info Kitchen LED Low: Channel 1 is on.
11:23:03 PM: info Kitchen LED Low: Channel 1 level is 71%.
11:23:03 PM: trace Kitchen LED Low: zwaveEndPointEvent(): EndPoint 2 has value: 180
11:23:03 PM: trace Kitchen LED Low: zwaveEvent(): SwitchMultilevelReport received from endPoint 2: SwitchMultilevelReport(value: 70)
11:23:03 PM: trace Kitchen LED Low: zwaveEvent(): MultiChannelCmdEncap received: MultiChannelCmdEncap(destinationEndPoint: 2, parameter: [70], sourceEndPoint: 2, command: 3, commandClass: 38, bitAddress: false)
11:23:03 PM: trace Kitchen LED Low: parse(): Parsing raw message: zw device: 0C, command: 600D, payload: 02 02 26 03 46
11:23:02 PM: info Kitchen LED Low: onX(): Setting channel 1 switch to on.

1 Like

v0.30.5
My Double Switch 2 still working ok with app status updating ok when using app or wall switch.

Single Switch 2 still not updating status in the app but if the app is showing switch is off then switch will turn on. If switch is on and app is showing on then will turn switch off but again no status update in the app.

So far so good, it’s working with the 8 and 13 endpoint devices. S2 is also working but there was a QR code issue that I reported.

1 Like

My Fibaro Flood is working again, with temp updating (although I had to trigger TMP to get it to wake up, as it is on battery).

This is great to see. I just applied for the beta program in hopes there would be a fix for the Fibaro FGK-10x. I look forward to being able to get 0.30.5 on my hub.

Looking good here, S2 appears to be working as well, had issues previously with S2 and communicating updates and parameter changes to first switch I changed to S2 during the original V30.3 episode/update (worked on v30.4). Only a Zooz ZSE18, on USB showing zwSwitchStatusLockout -err113:not responding to polls, on hub reboot but appears fine after a z wave repair, contacted Zooz Support. Most Z wave operations appear more responsive now as well.

Paul - I’m having serious Zwave mesh issues post update. Have someone contact me via DM I’m going to need an assist.

Edit - Extensive zwave repairs and some strategic excluding seems to have me back up and running - including responsive GE Motion Dimmers

Yep all my fibro UBS working again…