Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aqara T1M (CL-L02D): no effect on endpoints except on/off #2321

Open
grandslam18 opened this issue Dec 15, 2024 · 15 comments
Open

Aqara T1M (CL-L02D): no effect on endpoints except on/off #2321

grandslam18 opened this issue Dec 15, 2024 · 15 comments

Comments

@grandslam18
Copy link

grandslam18 commented Dec 15, 2024

describe the problem in Detail. What do you expect to happen ? What does happen ?

Installed an aqara T1M ceiling light today and added it to my zigbee adapter instance. Lamp marked as supported in zigbee2mqtt: https://www.zigbee2mqtt.io/devices/CL-L02D.html

No issues during interview:
Interview successful: {"friendly_name":"0x54ef441000b107d2","model":"CL-L02D","vendor":"Aqara","description":"Ceiling light T1M","supported":true} New device joined '0x54ef441000b107d2' model CL-L02D Device '0x54ef441000b107d2' announced itself Interview started: 0x54ef441000b107d2

link_quality, power_outage_count and device_temperature look accurate, msg_from_zigbee updates itself in intervals of few seconds:
{"type":"attributeReport","data":{"65522":{"type":"Buffer","data":[170,117,19,132,44,30,7,65,0,15,12,35,1,1,0,8,10,35,8,0,12,100,11,32,2]}},"linkquality":32,"groupID":0,"cluster":"manuSpecificLumi","meta":{"zclTransactionSequenceNumber":72,"manufacturerCode":4447,"frameControl":{"frameType":0,"manufacturerSpecific":true,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

state_rgb and state_white are effective / let me switch off both lights independently and as expected.

All other datapoints such as brightness_rgb, brightness_white, color_rgb, colortemp_white just produce error codes in the logs like this and show no effect:
zigbee.0 2024-12-15 21:44:39.033 error Send command to 0x54ef441000b107d2 failed with no error code (undefined)

Tried to exclude the device in adapter settings, tried multiple pairings and state cleanups without any effect.

Adapter version

1.10.13

Coordinator firmware version

1.0

Coordinator

cod.m ZigBee Coordinator CC2652P7 (CZC-1.0)

Setup

Raspberry Pi 4 (no docker)

Protocol of the error (as text, encapsulated in multiline code tags <>). Separate different occurrances into clearly split log sections

No response

Mod-Edit: Fixed Link

@grandslam18
Copy link
Author

grandslam18 commented Dec 17, 2024

Created a log when trying to change RGB color (using color_rgb, which is type level.color.rgb -> writing #ff00ff into the datapoint). This is not creating an error code, however the lamp still does not change its color:

zigbee.0
2024-12-18 09:57:03.449	warn	Error convert result for color_rgb with {"x":"0.3855","y":"0.1546"} is undefined on device 0x54ef441000b107d2.

zigbee.0
2024-12-18 09:57:03.449	warn	ELEVATED: convert result undefined for device 0x54ef441000b107d2

zigbee.0
2024-12-18 09:57:03.448	warn	ELEVATED: convert color_rgb, {"x":"0.3855","y":"0.1546"}, {"transition_time":2,"hue_calibration":"{\"x\":0.3,\"y\":0.6}","transition":2} for device 0x54ef441000b107d2

zigbee.0
2024-12-18 09:57:03.447	warn	ELEVATED: Setting' converter to converter with key(s)'["color","color_temp","color_temp_percent"]}

zigbee.0
2024-12-18 09:57:03.441	warn	ELEVATED Change state 'color_rgb' at device 0x54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-18 09:57:03.370	warn	ELEVATED: User stateChange zigbee.0.54ef441000b107d2.color_rgb {"val":"#ff00ff","ack":false,"ts":1734512223365,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1734512223365}

when writing e.g. 255,0,255 instead of #ff00ff hex-code style:

zigbee.0
2024-12-18 09:58:19.360	warn	Error convert result for color_rgb with {"x":"0.1355","y":"0.0399"} is undefined on device 0x54ef441000b107d2.

zigbee.0
2024-12-18 09:58:19.360	warn	ELEVATED: convert result undefined for device 0x54ef441000b107d2

zigbee.0
2024-12-18 09:58:19.359	warn	ELEVATED: convert color_rgb, {"x":"0.1355","y":"0.0399"}, {"transition_time":2,"hue_calibration":"{\"x\":0.3,\"y\":0.6}","transition":2} for device 0x54ef441000b107d2

zigbee.0
2024-12-18 09:58:19.358	warn	ELEVATED: Setting' converter to converter with key(s)'["color","color_temp","color_temp_percent"]}

zigbee.0
2024-12-18 09:58:19.350	warn	ELEVATED Change state 'color_rgb' at device 0x54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-18 09:58:19.296	warn	ELEVATED: User stateChange zigbee.0.54ef441000b107d2.color_rgb {"val":"255,0,255","ack":false,"ts":1734512299292,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1734512299292}

@grandslam18
Copy link
Author

grandslam18 commented Dec 17, 2024

When using brightness_white datapoint (0...100), this is the log I get (incl. the error code):
Same would happen when using brightness_rgb for the outer part of the lamp.

zigbee.0
2024-12-18 09:55:25.054	error	Send command to 0x54ef441000b107d2 failed with no error code (undefined)

zigbee.0
2024-12-18 09:55:25.052	warn	caught error {} is undefined on device 0x54ef441000b107d2.

zigbee.0
2024-12-18 09:55:25.051	warn	ELEVATED: convert brightness_white, 127, {"brightness_white":50,"transition_time":2,"hue_calibration":"{\"x\":0.3,\"y\":0.6}","transition":2,"brightness":127} for device 0x54ef441000b107d2

zigbee.0
2024-12-18 09:55:25.049	warn	ELEVATED: Overriding' converter to converter with key(s)'["state","brightness","brightness_percent","on_time","off_wait_time"]}

zigbee.0
2024-12-18 09:55:25.048	warn	ELEVATED: Setting' converter to converter with key(s)'["state","brightness","brightness_percent","on_time","off_wait_time"]}

