From f9e5d8189b095a360b2b987b507e16a4d0c333e7 Mon Sep 17 00:00:00 2001 From: Mario Guggenberger Date: Mon, 13 Nov 2023 15:27:23 +0100 Subject: [PATCH] Add HAOS+Raspi troubleshooting instructions to Idasen desk (#29686) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Add HAOS+Raspi troubleshooting instructions to Idasen desk * Apply suggestions from code review Co-authored-by: Abílio Costa --------- Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Co-authored-by: Abílio Costa --- source/_integrations/idasen_desk.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/idasen_desk.markdown b/source/_integrations/idasen_desk.markdown index c39af75ff9b..d7264815696 100644 --- a/source/_integrations/idasen_desk.markdown +++ b/source/_integrations/idasen_desk.markdown @@ -23,6 +23,8 @@ The recommended way to connect the desk to Home Assistant is by using an [ESPHom If you are not using an ESPHome Bluetooth Proxy, you need to keep `bluetoothctl` (or any other Bluetooth Agent) open during the integration setup, or it will fail to authenticate with the desk. The connection process is also less reliable than with ESPHome, so you may need to retry a few times until it succeeds. This is due to a limitation in the third-party Bluetooth implementation used by Home Assistant. +Also, if not using an ESPHome Bluetooth Proxy, you may experience the desk becoming unavailable and needing re-pairing after a restart of Home Assistant or a reload of the integration. To pair it permanently, [access the host over SSH](https://developers.home-assistant.io/docs/operating-system/debugging/#ssh-access-to-the-host), pair the desk with `bluetoothctl pair `, and validate it being listed by `bluetoothctl devices Paired`. If the desk is not listed as paired, repeat the command several times while entering pairing mode on the desk. + {% include integrations/config_flow.md %}