Fibaro Motion Sensor change type to temperature_sensor

[baran 1]

Hi all

this is the third time that happen.

My fibaro motion sensor change his type to temperature_sensor reporting 0 or 255 C as value.

There is no way to fix it. I have to remove and re-add it.

I have opened a bug. They close it saying that is a "known issue" and pointing to a "zwave frame corruption".

They say to reduce the z-wave network traffic.... i tried... same issue.

I think z-wave network have a good checksum.... don't know why it shoul corrupt such an info.. and don't undestand why there isn't an easy way to put the sensor back to his correct type.

Anyone with the same issue? any idea?

Please login or register to see this attachment.

Please login or register to see this attachment.

[valitasca 3]

I have the same problem, the only difference is that my motion sensor change his type to humidity_sensor reporting 0 or 1 % as value.

Same thing, i have uninstalled, installed, work for a couple of days, and turn back to humidity.

The movement scenes are working.

I have this kind of problem with only one of 4 fibaro motion sensor and with one of 3 aeon 4 in 1.

Please login or register to see this image.

/emoticons/default_icon_eek.gif" alt=":shock:" />

[JanJoh 1]

Anyone with the same issue? any idea?

Well known problem that Fibaro does not seem very keen on fixing.

Please login or register to see this link.

There is no workaround except "remove / re-add device". (which screws up all scenes using device ID etc etc)

[baran 1]

holy... crap.....

why we can have a quick fix that rolback the device type? should be easy

[JanJoh 1]

holy... crap.....

why we can have a quick fix that rolback the device type? should be easy

I agree. Technically i cannot understand why a device typ is not locked once created.

[baran 1]

yep. i thnk it should be locked or "changable" only by console after first discover...

the strange think is that when is a "motion sensor" i can change the type via list_of_value.... but when it change to temperature_sensor.... it is locked!

damn.. let me do a SQL update of that record!!!!! sigh

[ Added: 2014-05-19, 16:48 ]

I'm going crazy whith this motion sensor...

I buy a new one to be sure that the issue was not in the sensor.

I still got same issues...

it stay breached.... and after some day it is change to Temperature Sensor type!!!

it is unusable...

i have to remove and re-add it twice a week!

[Valken 0]

I now have the exact same problem.

My sensor was perfect for 3 weeks and then this morning i saw the same thing.

Is there another fix without removing and adding it again?

@baran - could you please share your feedback from fibaro:

(I have opened a bug. They close it saying that is a "known issue" and pointing to a "zwave frame corruption".

They say to reduce the z-wave network traffic....)

How do you reduce Z-Wave network traffic?

[JanJoh 1]

Is there another fix without removing and adding it again?

No.

They say to reduce the z-wave network traffic....)

How do you reduce Z-Wave network traffic?

You can't really. Unless you have increased the standard communication intervals, or have tons of devices the trafic volume is quite low.

[P. Ratajczak 0]

As for now, the solution is to re add the module to the network. To decrease the risk of retrial collision process, Z-wave network traffic should be reduced as described above. This should be done by increasing the pooling time interval in central unit and the wake-up interval in modules. We are planning to improove the communication mechanism in one of next software versions for Home Center units.

[JanJoh 1]

As for now, the solution is to re add the module to the network. To decrease the risk of retrial collision process, Z-wave network traffic should be reduced as described above. This should be done by increasing the pooling time interval in central unit and the wake-up interval in modules. We are planning to improove the communication mechanism in one of next software versions for Home Center units.

Yeah... We've heard the "will be fixed in the future" for more then a year now.

But, what I cannot understand is why the software allows an added device to change type as a runtime operation.

There simply can not be a good reason for why the device type is not locked once added, or at least manually CAN be locked.

Today i woke up to four sensors that had had this problem. One is (again) five meters up on a wall.

[robmac 173]

That is an interesting issue and it has been around for a long time. You will see my various posts when I had odd icons and temperature reported in liters, watts or even Btu (British thermal unit). Not sure why that one is even supported.

last time was in January on a pre-production motion sensor that Fibaro sent me to test.

I had taken to removing the device and any that were added at the same time and adding them again taking time (hours) between each one and making sure each is configured and working before the next. This is what I did then.

Can't say if it is this that made the issue stop on my system or just a fluke but might be worth a try.

