# Cant connect Eurotronic Spirit Zigbee to OH using BitronVideo Coordinator

**URL:** <https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244>\
**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:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![ibimms](https://community.openhab.org/letter_avatar_proxy/v4/letter/i/838e76/32.png) [@ibimms](https://community.openhab.org/u/ibimms)\
**Post date:** [April 11, 2020, 7:58pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/82 "2020-04-11T19:58:54Z")

</div>

Reinitialisation did not change anything.  
Still unidirectional.

[openhab.log](https://community.openhab.org/uploads/short-url/lZZrTXEGyHZSMATlQ3X3zEigjwf.log) (759.3 KB)

---

<div class="post-metadata">

**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 11, 2020, 8:01pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/83 "2020-04-11T20:01:58Z")

</div>

The configuration looks fine to me. The binding and reporting are set by the binding, and acknowledged by the device.

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/9/e/9e82bded2c34ba4fd4c28236bc42d9d0ed3959da.png)

---

<div class="post-metadata">

**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 11, 2020, 8:05pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/84 "2020-04-11T20:05:57Z")

</div>

If I change the setpoint in OH this takes effect at the device. But not in the other direction.

---

<div class="post-metadata">

**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 11, 2020, 8:08pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/85 "2020-04-11T20:08:27Z")

</div>

From what I can tell from the log, the binding is correctly setting the reporting - or at least some of the setpoints based on this log and the temperature. The device has acknowledged that, so it should work

---

<div class="post-metadata">

**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 11, 2020, 8:11pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/86 "2020-04-11T20:11:01Z")

</div>

Is there something more I can do to debug this?

---

<div class="post-metadata">

**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 11, 2020, 8:12pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/87 "2020-04-11T20:12:52Z")

</div>

Not that I can think of - if there’s absolutely nothing being received in the debug logs when configured as per the binding documentation, then I’m out of ideas.

---

<div class="post-metadata">

**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 11, 2020, 8:16pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/88 "2020-04-11T20:16:25Z")

</div>

😟  
I will setup a vanilla system tomorrow and see if that helps.

---

<div class="post-metadata">

**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 11, 2020, 8:18pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/89 "2020-04-11T20:18:01Z")

</div>

I don’t expect it will make much difference from the OH side - from what you’ve shown it looks like everything is working fine on the binding side.

---

<div class="post-metadata">

**Author:** ![ibimms](https://community.openhab.org/letter_avatar_proxy/v4/letter/i/838e76/32.png) [@ibimms](https://community.openhab.org/u/ibimms)\
**Post date:** [April 11, 2020, 8:18pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/90 "2020-04-11T20:18:59Z")

</div>

@chris does your device have the same firmware like ours (0x0122C380)?

---

<div class="post-metadata">

**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 11, 2020, 8:20pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/91 "2020-04-11T20:20:35Z")

</div>

I’m not sure - I don’t have it set up as I don’t use it personally.

This is standard ZigBee stuff though - binding and reporting is used everywhere. We use this with thousands of thermostats with one of our customers.

---

<div class="post-metadata">

**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 11, 2020, 8:23pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/92 "2020-04-11T20:23:14Z")

</div>

I have 8 identical devices - all bought in second half of 2019 and all behave the same way.

---

<div class="post-metadata">

**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 11, 2020, 8:24pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/93 "2020-04-11T20:24:45Z")

</div>

Sorry - I’m not sure why. This was certainly tested and working with this device early this year as you can also see from the forum posts.

---

<div class="post-metadata">

**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 11, 2020, 8:28pm UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/94 "2020-04-11T20:28:32Z")

</div>

It seems I have to try zigbee2mqtt to the the devices working.

OK - thank you for your support anyway.

---

<div class="post-metadata">

**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, 8:30am UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/95 "2020-04-12T08:30:15Z")

</div>

I had another look at the log, and at least for one of the setpoints, and therefore I suspect all of them, the device doesn’t support sending reports from the device to the binding -:

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/a/2/a21eefa715a292522227313eaf6b053ac38b4f02.png)

You see here that when setting attribute 17 for reporting, it is reporting that the attribute is unreportable so based on this the device cannot be configured to send these reports to the binding.

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/d/4/d4a34ab2b0e9a2eaa6ba3ad3ec617105cfc3cb44.png)

---

<div class="post-metadata">

**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, 9:37am UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/96 "2020-04-12T09:37:09Z")

</div>

The latest documentation of the device does not contain an attribute with ID 17.  
In fact there is a gap for this ID and there are no cooling configurations at all.  
[https://eurotronic.org/wp-content/uploads/2019/11/Spirit\_ZigBee\_BAL\_web\_DE\_Okt.-2019.pdf](https://eurotronic.org/wp-content/uploads/2019/11/Spirit_ZigBee_BAL_web_DE_Okt.-2019.pdf)  
Or have I missed something?

---

<div class="post-metadata">

**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, 9:49am UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/97 "2020-04-12T09:49:28Z")

</div>

> [@Ratimer](#):
>
> The latest documentation of the device does not contain an attribute with ID 17.

I guess that’s why it’s unsupported 🙂

In theory the binding should try to detect this, but it depends on what the device returns as to how successful this is. The binding tries to get a list of supported attributes, but some devices don’t support this function.

I do see though that unoccupied heating is correctly set and the device returns SUCCESS in this log so at least that should report

---

<div class="post-metadata">

**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:03am UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/98 "2020-04-12T10:03:13Z")

</div>

@chris, @ibimms  
I guess this is the wrong chat. I propose to shift further discussions to [Eurotronic Spirit Zigbee Thermostat again](https://community.openhab.org/t/eurotronic-spirit-zigbee-thermostat-again/94671#)

---

<div class="post-metadata">

**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:14am UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/99 "2020-04-12T10:14:15Z")

</div>

> [@Ratimer](#):
>
> I guess this is the wrong chat.

Why is it wrong? All of the discussion has been here - swapping around makes this a mess to try and work out. I suggest we keep this in one place.

---

<div class="post-metadata">

**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:23am UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/100 "2020-04-12T10:23:08Z")

</div>

I’ve had a look at the debug logs when I configured the setpoint at the physical device.  
[touch device.log](https://community.openhab.org/uploads/short-url/2bBBgovfnLUi6rDD1uII1n1iq7a.log) (1.7 KB)

> 2020-04-12 11:59:08.305 [DEBUG] [transaction.ZigBeeTransactionManager] - notifyTransactionCommand: ReportAttributesCommand [Thermostat: 605B/1 → 0000/1, cluster=0201, TID=C3, reports=[AttributeReport [attributeDataType=SIGNED\_16\_BIT\_INTEGER, attributeIdentifier=16387, **attributeValue=1650**]]]

attributeIdentifier=16387 meets the documentation and attributeValue=1650 is my configured value of 16.5°C

It seems the device reports the change to OH, but nothing happens.

---

<div class="post-metadata">

**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:25am UTC](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244/101 "2020-04-12T10:25:42Z")

</div>

> [@Ratimer](#):
>
> It seems the device reports the change to OH, but nothing happens.

Ok, that makes more sense. I did ask earlier if you were sure that there was nothing being received -:

> [@chris](#):
>
> if there’s absolutely nothing being received in the debug logs when configured as per the binding documentation, then I’m out of ideas.

The problem here is that the device is reporting using a non-standard attribute rather than the ones that the binding has configured reporting for (ie the standard ZigBee attributes).

[Previous page](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244.md?page=4)

[Next page](https://community.openhab.org/t/cant-connect-eurotronic-spirit-zigbee-to-oh-using-bitronvideo-coordinator/88244.md?page=6)
