Closed lysiong closed 1 year ago
Do a clean build.
Do a clean build.
I been try before to uninstall the entire ESPhome module & delete the ESPhome folder in home assistant, restart HA & install back ESPhome but seem like problem still occur. I also try change another ESP32 board. I not sure if my code is wrong but I just follow the official documentation from the ESPhome.io website.
Try the clean build option.
Try the clean build option.
can I have the actual step? I not so expert in this thing. where do I find the clean build option?
https://esphome.github.io/bluetooth-proxies/ above is the website that I use to built the bluetooth proxy
That's where you got the initial install, but that's not where you're doing the compiling. There should be a menu on the dashboard card for the device that has a "clean" option on it.
That's where you got the initial install, but that's not where you're doing the compiling. There should be a menu on the dashboard card for the device that has a "clean" option on it.
did you mean this? I also try to click that then rebuild with new wifi sensor option but somehow didn't fix it.
Yes, that. You still get the same error after that?
Yes, that. You still get the same error after that?
yes, same error come out.
I add the wifi signal sensor in this particular yaml file, I not sure if I add it correctly.
Try the clean build option.
I was having similar issue with my BT Proxy after I decided to add "sensor:" to the code. No matter what I did, I got the error. Landed on this page from google search and @ssieb you saved my day ;) Now it compiles properly with no errors!
@lysiong I am not sure if the indentations has anything to do with it but below is how I have mine.
sensor:
- platform: uptime
name: Uptime Sensor
Update: I decided to add another sensor and again same error. So I did a clean build option again and then Install and all went well.
sensor:
- platform: uptime
name: Uptime Sensor
- platform: template
name: BTProxy Free Memory
lambda: return heap_caps_get_free_size(MALLOC_CAP_INTERNAL) / 1024;
unit_of_measurement: 'kB'
state_class: measurement
Update2: I decided to add the wifi sensor also and at the same time played with the indentation. All is well even if I added the indentation. I did however have to do the clean build option before the install.
sensor:
- platform: uptime
name: "${friendly_name} - Uptime Sensor"
- platform: wifi_signal
name: "${friendly_name} - WiFi Signal"
update_interval: 60s
- platform: template
name: "${friendly_name} - Free Memory"
lambda: return heap_caps_get_free_size(MALLOC_CAP_INTERNAL) / 1024;
unit_of_measurement: 'kB'
state_class: measurement
@rleongcs
May I know that sensor is it add it to ESP.yaml file? maybe I add the sensor to wrong file :( below is my actual esp.yaml file content. that sample sensor I add didn't work as well, come out error when install.
substitutions:
name: "esp32-proxy1"
packages:
esphome.bluetooth-proxy: github://esphome/bluetooth-proxies/esp32-generic.yaml@main
esphome:
name: ${name}
name_add_mac_suffix: false
api:
encryption:
key: xxx
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
#sensor:
# -platform: wifi_signal
# name: "WiFi Signal Sensor"
# update_interval: 60s
sensor:
- platform: uptime
name: Uptime Sensor
@rleongcs I add the sensor in here
is this the correct place that I add the uptime sensor & other sensor as well?
Problem solved ! proper procedure is click "clean build files", then click "install". It work on latest version of ESPHOME
@lysiong Sorry missed your post. Good to hear you finally got it resolved. 🎉
Yes, you need to click "clean build files", then click "install"
The problem
ESPHOME always come out error when want install "WiFi Signal Sensor"
Which version of ESPHome has the issue?
2023.2.4
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
Home Assistant 2023.3.3
What platform are you using?
ESP32
Board
generic
Component causing the issue
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response