search

Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
12.11k stars 1.68k forks source link

[Livarno Home LED ceiling light HG08008] turns itself off when sending "on" command, after it being off for "some time" #14714

Closed GsakuL closed 1 year ago

GsakuL commented 2 years ago

What happened?

I bought the light in store and mounted it. Interviewing was not problematic, and worked the first time. I'm using HomeAssistant and mostly Amazon Alexa, for control. Come late evening and i want to use the light, so tell Alexa to do it. It turns on, but a few Milliseconds later turns off. Tell Alexa again to turn it on, it stays on. I've tested this manually within the Z2M Webinterface. It is not a HA/Alexa Problem. If I've used the lamp "recently enough", it will react "normally".

What did you expect to happen?

Stays on the "first" time. So no "flicker". As with any other light/device

How to reproduce it (minimal and precise)

"Enough time" seems to be something like 5-20minutes. I have not timed it yet. But cutting mains is faster and works every time - I just tried it for this very Issue.

Additional info:

I still have my "old" CC2531 lying around. But I don't own any other Hub/Gateway, nor can I borrow one from/visit someone, to use for Sniffing their traffic.

Zigbee2MQTT version

1.28.0 commit: 03ba647

Adapter firmware version

20211217

Adapter

Slaesh's CC2652RB stick

Debug log

This is the following:

tryptophan0 commented 1 year ago

I have the same problem with this lamp. I am sending messages to mqtt via a script. The light would make the transition from off to full brightness, which takes about 1 second and then turn off, instead of staying lit. One thing that popped up in the zigbee2mqtt log is an error about color_mode: info 2022-11-11 20:13:32: MQTT publish: topic 'zigbee2mqtt/livarno1', payload '{"brightness":99,"color":{"x":0.448,"y":0.4076},"color_mode":"color_temp","color_temp":350,"last_seen":"2022-11-11T19:13:32.486Z","linkquality":51,"state":"ON"}' error 2022-11-11 20:13:32: No converter available for 'set' 'color_mode' (color_temp)

After tinkering with different attributes in the mqtt message, I finally found a case, that would keep the light on after the transition. The message content is: {'brightness_move': 100, 'state': 'ON'}

