Hi. Can’t test this but for me:
If you are using Mosquitto for Hass, check the log journal of Mosquitto ; you Can see if login of your dev board is Ok or not.
On the configuration page maybe you have a submit or save button to store the informations in your dev board.
Regards. Emmanuel.
I’m not sure, but I see the Mosquito add-on has a login option. If you don’t configure this, surely it doesn’t need to be configured in the integration settings?
Hello Alex.
Anonymous connections are probably not allowed in mosquitto broker, I think, so in this case it goes through a HASS user.
If you are using the Hass MQTT Mosquitto broker and Ben’s project (Edilkamin_BT), then here’s how it should work:
Install / Home Assistant / Add-ons / Mosquitto broker.
Your MQTT broker uses the IP of your Home Assistant server.
Mosquitto broker configuration.
To keep it simple, do not change anything here. (The default port of the broker is 1883)
Create a new user for Mosquitto MQTT through your Home Assistant frontend Settings → People → Users (i.e., not on Mosquitto’s Configuration tab).
Notes: This name cannot be homeassistant or addons, as these are reserved usernames.
If you do not see the option to create a new user, make sure that Advanced Mode is enabled in your Home Assistant profile.
You can find the documentation in your Home Assistant instance.
For the Edilkamin_BT project, you must then provide the following information. Take a look at:
GitHub - netmb/Edilkamin_BT
WIFI :
SSID=‘“yourwlan”’
PASSWORD=‘“yourwlan_password”’
MQTT:
HOST=‘“mqtt_ip”’ => IP of your Home Assistant server. The Mosqitto broker.
PORT=‘1883’
USER=‘“mqtt_user”’ => new user for MQTT via your Home Assistant’s frontend Settings
PASSWORD=‘“mqtt_password”’ => new password for MQTT via your Home Assistant’s frontend Settings
NTP:
NTP_SERVER=‘“pool.ntp.org”’
NTP_GMT_OFFSET=‘7200’
WARNING:
When you start your Wemos module for the first time, it will create a WIFI access point to set it up. (192.168.4.1 / Edilkamin_BT_AP)
I think the Configure WIFI button allows you to provide this information.
When you save via the access point, the configuration is stored permanently in the Wemos memory.
The easiest way to reconfigure your Wemos might be to restart the Webflash?
Hope that helps… You’ll let me know. Emmanuel
Hi Emmanuel,
Your english is fine. I understand it perfectly.
At the moment I’m waiting for my ESP32’s.
I understand Ger is already busy. Perhaps he has a working system. 
Hi, an MQTT server must be running and the data must also be entered correctly in the setup. The devices are created in Home Assistant via MQTT, which is also used to perform status updates.
Hi all,
Will try ASAP, will keep you posted, thanks all
Yes!! Working!! Unbelievable I made it work. I had never worked with MQTT before, I tried earlier but was then too complex for me.
I made screenshots during install. I will create an manual with screenshots and will upload it here as pdf if possible and a good idea? Need to go for dinner in minutes. I am very happy, good work Ben!
Hi Ben, I had a post here for couple of minutes as I thought I lost BT connection but actually all is still working. I keep my fingers crossed. Thanks Ben, all, working on manual with screenshots right now
The original remote control and the ESP cannot be used in parallel; unfortunately, the oven can only operate one Bluetooth connection at a time.
The ESP regularly checks the status of the oven—to do this, it establishes and terminates the Bluetooth connection (just like the original remote control). The ESP terminates the connection between status queries and commands. Unfortunately, it is not possible to establish a permanent Bluetooth connection with the oven.
In addition, there must always be a delay between commands, as the oven does not like receiving commands too quickly. None of this is ideal, but it is due to the oven’s Bluetooth implementation.
Thanks Ben, still working here I think and hope. First thing I did now is quickly making a personal manual how (I think) I got it work 
I am not an IT man. So I have a pdf manual now, I think I can’t upload a pdf here right? Otherwise who wish to have send me a pm and we will find a way too share. Thanks a lot Ben.
Hello, FYI, the API has been updated to version 1.6.0, and it seems to be working fine in HA.
Just set "requirements": ["edilkamin==1.6.0"] in the manifest.json file, restart HA, and enjoy.
All credits go to AndreMiras and julcollas who updated the API 
Worked for me.
Thank you
Ah ok, that is also good news and I have a spare then if needed later.
This morning my living room is heated perfectly by the Bluetooth solution of Ben.
What I can tell is this solution acts much quicker then the nghaye integration although also perfect.
Gives a good feeling that I am not dependent anymore of the servers and Internet which edilkamin is using.
Thanks for updates
Ger
I had issues with Ben solution some time ago. This is why I dont use it although its a better approach than a cloud based one.
I should give it a try again to check.
Hi pck, don’t know your skills but I can send you a personal manual with screenshots during setup, maybe it helps.
Thanks a lot but I’m fine. The problem I hit with Ben’s solution is that my Celia was starting by itself. Sometimes in the middle of the night or when i wasn’t home. So , being a bit lazy, I stuck to the other solution.
I’ve reactivated the integration. At least HA “sees” the heater again. However, I do see that various settings can’t be adjusted. For example, I can’t control the power. I use this because I’ve built a kind of modulating control. Correct me if I’m wrong, but I suspect this isn’t due to the integration, because I still can’t do a lot in the app.
I’m going to seriously look into whether Ben’s version will work properly.
If you think about it, it’s ridiculous that almost every device in your home is controlled via a cloud solution.
I agree. I lately lost my Neato control because Neato’s new owner decided to pull the plug.
Regarding Edilkamin integration, at first, I also lost some entities. I reloaded it and they came back. Maybe it will help.
Hello,
I’m having the same behaviour.
With some struggle I made The Mind official app work again, update Algra Integration, now I can see the stove, power on and off, but unable to send other commands (eg. Set power level or power on/off fans) that was able before EK screwed things up.
Sorry for my poor English.
Cheers,
Chuck26
That shouldn’t happen. The ESP regularly checks the status. The commands are not sent. It could be that the oven uses other Bluetooth datagrams, but I can’t really imagine that, because it’s not mentioned in the official app.
Maybe you should try the latest version again. I’ve been using it for two years now and only experienced strange phenomena at the very beginning when I was still testing/debugging.