Lost connection

[PatrikPatrik2]

Did you read the instructions?

• [X] I have read the README.

The problem

Hi,

the integration works, and I get reading from the meeter, the problem is that after a while (max 4h) no more data is recorded - not available. By just reloading the integration it starts to read data again, for a while until it stops and I have to reload again.

Is there some why to correct this, or for instance automatically reload the integration every hour?

Integration version

2.6.0

Home Assistant version

2023.10.3

Python version

3.11

Home Assistant log

2023-10-14 11:31:22.470 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration kamstrup_403 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2023-10-14 17:31:58.356 ERROR (MainThread) [custom_components.kamstrup_403] Error fetching kamstrup_403 data: 

2023-10-15 19:35:51.049 ERROR (MainThread) [custom_components.kamstrup_403] Error fetching kamstrup_403 data: 

2023-10-14 11:31:22.470 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration kamstrup_403 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2023-10-14 17:31:58.356 ERROR (MainThread) [custom_components.kamstrup_403] Error fetching kamstrup_403 data:

Diagnostics

{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2023.10.3",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.11.5",
    "docker": true,
    "arch": "x86_64",
    "timezone": "Europe/Stockholm",
    "os_name": "Linux",
    "os_version": "6.1.56",
    "supervisor": "2023.10.0",
    "host_os": "Home Assistant OS 11.0",
    "docker_version": "24.0.6",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "wyzesense": {
      "version": "0.0.11",
      "requirements": [
        "wyzesense==0.0.4",
        "retry==0.9.2"
      ]
    },
    "frigate": {
      "version": "4.0.0",
      "requirements": [
        "pytz==2022.7"
      ]
    },
    "nodered": {
      "version": "1.1.3",
      "requirements": []
    },
    "samsungtv_tizen": {
      "version": "1.6.1",
      "requirements": [
        "websocket-client>=0.56.0",
        "wakeonlan>=2.0.0",
        "numpy>=1.19.2"
      ]
    },
    "gardena_smart_system": {
      "version": "1.0.0",
      "requirements": [
        "py-smart-gardena==1.3.7"
      ]
    },
    "sonoff": {
      "version": "3.4.0",
      "requirements": [
        "pycryptodome>=3.6.6"
      ]
    },
    "hacs": {
      "version": "1.32.1",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
    "easee": {
      "version": "0.9.54",
      "requirements": [
        "pyeasee==0.7.53"
      ]
    },
    "mass": {
      "version": "2023.6.0b3",
      "requirements": [
        "music-assistant==2.0.0b59"
      ]
    },
    "ha_kia_hyundai": {
      "version": "1.8.4",
      "requirements": [
        "kia-hyundai-api==1.2.14",
        "geopy>=2.0"
      ]
    },
    "kia_uvo": {
      "version": "2.14.1",
      "requirements": [
        "hyundai_kia_connect_api==3.8.6"
      ]
    },
    "kamstrup_403": {
      "version": "2.6.0",
      "requirements": [
        "pyserial==3.5"
      ]
    },
    "tapo": {
      "version": "2.8.2",
      "requirements": [
        "plugp100==3.10.3"
      ]
    },
    "xiaomi_miot_raw": {
      "version": "v1.3.1",
      "requirements": [
        "construct",
        "python-miio>=0.5.3"
      ]
    },
    "nordpool": {
      "version": "0.0.14",
      "requirements": [
        "nordpool>=0.2",
        "backoff"
      ]
    },
    "awox": {
      "version": "0.1.5",
      "requirements": [
        "pexpect>=4.6.0",
        "pycryptodome>=3.6.6",
        "pygatt[GATTTOOL]>=4.0.5"
      ]
    },
    "edgeos": {
      "version": "1.1.2",
      "requirements": [
        "aiohttp"
      ]
    },
    "spotcast": {
      "version": "v3.6.30",
      "requirements": []
    },
    "kodi_media_sensors": {
      "version": "5.1.2",
      "requirements": []
    }
  },
  "integration_manifest": {
    "domain": "kamstrup_403",
    "name": "Kamstrup 403",
    "codeowners": [
      "@golles"
    ],
    "config_flow": true,
    "documentation": "https://github.com/golles/ha-kamstrup_403/blob/main/README.md",
    "iot_class": "local_polling",
    "issue_tracker": "https://github.com/golles/ha-kamstrup_403/issues",
    "requirements": [
      "pyserial==3.5"
    ],
    "version": "2.6.0",
    "is_built_in": false
  },
  "data": {
    "config_entry": {
      "entry_id": "e983eb56b08945d99658bbb1412b635d",
      "version": 1,
      "domain": "kamstrup_403",
      "title": "/dev/serial/by-id/usb-FTDI_RJ-OPUSB-IEC-if00-port0",
      "data": {
        "port": "/dev/serial/by-id/usb-FTDI_RJ-OPUSB-IEC-if00-port0"
      },
      "options": {},
      "pref_disable_new_entities": false,
      "pref_disable_polling": false,
      "source": "user",
      "unique_id": null,
      "disabled_by": null
    },
    "data": {
      "60": {
        "value": 1.337,
        "unit": "MWh"
      },
      "68": {
        "value": 56.6,
        "unit": "m\u00b3"
      },
      "99": {
        "value": 0.0,
        "unit": ""
      },
      "113": {
        "value": 0.0,
        "unit": ""
      },
      "1001": {
        "value": 72763114.0,
        "unit": ""
      },
      "1004": {
        "value": 10567.0,
        "unit": "h"
      }
    },
    "registered_commands": [
      60,
      68,
      99,
      113,
      1001,
      1004
    ]
  }
}

