# Cant connect Eurotronic Spirit Zigbee to OH using BitronVideo Coordinator **URL:** \ **Category:** Bindings\ **Tags:** zigbee\ **Created:** [December 22, 2019, 1:52pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244 "2019-12-22T13:52:02Z")\ **Posts on this page:** 18\ **Page:** 6
**Author:** ![Ratimer](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Ratimer](https://community.openhab.org/u/Ratimer)\ **Post date:** [April 12, 2020, 10:33am UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/102 "2020-04-12T10:33:21Z")
That’s bad. This means the device is not really compatible with ZigBee - right? Is there a chance to implement a connector anyway? I am looking for some Spirit device specific source code or configuration at **[org.openhab.binding.zigbee](https://github.com/openhab/org.openhab.binding.zigbee)** , but I can’t find something. Is this the wrong location or is the ZigBee binding so generic that there is no device specific part needed? ---
**Author:** ![chris](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/958977/32.png) [@chris](https://community.openhab.org/u/chris)\ **Post date:** [April 12, 2020, 10:46am UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/103 "2020-04-12T10:46:32Z")
> [@Ratimer](#): > > This means the device is not really compatible with ZigBee Well, it’s still ZigBee I guess - devices are allowed to implement manufacturer specific features, but they are also required by ZigBee to implement certain standard features. One such feature is the setpoint - this is marked as mandatory in the standard. Now - they are implementing it - we can write to that attribute and it sets the setpoint, but when reporting changes, they use their non-standard setpoint attribute. This can be seen below. Attribute 12 (Heating setpoint) is supported - but it’s not reporting. The only attributes that are reporting are the non standard ones (and the standard current temperature). ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/6/b/6bfa73fc7b64dddedbaa416029fd14472c476aef.png) Ultimately, this would need a static definition to solve this. This should be mostly possible in the binding, but it’s not something I’ve looked at for a long time as most of my customers are using standard devices - unfortunately OH users tend to be the ones that buy the non-standard devices… The issue that is currently outstanding to resolve this is -: > > > There is ongoing work for supporting manufacturer-specific clusters, commands an…d attributes in https://github.com/zsmartsystems/com.zsmartsystems.zigbee/pull/498. One example where support for manufacturer-specific clusters is needed in this binding is the Centralite 3310 temperature/humidity sensor (see #359), as it uses a manufacturer-specific cluster for the humidity measurements. > > This issue is for discussing how to integrate the support for manufacturer-specific clusters into this binding. ---
**Author:** ![Ratimer](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Ratimer](https://community.openhab.org/u/Ratimer)\ **Post date:** [April 12, 2020, 12:01pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/104 "2020-04-12T12:01:26Z")
OK - I understand what’s the problem to receive manual changes to of the setpoint. Let’s hope Henning is still working on that. But this is still the framework, so until it is working for my devices this might take a while. So I have to live with it for now. Coming back to my initial question > [@Cant connect Eurotronic Spirit Zigbee to OH using BitronVideo Coordinator](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/58): > > Hi @chris, changing the system mode also seems not possible - At least I could not change the value neither via PaperUI nor in Basic UI. Changes to the …1\_thermostatsystemmode channel seems to be ignored. Is there a way I can implement #554 ? Could you please guide me? What’s about the **System Mode** that can’t be changed? It’s given as attribute with ID 0x001C, at the ZigBee specification as well as Spirits manual. Why is System Mode read only in Paper UI? And why doesn’t it change when I modify the value of an item with the same channel? ---
**Author:** ![chris](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/958977/32.png) [@chris](https://community.openhab.org/u/chris)\ **Post date:** [April 12, 2020, 12:03pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/105 "2020-04-12T12:03:33Z")
> [@Ratimer](#): > > What’s about the **System Mode** that can’t be changed? It’s given as attribute with ID 0x001C, at the ZigBee specification as well as Spirits manual. As requested earlier, please can you provide a log showing you changing this. From the earlier log you provided, it is working, so I need to see it changing. ---
**Author:** ![Ratimer](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Ratimer](https://community.openhab.org/u/Ratimer)\ **Post date:** [April 12, 2020, 12:12pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/106 "2020-04-12T12:12:43Z")
Here the logs. I changed from **off** (code 0) to mode **sleep** (code 9). [system mode - events.log](https://community.openhab.org/uploads/short-url/whoLl8MajHeMkBjZZVn658FIvNY.log) (567 Bytes) [system mode - openhab.log](https://community.openhab.org/uploads/short-url/tTYAChApM0GAtbn8FDUTC6y8WkC.log) (5.6 KB) ---
**Author:** ![Ratimer](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Ratimer](https://community.openhab.org/u/Ratimer)\ **Post date:** [April 12, 2020, 12:15pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/107 "2020-04-12T12:15:24Z")
There seems to be no way to set the system mode directly at the physical device. ---
**Author:** ![chris](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/958977/32.png) [@chris](https://community.openhab.org/u/chris)\ **Post date:** [April 12, 2020, 12:26pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/108 "2020-04-12T12:26:35Z")
Again, this appears to be fine -: ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/0/2/02adb20da2222f7971131db09c4397d209d24b8d.png) The binding is correctly sending attribute 28 to value 9 - as per the incoming command. The device has acknowledged that with the state SUCCESS. What the binding does is to read out an attribute called “sequence of operation” which has the following definition. ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/7/6/7692c46be3c7ef6a3390636f8e1391921dfea48c.png) Depending on the response, the binding will make only certain options available to the user, although this is not checked in the binding when the user sends a command, so you can set any mode you like between 0 and 9. Modes are defined as follows -: ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/8/1/81203930249fc93e280046597c78b2198e12f3fb.png) Again, the binding should provide these as options in theory and it should only provide the ones allowed as per the sequence attribute discussed above. From the logs you’ve provided, you’ve set 0 and 9 and these have both correctly been sent to the device, and the device has responded with SUCCESS. I’d suggest trying other values - maybe it only implements one or two of them. ---
**Author:** ![Ratimer](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Ratimer](https://community.openhab.org/u/Ratimer)\ **Post date:** [April 12, 2020, 12:48pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/109 "2020-04-12T12:48:18Z")
Now I’ve tried all modes from 0 to 9 and waited for some seconds in between. None changed the value in PaperUI. I can imagine that the thermostat does not support all modes. But al least OFF (0) should be there. Further one to switch between occupied and unoccupied heating, I guess this is Sleep - right? [all system modes - openhab.log](https://community.openhab.org/uploads/short-url/Puqb3lPELb7uhjRR15pIG2Cdwu.log) (50.2 KB) ---
**Author:** ![Ratimer](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Ratimer](https://community.openhab.org/u/Ratimer)\ **Post date:** [April 12, 2020, 12:50pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/110 "2020-04-12T12:50:45Z")
Looking at the logs, the response always seems to use attributeidentifier=0. Is this correct? ---
**Author:** ![chris](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/958977/32.png) [@chris](https://community.openhab.org/u/chris)\ **Post date:** [April 12, 2020, 12:52pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/111 "2020-04-12T12:52:00Z")
Yes (or No) - I also just noticed this. This is incorrect. The device should respond with the same attribute ID as the write command. ---
**Author:** ![chris](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/958977/32.png) [@chris](https://community.openhab.org/u/chris)\ **Post date:** [April 12, 2020, 12:55pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/112 "2020-04-12T12:55:19Z")
Can you please enable logging with -: ```auto log:set debug com.zsmartsystems.zigbee.dongle.ember.internal.ash ``` And send a mode command again. ---
**Author:** ![Ratimer](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Ratimer](https://community.openhab.org/u/Ratimer)\ **Post date:** [April 12, 2020, 1:03pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/113 "2020-04-12T13:03:39Z")
Here we are. [system mode - verbose.log](https://community.openhab.org/uploads/short-url/kYNCoAsOmg13mzeyhMJjXSirdkG.log) (17.8 KB) ---
**Author:** ![chris](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/958977/32.png) [@chris](https://community.openhab.org/u/chris)\ **Post date:** [April 12, 2020, 1:08pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/114 "2020-04-12T13:08:46Z")
Thanks. I think this is ok. The device is actually sending the short version of the report - so it doesn’t include the attribute IDs in the list. This is (IFRC) allowed in the standard if all requests return SUCCESS, but the ZSS ZigBee framework is just logging this incorrectly. So, we’re back to the position where the binding correctly sends the data, and the device responds with SUCCESS, but nothing changes. ---
**Author:** ![Ratimer](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Ratimer](https://community.openhab.org/u/Ratimer)\ **Post date:** [April 12, 2020, 1:18pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/115 "2020-04-12T13:18:38Z")
If OH is sending the correct command to the device but this does not behave accordingly, this seems to be a problem with the hardware, we can’t solve by software. I think I need to get in touch with Eurotronic to get it solved. Or do you see any other option? ---
**Author:** ![chris](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/958977/32.png) [@chris](https://community.openhab.org/u/chris)\ **Post date:** [April 12, 2020, 1:23pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/116 "2020-04-12T13:23:27Z")
I’m pretty confident that the binding will be sending the right thing - the logs show what is being sent to the NCP and it looks ok. We also support this for a number of large companies, and it was recently ZigBee certified for a Smart Energy product. So, from what I’ve seen, this looks fine. I also just checked the data type is correct in the device manual, and it seems to agree with the ZigBee definition which is what the ZSS library uses. ---
**Author:** ![Ratimer](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Ratimer](https://community.openhab.org/u/Ratimer)\ **Post date:** [April 12, 2020, 1:25pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/117 "2020-04-12T13:25:50Z")
There is one thing that makes me wonder: If OH behaves correctly, why doesn’t the value in Paper UI change? Is it because the actual value needs to be send by the device after it has changed this? ---
**Author:** ![chris](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/958977/32.png) [@chris](https://community.openhab.org/u/chris)\ **Post date:** [April 12, 2020, 1:30pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/118 "2020-04-12T13:30:02Z")
> [@Ratimer](#): > > If OH behaves correctly, why doesn’t the value in Paper UI change? I don’t know - but it’s not really relevant. Probably it’s related to how the item is configured, but what matters is what gets sent to the device and we can clearly see that in the logs. I solely focus on the device communication - what the binding receives from the user (be it from the UI, a rule, or the REST interface, or anywhere else) and what gets sent to the device. ---
**Author:** ![Ratimer](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/ecd19e/32.png) [@Ratimer](https://community.openhab.org/u/Ratimer)\ **Post date:** [April 12, 2020, 1:33pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/119 "2020-04-12T13:33:48Z")
OK - thank you for you support, your time and patience. You are doing a great job here! 👍 [Previous page](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244.md?page=5)