well i have gotten some luck, with changing the type to momentary (switch type) and device type (button)
now the log shows the following (but i havent been able to get the changes in webcore: dev:1872020-08-13 11:17:20.603 infoFibaro01 button child 1 button 1 was released
dev:1872020-08-13 11:17:19.319 infoFibaro01 button child 1 button 1 was held
has it been reported to Hubitat so the are looking into the problem?
i can add the UBS no problem (as i could before the new firmware), and the device reports states back, just not on "contact" mode, and i can seem to get anything to trigger of them when they are in momentary button mode
No, i have updated to newest firmware, still not working... I. Considering rolling back to an old version, i have these as the backbone of my system, and changed to hubitat because they where officially supported this sucks
Any hints on this? I know you wrote that the unit was somewhat problematic due to the way the pack child commands, but Will it be working in C7 anytime soon, or Should one consider buying the smartimplant instead? (Which i would believe is working..)
There has been several firmware releases since the reporting, but no love?
Feel like I'm on the way to a sponsorship deal now, but I gave up waiting and installed a stack of nodemcu's / konnected WiFi sensors instead. Work perfect, and cost about £2.50 each.
can you link to some of the devices ? i suspect the solution isn't as versatile as the Fibaro universal sensor (which can be powered from 9-30v DC) most of my systems are powering them with 12v - but has a limit of 300 mAh!
i am considering going after "Smart Implant" instead, but it will be an exspensive swap for something in place which should work from the beginning...
I think the smart implant and the ubs is rubbish, to be honest. I've struggled with them for years. Since using the (incredibly versitile) nodemcu, it's been great. Search for my recent post.... I'm at work at the minute =p
That's because they don't work with the z-wave plus+ chip yet. Now the HE staff has to work out how to get them going again. It's holding up my migration which is annoying as I have another hub sat in a box. The staff have said it should get fixed in the 2.2.4 firmware.
It pairs fine, and the events from it can be seen in the log if the setup selected is as "button"
but it doesn't trigger when used in automations...
do you know if the "Smart implant" works? i am considering buying a bunch of these instead and move on...