Search
684 results for “esphome”
-
Video of the Badger up and running showing multiple sensors and controlling smart home devices via its buttons!
https://www.youtube.com/watch?v=r-DjXnoWFrA
#esphome #homeassistant #badger #pimoroni #pipico #picow #raspberrypi #maker #homeautomation
-
Exciting! I have my Pimoroni Badger 2040W working in ESPHome including the buttons and display! You can see the code here:
#esphome #homeassistant #badger #pimoroni #pipico #picow #raspberrypi #maker #homeautomation
-
2023 Hackaday Prize: A Smart Powermeter That You Actually Want - [Jon] wanted to keep track of his home power use, but didn’t want to have to push ... - https://hackaday.com/2023/07/24/2023-hackaday-prize-a-smart-powermeter-that-you-actually-want/ #2023hackadayprize #powermanagement #currentsensing #homeautomation #classichacks #greenhacks #contests #esphome
-
I knocked a few improvements off my todo list for my wireless #esphome #grocy barcode scanner!
* Now handles very rapid barcode scans,
* "Bar Err" and "Net Err" screen messages for easier troubleshooting,
* Improved handling of large API calls. -
-
ESPHome Developers released #ESPHome version 2026.4.5. https://esphome.io/
-
Heute haben wir die Decoder-Funktion des Oszilloskops genutzt, um die Daten eines CO2-Sensors auszulesen. Der Port ist zwar mit RS-232 beschriftet, allerdings werden die Werte über einen Optokoppler in Open-Collector-Schaltung ausgegeben.
Im nächsten Schritt wird das Gerät über #ESPHome an #HomeAssistant angebunden.
Wer sich unter anderem für Elektronik interessiert, kann gerne den morgigen #Chaostreff besuchen. Die Türen sind ab 16 Uhr geöffnet.
-
ESPHome Developers released #ESPHome version 2026.4.4. https://esphome.io/
-
Also #progress on ManT1S @esphome support! First successful #compile and #boot. Took quite a bit of fiddling with the YAML to overrule the pin validator and add the LAN867x component. Weird to have to alter source code, but pull the library in in the project YAML. Not sure if there's a better way to do this. 🤔
Any #ESPHome experts here who might know?
-
**ESPHome update 2025.08.02: This little maneuvre will cost you … several days.**
TL;DR
Changing the ESPHome framework from Arduino to ESP-IDF is far from trivial. Don’t attempt it at home, if you’re a Home Assistant / ESPHome hobbyist with a poor C++ knowledge.
Read on…
After the last update of ESPHome, some of my compiled firmware images for my ESP32 boards suddenly became too big to fit in their memory. They said that Arduino libraries became too big and bloated. Yelp, I can’t update them anymore!
They (ESPHome developers) said we should switch from Arduion framework to ESP-IDF anyways, because it’s smaller, optimized and closer to the metal.
They said only a small change in esp configuration yaml is needed:
esp32: board: esp32dev framework: type: arduino # <-- change to esp-idfAnd that’s almost1 it!
You wish.
I changed the framework as described above (for one non-critical ESPCam).
I got compile errors (for my lambda functions). But wait, they said everything will work the same, no, even better!
But it looks like there are some differences between Arduino and ESP-IDF framework. For example, there is no String() in esp-idf! Isn’t that a … basic?
Ok, I surrendered and changed my lambda function that returned uptime in human readable format from:
- platform: uptime name: ${devicename} Uptime in Days id: uptime_sensor_days update_interval: 60s on_raw_value: then: - text_sensor.template.publish: id: uptime_human state: !lambda |- int seconds = round(id(uptime_sensor_days).raw_state); int days = seconds / (24 * 3600); seconds = seconds % (24 * 3600); int hours = seconds / 3600; seconds = seconds % 3600; int minutes = seconds / 60; seconds = seconds % 60; return ( (days ? String(days) + "d " : "") + (hours ? String(hours) + "h " : "") + (minutes ? String(minutes) + "m " : "") + (String(seconds) + "s") ).c_str();Changed the last bold bit (return…) that caused compile errors to:
...std::string result; if (days) result += std::to_string(days) + "d "; if (hours) result += std::to_string(hours) + "h "; if (minutes) result += std::to_string(minutes) + "m "; result += std::to_string(seconds) + "s"; return result;And then it compiled ok.
It also linked ok and uploaded firmware to my ESPCam.
Ping to my ESPCam worked, but sensors (camera web server, uptime, led switch,…) were unavailable.
ESPHome log returned only the following info:
changed lambda. log returns: Uploading: [============================================================] 100% Done... INFO Upload took 6.12 seconds, waiting for result... INFO OTA successful INFO Successfully uploaded program. INFO Starting log output from 192.168.0.15 using esphome API INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Trying to connect to esp32-cam01 @ 192.168.0.15 in the background INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.001s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000sThe connection to ESPCam looks ok.
But it wouldn’t connect to ESPHome API:
WARNING Can't connect to ESPHome API for esp32-cam01 @ 192.168.0.15: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.15', port=6053))]: [Errno 111] Connect call failed ('192.168.0.15', 6053) (SocketAPIError)I really wasn’t in the mood to research what went wrong and which part of my ESPCam configuration code is not compatible with ESP-IDF.
So I ditched esp-idf framework, reverted it back to arduino, recompiled, uploaded and my espcam works again.
Yes, I’ve searched for possible solutions2, but couldn’t find any that I could use.
My other ESP32 board (the one that has suddenly too big firmware after ESPHome update) will obviously stay in un-updated state for the rest of it’s life. I don’t wan’t to deal with breaking changes, modifying the code, re-learning C++ just to make it work again.
And this little maneuver caused me few days. Don’t go the same path.
Or, if the framework change works for you, please let me know.
Or, maybe I’ll try again when the issues3 are resolved.
- Official guide says: … Component Compatibility: Some components may need to be replaced with ESP-IDF compatible alternatives (<— WHICH ONES???)
Library Differences: Arduino-specific libraries won’t be available (<— WHICH ONES???) ↩︎ - Of course I checked the official guide: https://esphome.io/guides/esp32_arduino_to_idf/. When I read I should go to their Discord for help, I just gave up. ↩︎
- https://github.com/esphome/esphome/issues ↩︎
https://blog.rozman.info/esphome-update-2025-08-02-this-little-maneuvre-will-cost-you-several-days/
- Official guide says: … Component Compatibility: Some components may need to be replaced with ESP-IDF compatible alternatives (<— WHICH ONES???)
-
Kennt sich jemand mit C++ im Bereich Lowlevel im Zusammenhang mit esp-idf insbesondere rmt für #esphome aus?
Ich würde gerne ein Projekt auf den aktuellen Esphome Stand bringen, damit es auch wieder kompillierbar ist. Ich verzweifel an RMT und könnte da Hilfe brauchen.Gerne teilen und sich bei mir melden.
-
Meh, trying to read out my solar inverters using #ESPHome and an #RS485-to-#TTL module, but it turns out I need one that has auto flow control (which, of course, I don't have). Will have to wait another 5-7 days for #Aliexpress to deliver 🤷🏼♂️
-
CW: homeassistant
I don't know who need to hear this:
After last udate, #EspHome doesn't recognize BLE signals (anymore) from Xiaomi Mi thermomethers if beacon is set to "Mi". Reflashed them with #Telink flasher and set the beacon to 'Custom'.
Works again.
#homeassistant -
**ESPHome update 2025.08.02: This little maneuvre will cost you … several days.**
TL;DR
Changing the ESPHome framework from Arduino to ESP-IDF is far from trivial. Don’t attempt it at home, if you’re a Home Assistant / ESPHome hobbyist with a poor C++ knowledge.
Read on…
After the last update of ESPHome, some of my compiled firmware images for my ESP32 boards suddenly became too big to fit in their memory. They said that Arduino libraries became too big and bloated. Yelp, I can’t update them anymore!
They (ESPHome developers) said we should switch from Arduion framework to ESP-IDF anyways, because it’s smaller, optimized and closer to the metal.
They said only a small change in esp configuration yaml is needed:
esp32: board: esp32dev framework: type: arduino # <-- change to esp-idfAnd that’s it!
You wish.
I changed the framework as described above (for one non-critical ESPCam).
I got compile errors (for my lambda functions). But wait, they said everything will work the same, no, even better!
But it looks like there are some differences between Arduino and ESP-IDF framework. For example, there is no String() in esp-idf! Isn’t that a … basic?
Ok, I surrendered and changed my lambda function that returned uptime in human readable format from:
- platform: uptime name: ${devicename} Uptime in Days id: uptime_sensor_days update_interval: 60s on_raw_value: then: - text_sensor.template.publish: id: uptime_human state: !lambda |- int seconds = round(id(uptime_sensor_days).raw_state); int days = seconds / (24 * 3600); seconds = seconds % (24 * 3600); int hours = seconds / 3600; seconds = seconds % 3600; int minutes = seconds / 60; seconds = seconds % 60; return ( (days ? String(days) + "d " : "") + (hours ? String(hours) + "h " : "") + (minutes ? String(minutes) + "m " : "") + (String(seconds) + "s") ).c_str();Changed the last bold bit (return…) that caused compile errors to:
...std::string result; if (days) result += std::to_string(days) + "d "; if (hours) result += std::to_string(hours) + "h "; if (minutes) result += std::to_string(minutes) + "m "; result += std::to_string(seconds) + "s"; return result;And then it compiled ok.
It also linked ok and uploaded firmware to my ESPCam.
Ping to my ESPCam worked, but sensors (camera web server, uptime, led switch,…) were unavailable.
ESPHome log returned only the following info:
changed lambda. log returns: Uploading: [============================================================] 100% Done... INFO Upload took 6.12 seconds, waiting for result... INFO OTA successful INFO Successfully uploaded program. INFO Starting log output from 192.168.0.15 using esphome API INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Trying to connect to esp32-cam01 @ 192.168.0.15 in the background INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.001s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000sThe connection to ESPCam looks ok.
But it wouldn’t connect to ESPHome API:
WARNING Can't connect to ESPHome API for esp32-cam01 @ 192.168.0.15: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.15', port=6053))]: [Errno 111] Connect call failed ('192.168.0.15', 6053) (SocketAPIError)I really wasn’t in the mood to research what went wrong and which part of my ESPCam configuration code is not compatible with ESP-IDF.
So I ditched esp-idf framework, reverted it back to arduino, recompiled, uploaded and my espcam works again.
Yes, I’ve searched for possible solutions, but couldn’t find any that I could use.
My other ESP32 board (the one that has suddenly too big firmware after ESPHome update) will obviously stay in un-updated state for the rest of it’s life. I don’t wan’t to deal with breaking changes, modifying the code, re-learning C++ just to make it work again.
And this little maneuver caused me few days. Don’t go the same path.
Or, if the framework change works for you, please let me know.
https://blog.rozman.info/esphome-update-2025-08-02-this-little-maneuvre-will-cost-you-several-days/
-
**ESPHome update 2025.08.02: This little maneuvre will cost you … several days.**
TL;DR
Changing the ESPHome framework from Arduino to ESP-IDF is far from trivial. Don’t attempt it at home, if you’re a Home Assistant / ESPHome hobbyist with a poor C++ knowledge.
Read on…
After the last update of ESPHome, some of my compiled firmware images for my ESP32 boards suddenly became too big to fit in their memory. They said that Arduino libraries became too big and bloated. Yelp, I can’t update them anymore!
They (ESPHome developers) said we should switch from Arduion framework to ESP-IDF anyways, because it’s smaller, optimized and closer to the metal.
They said only a small change in esp configuration yaml is needed:
esp32: board: esp32dev framework: type: arduino # <-- change to esp-idfAnd that’s it!
You wish.
I changed the framework as described above (for one non-critical ESPCam).
I got compile errors (for my lambda functions). But wait, they said everything will work the same, no, even better!
But it looks like there are some differences between Arduino and ESP-IDF framework. For example, there is no String() in esp-idf! Isn’t that a … basic?
Ok, I surrendered and changed my lambda function that returned uptime in human readable format from:
- platform: uptime name: ${devicename} Uptime in Days id: uptime_sensor_days update_interval: 60s on_raw_value: then: - text_sensor.template.publish: id: uptime_human state: !lambda |- int seconds = round(id(uptime_sensor_days).raw_state); int days = seconds / (24 * 3600); seconds = seconds % (24 * 3600); int hours = seconds / 3600; seconds = seconds % 3600; int minutes = seconds / 60; seconds = seconds % 60; return ( (days ? String(days) + "d " : "") + (hours ? String(hours) + "h " : "") + (minutes ? String(minutes) + "m " : "") + (String(seconds) + "s") ).c_str();Changed the last bold bit (return…) that caused compile errors to:
...std::string result; if (days) result += std::to_string(days) + "d "; if (hours) result += std::to_string(hours) + "h "; if (minutes) result += std::to_string(minutes) + "m "; result += std::to_string(seconds) + "s"; return result;And then it compiled ok.
It also linked ok and uploaded firmware to my ESPCam.
Ping to my ESPCam worked, but sensors (camera web server, uptime, led switch,…) were unavailable.
ESPHome log returned only the following info:
changed lambda. log returns: Uploading: [============================================================] 100% Done... INFO Upload took 6.12 seconds, waiting for result... INFO OTA successful INFO Successfully uploaded program. INFO Starting log output from 192.168.0.15 using esphome API INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Trying to connect to esp32-cam01 @ 192.168.0.15 in the background INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.001s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000sThe connection to ESPCam looks ok.
But it wouldn’t connect to ESPHome API:
WARNING Can't connect to ESPHome API for esp32-cam01 @ 192.168.0.15: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.15', port=6053))]: [Errno 111] Connect call failed ('192.168.0.15', 6053) (SocketAPIError)I really wasn’t in the mood to research what went wrong and which part of my ESPCam configuration code is not compatible with ESP-IDF.
So I ditched esp-idf framework, reverted it back to arduino, recompiled, uploaded and my espcam works again.
Yes, I’ve searched for possible solutions, but couldn’t find any that I could use.
My other ESP32 board (the one that has suddenly too big firmware after ESPHome update) will obviously stay in un-updated state for the rest of it’s life. I don’t wan’t to deal with breaking changes, modifying the code, re-learning C++ just to make it work again.
And this little maneuver caused me few days. Don’t go the same path.
Or, if the framework change works for you, please let me know.
https://blog.rozman.info/esphome-update-2025-08-02-this-little-maneuvre-will-cost-you-several-days/
-
**ESPHome update 2025.08.02: This little maneuvre will cost you … several days.**
TL;DR
Changing the ESPHome framework from Arduino to ESP-IDF is far from trivial. Don’t attempt it at home, if you’re a Home Assistant / ESPHome hobbyist with a poor C++ knowledge.
Read on…
After the last update of ESPHome, some of my compiled firmware images for my ESP32 boards suddenly became too big to fit in their memory. They said that Arduino libraries became too big and bloated. Yelp, I can’t update them anymore!
They (ESPHome developers) said we should switch from Arduion framework to ESP-IDF anyways, because it’s smaller, optimized and closer to the metal.
They said only a small change in esp configuration yaml is needed:
esp32: board: esp32dev framework: type: arduino # <-- change to esp-idfAnd that’s almost1 it!
You wish.
I changed the framework as described above (for one non-critical ESPCam).
I got compile errors (for my lambda functions). But wait, they said everything will work the same, no, even better!
But it looks like there are some differences between Arduino and ESP-IDF framework. For example, there is no String() in esp-idf! Isn’t that a … basic?
Ok, I surrendered and changed my lambda function that returned uptime in human readable format from:
- platform: uptime name: ${devicename} Uptime in Days id: uptime_sensor_days update_interval: 60s on_raw_value: then: - text_sensor.template.publish: id: uptime_human state: !lambda |- int seconds = round(id(uptime_sensor_days).raw_state); int days = seconds / (24 * 3600); seconds = seconds % (24 * 3600); int hours = seconds / 3600; seconds = seconds % 3600; int minutes = seconds / 60; seconds = seconds % 60; return ( (days ? String(days) + "d " : "") + (hours ? String(hours) + "h " : "") + (minutes ? String(minutes) + "m " : "") + (String(seconds) + "s") ).c_str();Changed the last bold bit (return…) that caused compile errors to:
...std::string result; if (days) result += std::to_string(days) + "d "; if (hours) result += std::to_string(hours) + "h "; if (minutes) result += std::to_string(minutes) + "m "; result += std::to_string(seconds) + "s"; return result;And then it compiled ok.
It also linked ok and uploaded firmware to my ESPCam.
Ping to my ESPCam worked, but sensors (camera web server, uptime, led switch,…) were unavailable.
ESPHome log returned only the following info:
changed lambda. log returns: Uploading: [============================================================] 100% Done... INFO Upload took 6.12 seconds, waiting for result... INFO OTA successful INFO Successfully uploaded program. INFO Starting log output from 192.168.0.15 using esphome API INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Trying to connect to esp32-cam01 @ 192.168.0.15 in the background INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.001s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000sThe connection to ESPCam looks ok.
But it wouldn’t connect to ESPHome API:
WARNING Can't connect to ESPHome API for esp32-cam01 @ 192.168.0.15: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.15', port=6053))]: [Errno 111] Connect call failed ('192.168.0.15', 6053) (SocketAPIError)I really wasn’t in the mood to research what went wrong and which part of my ESPCam configuration code is not compatible with ESP-IDF.
So I ditched esp-idf framework, reverted it back to arduino, recompiled, uploaded and my espcam works again.
Yes, I’ve searched for possible solutions2, but couldn’t find any that I could use.
My other ESP32 board (the one that has suddenly too big firmware after ESPHome update) will obviously stay in un-updated state for the rest of it’s life. I don’t wan’t to deal with breaking changes, modifying the code, re-learning C++ just to make it work again.
And this little maneuver caused me few days. Don’t go the same path.
Or, if the framework change works for you, please let me know.
Or, maybe I’ll try again when the issues3 are resolved.
- Official guide says: … Component Compatibility: Some components may need to be replaced with ESP-IDF compatible alternatives (<— WHICH ONES???)
Library Differences: Arduino-specific libraries won’t be available (<— WHICH ONES???) ↩︎ - Of course I checked the official guide: https://esphome.io/guides/esp32_arduino_to_idf/. When I read I should go to their Discord for help, I just gave up. ↩︎
- https://github.com/esphome/esphome/issues ↩︎
https://blog.rozman.info/esphome-update-2025-08-02-this-little-maneuvre-will-cost-you-several-days/
- Official guide says: … Component Compatibility: Some components may need to be replaced with ESP-IDF compatible alternatives (<— WHICH ONES???)
-
**ESPHome update 2025.08.02: This little maneuvre will cost you … several days.**
TL;DR
Changing the ESPHome framework from Arduino to ESP-IDF is far from trivial. Don’t attempt it at home, if you’re a Home Assistant / ESPHome hobbyist with a poor C++ knowledge.
Read on…
After the last update of ESPHome, some of my compiled firmware images for my ESP32 boards suddenly became too big to fit in their memory. They said that Arduino libraries became too big and bloated. Yelp, I can’t update them anymore!
They (ESPHome developers) said we should switch from Arduion framework to ESP-IDF anyways, because it’s smaller, optimized and closer to the metal.
They said only a small change in esp configuration yaml is needed:
esp32: board: esp32dev framework: type: arduino # <-- change to esp-idfAnd that’s it!
You wish.
I changed the framework as described above (for one non-critical ESPCam).
I got compile errors (for my lambda functions). But wait, they said everything will work the same, no, even better!
But it looks like there are some differences between Arduino and ESP-IDF framework. For example, there is no String() in esp-idf! Isn’t that a … basic?
Ok, I surrendered and changed my lambda function that returned uptime in human readable format from:
- platform: uptime name: ${devicename} Uptime in Days id: uptime_sensor_days update_interval: 60s on_raw_value: then: - text_sensor.template.publish: id: uptime_human state: !lambda |- int seconds = round(id(uptime_sensor_days).raw_state); int days = seconds / (24 * 3600); seconds = seconds % (24 * 3600); int hours = seconds / 3600; seconds = seconds % 3600; int minutes = seconds / 60; seconds = seconds % 60; return ( (days ? String(days) + "d " : "") + (hours ? String(hours) + "h " : "") + (minutes ? String(minutes) + "m " : "") + (String(seconds) + "s") ).c_str();Changed the last bold bit (return…) that caused compile errors to:
...std::string result; if (days) result += std::to_string(days) + "d "; if (hours) result += std::to_string(hours) + "h "; if (minutes) result += std::to_string(minutes) + "m "; result += std::to_string(seconds) + "s"; return result;And then it compiled ok.
It also linked ok and uploaded firmware to my ESPCam.
Ping to my ESPCam worked, but sensors (camera web server, uptime, led switch,…) were unavailable.
ESPHome log returned only the following info:
changed lambda. log returns: Uploading: [============================================================] 100% Done... INFO Upload took 6.12 seconds, waiting for result... INFO OTA successful INFO Successfully uploaded program. INFO Starting log output from 192.168.0.15 using esphome API INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Trying to connect to esp32-cam01 @ 192.168.0.15 in the background INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.001s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000s INFO Successfully resolved esp32-cam01 @ 192.168.0.15 in 0.000sThe connection to ESPCam looks ok.
But it wouldn’t connect to ESPHome API:
WARNING Can't connect to ESPHome API for esp32-cam01 @ 192.168.0.15: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.15', port=6053))]: [Errno 111] Connect call failed ('192.168.0.15', 6053) (SocketAPIError)I really wasn’t in the mood to research what went wrong and which part of my ESPCam configuration code is not compatible with ESP-IDF.
So I ditched esp-idf framework, reverted it back to arduino, recompiled, uploaded and my espcam works again.
Yes, I’ve searched for possible solutions, but couldn’t find any that I could use.
My other ESP32 board (the one that has suddenly too big firmware after ESPHome update) will obviously stay in un-updated state for the rest of it’s life. I don’t wan’t to deal with breaking changes, modifying the code, re-learning C++ just to make it work again.
And this little maneuver caused me few days. Don’t go the same path.
Or, if the framework change works for you, please let me know.
https://blog.rozman.info/esphome-update-2025-08-02-this-little-maneuvre-will-cost-you-several-days/
-
Kennt sich jemand mit C++ im Bereich Lowlevel im Zusammenhang mit esp-idf insbesondere rmt für #esphome aus?
Ich würde gerne ein Projekt auf den aktuellen Esphome Stand bringen, damit es auch wieder kompillierbar ist. Ich verzweifel an RMT und könnte da Hilfe brauchen.Gerne teilen und sich bei mir melden.
-
Kennt sich jemand mit C++ im Bereich Lowlevel im Zusammenhang mit esp-idf insbesondere rmt für #esphome aus?
Ich würde gerne ein Projekt auf den aktuellen Esphome Stand bringen, damit es auch wieder kompillierbar ist. Ich verzweifel an RMT und könnte da Hilfe brauchen.Gerne teilen und sich bei mir melden.
-
Внезапно сделал открытие, что...
В #ESPHome завезли:
- поддержку ZigBee
- поддержку nRF52
- поддержку Thread (ESP32-C5, ESP32-C6, ESP32-H2)
То есть уже можно пилить всякие домашний IoT не чертыхаясь от WiFi и пользоваться мешем 🎉
素晴らしい！
#hardware #home #IoT #SmartHome #ZigBee #Thread #ESP32 #nRF52 #nrf52840 #ESPHome #HomeAssistant #mesh #log #news #nice
-
I’d like to build an #ESPHome device for data collection/display during an extended #poweroutage.
Ideas
1. powered normally via #USB / #ACpower
2. support second power source with AA/AAA battery backup: obtained easily, replaceable, no recharging
3. collect from cheap/common #Bluetooth #sensors (i.e. temp)
4. does not require a network (i.e. network down in power outage)
5. store data when #HomeAssistant is not available
6. upload data later
7. show information on a local #display -
Zigbee support for ESP32 in ESPHome has been merged into the dev branch! 🥳
-
Yesterday I installed the first of two devices which will allow me to have cloud-free automation control of our HVAC systems. We have Mitsubishi heat pumps and air handlers (similar to a traditional 'central air' system but vastly more efficient), and of course Mitsubishi offers their 'Kumo Cloud' system for automation. There are various integrations for Home Assistant to connect to Kumo Cloud, and it has a mobile app, but I don't want a vendor-managed cloud service in the path.
I used an ESPHome component called mUART which contains code for the mostly-undocumented-but-heavily-reverse-engineered protocol that these units speak on their UART ports. I also used some really nice boards named MahtanarM made by one of the primary authors of the ESPHome integration. The software is FOSS, the hardware is not 'open hardware' but it's quite simple, and these boards are not required they are just a quick and easy way to get things connected. One of the benefits this particular ESPHome component (there are at least four out there) is that it supports pass-through so the Mitsubishi wireless thermostat/controller continues operating normally - this is important for the Spousal Acceptance Factor.
This now the third such integration I've installed. I also have our LiftMaster garage door opener using the 'ratgdo' ESPHome component instead of the MyQ cloud, and our Rheem water heater using the 'econet' ESPHome component instead of the EcoNet cloud. All of this is FOSS, and the hardware to make the connections is simple and inexpensive.
https://muart-group.github.io/
https://github.com/tinwer-group/mahtanar
https://ratcloud.llc/
https://github.com/ratgdo/esphome-ratgdo
https://github.com/esphome-econet/esphome-econet -
My "Buurtmelder" (“Neighbourhood Notifier") project is coming along nicely.
It's an ESP32/RP2040-based device with a 433Mhz receiver that can be used to sniff RF codes sent by (cheap) home alarm systems and broadcast alarm activations to the entire neighbourhood (because neighbours are always closer than police in case of emergencies).
Initially it used LoRa for broadcasting, but because it has some reliability issues it now uses MQTT-over-WiFi with a LoRa fallback.
You can also add "beeper satellites” around the house so you don't have to be near the terminal to see if there's an active alarm. When there's an alarm, the main terminal will use ESP-NOW to tell the beepers to start beeping.
#esphome #homeautomation #homeassistant #lora #espnow #esp32 #rp2040 #mqtt #makers
-
Seems to be working. I’m going to test it with my ongoing project and it everything works as expected, a PR will follow.
-
Working on encryption support for ESP-NOW in ESPHome: https://github.com/robertklep/esphome/tree/esp-now-encryption
I’ve reached the point where configuration and compilation isn't failing anymore 😅 So tomorrow I'll check and see if it actually works as intended, and then hopefully soon a cheeky PR.
-
Working on a distributed alarm system, where an alarm (burglar, panic, fall, etc) is propagated to the rest of the street, using ESP-NOW between the ESP32C3 and the Seeed SenseCAP Indicator, and LoRa between the Indicator and other Indicators running at our neighbours’ houses.
The ESP32C3 is going to be hooked up to a cheap alarm system (hooked up to the siren output, probably); when the alarm sounds, it will send a message to the Indicator it's paired with, which in turn will broadcast the message across the rest of the street.
Initial tests show that the Indicator should have a range of at least 500m, which is more than enough. If not, I can always look into rebroadcasting.
-
Water Monitor Measures The Cost Of Your Shower Thinking Time - The shower is one of the top thinking places for many of us, but can get a bit out... - https://hackaday.com/2022/08/26/water-monitor-measures-the-cost-of-your-shower-thinking-time/ #batteryhacks #greatscott #techhacks #esp8266 #esphome
-
A new max7219 digit display running #esphome has been programmed in the space, must add more pixels