I also think it is strange that normal messages can change a device's type but I guess someone thought it was a good idea.

[harlin 0]

Same issue as the Aeon sensors. Pretty annoying, got 6 rather useless senors at home.

See

Please login or register to see this link.

[rattyman 0]

Yet another issue, I really am starting to give up.

20 devices, 3 motion controllers have all shown this issue...and of course it comes when I have guests to the house that are using the bathroom that one of the sensors are in, very

Please login or register to see this image.

/emoticons/default_icon_redface.gif" alt=":oops:" /> ...my wife is ready to kill me and throw the HC2 out the window.

And...I have my controller at the centre of my house...NO device is further than 6 meters! This whole system seems very, very, very flaky!

The default polling for the 20 devices is at 125s...just changed this to 250s.

Does anyone know what we should set this to?

[deanrparry 19]

Yet another issue, I really am starting to give up.

20 devices, 3 motion controllers have all shown this issue...and of course it comes when I have guests to the house that are using the bathroom that one of the sensors are in, very

Please login or register to see this image.

/emoticons/default_icon_redface.gif" alt=":oops:" /> ...my wife is ready to kill me and throw the HC2 out the window.

And...I have my controller at the centre of my house...NO device is further than 6 meters! This whole system seems very, very, very flaky!

The default polling for the 20 devices is at 125s...just changed this to 250s.

Does anyone know what we should set this to?

same problem with my wife! basically she told me get rid of that unreliable fibaro rubbish or else! i am past my tether now... try a rasp pi with zwave.me software but harder to setup but real mesh networking and every device speaks to each other properly its been flawless for me... i am putting both my hc2 units on ebay later will only come back to this forum for device support... this company has taken to much of my time up over the past couple of years! waste of money when compared to a £30 pi and £40 zwave gpio addon

[dw89 8]

I believe I read somewhere else that this 'issue' was down to all 3/4 in one sensors and the current zwave engine and that the new one (which is in 3.9 or 4.0 - please tell me which) will fix this? This came from Fibar. So if new engine is in the latest Beta then has it solved the problem? Or can Fibaro tell us if its solved in 4.0 with the new engine?

Thing is, as most people here have said, its a motion sensor predominently and thats what its sold and advertised as. I love the looks and what it does etc but if this continues to happen its an expensive piece of rubbish. I have x 9 of them, recently purchased (x6 of which were installed yesterday). I already experienced the temp issue once and Ive only had system a month. I have not spent >£1k on Fibar products for them not to work. Imagine a burglar breaks in, and on this day, the sensor decides to become a temp sensor?

One can always argue the point like Oh youve got more sensors etc etc but its not the point. Come on Fibaro, is it being solved or not with new engine? Only you know so please tell us. Otherwise I think I will be sending all your sensors back and getting my £450 back for them.

Dave

PS, i changed my polling time to 300 yestsrday, i Ctually got a system msg advising me to do so....I assume because it thinks I have >50 devices.

[ Added: 2014-07-06, 15:32 ]

I think this must be some kind of windup to be honest.

Wife's not well so I thought I would mess around with the HC2. Remember I just said I'd installed x6 Fibaro Eye Sensors yesterday? Well at least one from yesterday and one I installed weeks ago (that turned into temp) sensor just are not working at all.

One in the Hallway (which should measure every movement when we walk to and from kitchen i.e. all the time) is not reading ANYTHING. I've tested it (and filmed it) by walking up to it and watching it blink (done many times). I then go to events panel and nothing is seen AT all?! WTF. According to HC2 the last time any movement was sensed was last night at 10.20pm. That's blatantly wrong.

Then the new one, installed in my office, is currently 'stuck' on BREACHED for almost the last 4h according to device i.e. 11:11 this morning. So a) it's stuck b) I don't even know how it's been breached as a) it's in a room no ones been in since I put it there b) it's pointing directly at the door.......so how's it gone off at all?! It can hardly be blamed on light as its pointing away from window and the sun comes up at 5am not 11am.

Come on Fibaro, what's going on?! Help us out. This really is not helpful in any way as a motion sensor currently.

Dave

Please login or register to see this image.

