HomeAssistant integration

[trynqz]

Hi, I managed to use your dev branch, it works great with my IBT-6x via ESP32 wroom-32U. I got all the probes accessible via WIFI and WWW. Thanks for your great work. Can you please advice, how I can integrate received data with homeAssistant? I would like to track probe values and make use of them doing further automations...like turn of the smoker heater if the set temperature value is reached. This is my first Arduino and ESP32 tryouts, so sorry if this is low level question :)

[satrik]

hi @trynqz, sorry I've absolutely no experience with HomeAssistant and I've never used it. but if you access /probes of the esp, you get the "raw values" in JSON format and I think this integration could be what you need.

[trynqz]

HI, thanks for your comment. It was 100% accurate. I'm struggling little bit with converting 6552 to 0/off value. When I'll finish, I'll post the setup, maybe someone else will be interested. Still it works PERFECT, and gave me prety cool setup to automate the smoker :)

[trynqz]

Hi, so this is a big moment... for me :) it finally worked. Below I paste HomeAssistant config. In order to have nice statistisc graph I'm converting 6552 value to 0. I use inkbird only when smoking hot, so value "0" means "off" for me, and it never happens in real life.

configuration.yaml ` sensor:

konfiguracja interfejsu do odczytu wskazań temperatury z termometru BT inkBird poprzez ESP32

• platform: rest name: "meat_probe" resource: http://xx.xx.xx.xx/probes json_attributes:
  • "p1"
  • "p2"
  • "p3"
  • "p4"
  • "p5"
  • "p6" value_template: "OK"
• platform: template sensors: probe1_temperature: value_template: > {% if state_attr('sensor.meat_probe', 'p1') == 6552.0 %} 0 {% else %} {{ state_attr('sensor.meat_probe', 'p1') }} {% endif %} icon_template: > {% if state_attr('sensor.meat_probe', 'p1') == 6552.0 %} mdi:thermometer-alert {% else %} mdi:thermometer {% endif %} device_class: temperature unit_of_measurement: "°C" probe2_temperature: value_template: > {% if state_attr('sensor.meat_probe', 'p2') == 6552.0 %} 0 {% else %} {{ state_attr('sensor.meat_probe', 'p2') }} {% endif %} icon_template: > {% if state_attr('sensor.meat_probe', 'p2') == 6552.0 %} mdi:thermometer-alert {% else %} mdi:thermometer {% endif %} device_class: temperature unit_of_measurement: "°C" probe3_temperature: value_template: > {% if state_attr('sensor.meat_probe', 'p3') == 6552.0 %} 0 {% else %} {{ state_attr('sensor.meat_probe', 'p3') }} {% endif %} icon_template: > {% if state_attr('sensor.meat_probe', 'p3') == 6552.0 %} mdi:thermometer-alert {% else %} mdi:thermometer {% endif %} device_class: temperature unit_of_measurement: "°C" probe4_temperature: value_template: > {% if state_attr('sensor.meat_probe', 'p4') == 6552.0 %} 0 {% else %} {{ state_attr('sensor.meat_probe', 'p4') }} {% endif %} icon_template: > {% if state_attr('sensor.meat_probe', 'p4') == 6552.0 %} mdi:thermometer-alert {% else %} mdi:thermometer {% endif %} device_class: temperature unit_of_measurement: "°C" probe5_temperature: value_template: > {% if state_attr('sensor.meat_probe', 'p5') == 6552.0 %} 0 {% else %} {{ state_attr('sensor.meat_probe', 'p5') }} {% endif %} icon_template: > {% if state_attr('sensor.meat_probe', 'p5') == 6552.0 %} mdi:thermometer-alert {% else %} mdi:thermometer {% endif %} device_class: temperature unit_of_measurement: "°C" probe6_temperature: value_template: > {% if is_state_attr('sensor.meat_probe', 'p6', 6552.0) %} 0 {% else %} {{ state_attr('sensor.meat_probe', 'p6') }} {% endif %} icon_template: > {% if is_state_attr('sensor.meat_probe', 'p6', 6552.0) %} mdi:thermometer-alert {% else %} mdi:thermometer {% endif %} device_class: temperature unit_of_measurement: "°C" `