Additional information

No response

[golles]

Can you enable debug logging? and post full logs when the problem occurs. https://github.com/golles/ha-kamstrup_403#collect-logs As it seems to raise errors, but I don't see anything in the logs you provided.

This might also work from the integration page (I've never tried that to be honest).

There is a service you could call in an automation to reload an integration, but it's better to try to solve the problem, so I don't recommend using this. https://www.home-assistant.io/integrations/homeassistant/#service-homeassistantreload_config_entry Set the entity_id to one of the entities of this component.

In my opinion, most issues occur due to not correctly placed IR heads, please double-check check your reader is correctly placed and stable or even stuck.

You could also try to increase the read timeout value, I don't think this is your problem, but it's worth trying.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[PatrikPatrik2]

Sorry for late response. I thought I had something wrong with the USB in my home assistant computer, so I made a dedicated Home Assistance for the Kamstrup on a rasberry pi. Unfortunately the rasberry pi behaved exactly as my normal home assistant - after some minutes it says unknonw on the sensors, but if I restart the integtation it reads the values correctly. The log file is attached below

Logger: homeassistant.components.sensor.recorder Source: components/sensor/recorder.py:288 Integration: Sensor (documentation, issues) First occurred: 4:25:10 PM (1 occurrences) Last logged: 4:25:10 PM

Entity sensor.kamstrup_403_volume from integration kamstrup_403 has state class total_increasing, but its state is not strictly increasing. Triggered by state 123.91 (130.0) with last_updated set to 2023-11-19T15:24:51.636362+00:00. Please create a bug report at https://github.com/golles/ha-kamstrup_403/issues

[golles]

Could you please provide logging as I've asked in my previous comment and not copy it from the frontend?

From the message you provide, it looks like your meter is giving a lower number than it previously has provided, have you manually changed this? As I don't think the meter should ever do this.

[PatrikPatrik2]

I have not checked manually, but that sounds extremly stange. Sorry for a noob question, where do I find the integration specific log?

[golles]

You can find the logs in home-assistant.log file in your config directory.

[PatrikPatrik2]

After I reloaded the integration, it worked for about 1h 20 minutes these are the logs from where it stopped working

2023-11-23 23:19:10.576 DEBUG (MainThread) [custom_components.kamstrup_403] Get values for [60, 68, 99, 113, 1001, 1004]
2023-11-23 23:19:11.312 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 60, value: 4.7090000000000005 MWh
2023-11-23 23:19:11.313 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 68, value: 135.77 m³
2023-11-23 23:19:11.313 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 99, value: 0.0 
2023-11-23 23:19:11.313 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 113, value: 0.0 
2023-11-23 23:19:11.314 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 1001, value: 72763114.0 
2023-11-23 23:19:11.314 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 1004, value: 11481.0 h
2023-11-23 23:19:11.314 DEBUG (MainThread) [custom_components.kamstrup_403] Finished update, 0 out of 6 readings failed
2023-11-23 23:19:11.314 DEBUG (MainThread) [custom_components.kamstrup_403] Finished fetching kamstrup_403 data in 0.739 seconds (success: True)
2023-11-23 23:21:42.273 WARNING (SyncWorker_1) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:22:42.275 WARNING (SyncWorker_7) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:24:42.280 WARNING (SyncWorker_1) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:25:42.282 WARNING (SyncWorker_7) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:26:42.285 WARNING (SyncWorker_6) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:29:11.575 DEBUG (MainThread) [custom_components.kamstrup_403] Start update
2023-11-23 23:29:11.576 DEBUG (MainThread) [custom_components.kamstrup_403] Get values for [60, 68, 99, 113, 1001, 1004]
2023-11-23 23:29:12.297 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 60, value: 4.71 MWh
2023-11-23 23:29:12.298 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 68, value: 135.79 m³
2023-11-23 23:29:12.298 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 99, value: 0.0 
2023-11-23 23:29:12.299 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 113, value: 0.0 
2023-11-23 23:29:12.299 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 1001, value: 72763114.0 
2023-11-23 23:29:12.300 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 1004, value: 11481.0 h
2023-11-23 23:29:12.300 DEBUG (MainThread) [custom_components.kamstrup_403] Finished update, 0 out of 6 readings failed
2023-11-23 23:29:12.300 DEBUG (MainThread) [custom_components.kamstrup_403] Finished fetching kamstrup_403 data in 0.726 seconds (success: True)
2023-11-23 23:39:12.340 WARNING (SyncWorker_9) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:39:12.575 DEBUG (MainThread) [custom_components.kamstrup_403] Start update
2023-11-23 23:39:12.576 DEBUG (MainThread) [custom_components.kamstrup_403] Get values for [60, 68, 99, 113, 1001, 1004]
2023-11-23 23:39:13.313 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 60, value: 4.711 MWh
2023-11-23 23:39:13.314 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 68, value: 135.81 m³
2023-11-23 23:39:13.314 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 99, value: 0.0 
2023-11-23 23:39:13.315 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 113, value: 0.0 
2023-11-23 23:39:13.315 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 1001, value: 72763114.0 
2023-11-23 23:39:13.315 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 1004, value: 11481.0 h
2023-11-23 23:39:13.315 DEBUG (MainThread) [custom_components.kamstrup_403] Finished update, 0 out of 6 readings failed
2023-11-23 23:39:13.316 DEBUG (MainThread) [custom_components.kamstrup_403] Finished fetching kamstrup_403 data in 0.741 seconds (success: True)
2023-11-23 23:40:12.342 WARNING (SyncWorker_2) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:41:12.345 WARNING (SyncWorker_9) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:42:12.347 WARNING (SyncWorker_3) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:43:12.347 WARNING (SyncWorker_2) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:44:12.350 WARNING (SyncWorker_9) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:45:44.385 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid or incomplete color value '{'brightness': 254, 'color': {'x': 0.458, 'y': 0.41}, 'color_mode': 'color_temp', 'color_options': None, 'linkquality': 58, 'power_on_behavior': None, 'state': 'ON', 'update': {'installed_version': 318767730, 'latest_version': 587753009, 'state': 'available'}, 'update_available': True}' received for entity light.upstairs_korridor_tapphus
2023-11-23 23:45:44.492 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid or incomplete color value '{'brightness': 206, 'color': {'x': 0.458, 'y': 0.41}, 'color_mode': 'color_temp', 'color_options': None, 'linkquality': 54, 'power_on_behavior': None, 'state': 'ON', 'update': {'installed_version': 318767730, 'latest_version': 587753009, 'state': 'available'}, 'update_available': True}' received for entity light.trapphus
2023-11-23 23:46:42.358 WARNING (SyncWorker_1) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:47:42.361 WARNING (SyncWorker_2) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:48:42.363 WARNING (SyncWorker_9) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:49:13.575 DEBUG (MainThread) [custom_components.kamstrup_403] Start update
2023-11-23 23:49:13.575 DEBUG (MainThread) [custom_components.kamstrup_403] Get values for [60, 68, 99, 113, 1001, 1004]
2023-11-23 23:49:13.681 ERROR (MainThread) [custom_components.kamstrup_403] Error fetching kamstrup_403 data: 
2023-11-23 23:49:13.682 DEBUG (MainThread) [custom_components.kamstrup_403] Finished fetching kamstrup_403 data in 0.107 seconds (success: False)
2023-11-23 23:51:12.369 WARNING (SyncWorker_7) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:53:42.375 WARNING (SyncWorker_3) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:54:42.379 WARNING (SyncWorker_2) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:57:12.385 WARNING (SyncWorker_7) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:58:12.387 WARNING (SyncWorker_8) [homeassistant.components.rpi_power.binary_sensor] Under-voltage was detected. Consider getting a uninterruptible power supply for your Raspberry Pi.
2023-11-23 23:59:13.575 DEBUG (MainThread) [custom_components.kamstrup_403] Start update
2023-11-23 23:59:13.575 DEBUG (MainThread) [custom_components.kamstrup_403] Get values for [60, 68, 99, 113, 1001, 1004]
2023-11-23 23:59:13.609 DEBUG (MainThread) [custom_components.kamstrup_403] Finished fetching kamstrup_403 data in 0.034 seconds (success: False)

[golles]

The log isn't giving any clear indication of why it is failing, no error logs that are known, and also no stack traces.

You might want to sort out your Rpi power supply issue, see the many warnings. Power supply issues can result in weird behavior in general.

[PatrikPatrik2]

The thing is that exactly the same behaviour (worked for some hour then stoped, when the integration was restarted it worked again) was seen on my normal system, that is on old PC running HA OS, so I have a hard time thinking that this is because of the power issue

[golles]

Do you have logs from that machine?

[PatrikPatrik2]

Hi, now I installed the eye to the other machine:

2023-12-02 21:15:49.670 DEBUG (MainThread) [custom_components.kamstrup_403] Unregister command 60
2023-12-02 21:15:49.670 DEBUG (MainThread) [custom_components.kamstrup_403] Unregister command 68
2023-12-02 21:15:49.670 DEBUG (MainThread) [custom_components.kamstrup_403] Unregister command 99
2023-12-02 21:15:49.670 DEBUG (MainThread) [custom_components.kamstrup_403] Unregister command 113
2023-12-02 21:15:49.671 DEBUG (MainThread) [custom_components.kamstrup_403] Unregister command 1001
2023-12-02 21:15:49.671 DEBUG (MainThread) [custom_components.kamstrup_403] Unregister command 1004
2023-12-02 21:15:49.676 DEBUG (MainThread) [custom_components.kamstrup_403] Set up entry, with scan_interval of 3600 seconds and timeout of 1.0 seconds
2023-12-02 21:15:49.680 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 60
2023-12-02 21:15:49.680 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 68
2023-12-02 21:15:49.682 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 99
2023-12-02 21:15:49.682 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 113
2023-12-02 21:15:49.682 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 1001
2023-12-02 21:15:49.683 DEBUG (MainThread) [custom_components.kamstrup_403] Register command 1004
2023-12-02 21:15:49.689 DEBUG (MainThread) [custom_components.kamstrup_403] Start update
2023-12-02 21:15:49.689 DEBUG (MainThread) [custom_components.kamstrup_403] Get values for [60, 68, 99, 113, 1001, 1004]
2023-12-02 21:15:50.414 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 60, value: 5.8790000000000004 MWh
2023-12-02 21:15:50.414 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 68, value: 161.93 m³
2023-12-02 21:15:50.414 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 99, value: 0.0 
2023-12-02 21:15:50.414 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 113, value: 0.0 
2023-12-02 21:15:50.414 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 1001, value: 72763114.0 
2023-12-02 21:15:50.414 DEBUG (MainThread) [custom_components.kamstrup_403] New value for sensor 1004, value: 11695.0 h
2023-12-02 21:15:50.414 DEBUG (MainThread) [custom_components.kamstrup_403] Finished update, 0 out of 6 readings failed
2023-12-02 21:15:50.414 DEBUG (MainThread) [custom_components.kamstrup_403] Finished fetching kamstrup_403 data in 0.725 seconds (success: True)

2023-12-02 22:15:50.046 DEBUG (MainThread) [custom_components.kamstrup_403] Start update
2023-12-02 22:15:50.046 DEBUG (MainThread) [custom_components.kamstrup_403] Get values for [60, 68, 99, 113, 1001, 1004]
2023-12-02 22:15:50.050 ERROR (MainThread) [custom_components.kamstrup_403] Error fetching kamstrup_403 data: 
2023-12-02 22:15:50.050 DEBUG (MainThread) [custom_components.kamstrup_403] Finished fetching kamstrup_403 data in 0.004 seconds (success: False)

[golles]

Thanks for sharing the logs from the other machine. Sadly there isn't much I can do with this, as there is no information related to the error

[PatrikPatrik2]

Can you not write the code such that it checks every hour if the energy reading is Unavailable, and if the reading is unavailable it restarts the integration? It allways reads the energy correct when the integration is reloaded

[golles]

I don't know if that is a useful solution, since only you have this problem. Even though this isn't the best solution, could you try an automation to reload the integration?

automation:
  - id: reload_kamstrup_403_unavailable
    alias: Kamstrup 403 - Reload integration when unavailable
    mode: single
    trigger:
      - platform: state
        entity_id: sensor.kamstrup_403_heat_energy_e1
        state: unavailable
        for:
          minutes: 5
    action:
      - alias: Reload integration
        service: homeassistant.reload_config_entry
        target:
          entity_id: sensor.kamstrup_403_heat_energy_e1

[PatrikPatrik2]

Good idea, I tried but "state: unavailable" got an error message "property state is not allowed"

[golles]

My bad, it should be to

automation:
  - id: reload_kamstrup_403_unavailable
    alias: Kamstrup 403 - Reload integration when unavailable
    mode: single
    trigger:
      - platform: state
        entity_id: sensor.kamstrup_403_heat_energy_e1
        to: unavailable
        for:
          minutes: 5
    action:
      - alias: Reload integration
        service: homeassistant.reload_config_entry
        target:
          entity_id: sensor.kamstrup_403_heat_energy_e1

[PatrikPatrik2]

Looks very hopefull - it worked when I manually triggered the automation :)

[JackoAmmerlaan]

I am having the same issue since the update to 2023.12.1. I am losing the connection (or no data is received) every 10-20 minutes.
At this moment I have "solved" the issue by using a Node-Red flow which reloads the integration if it becomes Unknown of Unaviable.

Does it help if I also share some logging ?

[ohaue]

Just received the IR head yeasterday, so I installed this integration and I have the same issue. Created the automation to reload and I can see that the automation gets triggered almost exactly every 15 minuttes.

[JackoAmmerlaan]

I recently solved my issue.. I found that the NUC was losing it's USB connection, strange enough it was restored after a restart of the service. This happed every 5 minutes (I polled the IR head every 5 minutes). The solution was just to pull out and place the USB in again.... So I suggest to try that or use an other USB port.

[ohaue]

I actually also found out why the integration stopped every 15 minuttes. I was a wrong config in my ESP32. I needed to remove the API: line in the config: https://esphome.io/components/mqtt.html

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.