-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
convertSet throwing an unspecified error when trying to set specific values #8525
Comments
The initial problem has been solved - to a degree. It was a case of Garbage In , Garbage Out. I was able to find the error in the end - the key was wrong. Still, the issue that the catch around the call does not provide an error object is making this difficult to impossible to debug. Any suggestion how to fix this ? A. |
Do you have a clue on what line it goes wrong? |
In my code, yes: This call throws an error, but the error itself is empty. I also have (rare) cases where this line just does not return at all, any code afterwards is not being executed. The inability to pinpoint the error is the main issue there. A. |
Interesting, I cannot explain why this happens, what converter is it calling? |
It was this device:
the converter(s) generated by this code, and responsible for "brightness". Unfortunately I do not have the device myself so I cannot link the object directly
|
Hello,
I have an issue within the iobroker.zigbee Adapter where the converter for the device CL-L02D does not accept values for brightness, color and colortemp. It also does not seem to react correctly to brightness_move, colortemp_move, hue_move and saturation move events. I have been trying to track down the cause of the issue, but hit a wall when the code
with the following code going into the catch with no error message:
code:
Data going in (example with brightness_rgb):
Note that I have cut out the values for device, mapped and logger from the provided data. I have verified that device and mapped refer to the exact device. Also, the values for the device, mapped and logger are identical to the attempts when setting the state (on/off), which does work for both endpoints (white, rgb)
I have verified that the correct converter is being addressed.
What throws me for a loop most is the fact that an error is raised as the messages inside the catch path are provided, but the variable 'error' seems to contain an empty object.
I would appreciate any hint as to how to get closer to the root cause of the problem.
This was tested with the current (yesterday) zigbee_herdsman_converters version 21.9.2 as well as 20.58.0
A.
The text was updated successfully, but these errors were encountered: