Values are not getting updated in HomeAssistant

[CV-Private]

I've been able to successfully install the Bepacom-BACnet-IP-Installation.
It found my GTW-21 BACnet device from the heatpump manufacturer Brötje (BDR Thermea Group). It is a BACnet certified device, to which I can connect with YABE normally.

I'm able to see the Present Values in the HomeAssistant Entities.

However, the values are not getting updated at all. It look like they have been read once, and now they're frozen forever.
This is what I see in HA. It would be expected, though, that the temperature value would change very dynamically over time.

What did I miss to configure?
Any help would be much appreciated!
Best regards, Christian

[Bepacom-Raalte]

Hey Christian,

I think the configuration should be alright. Might be that there's a little bug somewhere.

Could you tell me which add-on and integration versions you're using?
In the add-on, if you look at the web UI, do values change in there?
Do you get any errors in the logs? Either in Home Assistant or in the add-on?

Answers on these questions can help narrow down what's causing these issues.

[CV-Private]

Dear Bepacom, thanks for your swift response!

Here's the HA version information:

• Core 2024.2.5
• Supervisor 2024.02.1
• Operating System 12.0
• Frontend 20240207.1

The values are not getting updated anywhere, neither in the WebUI nor in the visualization. Below is a screenshot that shows the same 47,1°C value that is shown in the flat chart in my first post. The value is unchanged since the last HA restart.

Attached is the Debug log, and I do see Errors related to the Bacnet refresh. Maybe that helps to pinpoint the reason?
Note that I deleted two days of logging to reduce the file size.

CV_home-assistant_bacnet_interface_2024-03-05T08-06-43.071Z.log

An another note: how's the refresh actually done? Is the Bepacom integration using the COV (Change of Value) method, or is it polling the values in regular intervals?
If it would poll in intervals: where can the interval be configured?
I see the same set of error logs every minute. Polling intervals of 1 min might be OK for certain purposes, but in case of more dynamic values, it should be possible to configure a higher update rate if COV wouldn't be possible.

[Bepacom-Raalte]

Hey Christian,

By default, the add-on uses CoV. If you want to disable this and continue by polling, you could do the following:

This will set the polling time to 15 seconds and no CoV subscriptions will be made.
You could set it even faster, but it might congest your network.

Did you encounter any errors in the add-on logs? I think the issue originates from the add-on.
Are you using the dev version of the add-on?

[CV-Private]

Thanks, that's good to know! CoV is certainly my preference.

I'm not using the dev version of the add-on. This is the set of errors that occurs each minute in the log file:

2024-03-05 09:05:51.410 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 256, in _handle_refresh_interval
    await self._async_refresh(log_failures=True, scheduled=True)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 412, in _async_refresh
    self.async_update_listeners()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 183, in async_update_listeners
    update_callback()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 492, in _handle_coordinator_update
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 989, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1110, in _async_write_ha_state
    state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
                                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1047, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 995, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 547, in state
    native_unit_of_measurement = self.native_unit_of_measurement
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/bacnet_interface/sensor.py", line 137, in native_unit_of_measurement
    self.device_class == SensorDeviceClass.TEMPERATURE
    ^^^^^^^^^^^^^^^^^
  File "/config/custom_components/bacnet_interface/sensor.py", line 111, in device_class
    in self.coordinator.data.devices[self.deviceid]
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'devices'
2024-03-05 09:05:51.417 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/config/custom_components/bacnet_interface/coordinator.py", line 65, in listen
    await self.interface.listen(callback=self.async_set_updated_data)
  File "/usr/local/lib/python3.12/site-packages/aioecopanel/aioecopanel.py", line 71, in listen
    message = await self._client.receive()
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/client_ws.py", line 232, in receive
    raise RuntimeError("Concurrent call to receive() is not allowed")
RuntimeError: Concurrent call to receive() is not allowed

[Bepacom-Raalte]

Could you also post the add-on logs? Maybe there's something useful in there.

[CV-Private]

Where do I find those add-on logs?

[Bepacom-Raalte]

On the add-on page, next to the configuration tab, there's a Log tab. In there you should be able to see if there's anything odd happening.

[CV-Private]

Ok, got it! Here's that log as a txt file:

Bepacom-BACnet-Log_2024-03-06.txt

Note that the Device ID 1507482 in this log is the Yabe Room Simulator that I used for some testing.

My real BACnet Device GTW-21 has Device ID 1

[CV-Private]

Below is the error message in HA when I'm trying to write to setpoint parZoneRoomManualSetpoint-3 AV_1688:

The object is writeable, as per the GTW-21 documentation:

This is how the object looks like in Yabe, from where I can change the Present Value:

[Bepacom-Raalte]

Could you try the following for me?

In HACS please redownload the integration and then select the main version. This is the latest version pushed to GitHub.
I hope this should at least solve the NoneType issue.

[CV-Private]

