I just noticed that my flood sensor is now a “temperature sensor”, and doesn’t update.
I’ll be honest. This is really horrible. The fact that an unwanted change in Vera caused an important sensor such as this to stop functioning --WITHOUT WARNING-- is really unacceptable. If I hadn’t just happened to notice the odd looking icon for the device, I wouldn’t have ever known. And if my basement happened to have flooded, I wouldn’t have been notified.
Over the years, I have dealt with a LOT of Vera’s quirky-ness, but this really pi$$es me off. I could accept that the FLOOD sensor showed up as a “MOTION” sensor. That’s fine, as long as the notifications actually worked (which they did). But now, as far as I can tell, it doesn’t do anything anymore, and I can’t even switch it back to being a “motion” sensor!
I updated my Nest plugin about a week ago. That was the only change.
I spent a good few hours trying to get this fixed last night, and it’s still showing up as a ‘temperature sensor’ with D_TempLeakSensor1.xml as the device file.
If I was to hazard a guess, it looks as though MCV started working on a proper leak sensor xml for this device, but somehow there’s a bug in it. If I get any free time today, I’ll endure a call to MCV and see if they can resolve it.
The reason I ask is that there is an issue that if a plugin uses a device type that is uses their own D_XXX.xml / D_XXX.json files, it will conflict with the other devices using that device type. So vera use only one set of files for that device type and not use the separate ones specified for each device. I would have a look at the temp leak sensor files to see what is going on.
[quote=“TheGadgetGuy, post:21, topic:172986”]I just noticed that my flood sensor is now a “temperature sensor”, and doesn’t update.
I’ll be honest. This is really horrible. The fact that an unwanted change in Vera caused an important sensor such as this to stop functioning --WITHOUT WARNING-- is really unacceptable. If I hadn’t just happened to notice the odd looking icon for the device, I wouldn’t have ever known. And if my basement happened to have flooded, I wouldn’t have been notified.
Over the years, I have dealt with a LOT of Vera’s quirky-ness, but this really pi$$es me off. I could accept that the FLOOD sensor showed up as a “MOTION” sensor. That’s fine, as long as the notifications actually worked (which they did). But now, as far as I can tell, it doesn’t do anything anymore, and I can’t even switch it back to being a “motion” sensor!
Very frustrating.[/quote]
Take a look at the notifications available for the device now. While there won’t be a visual notification on the dashboard as in the case of a tripped motion sensor, there are alerts for for leaks.
Ok. So after a 45 minute call to customer service, my flood sensors have been been restored to their previous state of “motion sensor”.
I never did get a fully accurate explanation as to what caused them to turn into “temperature sensor”, but it apparently had something to do with a totally unrelated plugin (they didn’t tell me which) being updated to a newer version. The only plugin that I am aware of being updated recently is the Nest Thermostat plugin, but I completely fail to understand how the two could be related.
In any event, my flood sensors are now functioning properly again (as motion sensors).
This leads to my question a few posts up. A plugin must have been using a device type with their own D_xxx files which were conflicting with your device.
That’s really strange. The ONLLY plugin that I have altered or upgraded recently was the Nest t-stat plugin. Seems odd that a thermostat and a flood sensor would be related at all, but I guess that has to be the case.
So far, the flood sensors are still working properly. I have them set up on a test rig today, to determine their reliability. Good to see that they’re working, and that notifications are being sent as expected.
When was the last time vera was rebooted or the luup engine reloaded? The issue could have lingered for awhile and not present itself until recently. I had a similar issue with my door locks. Another plugin was interfering with the locks and I did not notice until I needed to add a new pin via Vera’s interface. The issue was there for awhile until I noticed.
[quote=“TheGadgetGuy, post:26, topic:172986”]Ok. So after a 45 minute call to customer service, my flood sensors have been been restored to their previous state of “motion sensor”.
I never did get a fully accurate explanation as to what caused them to turn into “temperature sensor”, but it apparently had something to do with a totally unrelated plugin (they didn’t tell me which) being updated to a newer version. The only plugin that I am aware of being updated recently is the Nest Thermostat plugin, but I completely fail to understand how the two could be related.
In any event, my flood sensors are now functioning properly again (as motion sensors).[/quote]
Hi!
i have the same problem!
Could plz help me to solve it?
thx
[quote=“TheGadgetGuy, post:21, topic:172986”]I just noticed that my flood sensor is now a “temperature sensor”, and doesn’t update.
I’ll be honest. This is really horrible. The fact that an unwanted change in Vera caused an important sensor such as this to stop functioning --WITHOUT WARNING-- is really unacceptable. If I hadn’t just happened to notice the odd looking icon for the device, I wouldn’t have ever known. And if my basement happened to have flooded, I wouldn’t have been notified.
Over the years, I have dealt with a LOT of Vera’s quirky-ness, but this really pi$$es me off. I could accept that the FLOOD sensor showed up as a “MOTION” sensor. That’s fine, as long as the notifications actually worked (which they did). But now, as far as I can tell, it doesn’t do anything anymore, and I can’t even switch it back to being a “motion” sensor!
Very frustrating.[/quote]
Same problem after installing a new plugin. I think it was “MiOS Update Utility”
To be honest, I don’t know what they did to fix it. It was done remotely. The call took a while, but in the end, they got it back up and running. I suggest calling them.
Same Problem here, the only plugins I have installed are Program Logic Core, Program Logic Events & Program Logic Timer
I did install then uninstall MiOS Update Utility, could that have screwed things up (I was foolish to install it even though one of the reviews said not to).
I have try it again and it works. It must have been a firmware update. Sure.
I have removed the sensor form my vera and then I have paired it again. Now it works. The icon is form a temperature sensor but it can be configured to detect a water leak.
Apologies too,
I raised an MmCV support ticket, gave them access to Vera and they fixed it for me.
I can confirm that the update plugin was the culprit.
