-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
LS Deutschland GmbH Home Base (A319463) not working #2183
Comments
May require a newer version of the zigbee-herdsman-converters. It should come into the zigbee adapter soon. |
Please test with the current GitHub version |
Hi @asgothian I updated to the latest version, but the error message "Device 0xb... "A319463" not described in statesMapping." is still there. |
The message means nothing anymore. How do the objects look ? |
Please show the info tile of the device. Of special interest: the Manufaktur.ID and Manufacturer entries. A. |
This is strange. Which version exactly are you running ? Please post the log entries from starting the zigbee Adapter. it lists in Detail which version is running. A. |
Hi ... It should be the latest version from GIT: "starting. Version 1.10.9 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.16.0, js-controller: 6.0.11" |
Something is very fishy there - the device is supported for a while now and should provide the standard light states. Did the pairing go through successful or did you get a message about the device being not successfully paired ? A |
Hi ... so as far as I noticed it the pairing went through without any problem. The only error message I got is "Device 0xb... "A319463" not described in statesMapping." . I took a look at the "devices.js" and found out that there is no model with the corresponding ID (A319463). I played around with it a little bit and added a device by adding a device with the state configuration "lightStatesWithColortemp". I ended up with the device and all states corresponding to "lightStatesWithColortemp" created, but the device is still not working. Are there more steps to go to add a new device? |
When the pairing is successful, there should be no need to have the device present in the devices.js of the zigbee Adapter. This is a legacy option which only still exists as it would possibly break user scripts to remove it. The Adapter should generate the states based on what is called "exposes" from the zigbee-herdsman-converters library - hence the comment that the message no longer carries any real meaning.
Main issue why it won't work with you adding code to devices.js may be that they are using the wrong endpoint. Unfortunately, the screenshot from the info Display does not show the current endpoint for the relevant clusters. A. |
Same issue here with latest Github version 1.10.13 - Pairing without Problems - LS.js in /node_modules/zigbee-herdsman-converters/devices exists. Device 0xb43a31fffe776fb0 "A319463" not present in statesMapping - relying on exposes for device definition. No state for controlling the light is created there, basic information of the device (e.g. link quality) is created. |
Same issue with v1.10.14. I also tried to exclude A319463 to force usage of exposes but still got no objects. here is the response from the Gateway:
are there any hints? It's getting very frustrating :( |
Hi,
I tried yesterday to connect to my Home base (A319463) with the latest GIT release of this adapter (1.10.5). The connection to the device was established, but no states are mapped to the device.
Is this device already supported?
The text was updated successfully, but these errors were encountered: