I have an issue with model is TS0601 - TZE200_myd45weu reporting the wrong value

[alphatech69]

Does the issue really belong here?

• I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

• I have searched the existing issues and there is none for the bug at hand

Describe the bug

Steps to reproduce the behavior

The sensor is reporting the wrong info, this is a soil moisture device

Expected behavior

The sensor is reporting the wrong info, this is a soil moisture device

Screenshots

I have attached the screenshots

Environment

• Host system: (Raspberry Pi / PC / NAS / MAC)
• Running method: (Raspbian / Ubuntu / Home Assistent deCONZ Add-on / Marthoc Docker container / Windows / Virtual Machine)
• Firmware version: (26xxyy00)
• deCONZ version (not Home assistant Addon version!): (2.xx.yy)
• Device: (ConBee I / ConBee II / ConBee III / RaspBee I / RaspBee II)
• Do you use an USB extension cable: (yes / no) -- only relevant for ConBee I/II/III
• Is there any other USB or serial devices connected to the host system? If so: Which?

deCONZ Logs

PC, Homeseer and Home Assistant with decxonz.

Additional context

No response

[Mimiix]

Hi, not sure what the issue is. Also, the template is not complete.

[alphatech69]

Hi, this is a soil sensor not a thermostat as showed. It is reporting the wrong type, please see attached screenshots.
I'm new to this forum, what do you mean template is not complete?

[Smanar]

Hello, you have the issue only on phoscon ?
It's fine on HA/ Homeseer ?

You can too see the device direclty in the API, on phoscon/help/API Information/sensor (Raw value)

[Mimiix]

Hi, this is a soil sensor not a thermostat as showed. It is reporting the wrong type, please see attached screenshots. I'm new to this forum, what do you mean template is not complete?

By reading the template you filled. Instructions are in there.

I see in your screenshots that there's temperature and humidity. Which seem to be correct?

[alphatech69]

Thanks for your help. I have attached the screenshots that shows what I see in all the apps, not sure if you are seeing the same thing that I see but it shows that the sensor in ha report moisture to 0, that is incorrect. On the phoscon it shows the device as thermostat that is incorrect and in homeseer it only register the temperature sensor. As I mentioned before, this is a soil device it should register the soil moisture.

…

On Wed, Mar 27, 2024, 2:15 PM Smanar ***@***.***> wrote: Hello, you have the issue only on phoscon ? It's fine on HA ? You can too see the device direclty in the API, on phoscon/help/API Information/sensor — Reply to this email directly, view it on GitHub <#7682 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIOESBC53IJNDO4PWRVV2CDY2L5EHAVCNFSM6AAAAABFLJQCCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTGQ4DQOBWHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Mimiix]

Thanks for your help. I have attached the screenshots that shows what I see in all the apps, not sure if you are seeing the same thing that I see but it shows that the sensor in ha report moisture to 0, that is incorrect. On the phoscon it shows the device as thermostat that is incorrect and in homeseer it only register the temperature sensor. As I mentioned before, this is a soil device it should register the soil moisture.
…
On Wed, Mar 27, 2024, 2:15 PM Smanar @.> wrote: Hello, you have the issue only on phoscon ? It's fine on HA ? You can too see the device direclty in the API, on phoscon/help/API Information/sensor — Reply to this email directly, view it on GitHub <#7682 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIOESBC53IJNDO4PWRVV2CDY2L5EHAVCNFSM6AAAAABFLJQCCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTGQ4DQOBWHA . You are receiving this because you authored the thread.Message ID: @.>

Is it in the ground?

[alphatech69]

It is in a plant right now.

[Mimiix]

Looks like this device has bad firmware, or at least a high interval by reading this #6731

As this is not a bug report as described in #5113 I am closing this issue.