I have the same problem. Everything was fine until 2 releases ago. The last but one release worked but the triggering icon only briefly flashed for one of the inputs and then acted as if it wasn’t triggered. The other input didn’t flash at all yet it still detected the trigger and sent a notification. This latest release doesn’t trigger at all. Tried excluding etc but no good. I even swapped the unit out thinking it might be damaged but the new one behaves the same way. All the 4 temp sensors continue to work perfectly.
OK - Spent half and hour on phone to support - Steve was very patient - several excludes and includes and triggers later and logs captured - been passed to development to see if anything can be identified
I got just from support link to an older version of FW. Unfortunately, after the downgrade Fibaro multi sensor is still not recognized by the system. I changed to a new module, the system detects it correctly. I’m afraid to install the latest version of FW would not spoil the sensor.
Edit: Is Universal Binary Sensor operates someone on Vera Lite FW version 1.7.541?
Doesn’t look like there’s a fix included in the latest firmware release 1.7.1089 unfortunately.
I’ve excluded and re-included but the sensor appears to still not act on the input triggers
I got this replay from Vera support:
APR 21, 2015 | 01:04AM UTC
Brian replied:
Hello and thank you for contacting Vera Support.
We are aware of this issue and was already reported to our development team and they are working on fixing it. Once resolved it will be included into future software updates for your Vera controller.
A quick test this morning suggests that the 4th June firmware update has still not resolved this fundamental problem. This is very frustrating as my system utilises a significant number of these sensors…come on Support!! Get this fixed please!!!
OK - having spent reported this back in March and 30mins transatlantic support call I was told that this was being fixed - Vera internal tracking number VUI-4561
Having been disappointed with the lack of any mention in the last two releases I have chased this up again to be told today…
“The logs you?ve provided were not enough and as far as I can see from the issue?s status our developers are waiting for a sample to test this issue out. As a fix for this issue we can assist you in downgrading your unit?s software to before the 1.7.513”
Disappointing to say the least - does anyone in the same timezone as Vera care to pick this up to try to get a fix released as it really defeats one of the key areas of my system.
I have spent hours on trying to get this to work - has anyone found a solution please. I do have the latest firmware and I assume there is no firmware fix yet? Many thanks tonanyone who can help…
1st promise: we support all zwave devices
2nd promise if ui5 supports it ui7 will also
3rd promise we are aware of this issue in ui7 and work on it
4rd promise its a bug and will be resolved in 1st week of October
5th promise I have logged in on your unit and it should be solved
6th promise (today): Please know that the fix for this device was tested with success on multiple Vera units as this it is mandatory before including it into a firmware release. We also have applied it to other customer?s gateways without any issue.
And MONTHS LATER still not working. It worked flawless for 1.5 years on ui5.
Now I promise that i am constantly looking alternatives to vera.
Sorry vera, one time I was in love with you but our relationship turned into the rut.
Best Home Automation shopping experience. Shop at Ezlo!