After much experimentation I have been able to successfully integrate my FlameBoss 400 into HA. Currently, I have just the basics but the foundation for integration is here.
To acquire userID and authentication token, execute in an elevated CMD prompt or in a Linux Shell:
curl -X POST https://myflameboss.com/api/v4/sessions -d session[login]=(email_address) -d session[password]=(password)
Response should be: {“user_id”:(your_userID),“username”:"(your_username)",“auth_token”:"(your_authentication_token)"}
Take note of the userID and authentication token
Setting up MQTT Broker bridging:
I am assuming you already are using MQTT Broker within HA AND you are using Samba in HA
Go to your \(your_HA)\share
Create a directory named mosquitto
Create a file named flameboss.conf
Add the following to your flameboss.conf file:
connection myflameboss.com
address (server from above step [s7.myflameboss.com]):1883
topic flameboss/(your_deviceID)/send/open in 1 homeassistant/sensor/
topic flameboss/(your_deviceID)/send/data in 1 homeassistant/sensor/
bridge_attempt_unsubscribe true
bridge_protocol_version mqttv31
cleansession true
remote_username T-(your_userID)
remote_password (your_authentication_token)
In HA goto Supervisor->Mosquitto Broker->Configuration and change your options to match for customize section:
If you want the additional information you can connect your MQTT Explorer to HA and see both the homeassistant/sensor/flameboss/(your_deviceID)/send/open and also homeassistant/sensor/flameboss/(your_deviceID)/send/data which are the two topics your FlameBoss will communicate to the myFlameBoss MQTT cloud servers.
The password needs to be the authentication token you received when doing the CURL. Not your flame boss password. Also the userID should be coming from that same CURL request but you append a “T-“ in front of the userid.
I also am assuming you named the file flameboss.conf correct?
What mqtt broker are you using. I can see it is mosquitto, but how did you install it?
I installed the Mosquitto broker add on using the supervisor panel. I am running the HASS image on a RPi4.
The password needs to be the authentication token you received when doing the CURL. Not your flame boss password. Also the userID should be coming from that same CURL request but you append a “T-“ in front of the userid. I also am assuming you named the file flameboss.conf correct?
I am using the token received from the CURL, not my flameboss password. I thought based on your example the UserID needed to be appended with the T-. I have removed this and now my flameboss.conf file reads:
Not that I don’t love what you have done, but the flame boss device itself listens on http & mqtt ports. I connected HA straight to the device over MQTT… no cloud, no auth, no problem. Still used the value templates ya have. Thought you may want to know.
Please write up and share how you did this. I was not able to connect to the device directly and still be able to use the cloud integration. It was one or the either.
Note: It appears that the connection limit to the device is like 2 or 3. So it you are browsing via MQTT Explorer, have a mosquitto_sub running all while trying to get it to bridge - that may be your issue.
Hi! this looks great. Didn’t dive into it yet, since I’m still considering wich one to buy. Will it work with the flameboss 500 the same way you think?
Hi there! This really is an amazing guide to implement this device with mqtt. I’m not too technical, but I got this to work, almost… I hope you can help me out a bit! I have two problems (which may be related, but i’m not sure). I have the following in my broker log:
This seems that something is not right, but I don’t know what…?
Also: the sensors seem to update but not showing the right data. All I did was remove the value_template (because I want to use Celsius) and add my device ID.
All sensors show this:
{“name”:“temps”,“cook_id”:2404791,“sec”:1638915992,“temps”:[196,189,-32767,-32767],“set_temp”:1072,“blower”:0} °C
Would you know how to fix those sensors, and even add my third and fourth sensor (I have just a 4 probe thermometer, no fan). Is there more info to be extracted, like battery level, cook time etc? Or don’t they publish that on mqtt?
Thanks for your help and great work on this so far
Regards, Patrick
For connectivity you will want to test your connection using the above steps to get your flameboss information using a tool like MQTT Explorer. If you can connect with that then HA should be able to connect if you setup the mosquitto.conf file correctly.
For the Celsius, Flameboss sends information as decidegrees. So to change to Celsius you just divide by 10.
As for the additional sensors - you can see you have (4) probes from the “temps”. The -32767 means you do not have any probes connected to those two ports. To create the 3rd and 4th sensor you would just need to add two additional “Probe Temp” platform templates.
Thanks a lot for your explaination!! I do get the right results now, that’s awesome! I thought the value_template was for converting to F only, but now I see it is to split up the probe information as well!
I do get the information now, but the flow of mqtt messages is not that constant as I would expect. How do you experience this? When I open the web-ui of flame boss (just by going to the internal ip in a web browser), I always get the same information as the device display shows. MQTT is sometimes not updated for 20+ minutes, see my screenshot
Do you know of a way to make the flow of information more constant?
Would the way @theOrakle suggest to connect make any difference in the messages that are received? I did not get that to work without knowing the redacted section…