/emoticons/default_icon_sad.gif" alt=":-(" />

[remcoploeg 10]

dw89,

I have the same problems. I have even the problems with my AEON LABS suddenly. Sometimes they see movement, sometimes always en sometimes not. I have this issue since 3.591.

I really hope that Fibaro do something in the coming week (not weeks!), else they lose a lot of customers. I see a lot of topics on this forum with people no happy with your product. I invested more than 3000 euro in this setup. I have a complaning wife, frined are laughing when something does not work again.

I really like your product and looks, but I don't like they promises you make and the terrible marketing strategy that you have.

[dw89 8]

Remco,

I agree and I hope that Fibaro read all of this tomorrow and get on it asap. This is very vey bad. It's no point having great marketing if its vaporware as Dalle put it. Not sure about other countries but they had a big stand (and made a lot of it) at Grand Designs live in UK this year. I'm one of the people who was there....why? I got a lot of products over the years from things I found at trade shows etc but this is the first time I've ever bought something that, from the get go, doesn't work reliably nor do what it says 'on the tin.'

Many years ago I knew a contractor (in my line of work) who spent two years on a project for one of the uk's biggest banks. He was getting paid probably @£1000/day back then. After two years the bosses got impatient and asked to see his work...working. It all looked impressive and soon enough he left with a big grin on his face. Not much later we found out why.....he'd done f all for two years! The 'big' program he'd spent all his time on was nothing but echo's to screen, timeouts and more echos!!! Hilarious...but he got away with it. A bit like the 'emperors clothes' if you know the famous story.

I hope that this isn't another example because all I can see is excuses, delays and not much else. Why is it that, on a vanilla box (like mine) when they're working on new releases a, supposedly tested product, works so badly? I have about 30 sensors and you know, the only ones that DON'T work consistently? Fibaro's own! All the others have worked without issue since the day I had them.

More than anything it hacks me off because it's a good system, looks great and has so much potential. Please fix this and don't lose your customers. If, in my job, I had bugs and a) pretended they weren't there or b) didn't fix them with communication to the client as to when they'd be fixed.....I'd have been fired a long long time ago.

Come on guys, help your customers out....otherwise it's all going back!

Dave

Please login or register to see this image.

/emoticons/default_icon_neutral.gif" alt=":-|" />

[j.nowacki 5]

dw89, we fully understand your problem but it is deeper than creating a quick fix. We need to modify the way our Z-wave works. This issue is now removed in alpha version, but you need to wait a little longer for a stable release. For now please reduce traffic in Z-wave network and increase intervals of sending temperature reports.

[dw89 8]

J.Nowacki,

Thanks for your message

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" /> Sure we all appreciate it and that you 'are' doing something with it.

I think I speak for everyone in saying that all people want is a bit of clarity of information and to know, for definite, when things will be fixed. I've looked through bugtracker and seen no info on this and its a serious thing, for all of us, to effectively have no use at all of our motion related actions (security/scenes or whatever) because of whatever bugs.

I'm happy to wait if it isn't forever. How long more or less are we talking here? I'm sure you will understand my worry that a burglar will not be waiting for your next release and therefore why I want a bit more information date-wise. Hence the urgent nature of the question. There will always be bugs but ones like these render the whole thing redundant.

I have indeed done what you said, and changed parameter 24 to 0 or 1 as per a bugtracker note I saw a while back.

KR, Dave

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />

[ Added: 2014-07-08, 17:54 ]

Just to be sure, which problems exactly is it (regarding the Motion Sensor) that you are fixing; just so we all know:

1) Motion Sensor turning to Temp Sensor

2) Sensor 'sticking' on breached

3) Breach status not being reported to Events (ie. shows breach but never goes back to safe)

4) Others?

Thanks

[ Added: 2014-07-08, 20:25 ]

Sorry J Nowacki,

Confused about the temperature reports interval you mentioned.....Parameter 64? It is '0' by default which means it isn't sent so not sure why you asked that? Unless you assume people change that that is?

[j.nowacki 5]

Dear dw89, in next update the motion sensor becoming temperature will be repaired. Issues with sensors stuck in breached state may be caused by inappropriate configuration, please try different settings of its parameters or shutting down tamper reports completely. If you need any help with configuration of your system please contact our support team with an e-mail: [email protected], so we can take a closer look on your problem and establish remote connection if needed. By changing temperature reports settings i meant eg.

60 -> 0

62 -> 0

64 -> 900

This should decrease frequency of errors. Also make sure to increase polling time intervals of other devices.