Some progress: after the update and HA restart, I am initially able to write the value. If no errors occur, then the value is getting accepted by the controller, and changes are visible in the HA graph:

However, after several successful write actions, the same NoneType error occurs again, and new values are not getting written before I restart HA.

There's not much to see in the Bepacom log:

2024/03/07 10:26:48 [info] 325#325: *359 client 127.0.0.1 closed keepalive connection
ERROR:    Disconnected...

2024/03/07 10:36:48 [info] 325#325: *368 client 127.0.0.1 closed keepalive connection
2024/03/07 10:37:20 [info] 325#325: *370 client 127.0.0.1 closed keepalive connection
2024/03/07 10:37:52 [info] 325#325: *372 client 127.0.0.1 closed keepalive connection
2024/03/07 10:38:38 [info] 325#325: *374 client 127.0.0.1 closed keepalive connection
ERROR:    Disconnected...

There are some errors in the HA log, though:

Bepacom-BACnet-Log_2024-03-07.txt

[Bepacom-Raalte]

So it seems the integration is at fault. For some reason the data gets lost.
After a restart of Home Assistant it works again for a little bit and then stops?
Is there a consistent way to get it to crash like this

Could you reinstall through HACS again? I pushed some changes again for the main.

[CV-Private]

In the meantime, I made the following steps:

• uninstalling the entire Bepacom repository and all related devices and entities
• HA reboot
• reloading and reinstalling the latest Bepacom repository
• HA reboot
• wait until all entities had been discovered
• deactivated all of the 1279 BACnet entities except one: GTW-21-BACNET-783351856 parZoneRoomManualSetpoint-3, which is AV_1688
• HA reboot
• changing the parZoneRoomManualSetpoint-3 temperature value on my HA dashboard by typing and by using the up/down buttons
• watching if my room controller accepts the values from HA or whether there are any errors

Observations:

1. Values written from HA are changing the setting in my room controller (good).

2. The Present Value in the HA entity is not getting updated when I change the temperature setting on my room controller (not good).

3. Changes that I make in HA with the up/down buttons are being queued and sequentially processed, which makes the process quite slow. For example, when I press the up-button 10 times to adjust by +1°C, then all ten 0.1°C steps are being written, one after another, which takes quite some time. It would be better to only send the latest update to the BACnet and delete previous commands from the queue as long as they're still unprocessed.

4. The latest repository update did NOT yet fix the NoneType error that occurs after a while.
   Unfortunately, I have not been able yet to identify a trigger for the failure.
   So far, it occurred at some point after every reboot, but not at a specific time or after a particular action.
   If the failure occurred, then I could always resolve it by restarting HA. That at least is 100% reproducible.

5. I noticed in the Bepacom log that there are many log entries like below. Could that indicate a problem with the data-base size?

ERROR: Error while subscribing to device,1, analog-value,7505: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,7506: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,7507: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,21001: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,21020: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,21021: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,21022: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,21023: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,21024: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,21025: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,21026: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,21027: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,21028: resources: no-space-to-add-list-element
ERROR: Error while subscribing to device,1, analog-value,21030: resources: no-space-to-add-list-element

[GravySeal]

In the add-on, I made some changes so logging can be exported.
Could you, in the add-on store, press the button "Check for updates"?

After waiting for a couple of seconds, on the add-on page, press Rebuild.

If everything went correctly, in the configuration there should be a new setting available called "Log Export". Please enable this to get logs written to Home Assistant's /share folder as well as make the logs downloadable through the web UI.

This way we're not bound to Home Assistant's logging limit and I can see a little more detailed what's actually happening.
When you run the add-on until the integration fails, please export those logs through the web UI and paste the file here. Hopefully everything will be clear then...

[CV-Private]

I just installed the Developer Version 1.3.4 and turned the Logs On. I also changed the logging level to Debug.
I'm wondering now where to find the /share folder and how to export logs through the webUI. Do you mean this Protocol tab?

Unfortunately, I'm having big problems with the new add-on version. Since I loaded it, I'm not able to connect to the GTW-21 and the Add-On shows a configuration error. This is new and I didn't see that with version 1.3.3:

Here's a log that I got after one of the initial restarts:

Bepacom-BACnet-Log_2024-03-09.txt

I tried to change the configuration without success. After some more restarts, I saw in the log that the Add-On did get some device information from the GTW-21, but the entities were still not working:

Bepacom-BACnet-Log_2024-03-09b.txt

The GTW-21 Entities had a red circle and were not usable in the Dashboard.
After many restarts and attempt to reset/restore the configuration, I deleted the GTW-21 device and all entities from HA and removed and reinstalled the Add-On.

Now it doesn't even recognized the GTW-21. The Who-Is requests from 192.168.66.69 came from a Node-Red server in my network. I turned that off meanwhile.

I'm not sure what else I could do, as I can't establish the connection from Add-On v1.3.4 to the GTW-21.