Issues with temperature sensors

I often have several sensors (FIBARO and AEON) that report wrong temperatures. Either they report fire or freeze.

2015-06-07 08:12:13.740 Z-Wave received "Temperature 1" sensor update to 473 °F
2015-06-07 08:12:13.747 Z-Wave received "Temperature 1" units changed to °F
2015-06-07 08:22:04.920 Z-Wave received "Temperature 1" sensor update to 25.0 °C
2015-06-07 08:22:04.927 Z-Wave received "Temperature 1" units changed to °C
2015-06-07 08:22:14.896 Z-Wave received "Brightness 1" sensor update to 468 lux

They always change to °F and switch back to °C the next update (where the temperature is right again). The temperature can be 0, 80, 473 or else. I suspect this also happens to motion sometimes (false alarm).

The value in the last case is clearly the lux reading which was wrong interpreted by Indigo?

Can you define & sync one of the devices and post the log snippet for Matt/Jay to check when they pop by.

Thanks for the advice. I have done it this morning.
"Bewegung Treppe" is the one that failed this night with the fire alarm.

Here's the log:

2015-06-07 10:25:29.590 Z-Wave Syncing - started for device "Bewegung Treppe"
2015-06-07 10:25:29.597 Z-Wave Syncing - retrieved module neighbors list: 4, 5, 6, 14, 15, 17, 20
2015-06-07 10:25:29.598 Z-Wave Syncing - requesting neighbor list update of "007 - Bewegung Treppe"
2015-06-07 10:25:44.697 Z-Wave Syncing - neighbor list update failed -- will try to update nearby neighbors first
2015-06-07 10:25:44.699 Z-Wave Syncing - requesting neighbor list update of "004"
2015-06-07 10:25:48.020 Z-Wave Syncing - nearby neighbor list update complete (no change)
2015-06-07 10:25:48.021 Z-Wave Syncing - requesting neighbor list update of "005"
2015-06-07 10:25:50.675 Z-Wave Syncing - nearby neighbor list update complete (no change)
2015-06-07 10:25:50.676 Z-Wave Syncing - requesting neighbor list update of "006"
2015-06-07 10:25:54.101 Z-Wave Syncing - nearby neighbor list updated from 4, 5, 11, 12, 14, 15, 17, 20, 31, 32 to 4, 5, 12, 14, 15, 17, 20, 31, 32
2015-06-07 10:25:54.109 Z-Wave Syncing - requesting neighbor list update of "014"
2015-06-07 10:25:54.922 Z-Wave Syncing - nearby neighbor list update complete (no change)
2015-06-07 10:25:54.923 Z-Wave Syncing - requesting neighbor list update of "015"
2015-06-07 10:25:55.889 Z-Wave Syncing - nearby neighbor list update complete (no change)
2015-06-07 10:25:55.890 Z-Wave Syncing - requesting neighbor list update of "017"
2015-06-07 10:25:57.232 Z-Wave Syncing - nearby neighbor list updated from 4, 5, 6, 14, 15, 20, 31, 32 to 4, 5, 6, 12, 14, 15, 20, 31, 32
2015-06-07 10:25:57.240 Z-Wave Syncing - requesting neighbor list update of "020"
2015-06-07 10:25:58.387 Z-Wave Syncing - nearby neighbor list update complete (no change)
2015-06-07 10:25:58.388 Z-Wave Syncing - requesting neighbor list update of "007 - Bewegung Treppe"
2015-06-07 10:26:02.030 Z-Wave Syncing - neighbor list updated from 4, 5, 6, 14, 15, 17, 20 to 5, 6, 12, 14, 15, 17, 20, 27, 31, 32
2015-06-07 10:26:02.031 Z-Wave Syncing - assigning return route to "007 - Bewegung Treppe"
2015-06-07 10:26:02.667 Z-Wave Syncing - assigned return route
2015-06-07 10:26:02.917 Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Motion Sensor (FGMS001) - 08001001
2015-06-07 10:26:03.051 Z-Wave Syncing - retrieved protocol version 3.67, app version 2.04
2015-06-07 10:26:03.310 Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Binary Sensor : Binary Sensor (routing) (04 : 20 : 01, base 30)
2015-06-07 10:26:03.311 Z-Wave Syncing - retrieved command classes: 20v1 80v1 84v1 85v1 86v1 70v1 8Ev1 8Fv1 30v1 31v5 72v1 56v1 7Av1 9Cv1
2015-06-07 10:26:03.444 Z-Wave Syncing - retrieved wake interval of 60 minutes
2015-06-07 10:26:03.572 Z-Wave Syncing - device "007 - Bewegung Treppe" wake interval changed to 60 minutes
2015-06-07 10:26:03.838 Z-Wave Syncing - retrieved group 1 associations: [1]
2015-06-07 10:26:03.972 Z-Wave Syncing - retrieved group 2 associations: [1]
2015-06-07 10:26:04.105 Z-Wave Syncing - retrieved group 3 associations: [1]
2015-06-07 10:26:04.106 Z-Wave Syncing - group 1 association to interface already exists (skipping)
2015-06-07 10:26:04.106 Z-Wave Syncing - group 2 association to interface already exists (skipping)
2015-06-07 10:26:04.107 Z-Wave Syncing - group 3 association to interface already exists (skipping)
2015-06-07 10:26:04.239 Z-Wave Syncing - retrieved parameter 1 "Motion sensor sensitivity (8: most sensitive, 255: least sensitive)" is 10
2015-06-07 10:26:04.372 Z-Wave Syncing - device "007 - Bewegung Treppe" parameter 1 "Motion sensor sensitivity (8: most sensitive, 255: least sensitive)" changed to 8 (was 10)
2015-06-07 10:26:04.505 Z-Wave Syncing - retrieved parameter 8 "Motion sensor mode (0: always active, 1: day only, 2: night only)" is 0
2015-06-07 10:26:04.637 Z-Wave Syncing - retrieved parameter 6 "Delay after no motion before OFF sent" is 30 seconds
2015-06-07 10:26:04.772 Z-Wave Syncing - retrieved parameter 9 "Night luminance threshold (used to determine day/night if mode 1 or 2 is used above)" is 200
2015-06-07 10:26:04.905 Z-Wave Syncing - retrieved parameter 12 "Group 1 command type" is 0
2015-06-07 10:26:05.037 Z-Wave Syncing - retrieved parameter 20 "Tamper sensor sensitivity (0: inactive, 1: most sensitive, 122: least sensitive)" is 0
2015-06-07 10:26:05.170 Z-Wave Syncing - retrieved parameter 24 "Tamper operating mode" is 0
2015-06-07 10:26:05.304 Z-Wave Syncing - retrieved parameter 40 "Luminance report sensitivity (0: disable reporting, 1 to 65535: lux)" is 0 LUX
2015-06-07 10:26:05.437 Z-Wave Syncing - retrieved parameter 42 "Delay between reporting Luminance changes (0: disable reporting, 1 to 65535: seconds delay)" is 300 seconds
2015-06-07 10:26:05.570 Z-Wave Syncing - retrieved parameter 60 "Temperature change sensitivity (0: disable reporting, 1: 0.1°C, 2: 0.2°C, 10: 1.0°C, 20: 2.0°C, 50: 5.0°C, ..., 255: 25.5°C)" is 1
2015-06-07 10:26:05.699 Z-Wave Syncing - retrieved parameter 62 "Delay between measuring temperature changes (0: disable measuring, 1 to 65535: seconds delay)" is 300 seconds
2015-06-07 10:26:05.831 Z-Wave Syncing - retrieved parameter 64 "Delay between reporting temperature changes (0: disable reporting, 1 to 65535: seconds delay)" is 0 seconds
2015-06-07 10:26:05.961 Z-Wave Syncing - device "007 - Bewegung Treppe" parameter 64 "Delay between reporting temperature changes (0: disable reporting, 1 to 65535: seconds delay)" changed to 300 seconds
2015-06-07 10:26:06.092 Z-Wave Syncing - retrieved Temperature calibration offset in 0.1 degrees is 0 * 0.1 degrees
2015-06-07 10:26:06.228 Z-Wave Syncing - retrieved parameter 80 "LED signaling mode (see manual for values)" is 0
2015-06-07 10:26:06.362 Z-Wave Syncing - retrieved parameter 81 "LED brightness (0: auto from ambient, 1 to 100: brightness percentage)" is 50
2015-06-07 10:26:06.494 Z-Wave Syncing - retrieved parameter 82 "Luminance threshold for 1% LED brightness (only if LED brightness value is 0)" is 100 LUX
2015-06-07 10:26:06.629 Z-Wave Syncing - retrieved parameter 83 "Luminance threshold for 100% LED brightness (only if LED brightness value is 0)" is 1000 LUX
2015-06-07 10:26:06.760 Z-Wave Syncing - retrieved parameter 86 "Temperature threshold for triggering blue LED (only if LED signaling mode value is 1, 10, 19)" is 18 degrees
2015-06-07 10:26:06.892 Z-Wave Syncing - retrieved parameter 87 "Temperature threshold for triggering red LED (only if LED signaling mode value is 1, 10, 19)" is 28 degrees
2015-06-07 10:26:07.023 Z-Wave Syncing - retrieved LED flashes red, white, blue on tamper is true
2015-06-07 10:26:07.159 Z-Wave Syncing - retrieved battery level of 100%
2015-06-07 10:26:07.392 Z-Wave Syncing - complete

