Hello everyone, I wanted to share my recent experience integrating Esphuino and ESP32 devices into my smart home setup. It’s been quite a journey, but I’m thrilled to say I’ve managed to overcome the challenges and get everything working smoothly. Here’s my story:Earlier this week, I decided to enhance my home’s security system by adding presence detection using two Espruino Pucks and an ESP32 dev kit. The goal was to create a reliable setup where the ESP32 would detect the Pucks via BLE and trigger specific actions when I or my spouse entered or left the house. Sounds straightforward, right? Well, it turned out to be a bit more complex than I anticipated.Initially, I configured the ESP32 with the default scan parameters: interval 1s, window 1s, and duration 30s. The idea was to ensure the ESP32 could detect the Pucks reliably. However, after setting it up, I noticed occasional false triggers where the system would think I was away even when I was still at home. This was frustrating, especially since the Pucks were advertising every 375ms, which should have been more than enough for the ESP32 to detect them consistently.I spent hours tweaking the scan parameters, trying different intervals and windows, and even adjusting the duration. I scoured the Esphome documentation and forums, trying to understand how these parameters interact and affect detection reliability. It was a bit overwhelming, but I persisted.Finally, I stumbled upon a crucial piece of information: the scan parameters need to be carefully balanced to ensure they don’t miss any advertisements while also avoiding unnecessary power consumption. After some trial and error, I settled on adjusting the interval to 500ms and the window to 500ms, which seemed to provide a better balance. The duration was kept at 30s to ensure thorough scanning.To test the new configuration, I set up a controlled environment where I could monitor the ESP32’s detection accuracy. I moved the Pucks in and out of range, simulating my comings and goings, and watched the logs closely. The results were promising—false triggers decreased significantly, and the system responded more accurately to my presence.Of course, there were still occasional hiccups, especially when the ESP32 rebooted or when there was network interference. But with each adjustment, the system became more robust. I even implemented a fallback mechanism where the system would send a notification if it detected an unexpected away trigger, allowing me to address any issues promptly.Reflecting on this experience, I realize how important it is to thoroughly understand the underlying technology and configuration options when setting up smart home devices. It’s easy to overlook small details like scan parameters, but they can have a big impact on reliability. I also learned the value of persistence and meticulous testing when troubleshooting technical issues.I hope sharing my journey can help others who might be facing similar challenges. If you’re working on integrating BLE devices or optimizing scan parameters, don’t hesitate to reach out—I’m happy to share more details or tips. Happy tinkering!