Alright, so I’ve been doing some testing with different ESP32 models as proxies in different configurations. The only time I did see errors like you mentioned is when there is in fact a communications issue. Could be interference, but in my case I was seeing it due to range. I already know from previous testing that the signal is pretty bad in my situation as it is due to the location of the module close to the metal frame and meshing covering the fireplace front. So that was the easiest issue for me to reproduce.
In that case it didn’t really make a difference which module saw the fireplace if the one with the best signal path to it didn’t have a signal that is also usable. That’s when the errors appeared. I’m guessing there could be an imbalance of the signal levels on the RX/TX sides (i.e. the ESP32 can “hear” the fireplace just fine, but the fireplace can’t really hear the ESP32) and the BT proxies deciding that the one ESP32 that “hears” the fireplace the best must also be the one that the fireplace can hear the best. I will have to look into that theory more closely.
What I did find is that the metal meshing that is in front of the glass has a very significant impact on signal quality.
In my instance the Bluetooth controller sits under the firebox towards the front of the fireplace, near the IFC. When the ESP32 is located facing the fireplace head on I get a barely usable signal, even when very close by. If it is off to the side, about 2m away (which is where I usually have my ESP proxy), I get a signal that is not great but very stable. In this instance I’m hitting the side of the framing around my fireplace.
As a result I will implement more logging in the bonaparte library to include signal information in the output to allow for quicker diagnosis of what’s going on in that regard.
I’ll try to find some time on the weekend to work on it.
Would love better signal reporting – I am using a high performance bluetooth dongle on my server, sitting just behind the wall where the fireplace sits. I also have a front door lock ~1000 square feet and 3 walls away connected via bluetooth.
I occassionally (once a week, for 4-8 hours) see the fireplace connection drop, never happens with the front door lock.
Not sure if its a connection issue or something else – but being able to diagnose signal strength would at least narrow down the issue.
Yea it works great, using a ESP32 would be better due to cost. I am sure that is just about all that is in the napoleon part. I purchased the Napoleon Bluetooth Control Module part number (W190-0090) and I have a Turenorth TN24 gas stove that has a proflame 2 IFC. It was ~$85 with shipping so a lot more expensive than a ESP32.
I am not sure what all Proflame2 IFC modules it will work with but mine does not have the green print that is required for the wifi dongle to work.
Thank you so much for looking into it!!! I will try to open things up and place the M5Stack Atom Lite as close as possible then play around again to see if that resolves things.
Sub’d. Have a Napoleon fireplace and very interested. Will get this installed this weekend
UPDATE: Gave it a shot, but I think my BT dongle (which is connected to my HA server in the basement) doesn’t have the reach to the top floor for the fireplace.
I use a MacMini 2011 with a usb bluetooth dongle
[ TP-Link USB Adapter for PC, Bluetooth 4.0 Dongle Receiver]
Bluetooth integration is enabled already, so that sucks for now.
Will stay tuned for any updates with the ESP modules
All I get is this when attempting to add the integration
You’ll probably be unhappy with that one as these adapters do not have a reset pin. If they stop responding, there is currently no way for the kernel to reset them automatically and you’ll get the pleasure of unplugging and replugging it manually.
Click on the link titled “Bluetooth Proxies with ESPHome” to learn how they work. It’s very simple to set up, as the Bluetooth proxy is auto-detected by Home Assistant if it is on the same network. You can add multiple of those around your house.
just an update… regardless of there being no reset button on realtek bluetooth dongle w/external ant that I mentioned, this arrived today and HA picked it up immediately. But I believe the distance and/or interference between the server to the fireplace is too great for this device. I was unable to see anything with it, so I will continue down the path of bluetooth proxies.
I did also order the 2 Atom devices mentioned above, just looking for a short power adapter with a USB port to power the Atom M5 stick. The fireplace is someone confined on space under it.
I rebooted home assistant and still getting the same interview screen when attempting to enable my napoleon fireplace. The M5 Bluetooth proxy is 3 feet from the fireplace.
I feel like I am missing something… anyone have a suggestion?
EDIT: (UPDATE)
holy cow… finally got it working.
ESP device was perfectly fine, it was the fireplace that for whatever reason was not discoverable on BT. Had to unplug it to reset it, then it popped up immediately.
Starting to play with controls now…
Big thanks to @FelixKa for the integration and @bdraco for your guidance on getting a BT Proxy!
This just made winter a little more FUN!
And for complete-ness…
I took an apple 5w usb-a power plug (smallest ones they make) and plugged then in under the fireplace in the last outlet, then inserted the AtomU into it. Hopefully these things are stable and do not require much interaction.
As far as I know (and that’s quite a lot now, as it pertains to the Napoleon controller) there is no update mechanism built into the official app. So there are no updates to be had.
Hello, and thank you for the integration! My fireplace unit has the LED lights and would love to get that feature included. Sadly I do not yet have the knowledge to do it myself. Is there any chance of getting it implemented with my assistance?
