The integration is not working when NordicPanel is connected

[atlaide]

The problem

I have Flexit Nordic S3 and noticed when I connected the device to NordicPanel the integration through home assistant stopped working. I still see all the sensors and the data is accurate, but I am not able to make any changes like change the mode (it changes back to the one that is set through NordicPanel). Is there a solution for this or the integration is not compatible with NordicPanel? Many thanks

What version of Home Assistant Core has the issue?

core-2024.8.2

What was the last working version of Home Assistant Core?

2024.10.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Flexit bacnet

Link to integration documentation on our website

https://www.home-assistant.io/integrations/flexit_bacnet/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @lellky, @piotrbulinski, mind taking a look at this issue as it has been labeled with an integration (flexit_bacnet) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of flexit_bacnet can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign flexit_bacnet Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

flexit_bacnet documentation flexit_bacnet source _{^{(message by IssueLinks)}}

[lellky]

Thank you for reporting this!

I have the CI70 panel and the Nordic S4 and that works with the Home Assistant integration.

The Nordic panel was not tested by us during the development of the integration. Do you have any logs to share with us?

/lellky

[atlaide]

I hope this helps.

Logger: aiohttp.server Source: /usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py:448 First occurred: October 15, 2024 at 23:24:50 (659 occurrences) Last logged: 09:48:26

Error handling request Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 377, in data_received messages, upgraded, tail = self._request_parser.feed_data(data) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "aiohttp/_http_parser.pyx", line 563, in aiohttp._http_parser.HttpParser.feed_data aiohttp.http_exceptions.BadStatusLine: 400, message: Invalid method encountered:

b'\x10L'
  ^

[MindDesign]

I am running home assistant in docker, and I experience the same error. This is from my log when trying to change the Flexit Nordic Away extract fan setpoint:

Edit: didn't add the complete log:

  File "/usr/src/homeassistant/homeassistant/components/number/__init__.py", line 122, in async_set_value
    await entity.async_set_native_value(native_value)
  File "/usr/src/homeassistant/homeassistant/components/flexit_bacnet/number.py", line 203, in async_set_native_value
    raise HomeAssistantError from exc
homeassistant.exceptions.HomeAssistantError
2024-10-26 11:05:49.300 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140512265206752] Unexpected exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/flexit_bacnet/bacnet.py", line 518, in write
    return _parse_write_property_response(response)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/flexit_bacnet/bacnet.py", line 418, in _parse_write_property_response
    raise DecodingError(f"unsupported response type: {apdu_type}")
flexit_bacnet.bacnet.DecodingError: unsupported response type: 5

The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2761, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2804, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 996, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1068, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/number/__init__.py", line 122, in async_set_value
    await entity.async_set_native_value(native_value)
  File "/usr/src/homeassistant/homeassistant/components/flexit_bacnet/number.py", line 203, in async_set_native_value
    raise HomeAssistantError from exc
homeassistant.exceptions.HomeAssistantError

The Flexit Nordic Electric heater works fine.

[atlaide]

Just wanted to add that electric heater works fine for me as well. The only issue seems to be with preset modes.

[piotrbulinski]

Response type 5 in BACnet is an error response from the unit. To be able to debug the issue, I would need the whole BACnet message dump. It should be part of the log output, e.g.:

flexit_bacnet.bacnet.DecodingError: response decoding failed: unsupported response type: 7
810a00090100710109

[MindDesign]

Thank you for responding, I found this line:

flexit_bacnet.bacnet.DecodingError: response decoding failed: unsupported response type: 5
810a000d010050010f91029125

Hope it helps!

[piotrbulinski]

Thank you for responding, I found this line:

flexit_bacnet.bacnet.DecodingError: response decoding failed: unsupported response type: 5
810a000d010050010f91029125

Hope it helps!

@MindDesign in your case, it would be property value-out-of-range. What value were you trying to set for the extract fan setpoint and what's your Flexit model?

[MindDesign]

Oh, I see. I was trying to set the Flexit Nordic Away extract fan setpoint to anything, but must have tried anything above 60%, and see now that it works as long as it is 60% or below. I have the S3. Had I a few seconds more on the Flexit GO app, I would have noticed that the away preset does not allow for the fan to go over 60%.

Sorry for polluting this thread.

[atlaide]

In my case disabling "Fan Monitoring" option in the FlexitGo app fixed the issue.

[atlaide]

Unfortunately, disabling 'Fan Monitoring' doesn't resolve the issue. Toggling it temporarily normalizes the process and allows preset modes to be changed through Home Assistant, but the problem soon reappears.

I've tried everything - any suggestions on where to look next?

[lellky]

Thank you for responding, I found this line:

flexit_bacnet.bacnet.DecodingError: response decoding failed: unsupported response type: 5
810a000d010050010f91029125

Hope it helps!

@MindDesign in your case, it would be property value-out-of-range. What value were you trying to set for the extract fan setpoint and what's your Flexit model?

@piotrbulinski I reported that here: https://github.com/home-assistant/core/issues/133378 It seems that the setpoints are dependant on each other. I have fixed it in a PR here https://github.com/home-assistant/core/pull/133388 please have a look, and if possible test the code.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.