[matt (support)]

Your Define/Sync looks good – no errors and all the values look okay.

Indigo is just reacting to the incoming commands. In this case the commands coming in are scrambled and have invalid bytes, which is causing the bogus values. Indigo cannot prevent this, and I don't believe it is an Indigo bug.

What is causing the scrambling? I'm not sure. It sounds like you have some systemic problems though given all the issues you have across several different modules. This leads me to think that the issue is either: 1) some type of RF interference, 2) congestion because of lots of status polling or status broadcasting, 3) a malfunctioning module or controller (Z-Stick), 4) USB level problem.

Re #1 try to temporarily eliminate anything that could be causing RF interference.

Re #2, do you have polling turned on the Edit Device Settings dialog for any modules? If so, how frequently do you have it polling? Do you have reporting intervals set really low (short durations) for some modules? If you are polling often that will cause lots of Z-Wave commands, which can lead to collisions and problems.

Re #3, swapping in a different Z-Stick would determine if it is the controller. That is a pain to do, so I would try that last.

Re #4, do you have the Z-Stick plugged directly into your Mac? USB extension cables and hubs can cause scrambled packets (I've witnessed this one myself).

2015-06-08 21:08:39.228 Z-Wave received "Temperature" sensor update to 0.00243 °C

Thanks for your help. Well I removed the extension cable and got this.

I could imagine it is because of my Philio energy meters that report the values very often (PAN04). I will try to disable that. Other devices poll every our or report every 5 minutes.

That Fibaro motion sensor is V2.04 firmware which has known issues with 3rd party controllers. You should return it to be replaced with V2.06 given there is no over the air updates.

Sensors have been updated, problem is still present.

If I don't update the values if they are 0 or above 100°C I can avoid it. Can't Indigo detect this command as corrupt?

btw. png seems to have the same issue:
viewtopic.php?f=58&t=13373&p=91643

Z-Wave received "Kitchen.MotionSensor.Luminance" sensor update to 42 lux
Z-Wave received "Kitchen.MotionSensor.Luminance" sensor update to 42 lux

Z-Wave received "Kitchen.MotionSensor.Temperature" sensor update to 42 °F
Z-Wave received "Kitchen.MotionSensor.Temperature" units changed to °F

Z-Wave received "Kitchen.MotionSensor.Luminance" sensor update to 42 lux
Z-Wave received "Kitchen.MotionSensor.Luminance" sensor update to 42 lux
Z-Wave received "Kitchen.MotionSensor.Luminance" sensor update to 42 lux

I can only assume the sensor is getting polled and reports the lux levels as temperature while changing °C to F.
I will try to disable wakeup.

[matt (support)]

Did you get the 2.06 firmware version of the sensors yet? The commands are all checksummed at multiple layers (Z-Wave network, interface to Indigo, etc.), so if Indigo is receiving the commands showing the sensor is at that value then that means the module most definitely sent that value (probably because of a firmware bug).

Yes they are updated.

I might have found a solution:

viewtopic.php?f=107&t=16128

Hope this helps someone.