zigbee.0
2024-12-18 09:55:25.037	warn	ELEVATED Change state 'brightness_white' at device 0x54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-18 09:55:24.933	warn	ELEVATED: User stateChange zigbee.0.54ef441000b107d2.brightness_white {"val":50,"ack":false,"ts":1734512124927,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1734512124927}

@grandslam18
Copy link
Author

grandslam18 commented Dec 17, 2024

Datapoint colortemp_move (entered as -50...50) is effective for the primary light, creating this log:
Same applies to brightness_move, dimming the primary light
But it feels as if the transition is super fast...


zigbee.0
2024-12-18 09:59:51.855	warn	ELEVATED publishToState: value generated '100' from device 54ef441000b107d2 for 'Brightness white'

zigbee.0
2024-12-18 09:59:51.854	warn	ELEVATED publishToState: message received '{"brightness_white":254}' from device 54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-18 09:59:51.829	warn	ELEVATED publishToState: value generated '21' from device 54ef441000b107d2 for 'Link quality'

zigbee.0
2024-12-18 09:59:51.828	warn	ELEVATED publishToState: message received '{"linkquality":21}' from device 54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-18 09:59:51.806	warn	ELEVATED: Zigbee Event of Type attributeReport from device "0x54ef441000b107d2", incoming event: {"type":"attributeReport","device":"0x54ef441000b107d2","endpoint":1,"data":{"245":14629176,"currentLevel":254},"linkquality":21,"groupID":0,"cluster":"genLevelCtrl"}

zigbee.0
2024-12-18 09:59:51.542	warn	Error convert result for brightness_move with 1 is undefined on device 0x54ef441000b107d2.

zigbee.0
2024-12-18 09:59:51.542	warn	ELEVATED: convert result undefined for device 0x54ef441000b107d2

zigbee.0
2024-12-18 09:59:51.375	warn	ELEVATED: convert brightness_move, 1, {} for device 0x54ef441000b107d2

zigbee.0
2024-12-18 09:59:51.373	warn	ELEVATED: Overriding' converter to converter with key(s)'["brightness_move","brightness_move_onoff"]}

zigbee.0
2024-12-18 09:59:51.372	warn	ELEVATED: Setting' converter to converter with key(s)'["brightness_move","brightness_move_onoff"]}

zigbee.0
2024-12-18 09:59:51.359	warn	ELEVATED Change state 'brightness_move' at device 0x54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-18 09:59:51.299	warn	ELEVATED: User stateChange zigbee.0.54ef441000b107d2.brightness_move {"val":1,"ack":false,"ts":1734512391294,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1734512391294}

@grandslam18
Copy link
Author

Important: all logs have been created while device was excluded. Let me know if I should re-do the test without the exclusion as well, and if other datapoints are of interest. Thanks for your support!

@asgothian
Copy link
Collaborator

Please set the adapter back to info instead of debug, and instead run the same test with the IEEE of the device(s) entered into the zigbee.0.info.debugmessages state (without the 0x). It will generate warning messages with the keyword ELEVATED. Those are a lot easier to read and generate less noise.

As far as I see it currently, the issue is with the device, as the command is sent to the device but it does not respond.

A.

@grandslam18
Copy link
Author

@asgothian: I changed the logs as requested in the comments above, let me know if I can support debugging further.

@asgothian
Copy link
Collaborator

Thanks for the change. Please make the following by entering the given strings into the "send_payload" state for the device and check for the lamps reaction (and the logs) Please also post the logs for each of the tests separately.

  • {"state_white":"ON"} - expected result: White section turned on.
  • {"brightness_white":128} - expected result: brightness of the "white" part set to 50%
  • {"state":"ON"} - expected result:other section on.
  • {"brightness":128} - expected result: brightness
  • {"brightness_move":25} - expected result: brightness dimming up from 50 % to 100% in 5 seconds
  • {"brightness_move":-25} - expected result brightness dimming down from 100% to off in 10 seconds

This will indicate if it is an issue with the converters or the zigbee Adapter.

A.

@grandslam18
Copy link
Author

Just copying screenshots from the device in the adapter view to have all information on one place:
image
image
image

@grandslam18
Copy link
Author

grandslam18 commented Dec 19, 2024

Logs...

Device consists of a inner lamp that should have dimmable brightness and changeable white-tone (CCT) and an RGB outer ring

{"state_white":"ON"}

  • expected result: White section turned on.
  • actual result: none of the sections turned on
zigbee.0
2024-12-19 11:48:41.052	error	No converter available for '' with key 'state_white'

zigbee.0
2024-12-19 11:48:41.042	warn	ELEVATED Change state 'send_payload' at device 0x54ef441000b107d2 type 'CL-L02D'



zigbee.0
2024-12-19 11:48:40.988	warn	ELEVATED: User stateChange zigbee.0.54ef441000b107d2.send_payload {"val":"{\"state_white\":\"ON\"}","ack":false,"ts":1734605320984,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1734605320984}

{"brightness_white":128}

  • expected result: brightness of the "white" part set to 50%
  • actual result: no brightness change on any section
zigbee.0
2024-12-19 11:52:31.586	error	No converter available for '' with key 'brightness_white'

zigbee.0
2024-12-19 11:52:31.577	warn	ELEVATED Change state 'send_payload' at device 0x54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-19 11:52:31.484	warn	ELEVATED: User stateChange zigbee.0.54ef441000b107d2.send_payload {"val":"{\"brightness_white\":128}","ack":false,"ts":1734605551480,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1734605551480}

{"state":"ON"}

  • expected result:other section on.
  • actual result: it switches on the inner CCT white lamp / primary lamp
zigbee.0
2024-12-19 11:55:41.732	warn	ELEVATED: convert result {"state":{"state":"ON"},"readAfterWriteTime":0} for device 0x54ef441000b107d2

zigbee.0
2024-12-19 11:55:41.692	warn	ELEVATED: convert state, "ON", {} for device 0x54ef441000b107d2

zigbee.0
2024-12-19 11:55:41.691	warn	ELEVATED: Overriding' converter to converter with key(s)'["state","brightness","brightness_percent","on_time","off_wait_time"]}

zigbee.0
2024-12-19 11:55:41.690	warn	ELEVATED: Setting' converter to converter with key(s)'["state","brightness","brightness_percent","on_time","off_wait_time"]}

zigbee.0
2024-12-19 11:55:41.682	warn	ELEVATED Change state 'send_payload' at device 0x54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-19 11:55:41.629	warn	ELEVATED: User stateChange zigbee.0.54ef441000b107d2.send_payload {"val":"{\"state\":\"ON\"}","ack":false,"ts":1734605741626,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1734605705257}

Decided to also try payload {"state_rgb":"ON"}, nothing happens:

zigbee.0
2024-12-19 11:59:16.696	error	No converter available for '' with key 'state_rgb'

zigbee.0
2024-12-19 11:59:16.686	warn	ELEVATED Change state 'send_payload' at device 0x54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-19 11:59:16.635	warn	ELEVATED: User stateChange zigbee.0.54ef441000b107d2.send_payload {"val":"{\n \"state_rgb\": \"ON\"\n}","ack":false,"ts":1734605956632,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1734605956632}

{"brightness":128}

  • expected result: brightness
  • actual result: brightness of primary (CCT white) part of the lamp is at 50%
zigbee.0
2024-12-19 12:00:58.121	warn	ELEVATED publishToState: value generated '51' from device 54ef441000b107d2 for 'Brightness white'

zigbee.0
2024-12-19 12:00:58.120	warn	ELEVATED publishToState: message received '{"brightness_white":128}' from device 54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-19 12:00:58.105	warn	ELEVATED publishToState: value generated '14' from device 54ef441000b107d2 for 'Link quality'

zigbee.0
2024-12-19 12:00:58.104	warn	ELEVATED publishToState: message received '{"linkquality":14}' from device 54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-19 12:00:58.091	warn	ELEVATED: Zigbee Event of Type attributeReport from device "0x54ef441000b107d2", incoming event: {"type":"attributeReport","device":"0x54ef441000b107d2","endpoint":1,"data":{"245":14629156,"currentLevel":128},"linkquality":14,"groupID":0,"cluster":"genLevelCtrl"}

zigbee.0
2024-12-19 12:00:57.930	warn	ELEVATED publishToState: value generated 'true' from device 54ef441000b107d2 for 'Switch state white'

zigbee.0
2024-12-19 12:00:57.928	warn	ELEVATED publishToState: message received '{"state_white":"ON"}' from device 54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-19 12:00:57.917	warn	ELEVATED publishToState: value generated 'true' from device 54ef441000b107d2 for 'Switch state white'

zigbee.0
2024-12-19 12:00:57.916	warn	ELEVATED publishToState: message received '{"state_white":"ON"}' from device 54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-19 12:00:57.903	warn	ELEVATED publishToState: value generated '14' from device 54ef441000b107d2 for 'Link quality'

zigbee.0
2024-12-19 12:00:57.902	warn	ELEVATED publishToState: message received '{"linkquality":14}' from device 54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-19 12:00:57.889	warn	ELEVATED: Zigbee Event of Type attributeReport from device "0x54ef441000b107d2", incoming event: {"type":"attributeReport","device":"0x54ef441000b107d2","endpoint":1,"data":{"245":14629156,"onOff":1},"linkquality":14,"groupID":0,"cluster":"genOnOff"}

zigbee.0
2024-12-19 12:00:57.584	warn	ELEVATED: convert result {"state":{"brightness":128,"state":"ON"},"readAfterWriteTime":0} for device 0x54ef441000b107d2

zigbee.0
2024-12-19 12:00:57.540	warn	ELEVATED: convert brightness, 128, {} for device 0x54ef441000b107d2

zigbee.0
2024-12-19 12:00:57.539	warn	ELEVATED: Overriding' converter to converter with key(s)'["state","brightness","brightness_percent","on_time","off_wait_time"]}

zigbee.0
2024-12-19 12:00:57.538	warn	ELEVATED: Setting' converter to converter with key(s)'["state","brightness","brightness_percent","on_time","off_wait_time"]}

zigbee.0
2024-12-19 12:00:57.530	warn	ELEVATED Change state 'send_payload' at device 0x54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-19 12:00:57.479	warn	ELEVATED: User stateChange zigbee.0.54ef441000b107d2.send_payload {"val":"{\"brightness\":128}","ack":false,"ts":1734606057476,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1734606057476}

