Missing channels for Bitron Home 902010/25 #625
Comments
|
We need to work out the attributes that the device requires. I can guess what they might be, but I noted that somewhere in the forum post there's mention about "non standard". In the |
|
I found a file zigbee-network--zigbee_coordinator_telegesis_0500201F.xml located in /var/lib/openhab2/zigbee. If yes, the file has about 21.000 lines. |
|
Hmmm - I'm surprised it's that long. Is that a single "network.xml" file, or is it named based on the single device? The older bindings used a single file for all devices, but this changed quite a while ago so that files were shorter and writing was quicker on slow computers. I need all the information for the device in question... |
|
Hhhmmm, maybe this an oder file from a backup that is not any longer used. I found a directory /var/lib/openhab2/zigbee/zigbee_coordinator_telegesis_0500201F Inside this directory I found an XML file named 00124B00073009AA.xml (that is the id of the recently added device). This file has 14.500 lines - so I'm not able to post the content ... too many chars :-( |
|
Here the first around 1000 lines:
After this, I found >10.000 lines with "... Tier 3 ..." to "... Tier 15 ...". And at the end, there are the following lines:
|
|
Can you put one of these files somewhere like dropbox and then paste the link here? I think that at least one of these is using the SmartEnergy clusters which I wasn't really expecting. It's not a problem, but just shows that we need to properly understand what to implement. |
|
Here is the link: https://www.dropbox.com/s/ckctw2k2mgzn170/00124B00073009AA.xml?dl=0 |
|
So this confirms that it is using the SEP clusters, which is fine, but these clusters have a huge number of attributes and most devices only support a small number... Are you able to upgrade to the latest 2.5 binding? If so, we can try a new console command I added yesterday. This was created recently in the ZSS library for pretty much this exact reason - to find out EXACTLY what a device supports... |
|
Do you have a download link for the latest version? |
|
Are you using Linux? If so, the best thing is to use the script from @5iver on the forum as it will sort out the dependencies.
https://community.openhab.org/t/zigbee-and-zwave-manual-install-script/50270
If you don’t use a ’nix device, then let me know and I’ll try and provide links - it’s not just a single JAR though so it’s not quite as simple as some bindings as we need to manage the dependencies.
|
|
I‘m using a Raspberry Pi 4 ... so I will try the script ... |
|
Before I upgrade : is the latest version of the binding compatible with OpenHAB 2.5.6 ? |
|
Hmmm - that is a good question. I have a funny feeling that there were some breaking changes introduced in the core at some point that then needed changes in bindings, so the answer might be no. I’m just not sure unfortunately.
Let’s do something different…
Please try the following command
zigbee attsupported ENDPOINT 0x702
Where endpoint is the node/endpoint format - so 1234/1 or ox1234/1. You should be able to use the zigbee endpoints command to list the endpoints.
That should dump a list of attributes supported by that cluster and hopefully will tell us what is needed.
|
|
That is the output: Maybe this helps: |
|
Unfortunately the list above is just the standard list of all the attributes, so this I know. I was hoping that the device would report what attributes is actually supports - it won't be all of them, and is probably only a very small number. I guess it doesn't support this then. Ok, let's try something else.....
Change ATTR to be one of the attributes you want to test from the list above. Eg -: would be Please provide the attribute numbers that return something, and also what they return - probably you only need to test a couple to get what you want. |
|
HHmmmm, I tried a lot ... but without success: |
|
I found this pdf : http://media.bitronvideo.eu/bitronhome/Bitron_Home_ZigBee_Clusters_and_Attributes_-_en_0814.pdf Page 5 refers to the smartmeter. |
|
Try 0 and 1024 - it seems these are the only ones available. |
|
:-( `openhab> smarthome:zigbee read 52910/1 0x0702 0 openhab> smarthome:zigbee read 52910/1 0x0702 1024 |
|
It's strange that these are returning a timeout? Are you able to communicate at all with the device? Eg. use the on/off commands (on 52910/1 and off 52910/1). Another thing would be to get the debug log - I don't think it will help too much, but... Also, please use three ticks on a separate line above and below when posting logs etc - not one. I've edited most of your earlier posts, but you can see in the last post above what is wrong. It just makes it easier to read :) |
|
Yes, communication seems to work: What do you mean with "use the on/off commands"? Switching between on and off using PaperUI works perfect. No issues. Regarding formatting : I tried it several times with one or two ticks ... but it didn`t work. No I know why :-) |
|
Maybe this helps: or this |
|
These are really just different views of the same information I already have. I don't really know why the device isn't responding to this... Hmmm - I think I know what might be up. Please get a debug log - I think there will be an error about unsupported local cluster...
Exactly as I wrote - there are simple console commands that send on and off commands. If it works in P-UI, then fine. I think the issue will be what I've written above. If you can confirm that, I will look to implement these two channels... At some point though, we will come back to your earlier question -:
Clearly you will need to upgrade to get this functionality... |
|
What Debug-Log do you need / mean? Just set the log level of the binding with this command: And afterwards run this command : ? |
|
Here is the output: |
|
This is what I performed: |
|
That's perfect - thanks. That confirmed what I thought was the problem... I will take a look at adding these two channels. |
|
Good to read that you found the problem. |
Outline
I was able to add a smartplug from Bitron (Bitron Home 902010/25) to OpenHAB, but I only see the Switch-Channel and not to ActivePower, RmsCurrent or RmsVoltage channels.
I now that the device is able to deliver these values, since I used the devices with another smarthome plattform (from german Telekom - Qivicon) and these values were available.
Configuration
Logs
I'm not sure if this part of the logfile is correct or enough ... I have a lot more available.
The text was updated successfully, but these errors were encountered: