i noticed a problem with the Qubino temp sensors.
I do not know if it is a problem related to the modules or to domoticz.
i noticed the Qubino generated a lot of double devices for energy, power, and temperatures.
It generates 2 devices for temperature(unit 1 and unit 2)
if you do not change the temp offset in the module the graphics are exactly the same and you can use both of them.
However i have added a temp offset of 4 in the module which add's .4C to the value.
The unit reports changes of 0.1C so the graphics are very accurate
If you compare the graphics of both temp devices You will notice spikes.
These spikes are exactly the value of the offset.
unit 1 has the spikes, unit 2 has not.
so apparently the module(or domoticz) does not always take in to account the offset value. sometimes it does thus generating spikes because 1 minute later the temp drops exactly the offset value
Qubino ZMNHAD1 temp graphics wrong/spikes
Moderator: leecollings
- gizmocuz
- Posts: 2712
- Joined: Thursday 11 July 2013 18:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Top of the world
- Contact:
Re: Qubino ZMNHAD1 temp graphics wrong/spikes
We just log what is being reported... it's no domoticz issue
Quality outlives Quantity!
-
Gravityz
- Posts: 652
- Joined: Wednesday 16 December 2015 19:13
- Target OS: NAS (Synology & others)
- Domoticz version: 2025.1
- Location: Netherlands
- Contact:
Re: Qubino ZMNHAD1 temp graphics wrong/spikes
that was my thought also otherwise we would have seen his everywere
I however do not know if this is Qubino related or that Fibaro has this also .
when i reincluded this module. i only had one temp
i did some start/stop/reset things but still 1 temp device.
Then i added the offset to the module and after that the second device appeared.
so it looks like the offset is passed to the second device while the first device cabn not manage it correctly.
hopefully somebody else will look at their Qubino devices to see if they have this behaviour also
also disabling endpoint I2 and I3 instantly kills the temperature readouts, something that should not be possible since I2 and I3 are linked to extra switches which i do not use and have nothing to do with internal temperature readouts.
I however do not know if this is Qubino related or that Fibaro has this also .
when i reincluded this module. i only had one temp
i did some start/stop/reset things but still 1 temp device.
Then i added the offset to the module and after that the second device appeared.
so it looks like the offset is passed to the second device while the first device cabn not manage it correctly.
hopefully somebody else will look at their Qubino devices to see if they have this behaviour also
also disabling endpoint I2 and I3 instantly kills the temperature readouts, something that should not be possible since I2 and I3 are linked to extra switches which i do not use and have nothing to do with internal temperature readouts.
Who is online
Users browsing this forum: No registered users and 1 guest