Temp sensors suddenly recognized as Temp+Hum

[Quax1507]

I have four DS18B20 (temperature) sensors attached to an Fibaro FGBS-001 which were working good for several months.
These were discovered as "Lacrosse TX3" which was correct.

Now, suddenly these sensors stopped working. No more temperature values updates.

I had a look at the devices and discovered that there were newly created devices (same ID) as WTGR800 which is a Temp+Hum sensor.
I deleted all devices but they keep coming back as WTGR800.

Any ideas what happened here and how to fix it?

Thanks,
Quax

[LouiS22]

I have four DS18B20 (temperature) sensors attached to an Fibaro FGBS-001 which were working good for several months.
These were discovered as "Lacrosse TX3" which was correct.

Now, suddenly these sensors stopped working. No more temperature values updates.

I had a look at the devices and discovered that there were newly created devices (same ID) as WTGR800 which is a Temp+Hum sensor.
I deleted all devices but they keep coming back as WTGR800.

Any ideas what happened here and how to fix it?

Thanks,
Quax

Do the new devices have correct readings? If yes, then IMHO you can use them. Other thing you can do: exclude the sensor from your network, then include it again.

[Quax1507]

Do the new devices have correct readings? If yes, then IMHO you can use them. Other thing you can do: exclude the sensor from your network, then include it again.

They seem to show the correct readings but also display humidity.
Do You have any idea what is the resaon for the problem? Will it come back again?

[bmhi]

I have exactly the same problem as Quax1507. My sensors was redefined as WTGR800 2017-08-30 02:19 UTC

[Quax1507]

Anybody found a solution for that?

It is still happening here from time to time!

[AndersSandell]

Hi

I have the same issue here...

Has anyone foundation a solution to this?

[gizmocuz]

@AndersSandell, you can't reply on a topic thats over a year old without providing all needed information, software version, hardware etc..

[AndersSandell]

Ok, sorry. Here is a little more verbose description.

I am running Domoticz 4.97 under Raspbian on a raspberry pi with a razberry. I have, among other things, four Fibaro FGBS-001 that are all showing the same symptom, after a few months the original "Lacrosse TX3" temperature sensors stops reporting values and new WGTR800 sensors appear and start reporting temp + hum. Temperature readings of the WGTR800 sensors seems to be correct but humidity readings are at a constant level.

I have also discovered that on one of my Qbino dimmers (a ZMNHSD1) that has a temperature sensor attached to it behaves the same way, the original LaCrosse TX3 temperature sensor stopped reporting values and a new WGTR800 sensor appeared and started to report temp and hum.

Even though i do get temperature values it is annoying that the humidity values shows up...

[lost]

@AndersSandell, you can't reply on a topic thats over a year old without providing all needed information, software version, hardware etc..

Hello,

I also have this problem with a z-wave Fibaro PIR (the eye, old non + version): Tre sensor was reported as Lacross TX3 and changed for unknown reason at the beginning of october. By the end of the month, had time to try to figure out what was wrong so stopped Domoticz, suppressed the new sensor type from the zwave xml (saw this in another thread dealing with the exact same problem), restarted Domoticz & Tre was updated again... Until the next day, when the new Tre+Hum device came back (with same sub-ID: The low order part after z-wave device got at inclusion): So I gave up...

On my side, no recent change in Domoticz version: I'm still on the old-stable (8153 I presume, not at home right now to check) as I did not update to 9700. This sensor never showed this problem before, several month with no change, and even before with old-old-stable.

I also have a second exact same device, installed almost at the same time, that does not show this problem and still reports Tre as TX3.

Don't know if this is a Domoticz/OZW problem or a device problem. As correction does not last, I would say next device wake-up reversed it. Don't know if this is the device that exhibits a change, so would be a firmware bug, or OZW that accept such change but should not (so far away from inclusion process).

Can make other checks/provide more infos on demand by the end of the day or today.

Regards

[peterchef]

Hi
I have had the same problem with the Horstmann HRT4-ZW. For the last 2 years no problem and then on the 18th nov it stopped reporting the actual temperature via the device Lacrosse TX3 however the new device WTGR 800 reported the correct temperature and a fixed humidity.
OS :windows 10
Domoticz :4.9954

[gizmocuz]

Could you check in the zwave control panel if there is any humidity value there ?
Very weird that without software changes, suddenly it changes to a temp+hum
Of course, maybe, there could be some RF noise, but still
You might want to try updating to the latest beta version, it also includes the latest OZW library

[peterchef]

There is no separate humidity value.
The only other z wave device i have that reports humidity is an aeotec multi sensor 6 that reports as type wtgr800. I wonder if at some point there has been a system crash and when recovering there has been some 'crossover'.

[AndersSandell]

For me in control panel one reports humidity value, together with luminance and power. Another reports humidity value together with barometric pressure and power, this one also reports 30+ sensors...??

[lost]

Could you check in the zwave control panel if there is any humidity value there ?
Very weird that without software changes, suddenly it changes to a temp+hum
Of course, maybe, there could be some RF noise, but still
You might want to try updating to the latest beta version, it also includes the latest OZW library

For my FGMS001 on Domoticz v3.8153 (old-stable), I have a faulty (currently >200 million... percent!!!) humidity reported in OZW control panel as well.

Here are the zwcfg_XXX.xml extracts from a known good backup for this device & when it became faulty:

Code: Select all

    <Node id="31" name="" location="" basic="4" generic="32" specific="1" type="Routing Binary Sensor" listening="false" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="CacheLoad">
        <Manufacturer id="10f" name="FIBARO System">
            <Product type="800" id="1001" name="FGMS001 Motion Sensor" />
        </Manufacturer>
        <CommandClasses>
            <CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" request_flags="4" after_mark="true" mapping="48" setasreport="true">
                <Instance index="1" />
            </CommandClass>
            <CommandClass id="48" name="COMMAND_CLASS_SENSOR_BINARY" version="1" request_flags="4" innif="true">
                <Instance index="1" />
                <Value type="bool" genre="user" instance="1" index="0" label="Sensor" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="False" />
                <SensorMap index="0" type="34" />
                <SensorMap index="0" type="50" />
                <SensorMap index="0" type="204" />
                <SensorMap index="0" type="205" />
                <SensorMap index="0" type="220" />
                <SensorMap index="0" type="221" />
            </CommandClass>
            <CommandClass id="49" name="COMMAND_CLASS_SENSOR_MULTILEVEL" version="5" innif="true">
                <Instance index="1" />
                <Value type="decimal" genre="user" instance="1" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3.5" />
                <Value type="decimal" genre="user" instance="1" index="3" label="Luminance" units="lux" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="222" />
            </CommandClass>
(...)

Code: Select all

    <Node id="31" name="" location="" basic="4" generic="32" specific="1" type="Routing Binary Sensor" listening="false" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Configuration">
        <Manufacturer id="10f" name="FIBARO System">
            <Product type="800" id="1001" name="FGMS001 Motion Sensor" />
        </Manufacturer>
        <CommandClasses>
            <CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" request_flags="4" after_mark="true" mapping="48" setasreport="true">
                <Instance index="1" />
            </CommandClass>
            <CommandClass id="48" name="COMMAND_CLASS_SENSOR_BINARY" version="1" request_flags="4" innif="true">
                <Instance index="1" />
                <Value type="bool" genre="user" instance="1" index="0" label="Sensor" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="False" />
                <SensorMap index="0" type="2" />
                <SensorMap index="0" type="34" />
                <SensorMap index="0" type="50" />
                <SensorMap index="0" type="98" />
                <SensorMap index="0" type="197" />
                <SensorMap index="0" type="204" />
                <SensorMap index="0" type="205" />
                <SensorMap index="0" type="220" />
                <SensorMap index="0" type="221" />
                <SensorMap index="0" type="253" />
            </CommandClass>
            <CommandClass id="49" name="COMMAND_CLASS_SENSOR_MULTILEVEL" version="5" innif="true">
                <Instance index="1" />
                <Value type="decimal" genre="user" instance="1" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="13.5" />
                <Value type="decimal" genre="user" instance="1" index="2" label="General" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.0" />
                <Value type="decimal" genre="user" instance="1" index="3" label="Luminance" units="lux" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="123" />
                <Value type="decimal" genre="user" instance="1" index="4" label="Power" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.0" />
                <Value type="decimal" genre="user" instance="1" index="5" label="Relative Humidity" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.0" />
                <Value type="decimal" genre="user" instance="1" index="6" label="Velocity" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.0" />
                <Value type="decimal" genre="user" instance="1" index="7" label="Direction" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.0" />
                <Value type="decimal" genre="user" instance="1" index="8" label="Atmospheric Pressure" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.0" />
            </CommandClass>
(...)

You can see several sensors were added (not only the one that now appears as T+H).

I tried removing all that was supposed wrong in COMMAND_CLASS_SENSOR_MULTILEVEL section, but this did not worked for long. Maybe I should also have restored COMMAND_CLASS_SENSOR_BINARY contents?

Anyway, very strange to have all these devices appear...

Something else that may help: Just see I have "accept new devices " that is always checked in tuning/parameters. Maybe this should only be set when pairing new devices as this may allow screwing things more easily? But this is not new setup, I think I forgot this for long, + did not add any new hardware since months when the issue occurred.

Can't update to beta right now, quite risky IMO (+DB format seem to have changed since old-stable thus reverting may cause issues) as I have only one setup that is my production one... But if any non-breaking experiment is useful on my setup, I can help if needed.

Regards.

[bjacobse]

Hi I can only also confirm I have weird temp+hum zwave qubino ZMNHADx (relay with DS18B20 temp sensor), I have in total 6 pcs and 1 or 2 of them "became" a combined temp/hum sensor. I deleted them and hoped the reverted back to the temp sensor only. but this was not the case. I use Version: 4.9700 on a RPI3
I have a time thought it was my SD card that got corrupted, so I have done the database check integrity, and no errors found. So have been trying to understand if this is openzwave related, or the connection between zwave data and Domoticz.
I can verify that I get temperature reading in ozwave
The picture show the openzwave with temp 27 degree the reading few minutes before were 22, so Openzwave receive correct temp readings

ozwave.png (151.59 KiB) Viewed 3895 times

[gizmocuz]

If there is humidity reported here, it is being reported to domoticz, and domoticz will use it...
It's not a domoticz issue

[gerardvs]

Hi I can only also confirm I have weird temp+hum zwave qubino ZMNHADx (relay with DS18B20 temp sensor).....

Same here. This is definitely a Domoticz issue... Well may be not an issue but a design flaw. Sensors shouldn't be combined unless explicitly done by the user. Automatically combining sensors just based on id's is crazy.

[gizmocuz]

@gerardvs, thats your opinion !
I find a sensor that reports temp + humidity a 'temp+hum' sensor and want to see them like that
Anyway, again, this is NOT a Domoticz issue (yes gerardvs) it's a problem that this is reported by the zwave node

And now for a solution... it might be possible to configure (in the node configuration file), not not report the humidity value

something like (but different) as

<!-- COMMAND_CLASS_ALARM AlarmCmd_Get not supported -->
<CommandClass id="113" getsupported="false"/>

But this may have to be asked @ openzwave

[gerardvs]

Indeed this is my opinion and is not only related to zwave. In mysensors something alike happens.

And for that, my opinion is that there is a design flaw in the code (/hardware/MySensorsBase.cpp). For types V_TEMP and V_HUM the code searches for other children. This ludicrous. Since a mysensor node can have many sensors (in my case 12) it is likely that there is absolutely no relationship between multiple (hum/temp) sensors.
My last remark is a bit off-topic (!==zwave) so you can ignore me on this.

[bjacobse]

If there is humidity reported here, it is being reported to domoticz, and domoticz will use it...
It's not a domoticz issue

Thank you for a fast reply, as I understood your answers, Domoticz sees a humidity sensor since Openzwave are reporting the relay and temperature sensor wrongly. So I somehow need to change something in OpenZwave configuration files so the humidity sensor disappears
I will check if I can find some help at OpenZwave forum site for some details, as I were unclear in which direction I shall look at