Version: Zigbee2MQTT version 1.28.2 (commit #360a777) and zigbee-herdsman (0.14.68)

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

GsakuL commented 1 year ago

using 1.28.4 commit: 52e545f the issue still exists

flosch-dev commented 1 year ago

Hello, I'm having the same issue but with different Livarno Ceiling Lamp: https://www.zigbee2mqtt.io/devices/14153806L.html In my case, I have 4 of those ceiling lamps some controlled via motion sensor (via HomeAssistant automation) and some other with Philips wall switch module. The strange thing is, that I only hit the problem when triggered by motion sensor, but not when triggered by hue wall switch. In both cases, HomeAssistant will control. I have also different motion sensors, all with the same problem. (IKEA, Aqara, Ali Express Tuya).

Is there anything I can bring in to investigate into the problem?

GsakuL commented 1 year ago

@flosch-dev I'm out of town atm, so I'm not completely sure. But I think the Ikea Sensor at least has a setting for brightness (button under the cover) that it will set the light to. Which in this case seems to be the cause/solution why they work together.

Sending brightness and "on" together (eg via mqtt) works. So I assume it's doing that.

I think what you can do to "investigate" is to sniff traffic, if you have a USB router left over: https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html

I have fooled around least week a bit with the dev console and some device regulations/documentations and pretty found out sending any command that alters brightness, work's (eg "move to _ and on". I also noticed "toggle" command will turn on the lamp, but it's not "very predictable" since you would have to know the current state

flosch-dev commented 1 year ago

just need to correct my statement, it also occours when trigger of automation is philips wall switch. However I have one lamp I'm only switching via wall-switch and this one seems to work fine.

flosch-dev commented 1 year ago

unfortunately I don't have such sniffer device, but maybe I need to buy one in future. Currently I'm using aqara motion sensor and I just run into the problem again.

I'm fearing the only option to nail down what's going on is to sniff the traffic?

flosch-dev commented 1 year ago

one more observation I want to share... I can trigger as well as recover the problem by frequently switching on and off (either via HA gui or via automation with ext. trigger). In that case I switch on/off faster than the transition itself. I also set transition time to 5 sek (just for testing) and noticed that transition usually works. When the problem exists, the transition seems to be less than 1 sek and behaves like in the initial descriptions. It turns on fast and switches off immediately (like less 1 sec).

tomiisp commented 1 year ago

Any news about this problem ? I have the same problem with this light and also there is a timeout on "power_on_behavior" option (and also exact same scenario - motion sensor triggered > light just flash, with scene switch or via web Z2M/HA seems it always turn on/off fine). (Btw, I have also original Lidl Gateway with linked TuYa dev account, another Lidl Gateway flashed with "hacked" FW and also some free USB CC2531 sticks... if someone point me to how to sniff traffic with original GW or via TuYa account I can do it, I only use CC2531 as sniffer for GW with CC2652P which I normally use with Z2M)

GsakuL commented 1 year ago

@tomiisp sadly no news

I've been trying to "at least" make it "somewhat work" (="maybe flicker, but only one voice/button command") in HomeAssistant via an "Template: Light" and a number Helper ("last known 'on'-brightness") Entities with a script, but i can't seem get it to "turn on at x%". I've tried to hack it via the script and send multiple custom MQTT Commands in order, but it doesn't work as expected. Either it flickers and stays off (as it would currently) or it would step/move up to 100%, regardless of canceling (with MQTT "*move/step": "stop" as listed on the device page). I've also tried different QoS Level, but with no luck. Either my script is "too fast" (which could very well be the case) or it does something i don't know.

I've never sniffed traffic, so all I can do is link you to the Z2M page again: https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html 🙁

I've "poked around a bit", and found the defintion for the converter: https://github.com/Koenkk/zigbee-herdsman-converters/blob/64e6e5e6be8e35d47291ea3b4f1bf082347c8efd/devices/lidl.js#L585 Which has been initially added via this PR: https://github.com/Koenkk/zigbee-herdsman-converters/pull/4128 by @pcedik

The only other thing I could think of is asking @Koenkk (I'm sorry to ping you) with regards to the device/Issue itself and the sniffing

tomiisp commented 1 year ago

@GsakuL have you tried to update to latest version 1.29.1 ? Today I mess around that light and also no luck but afternoon I spot new release, update it and problem is gone but I tested this only few hours but it never happen again after update, maybe it's just a coincidence and that light have only "good day" today but it is worth to try, of course it still need more time to test.

GsakuL commented 1 year ago

@tomiisp i was running 1.29.0, but just updated to 1.29.1 to report. Updated, "About" is showing the new version, yes. But the issue persists. :(

As said above, you can also "force" this "wrong/flashy behaviour", if you set/send the "off" command twice or more in a row. Or you could "hard reset" (like I wrote in the opening message), or "just wait some time". Remember: if you turn the light on once, and get past "the flickering", it works as any light/lamp should for ""some time"", until it falls back into its "wacky state".

tomiisp commented 1 year ago

@GsakuL Ok, I setup original TuYa gateway + SmartLife app, I set sniffer and grab network key and pair that light. What exactly need to be sniffed ? For example I just made this steps and all traffic is in attached file.

livarno-388125_2104_1_08012023.zip

Koenkk commented 1 year ago

@tomiisp Can you also provide a sniff when pairing the device? I need the network key of your tuya hub.

tomiisp commented 1 year ago

@Koenkk 38:72:ed:25:0e:52:f5:52:c5:ed:f0:32:4f:b3:33:ce / 3e:bb:d3:2e:d8:c4:de:0c:22:21:1c:1c:37:2f:67:44 is enough or you need log too ? (don't worry about publishing this keys, it is test environment)

Koenkk commented 1 year ago

@tomiisp thanks, it seems the normal ON command is used. Can you provide the herdsman debug logging when turning the light ON from zigbee2mqtt (at this point it should immediately turn OFF).

See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files.

tomiisp commented 1 year ago

@Koenkk sorry had not time for this kind of logging in past days (maybe tomorrow I try log it) but maybe I found a source of this problem, for me that light work fine for last few days, no flash at all and now I check what I change and seems it is related to transition value, I have set 1 second at brightness 20 = works without problem, yesterday I changed this value to 3 second and light just blink, everytime, I changed value (in HA) back to 1sec and it start working properly again. I will try to do more test and that log tomorrow.

GsakuL commented 1 year ago

@tomiisp I had some time, and tried setting transition=1, but this does not solve the flickering with my lamp. If its in "deep sleep"(?) aka the "long off"/"borked" state, it will just flicker, and i still have to send a second 'on' command :(

tomiisp commented 1 year ago

@GsakuL I start have similar problem with another Livarno light ( _TZ3210_c0s1xloa, TS0505B, big one 34W - 399629_2110), no motion sensor just scene switch. Light turn on then after 1sec turn off, that On/Off I see also on Z2M web frontend, same if I turn on that light via frontend switch BUT in this case it can be "fixed" by hitting blue refresh button on State, after this light start working again normal, odd. @Koenkk this "refresh state fix" remember me sniffed communication with original TuYa in log (must look again) where request for light state was sent after every action and also it repeats in log every ~3 minutes not matter if that light was on or off.

tomiisp commented 1 year ago

@Koenkk just my little investigation, two same lights, one connected to Z2M, second to TuYa, I see from log some difference in communication, maybe it is not important but maybe evil is hiding in details. Z2M:

Tuya:

Just thinking, maybe this kind of lights doesn't like some type of commands or sequences ? Or maybe that missing periodical Read/Report attributes commands send that light to unknown state or some "sleep" mode ? Maybe I am absolute out of topic but I see this difference between Z2M and TuYa communication and same problem appears also on another Livarno light (as I posted above).

livarno-388125_2104_2_20012023.zip

Koenkk commented 1 year ago

@tomiisp can you try the following and see if this issue does not appear when:

tomiisp commented 1 year ago

@Koenkk I tested that and it works fine BUT I was able confuse that light in odd way, this steps I repeat few times and its maybe 60/40 ratio between fine/odd response from light :

From my point of view I still think it have something to do with cmds, just "Move to level with OnOff" (Dev 1/8/4) vs. "Move to level" (Dev 1/8/0) & "OnOff" (Dev 1/6/0-1).

Koenkk commented 1 year ago

The transition is probably the problem, what if you just send {"state":"OFF"} ?

Barsonax commented 1 year ago

The transition is probably the problem, what if you just send {"state":"OFF"} ?

For me this does not fix the problem. Only sending a On twice seems to atleast end up with a lamp thats actually on (with some flicker :().

EDIT: iam using a conbee II as coordinator.

tomiisp commented 1 year ago

@Barsonax just a question, have you also that problem after some time of light inactivity and after "wakeup" it works for some time normally ?

Barsonax commented 1 year ago

@Barsonax just a question, have you also that problem after some time of light inactivity and after "wakeup" it works for some time normally ?

I suspect so but it's hard to really verify.

One way to force this behaviour is sending 2 off's. Then at the next on it will transition to the on state and then turn off by itself.

Sending another on (without a off in between) will fix this buggy state. That's actually my workaround for now, my code uses 2 on's to turn the light on. Hope that will at least make it reliable.

tomiisp commented 1 year ago

@Barsonax just for test, can you try to setup reporting for that light (also @GsakuL ) like on this screen ? original TuYa do this every 3 minutes and maybe it help prevent odd state of light... its worth to try this too, at least we eliminate one thing what original TuYa do

EDIT: I am not able upload any image, always get a "something went really wrong"..hmm

here is the list: Endpoint - Cluster - Attribute - Min rep interval - Max rep interval

Barsonax commented 1 year ago

In the meantime the light broke as in the warm leds stopped working so only cold light.

I have had nothing but problems with the lidl lights. I bought several of them and they all have issues. This is not a zigbee2mqtt issue I believe but a issue with the lights themselves.

Iam going to replace the lights with philips as I never have issues with those.

GsakuL commented 1 year ago

@tomiisp I'm sorry. I completely forgot about doing this. Done it now, I'll keep an eye on it. Though it still does blink/flicker, if I "force double turn off and once turn on" the lamp. I'll wait and try, when "sleep mode kicks in" (or would).

I undersand @Barsonax 's reasoning. I'd consider returning myself, while I still can. Z2M is really great, but "bad hardware" can make so much work/problems. Since I still have warranty, and I know LIDL is (at least here) pretty chill with returns in that period, I'll keep it for a bit longer.

I don't want to "put pressure" on anyone. But at the end of the day it's "just a generic ceiling light", so "nothing special". So maybe, if we couldn't solve this at all, perhaps consider putting a warning/note onto the Website/Index referencing this issue.

Barsonax commented 1 year ago

I agree. If it's not trivial to fix then at least a warning these lights have some issues in de docs would help ppl avoid this

Yakie996 commented 1 year ago

I also have this issue with my lidl lamps HG08008 and 14153806L, turning on and it turns off within a couple of milliseconds this behaviour keeps happening until I change the brightness or color of the lamp, sadly this is a temporary fix as the issue returns a couple of minutes later.

petrows commented 1 year ago

Have the same issue, and i did not found workaround for it yet :-(

In my setup i have 10 commands in loop with 100ms delay, lamps have annoying flickering, but at least they are return to ON back. In my case problem is very easy to reproduce: just send second OFF, when device is on OFF state, and next ON will have this issue. For me it is hard to avoid second OFF, as i have a lot of control, based on device groups in Openhab.

Having same feeling as @GsakuL : i also thinking about to return devices to LIDL, but i like lamps itself, they are really bright and nice looking in my setup.

petrows commented 1 year ago

Found workaround working for me - i have added special proxy item in OpenHAB, which connects to groups instead of original item, and updates original item only if state is changed. Without repeating OFF events (via groups) my devices now works much better. Now i have only problem with quick ON/OFF and hardcoded transition in lamps, but normal usage now does not flicker or turning off.

Commit: ef59891

tomiisp commented 1 year ago

Just a basic question to all : why this lights works fine with original TuYa gateway and app but doing strange things with Z2M ?... it is FW problem or implementation ? I wrote above (Jan20) some differences in commands (on zigbee level) how that lights is turned On/Off via TuYa and via Z2M.

GsakuL commented 1 year ago

@tomiisp Like I've mentioned earlier, I set up your reportings. I used the light now from time to time, but using this without any "proxy device" still has the issues of turning itself off. Using it with my non-optimized proxy it wont turn off (maybe because the delay is now longer, until the second command from the proxy arrives). But this is still bad, since my proxy is buggy an sometimes slowly ramps up brightness (due to my setup). Also i have one of those Multi-Button-Switches, which can send events like "brightness start up" and "brightness stop" (which i like, since it's just two events for a continuous change), but for that, i use MQTT directly anyways (for the required payload to the lamp)

To your question: Could it be, that the TuYa gateway uses some unknown/undocumented(?) setup-commands? Or is that ruled out by the traffic sniff?. Like the TuYa TS004F 4-Button-Switch was once changed in Z2M, to put it in "switch mode", so it reports all 12 events (single, double, long click for each button), instead of it's "dimmer mode". I have this switch, and have noticed the change. (but now the documentation says, this can be done in hardware, which is even never)

Regarding different commands: I've found this site: https://csa-iot.org/csa_product/smart-led-ceiling-light/ there you can "Download Compliance Document", which is a ZIP file with several long docx files. In there are function descriptions and Test Logs. I don't understand all the terminology. But if I take a look at 15-0309-006-0x0006-OnOff-Cluster-Test-Specification-Editors.docx at section 5.3.2 OO-TC-02S: Primary functionality with server as DUT 26 (just search OO-TC-02S) it shows a test sequence (table) where I've seen the following: grafik Take a look at step 2 and 3. It seems to be that a on/off command is immediately followed by a read command - as listed in your differences. Also the fact, that these two steps are *a and *b somewhat makes me think, that this is necessary/intended/required, even though the wording in the last column does not explicitly mention this.

tomiisp commented 1 year ago

@GsakuL thanks for that link, I have a look deeper on that but I quickly look at that section 5.3.2 and I not see there command what is used by Z2M, I reporting above main differences how is On/Off sent to device (except Read attributes): Tuya: sent single ON or OFF command and then followed by "Move to level" command Z2M: sent "combined" single command "Move to level with OnOff" (0x04) for both ON and OFF

EDIT: I forgot to mention - I have same problem with other non-Lidl lights too, its E27 bulbs TS0505B - _TZ3210_r5afgmkl (Aliexpress), I have only 2 of this bulbs but both do exact same things over random time...

petrows commented 1 year ago

Hey @tomiisp ,

I start have similar problem with another Livarno light ( _TZ3210_c0s1xloa, TS0505B, big one 34W - 399629_2110), no motion sensor just scene switch. Light turn on then after 1sec turn off, that On/Off I see also on Z2M web frontend, same if I turn on that light via frontend switch BUT in this case it can be "fixed" by hitting blue refresh button on State, after this light start working again normal, odd.

I just observed exactly the same behavior for another Livarno light: E14 RGB bulb (HG07834B, _TZ3000_th6zqqy6, TS0505B). It seems to be this problem is at least common for this Zigbee device implementation.

I can also add, that problem is also "fixed" by requesting state property via <device>/get endpoint.

tomiisp commented 1 year ago

@petrows hm, seems this is common problem for most TS0505B based devices and about that requesting state, that is what Z2M not do after sending commands to device but TuYa issue "request attributes" command after each command sent to device and also it is mentioned in that docs what was posted by GsakuL, maybe this is real root of this problem.

Yakie996 commented 1 year ago

this happens to me with this and this light. turn it on and turn itself off, this is happening for me for more than 4 months. it makes the lights not usable, is a fix coming soon?

tomiisp commented 1 year ago

@Yakie996 tag this response to @Koenkk too, this problem with "Lidl lights based on TS0505B" must be solved somehow, this Lidl lights have CSA certificate and works fine with Tuya/Lidl gw/apps but Z2M have problem with it and it is clearly problem of Z2M implementation and not Lights itself which follow Tuya protocols and pass CSA certification...

Yakie996 commented 1 year ago

this happens to me with this and this light. turn it on and turn itself off, this is happening for me for more than 4 months. it makes the lights not usable, is a fix coming soon?

@Yakie996 tag this response to @Koenkk too, this problem with "Lidl lights based on TS0505B" must be solved somehow, this Lidl lights have CSA certificate and works fine with Tuya/Lidl gw/apps but Z2M have problem with it and it is clearly problem of Z2M implementation and not Lights itself which follow Tuya protocols and pass CSA certification...

@Koenkk

Koenkk commented 1 year ago

Does the device work with the following external converter?

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const ota = require('zigbee-herdsman-converters/lib/ota');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const utils = require('zigbee-herdsman-converters/lib/utils');
const globalStore = require('zigbee-herdsman-converters/lib/store');
const e = exposes.presets;
const ea = exposes.access;

const tzLocal = {
    led_control: {
        key: ['brightness', 'color', 'color_temp', 'transition'],
        options: [exposes.options.color_sync()],
        convertSet: async (entity, _key, _value, meta) => {
            const newState = {};

            // The color mode encodes whether the light is using its white LEDs or its color LEDs
            let colorMode = meta.state.color_mode ?? colorModeLookup[ColorMode.ColorTemp];

            // Color mode switching is done by setting color temperature (switch to white LEDs) or setting color (switch
            // to color LEDs)
            if ('color_temp' in meta.message) colorMode = colorModeLookup[ColorMode.ColorTemp];
            if ('color' in meta.message) colorMode = colorModeLookup[ColorMode.HS];

            if (colorMode != meta.state.color_mode) {
                newState.color_mode = colorMode;

                // To switch between white mode and color mode, we have to send a special command:
                const rgbMode = (colorMode == colorModeLookup[ColorMode.HS]);
                await entity.command('lightingColorCtrl', 'tuyaRgbMode', {enable: rgbMode}, {}, {disableDefaultResponse: true});
            }

            // A transition time of 0 would be treated as about 1 second, probably some kind of fallback/default
            // transition time, so for "no transition" we use 1 (tenth of a second).
            const transtime = 'transition' in meta.message ? meta.message.transition * 10 : 1;

            if (colorMode == colorModeLookup[ColorMode.ColorTemp]) {
                if ('brightness' in meta.message) {
                    const zclData = {level: Number(meta.message.brightness), transtime};
                    await entity.command('genLevelCtrl', 'moveToLevel', zclData, utils.getOptions(meta.mapped, entity));
                    newState.brightness = meta.message.brightness;
                }

                if ('color_temp' in meta.message) {
                    const zclData = {colortemp: meta.message.color_temp, transtime: transtime};
                    await entity.command('lightingColorCtrl', 'moveToColorTemp', zclData, utils.getOptions(meta.mapped, entity));
                    newState.color_temp = meta.message.color_temp;
                }
            } else if (colorMode == colorModeLookup[ColorMode.HS]) {
                if ('brightness' in meta.message || 'color' in meta.message) {
                    // We ignore the brightness of the color and instead use the overall brightness setting of the lamp
                    // for the brightness because I think that's the expected behavior and also because the color
                    // conversion below always returns 100 as brightness ("value") even for very dark colors, except
                    // when the color is completely black/zero.

                    // Load current state or defaults
                    const newSettings = {
                        brightness: meta.state.brightness ?? 254, //      full brightness
                        hue: (meta.state.color ?? {}).hue ?? 0, //          red
                        saturation: (meta.state.color ?? {}).saturation ?? 100, // full saturation
                    };

                    // Apply changes
                    if ('brightness' in meta.message) {
                        newSettings.brightness = meta.message.brightness;
                        newState.brightness = meta.message.brightness;
                    }
                    if ('color' in meta.message) {
                        // The Z2M UI sends `{ hex:'#xxxxxx' }`.
                        // Home Assistant sends `{ h: xxx, s: xxx }`.
                        // We convert the former into the latter.
                        const c = libColor.Color.fromConverterArg(meta.message.color);
                        if (c.isRGB()) {
                            // https://github.com/Koenkk/zigbee2mqtt/issues/13421#issuecomment-1426044963
                            c.hsv = c.rgb.gammaCorrected().toXY().toHSV();
                        }
                        const color = c.hsv;

                        newSettings.hue = color.hue;
                        newSettings.saturation = color.saturation;

                        newState.color = {
                            hue: color.hue,
                            saturation: color.saturation,
                        };
                    }

                    // Convert to device specific format and send
                    const zclData = {
                        brightness: utils.mapNumberRange(newSettings.brightness, 0, 254, 0, 1000),
                        hue: newSettings.hue,
                        saturation: utils.mapNumberRange(newSettings.saturation, 0, 100, 0, 1000),
                    };
                    // This command doesn't support a transition time
                    await entity.command('lightingColorCtrl', 'tuyaMoveToHueAndSaturationBrightness2', zclData,
                        utils.getOptions(meta.mapped, entity));
                }
            }

            // If we're in white mode, calculate a matching display color for the set color temperature. This also kind
            // of works in the other direction.
            Object.assign(newState, libColor.syncColorState(newState, meta.state, entity, meta.options, meta.logger));

            return {state: newState};
        },
        convertGet: async (entity, key, meta) => {
            await entity.read('lightingColorCtrl', ['currentHue', 'currentSaturation', 'currentLevel', 'tuyaRgbMode', 'colorTemperature']);
        },
    },
};
const definition = {
    fingerprint: tuya.fingerprint('TS0505B', ['_TZ3210_c0s1xloa', '_TZ3210_iystcadi', '_TZ3210_p9ao60da']),
    model: 'TS0505B_2',
    vendor: 'TuYa',
    description: 'Zigbee RGB+CCT light',
    whiteLabel: [
        tuya.whitelabel('Lidl', '14149505L/14149506L_2', 'Livarno Lux light bar RGB+CCT (black/white)', ['_TZ3210_iystcadi']),
        tuya.whitelabel('Lidl', '399629_2110', 'Livarno Lux Ceiling Panel RGB+CCT', ['_TZ3210_c0s1xloa']),
    ],
    toZigbee: [tz.on_off, tzLocal.led_control],
    fromZigbee: [fz.on_off, fz.tuya_led_controller, fz.brightness, fz.ignore_basic_report],
    exposes: [e.light_brightness_colortemp_colorhs([153, 500]).removeFeature('color_temp_startup')],
    configure: async (device, coordinatorEndpoint, logger) => {
        device.getEndpoint(1).saveClusterAttributeKeyValue('lightingColorCtrl', {colorCapabilities: 29});
    },
};

module.exports = definition;
tomiisp commented 1 year ago

@Koenkk for me not, still "flash" and have exact same issues as I report yesterday about version 1.30.4 disaster (Issue #17527) and this converter in my case affect devices _TZ3210_p9ao60da which was "untouched" in 1.30.4 update

Koenkk commented 1 year ago

@tomiisp from your findings in https://github.com/Koenkk/zigbee2mqtt/issues/14714#issuecomment-1399446243 I think this has something to do with the transition. Did you already try without a transition?

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

petrows commented 1 year ago

Dear @Koenkk , i have tested a lot, with/without transition, seems to be it does not affect this issue. Transition has another issue there, for example, lamp may have delayed "off" command on transition, for example, it may switch off after transition delay second time, but this looks like another issue and disabling it does not helps with original problem.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

GsakuL commented 1 year ago

I'm sorry for responding so late, but I had critical personal matters to attend to.

Currently running Z2M v 1.31.2, just wanted to test this real quick, so didn't want to "risk" an update and letting this go stale.

@Koenkk I've tried your converter. On first impression, turning the lamp on works without flashing. However other functions fail, e.g. set/get brightness:

debug 2023-07-10 20:48:46Publishing 'set' 'brightness' to 'home/device/ground_floor/office/ceiling/light/Lidl_Fixture_0'
error 2023-07-10 20:48:46Publish 'set' 'brightness' to 'home/device/ground_floor/office/ceiling/light/Lidl_Fixture_0' failed: 'ReferenceError: colorModeLookup is not defined'
debug 2023-07-10 20:48:46ReferenceError: colorModeLookup is not defined at Object.convertSet (/app/data/extension/externally-loaded.js:25:47) at Publish.onMQTTMessage (/app/lib/extension/publish.ts:247:52)
info 2023-07-10 20:48:46MQTT publish: topic 'zigbee2mqtt/home/device/ground_floor/office/ceiling/light/Lidl_Fixture_0', payload '{"brightness":1,"color":{"h":227,"hue":227,"s":53,"saturation":53,"x":0.2607,"y":0.2633},"color_mode":"color_temp","color_temp":60,"level_config":{"execute_if_off":true},"linkquality":142,"state":"ON"}'
debug 2023-07-10 20:51:00Received MQTT message on 'zigbee2mqtt/home/device/ground_floor/office/ceiling/light/Lidl_Fixture_0/get' with data '{"brightness":""}'
debug 2023-07-10 20:51:00Publishing get 'get' 'brightness' to 'home/device/ground_floor/office/ceiling/light/Lidl_Fixture_0'
error 2023-07-10 20:51:00Publish 'get' 'brightness' to 'home/device/ground_floor/office/ceiling/light/Lidl_Fixture_0' failed: 'Error: Cluster 'lightingColorCtrl' has no attribute 'currentLevel''
debug 2023-07-10 20:51:00Error: Cluster 'lightingColorCtrl' has no attribute 'currentLevel' at Object.getAttribute (/app/node_modules/zigbee-herdsman/src/zcl/utils.ts:93:19) at Endpoint.read (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:546:87) at Object.convertGet (/app/data/extension/externally-loaded.js:110:26) at Publish.onMQTTMessage (/app/lib/extension/publish.ts:274:37) at EventEmitter.emit (node:events:525:35) at EventBus.emitMQTTMessage (/app/lib/eventBus.ts:109:22) at MQTT.onMessage (/app/lib/mqtt.ts:140:27) at WebSocket.<anonymous> (/app/lib/extension/frontend.ts:126:27) at WebSocket.emit (node:events:513:28) at Receiver.receiverOnMessage (/app/node_modules/ws/lib/websocket.js:1184:20)

@tomiisp i had to "reconfigure" (yellow double arrow button on device "About" page) the lamp, because otherwise the external converter seemed not to be used.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

Yakie996 commented 11 months ago

@Koenkk The problem is still present with my lidl ceiling lights, when i turn the light on it briefly turns on for 0.5 sec turns off again (still displays as on in ha) when I change the brightness the light turns on again and stays on. (https://www.zigbee2mqtt.io/devices/HG08008.html#lidl-hg08008 and https://www.zigbee2mqtt.io/devices/14153806L.html#lidl-14153806l)

How can I help solving this problem?

I have home assistant on my synology nas using a vm and the skyconnect stick.