-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Answer from boiler #1
Comments
If one of the last lines you get is "Send our UID", then I know what the problem is. It has been brought to my attention that the 6-byte string hidden in this array isn't just an unimportant random value, but it's used by the boiler to maintain some sort of pairing. If your problem is the UID, then you have 3 choices:
|
My log INFO Reading configuration /config/esphome/bojler.yaml... |
and my setup web_server: captive_portal: Example configuration entry#esp32_ble_tracker: #text_sensor: - platform: ble_scannername: "BLE Devices Scanner"substitutions: external_components:
mqtt: id: mqtt_clientsensor: binary_sensor: select: climate: esp32_ble_tracker: ble_client:
smartboiler: |
It seems the whole ESP32 crashes somewhere between the completion of BLE service discovery and the successful subscription to a characteristic. I'm also working on a Go version for Raspberry Pi 3+ / any Linux system with a BLE-capable adapter. I haven't published the sources yet, but it could also be a solution for you if ESP32 is too unstable... |
ok, |
I have it right next to the boiler now, but I've had success with using at a 15m distance (through ceilings and walls). |
thanks |
During the connection attempt, the display shows the pairing code. |
I solved the pairing process in my fork - https://github.com/pedobry/esphome-smartboiler |
Cool! Will you submit a pull request? |
I can, but I'm not sure it's good idea - I did a lot of other changes (change in YAML to support multiple heaters, removed custom MQTT topics) which would break existing integrations using your repo. |
Nice work. Now I can connect me bojler and reading data and mode. |
I join the question. The situation is similar to that of robert10055. It is impossible to change the operating modes of the boiler, are they read-only? |
@pedobry I use your integration and everything works great but i cannot change operating mode, it is only changing between SMART and SMARTHDO but if i want choose for example ANTIFROST, nothing is changed. Is it a bug or it should work so and it is not possible to change other operating modes? Thank you so much! |
@pedobry I ended up merging your fork. |
Hello @LubosD , because fork is merged now, i have changed my ESP device to your git code. Is there any chance to repair correctly changing operating modes? Is there any possiblity to read actual HDO state from water heater? Now "Water heater HDO" only tells that the HDO detect function of water heater is active but nice to have function of reading HDO for other devices in home assistant. For example if HDO is active, turn on floor heating etc. Thank you. |
I fixed the issue with operating mode changing in pull request #7 |
Ahoj Luboši, prosím nedaří se mi spárovat můj bojler s ESP32. Po instalaci displej na kterém se střídá čas a teplota vody, se začne zvláštně chovat, jakoby se zvýrazňovaly číslice jasnějším svitem, ale nezobrazí se žádný PIN. Netuším ani kam bych jej zadal. EDIT: vyřešeno, děkuji za tvůj komponent pro kotel Dražice |
Hello Luboš,
I tested your project, I don't seem to get any response from Ble.
I right found MAC adress Ble and in the log I see a connectionto the device but not response
Do you have any advice for me?
The text was updated successfully, but these errors were encountered: