search

Jey-Cee / ioBroker.deconz

Connects to deConz software developed by dresden-elektronik. This software aims to be a universal ZigBee Gateway solution, using hardware from dresden-elektronik the ConBee USB stick and RaspBee a modul for the Raspberry Pi.
Apache License 2.0
54 stars 34 forks source link

[Bug]: ct-Value too high. Appeared with the latest version #359

Closed unstressable closed 2 days ago

unstressable commented 5 months ago

Contact Details

No response

What happened?

Since some weeks I see these errors in my log: State value to set for "deconz.0.Lights.31.ct" has value "28673" greater than max "8000"

It happened suddenly without any changes except updates of deconz and phoson container (Docker)

I think the number of light-groups that are claiming this is increasing.

Adapter Version

1.4.0

deConz (Phoscon) Version

2.26.3

JS-Controller Version

5.0.19

Node JS Version

18.20.2

NPM Version

10.5.2

Operating System

Ubuntu

Relevant log output

deconz.0
2024-04-29 21:12:46.667 warn    State value to set for "deconz.0.Lights.27.ct" has value "27878" greater than max "8000"

deconz.0
2024-04-29 21:12:45.905 warn    State value to set for "deconz.0.Lights.31.ct" has value "28382" greater than max "8000"

deconz.0
2024-04-29 21:12:45.660 warn    State value to set for "deconz.0.Lights.27.ct" has value "28170" greater than max "8000"

deconz.0
2024-04-29 21:12:44.829 warn    State value to set for "deconz.0.Lights.31.ct" has value "28673" greater than max "8000"

deconz.0
2024-04-29 21:12:44.645 warn    State value to set for "deconz.0.Lights.27.ct" has value "28462" greater than max "8000"

deconz.0
2024-04-29 21:12:43.849 warn    State value to set for "deconz.0.Lights.31.ct" has value "28965" greater than max "8000"

deconz.0
2024-04-29 21:12:43.557 warn    State value to set for "deconz.0.Lights.27.ct" has value "28754" greater than max "8000"

deconz.0
2024-04-29 21:12:42.708 warn    State value to set for "deconz.0.Lights.31.ct" has value "29258" greater than max "8000"

deconz.0
2024-04-29 21:12:42.593 warn    State value to set for "deconz.0.Lights.27.ct" has value "29044" greater than max "8000"

deconz.0
2024-04-29 21:12:41.805 warn    State value to set for "deconz.0.Lights.31.ct" has value "29550" greater than max "8000"

deconz.0
2024-04-29 21:12:41.583 warn    State value to set for "deconz.0.Lights.27.ct" has value "29336" greater than max "8000"

Anything else?

No response

mattreim commented 5 months ago

What kind of devices are these (company/model)? Just out of interest.

unstressable commented 5 months ago

Philips Hue Gu10 tuneable white (latest with bluetooth)

mattreim commented 5 months ago

think the device is not yet properly supported by deConz. You can use RESTED/deConz REST-API to check whether the correct values ​​are being transferred.

GET -> http://<IP>/api/<apikey>/lights/<ID>

unstressable commented 5 months ago

I habe these devices since about 4 years now and I never had problems.

I think it is supported yet.

mattreim commented 5 months ago

They are currently converting all devices to DDF and yours must also be included in one.

unstressable commented 5 months ago

I dont know what ddf is, I dont know why this error happened suddenly without any changes in my setting. Now I changed the log level to "fault" and I hope its silence now ;)

TimoGoerlich commented 4 months ago

I have the same issue with a Hue Lightstrip. Also appeared suddenly after update.

State value to set for "deconz.0.Lights.60.ct" has value "42404" greater than max "8000"

mattreim commented 4 months ago

I still think it's a problem form Fix state of Hue lights not always updated correctly #7704

mattreim commented 4 months ago

Does adjusting the color temprature(ct) work? With a value of "42404" it would now only be blue.

color-temperature-scale

unstressable commented 4 months ago

In my case everything works fine. The error happens even without changing the ct value.

actually my log level is „fault“ this makes it silence.

kopierschnitte commented 4 months ago

Interesting problem. I've also noticed that "colormode" always changes back from "ct" to "effect", although "effect" isn't a valid option there. For me, setting the log level to "fault" also fixes flooding the log.

Jey-Cee commented 4 months ago

I've also noticed that "colormode" always changes back from "ct" to "effect", although "effect" isn't a valid option there.

You are right, effect isnt a valid value and more important: This does not exist as a state value on the object colormode. If this value is really printed in colormode provide more information on which device this happens and the version of deconz software it is happen.

kopierschnitte commented 4 months ago

Yes, that's the case.

It's happening on my "Hue Spot GU10"'s (LCG002) and "Hue White and color ambiance" (bulbs / LCT015). Deconz release is 2.26.3

Jey-Cee commented 4 months ago

Yes, that's the case.

It's happening on my "Hue Spot GU10"'s (LCG002) and "Hue White and color ambiance" (bulbs / LCT015). Deconz release is 2.26.3

Seems that effect is defined as colormode in deConz for this models.

mattreim commented 2 days ago

This issue should be resolved with v2.28.1 stable.

Jey-Cee commented 2 days ago

Thanks @mattreim.