Hub Firmware Beta 0.30.4

[mpikounis (Michael Pikounis)]

Same here. Multichannel switch fixed but no temperature readings from Fibaro UBS.

[immortal (Martin Lane)]

How do I get the beta firmware. I could really do with this update?

[GSzabados (Gabor Szabados)]

@immortal, for now you are late for the beta. If there are not other issues, then you will receive the production version next week, if the planned release will go by the 12th as it was expected.

[immortal (Martin Lane)]

Ok. For future reference, how do I get beta firmware. If a problem like this arises again.

[immortal (Martin Lane)]

Are all new firmwares released as beta first? If so, how was this problem not picked up earlier?

[GSzabados (Gabor Szabados)]

@mpikounis, @johnny2678 and @immortal, have a look here for a detailed explanation what was happening and how the UBS should be fixed.

Z-Wave Issues with Firmware Update 30.3

I wrote the following write up to help explain the situation to our users and provide potential workarounds to those are still experiencing issues post 0.30.4 release. Background Info Let’s talk a little Z-Wave, so we are all on the same page about this particular situation. In Z-Wave, when a device is added to the network, it is assigned a Network ID (valid ranges 1-232), even when Multi Channel devices, for example a Z-Wave Power Strip or a Double Switch, joins the network, it gets assigned ONE number. In many protocols (i.e. Bluetooth Mesh), similar devices will have unique address for each endpoint/entity. So this means that addressing these entities must be done in the application layer instead of the transport/network layer. The power strip that we are using in this scenario here…

And some advice from @jody.albritton, if you are using the UBS with custom DH.

Z-Wave Issues with Firmware Update 30.3 - #128 by jody.albritton

[mpikounis (Michael Pikounis)]

@GSzabados

@mpikounis, @johnny2678 and @immortal, have a look here for a detailed explanation what was happening and how the UBS should be fixed.

All is working now - including the temp sensor by polling as suggested by @Kailash_Sabhnani. I still have some objections regarding the handling of this crisis by ST but that’s a different discussion I guess.

[mpikounis (Michael Pikounis)]

Actually… not everything is OK. I am having issues with a FIBARO Double Relay (222). The first device works fine - turns on, reports status etc. However, the second child device is tuning on/off but status is not updated as it should.

I hit ON and I get a “Turning On” icon with no status notifications in the “Recently” tab of the child device. This was working prior to 0.30.3.

Any ideas?

[slimshizn]

I have joined the beta program, any chance the application can be accepted to see if this fixes my zigbee, multipurpose sensors, and motion sensors being offline? Thank you in advance.

[jody.albritton (Jody)]

@immortal

Are all new firmwares released as beta first? If so, how was this problem not picked up earlier?

Noone in the beta had these specific devices.

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Did a test with a 10 endpoint device and it’s working as expected.

[jlv]

I got the 0.30.4 beta firmware but I don’t seem to have been accepted at centercode so I am unable to leave feedback. My Fibaro Flood Sensor is still not reporting temperature. I opened it up and pressed TMP while selecting ‘configuration’ from the app. I got an updated battery report from it, but still no temperature.

[FishFlu (Blub blub... *cough*)]

+1 to this. Finally back to stock DTH and local processing on 5 fibaro dimmer 2’s. Yay!

[GSzabados (Gabor Szabados)]

@jlv, have you tried what @Kianoosh_Karami suggested with the polling of the device, by changing the code with that snippet?