Lovelace code:

` type: horizontal-stack cards:

• type: vertical-stack cards:
  • type: entities entities:
    • entity: switch.sonoff_10005bb0fc secondary_info: last-changed icon: mdi:grill-outline
    • entity: sensor.sonoff_10005bb0fc_temperature secondary_info: last-changed show_header_toggle: false title: BBQ
  • type: history-graph entities:
    • entity: sensor.sonoff_10005bb0fc_temperature hours_to_show: 10
• type: thermostat entity: climate.booxasmooker_termostat
• type: vertical-stack cards:
  • type: entities entities:
    • entity: sensor.probe1_temperature
    • entity: sensor.probe2_temperature
    • entity: sensor.probe3_temperature
    • entity: sensor.probe4_temperature
    • entity: sensor.probe5_temperature
    • entity: sensor.probe6_temperature
  • type: history-graph entities:
    • entity: sensor.probe1_temperature name: szynka_nisko
    • entity: sensor.probe2_temperature name: szynka_wysoko
    • entity: sensor.probe3_temperature name: schab_nisko
    • entity: sensor.probe4_temperature name: schab_wysoko
    • entity: sensor.probe5_temperature
    • entity: sensor.probe6_temperature hours_to_show: 10 refresh_interval: 0

`

[trynqz]

@satrik thanks for this integration!!

[satrik]

@trynqz looks really nice! You should check if you can parse the json and generate the templates dynamically according to the number of probes provided by the esp. I think there should be something like a foreach or for in loop which can do this. This would make it easier to use for other devices with more/less probes 🙂

[trynqz]

Thanks. One question, how do you handle inkbird battery state? My observation is, that batteries like to die, not at the begining of cooking, when there is time to prepare, but just about when the meat is almost ready... It would be great to program some sort notification, aspecially now when I do not need to use BBQ go app. Regards Rafał

śr., 24 lis 2021, 15:13 użytkownik satrik @.***> napisał:

@trynqz https://github.com/trynqz looks really nice! You should check if you can parse the json and generate the templates dynamically according to the number of probes provided by the esp. I think there should be something like a foreach or for in loop which can do this. This would make it easier to use for other devices with more/less probes 🙂

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/satrik/esp32_ble_inkbird/issues/3#issuecomment-977916662, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASJFECEKT3HVKEQTYOPDVYDUNTXKFANCNFSM5HCPF2EA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[satrik]

the code don't handle it at all because it doesn't make sense for me to know the current state in percent. in my case it's quite simple, if the esp isn't reachable, i assume the battery is empty 😄

but if you need this feature, it shouldn't be hard to implement it yourself as there are a lot of other projects which use this feature.

[trynqz]

Not reachable = dead is best simple solution, but sometimes when I do beef ribs and they stay in the smoker during the night, it would be great just to prepare myself for battery change before I go to sleep.

I'm copy/paste hacker ... Not even close to be possible to do any implementation myself. If you could in some future add it, maybe as an addition to other implementation changes, I will be more than grateful. If not - I will just changed batteries more often.

czw., 25 lis 2021, 12:01 użytkownik satrik @.***> napisał:

the code don't handle it at all because it doesn't make sense for me to know the current state in percent. in my case it's quite simple, if the esp isn't reachable, i assume the battery is empty 😄

but if you need this feature, it shouldn't be hard to implement it yourself as there are a lot of other projects which use this feature.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/satrik/esp32_ble_inkbird/issues/3#issuecomment-979095182, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASJFECG2QH4PLA7NIPXJTW3UNYJPJANCNFSM5HCPF2EA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.