Feedback on Edge Drivers

So I have been slowly converting over from DTHs to edge drivers as they become available for my devices. I have some feedback and comments:

  • In general edge drivers when seem faster to me than local DTH. I’m not sure if this is actually true but they do seem very responsive to me.

  • The Smartthings Zibgee Button edge driver when used with the Ikea two-button remote works pretty good but seems to have problems if you press buttons too rapidly in succession. If you do this it seems to stop receiving commands and timeouts eventually. If you wait a few seconds and try again it seems to start working again

  • The Smartthings Zibgee Button edge driver when used with the Ikea five-button remote is very flaky. Automations don’t seem to stay tied with the buttons assigned. I have been unable to get the remote stable enough to use. More interestingly I don’t see a way to move this one back to a DTH without doing the same for my other 2 button Ikea remotes that are working.

  • The driver list in Smarthigns app β€˜driver’ menu needs to include the channel name in addition to the device name. For example, Samsung has a Zigbee Button driver and iquix has one named the same as well. I can’t tell from the current UI which is which.

  • Under driver information the Developer is listed as their GUID rather than a human-readable name

Overall I like where this edge driver system is going. Looking forward to when more automation features are local as well.

This is a UI plug-in bug affecting all multi button devices.

1 Like

Started using IKEA 5 button yesterday - all good so far, one exception: from start battery (new) was reported at 50%. Some details:
4 β”‚ IKEA Remote Control β”‚ five-buttons-battery β”‚ ZIGBEE
main component
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Capability β”‚ Attribute β”‚ Value β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ battery β”‚ battery β”‚ 50 % β”‚
β”‚ firmwareUpdate β”‚ lastUpdateStatusReason β”‚ β”‚
β”‚ firmwareUpdate β”‚ availableVersion β”‚ β€œ23014631” β”‚
β”‚ firmwareUpdate β”‚ lastUpdateStatus β”‚ β”‚
β”‚ firmwareUpdate β”‚ state β”‚ β€œnormalOperation” β”‚
β”‚ firmwareUpdate β”‚ currentVersion β”‚ β€œ23014631” β”‚
β”‚ firmwareUpdate β”‚ lastUpdateTime β”‚ β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Similar for IKEA motion sensor - started using 1 week ago; on DTH battery was reported at about 64% (after over 18 months of use), after upgrade it is steady at 30%.
12 β”‚ motion 1 β”‚ motion-battery β”‚ ZIGBEE
smartthings devices:status 12
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Capability β”‚ Attribute β”‚ Value β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ motionSensor β”‚ motion β”‚ β€œinactive” β”‚
β”‚ battery β”‚ battery β”‚ 30 % β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

… have a second IKEA motion sensor left on DTH … status (after over 16 months of use):
13 β”‚ motion 2 β”‚ IKEA Motion Sensor β”‚ DTH
smartthings devices:status 13
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Capability β”‚ Attribute β”‚ Value β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ healthCheck β”‚ checkInterval β”‚ 43920 s β”‚
β”‚ healthCheck β”‚ healthStatus β”‚ β”‚
β”‚ healthCheck β”‚ DeviceWatch-Enroll β”‚ β”‚
β”‚ healthCheck β”‚ DeviceWatch-DeviceStatus β”‚ β”‚
β”‚ motionSensor β”‚ motion β”‚ β€œinactive” β”‚
β”‚ battery β”‚ battery β”‚ 66 % β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Yes that is happening for all the IKEA devices supported by the stock Edge drivers.

When you look at the DTH for the motion sensor you can see it is using the voltage. That is reported in 100 mV units and is correctly being divided by ten. However if you look at the DTH for the buttons they are using the percentage remaining and using it as is, indicating it is in whole percent units. The Zigbee standard requires half a percent units.

So the Edge drivers will need battery reporting tweaked for IKEA devices.

Appreciate your quick reply, thank you!

I’ve noticed a significant variation in speed of automations with Edge (only) drivers. Both Z-Wave and ZigBee seem to be the same.

Sometimes the delay can be many seconds.

Also particularly noticeable when multiple bulbs are triggered at the same time. Definitely sequential and not fast.

I’d say overall, automations are faster and more consistent in classic DTH!