{"brightness_move":25}

  • expected result: brightness dimming up from 50 % to 100% in 5 seconds
  • actual result: brightness dimming up from 50% to 100% in about a second (defintely way faster than the 5 seconds mentioned) -> applies to the primary (CCT white) part of the lamp
zigbee.0
2024-12-19 12:07:05.510	warn	Error convert result for brightness_move with 25 is undefined on device 0x54ef441000b107d2.

zigbee.0
2024-12-19 12:07:05.510	warn	ELEVATED: convert result undefined for device 0x54ef441000b107d2

zigbee.0
2024-12-19 12:07:05.464	warn	ELEVATED: convert brightness_move, 25, {} for device 0x54ef441000b107d2

zigbee.0
2024-12-19 12:07:05.461	warn	ELEVATED: Overriding' converter to converter with key(s)'["brightness_move","brightness_move_onoff"]}

zigbee.0
2024-12-19 12:07:05.460	warn	ELEVATED: Setting' converter to converter with key(s)'["brightness_move","brightness_move_onoff"]}

zigbee.0
2024-12-19 12:07:05.444	warn	ELEVATED Change state 'send_payload' at device 0x54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-19 12:07:05.386	warn	ELEVATED: User stateChange zigbee.0.54ef441000b107d2.send_payload {"val":"{\"brightness_move\":25}","ack":false,"ts":1734606425381,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1734606425381}

{"brightness_move":-25}

  • expected result brightness dimming down from 100% to off in 10 seconds
  • actual result: brightness dimming down from 100% to off in about a second of primary (CCT white) lamp -> without accuartely measuring the timings, it still feels as if there's no difference in timing if I enter -1 or -50 for dimming down or 1 or 50 for dimming up
zigbee.0
2024-12-19 12:09:55.708	warn	Error convert result for brightness_move with -25 is undefined on device 0x54ef441000b107d2.

zigbee.0
2024-12-19 12:09:55.708	warn	ELEVATED: convert result undefined for device 0x54ef441000b107d2

zigbee.0
2024-12-19 12:09:55.666	warn	ELEVATED: convert brightness_move, -25, {} for device 0x54ef441000b107d2

zigbee.0
2024-12-19 12:09:55.666	warn	ELEVATED: Overriding' converter to converter with key(s)'["brightness_move","brightness_move_onoff"]}

zigbee.0
2024-12-19 12:09:55.665	warn	ELEVATED: Setting' converter to converter with key(s)'["brightness_move","brightness_move_onoff"]}

zigbee.0
2024-12-19 12:09:55.658	warn	ELEVATED Change state 'send_payload' at device 0x54ef441000b107d2 type 'CL-L02D'

zigbee.0
2024-12-19 12:09:55.609	warn	ELEVATED: User stateChange zigbee.0.54ef441000b107d2.send_payload {"val":"{\"brightness_move\":-25}","ack":false,"ts":1734606595606,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1734606595606}

Maybe there is a mapping issue between datapoints shown in iobroker and the 2 sections of the lamp? I couldn't find any action that works for its RGB part, while the white section works on some datapoints.

@asgothian
Copy link
Collaborator

Possibly. I’ll need to take a close look at the implementation in the code. Are you comfortable using the developer tab in the adapter to see if the lamp reacts properly ?

@grandslam18
Copy link
Author

grandslam18 commented Dec 21, 2024

Hi @asgothian!
First of all, thanks for your support and a huge shout out to everyone contributing to this project - from implementation to documentation. I used the dev mode first time today, and I just had some few issues in the beginning with writing data in the appropriate format. However, I can report 100% positive results from my test - basically all functionalities that I need are working through dev mode:

  • on/off for both endpoints
  • dimming both endpoints
  • white tone for both endpoints
  • color setting the RGB part of the lamp

Since I'm handing over all data to a Loxone Miniserver, I only need datapoints to set acutal values, means only "moveTo..." type of messages.

My results in detail:

Switching on/off:
image

Works for both endpoints where 1…CCT white part and 2…RGB part of the lamp
Works both for on(1) and off(0) command

Logs
for off command (independent from endpoint):
SUCCESS {"cmdId":0,"statusCode":0}

for on command (independent from endpoint):
SUCCESS {"cmdId":1,"statusCode":0}

Dimming:
Expert mode was required for the payload level and transtime:
image
image

Works for both endpoints where 1…CCT white part and 2…RGB part of the lamp
Expects values between 0…255

Log (independent from endpoint):
SUCCESS {"cmdId":0,"statusCode":0}

CCT White Tuning:
Expert mode was needed for payload colortemp and transtime:
image
image

Expects values between 0…65535, where 65535 is the warmest tone
Works for both endpoints where 1…CCT white part and 2…RGB part of the lamp

Logs (independent from endpoint):
SUCCESS {"cmdId":10,"statusCode":0}

Color Tuning on RGB part
Again, expert mode was required for colorx, colory and transtime:
image
image

Works with endpoint 2 (RGB part of the lamp)
Expects values between 0…65535, for x=0…1 and y=0…1

Log:
SUCCESS {"cmdId":7,"statusCode":0}

Final remark:
I would say that the transtime is not effective. It expects values between 0 and 65535, but whatever I enter, the timing of the transitions seem to be the same – roundabout a second

@asgothian
Copy link
Collaborator

what happens if you do not use the expert mode to include the trans time, just add the level / color / colortemp ? Does it refuse or will it at least set the correct value ?

I will need to build additional logging to see if the iobroker states send the data to the correct EP. That could explain the issue. I can't promise if I manage that before Christmas, though.

A.

@grandslam18
Copy link
Author

I didn't add the reason why I used expert mode in my previous posting:

Maybe I am not using the dev-mode in the right way, please correct me if I'm wrong:

  1. I choose the device from the list (given it's IEEE address)
  2. I choose the endpoint (1 or 2)
  3. I choose cluster ID (found everything in the docs related to the dev-mode) -> check the screenshots in previous posting
  4. I choose command type "Functional" given the commands I have to use
  5. I choose the commands themselves
  6. Now, I'd have to choose an Attribute ID which is exactly named like the parameter I have to pass on (???)
  7. Value required checked + value written in the field

The problem I'm facing is in step 6, since I can't find the right named attributes from the dropdown. Even if I use the closest possible thing I find in the dropdown of attribute ID, it doesn't work. Example:

image

There is no "level" attribute available in the dropdown, choosing "onLevel" instead.

Log:
undefined "ZCL command 0x54ef441000b107d2/1 genLevelCtrl.moveToLevel({\"onLevel\":100}, {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"reservedBits\":0,\"writeUndiv\":false}) failed (Parameter 'level' is missing)"

Please let me know which attribute IDs I should use / where I could find the right ones. Thanks!

fyi: I am allowed to send the lamp back to the vendor until Jan 31st, 2025. I cannot and do not want to put any pressure on you. If you either think that it's not even feasible to make the lamp compatible or that you don't have the time to support it, I'm 100% fine if you tell me any time before end of January. Then I'd return the lamp and find something compatible (found a nice looking Philips Hue Lamp that is only slightly more expensive and seems supported an all websites from blackadder to zigbee2mqtt).

Thank you!

@asgothian
Copy link
Collaborator

I do hope that I will be able to get to the bottom of this before Jan 31st. I already have a suspicion on what is going wrong.
My suspicion is that the command is not sent to the correct endpoint, if to any endpoint at all. Your ability to send the data to the correct endpoint and achieve the correct result hints at this being the main cause.

As far as the expert mode with the moveToLevel is concerned - this can be a remnant of the old system. There was a refactor in the underlying library at some point where some keywords were changed, which explains why the attribute-ID is not mapped out correctly. So you are using the expert mode correctly.

I will try to fix a log output first to confirm this, and then dig through where the endpoint might have gotten lost. Unfortunately, I cannot run the tests myself as I do not have any light with 2 endpoints.

A.

@grandslam18
Copy link
Author

Thanks a lot, all clear. If I can assist the debugging, please let me know, we could sync over discord or whatever is convenient for you!

Merry Christmas!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants