Hi… what MQTT are you using? i try the add-on Mosquitto broker but i was able to make it work…websocket issue… Any cookbook are print screen will help.
I use Mosquitto for years running fine on HA. Where did you get stuck? What do the logs say? What version of HA are you running and how did you install HA?
Hello
i am running HomeAssistant on a RaspberryPI 3,
- Core-2021.2.2
- Operating System Home Assistant OS 5.11
- Mosquitto broker version: 5.1
the Mosquitto broker is working with my Victron integration
i am trying to integrate Afterburnuer (DieselHeater) to my HomeAssistant
the error message is
AMQJS0007E Socket error:undefined.
Broker (must be websocket)
Any help would be apreaciated
`
Maybe you could try with a custom .conf file and enable websockets like this.
The options to enable websockets are:
listener 9001
protocol websockets
@Burningstone tks for your help… but i getting a bit complicated for me :-(… i really don’t how to do that 
Hi
How did you go with Afterburner integration?
I added this to my config so i could access the web UI in HA
panel_iframe:
afterburner:
title: heater panel
icon: mdi:radiator
url: http://192.168.1.31:80
I did try to connect to the MQTT broker too when i received my afterburner but then realised there needs to be a add-on created in HA so that HA knows what to listen for form the afterburner.
Ill have a look at my settings and i post a pic of my MQTT settings.
Thanks
1 Like
Did you get sorted with this, looks to be broker (MQTT) is not set, change core-mosquitto to your home assistant IP or homeassitant.local if hostname is default.
I’ve got my afterburner en-route so researching issues beforehand…
I just got mine working with help from Ray, you need to type your IP address in Broker port 1884 for websocket (default Mosquitto broker settings), my Afterburner settings attached and Home assistant config below. They needed to be added manually as wouldn’t auto discover the sensors/switch… Happy automating 
switch:
- platform: mqtt
name: Afterburner
state_topic: “Afterburner34C224/sts/RunString”
command_topic: “Afterburner34C224/cmd/RunState”
payload_on: “1”
payload_off: “0”
sensor: - platform: mqtt
state_topic: “Afterburner34C224/sts/TempDesired”
name: “Heater Desired Temperature” - platform: mqtt
state_topic: “Afterburner34C224/sts/TempCurrent”
name: “Heater Current Temperature” - platform: mqtt
state_topic: “Afterburner34C224/sts/Temp2Current”
name: “Heater Current Temperature 2” - platform: mqtt
state_topic: “Afterburner34C224/sts/TempBody”
name: “Heater Body Temperature” - platform: mqtt
state_topic: “Afterburner34C224/sts/FuelUsage”
name: “Heater Fuel Usage” - platform: mqtt
state_topic: “Afterburner34C224/sts/TotalFuelUsage”
name: “Heater Fuel Used” - platform: mqtt
state_topic: “Afterburner34C224/sts/FuelRate”
name: “Heater Fuel Rate” - platform: mqtt
state_topic: “Afterburner34C224/sts/InputVoltage”
name: “Heater Voltage” - platform: mqtt
state_topic: “Afterburner34C224/sts/PumpActual”
name: “Heater Pump” - platform: mqtt
state_topic: “Afterburner34C224/sts/PumpFixed”
name: “Heater Pump Fixed” - platform: mqtt
state_topic: “Afterburner34C224/sts/FanRPM”
name: “Heater Fan RPM” - platform: mqtt
state_topic: “Afterburner34C224/sts/GlowVoltage”
name: “Heater Glow Plug Voltage” - platform: mqtt
state_topic: “Afterburner34C224/sts/GlowCurrent”
name: “Heater Glow Plug Current” - platform: mqtt
state_topic: “Afterburner34C224/sts/ErrorString”
name: “Heater Error State” - platform: mqtt
state_topic: “Afterburner34C224/sts/RunString”
name: “Heater State” - platform: mqtt
state_topic: “Afterburner34C224/sts/Thermostat”
name: “Heater Glow Thermostat”
4 Likes
Tks it is working
1 Like
Hi Ashley
Thanks for looking up this info.
Did you just copy the switch and sensor info into the config file.
My Mqtt broker hasn’t detected the heater
Was there any thing else i need to do
I’m adding this post to show how to add the afterburner as a device in the Mqtt integration.
Hi Nicko1,
Sorry for the late reply, where is states Afterburner34C224/ in the config you will need to change 34C224/ to your own specific Afterburner…
But here’s another link i’d like to point you to from pturner1989, this show’s a better way now with perfected thermostat option, but again change his 626E9C/ config to your own…
2 Likes
Where is this thermostat bought from?
This a great little device from down under to control your cheap Chinese diesel heater - a bummer for the rich who can afford a £1k+ Webasto unit as it does not work with that 
Head over to Home and talk to Ray.
3 Likes
I’ve tried this, it’s cool.
I had two problems though. I does not work remotely (http vs https issue) and although I am Ray’s one of the biggest fan, I don’t particularly like the aesthetics of the web page
Anyway, thanks for posting it!
I agree, the device is amazing and mine is used daily however the interface is not the strongest area, easy to rectify in Home Assistant though as most of the functionality can be lifted and shifted into a nice dashboard.
Hi All,
Looking at this implementation & seem to be hitting a problem that’s out of my league.
I’m Getting Entities I read for some things but also getting an error in the code.
Any thoughts?
My Code in Configuration.yaml
mqtt:
climate:
- name: Van Heating
action_topic: "AfterburnerFF4E3C/sts/RunState"
action_template: >
{% if value in ("0", "1", "6", "7", "8") %}
off
{% elif value in ("10", "12") %}
idle
{% else %}
heating
{% endif %}
current_temperature_topic: "AfterburnerFF4E3C/sts/TempCurrent"
max_temp: 35
min_temp: 8
modes:
- "off"
- "heat"
mode_state_topic: "AfterburnerFF4E3C/sts/Run"
mode_state_template: >
{% if value == "1" %}
heat
{% else %}
off
{% endif %}
mode_command_topic: "AfterburnerFF4E3C/cmd/Run"
mode_command_template: >
{% if value == "heat" %}
1
{% else %}
0
{% endif %}
precision: 0.1
temperature_command_topic: "AfterburnerFF4E3C/cmd/TempDesired"
temperature_state_topic: "AfterburnerFF4E3C/sts/TempDesired"
temp_step: 0.5
sensor:
- name: Afterburner Status
unique_id: afterburner_status
state_topic: "AfterburnerFF4E3C/sts/RunString"
- name: Afterburner Error
unique_id: afterburner_error
state_topic: "AfterburnerFF4E3C/sts/ErrorString"
- name: Afterburner Internal Temperature
unique_id: afterburner_internal_temp
state_topic: "AfterburnerFF4E3C/sts/TempBody"
device_class: temperature
unit_of_measurement: °C
state_class: measurement
- name: Afterburner Consumption (Total)
unique_id: afterburner_consumption
state_topic: "AfterburnerFF4E3C/sts/TotalFuelUsage"
unit_of_measurement: mL
state_class: total_increasing
- name: Afterburner Pump Rate
unique_id: afterburner_pump
state_topic: "AfterburnerFF4E3C/sts/PumpActual"
unit_of_measurement: Hz
device_class: frequency
state_class: measurement
- name: Afterburner Fan Speed
unique_id: afterburner_fan
state_topic: "AfterburnerFF4E3C/sts/FanRPM"
unit_of_measurement: RPM
state_class: measurement
- name: Afterburner Glow Plug
unique_id: afterburner_glowplug
state_topic: "AfterburnerFF4E3C/sts/GlowCurrent"
device_class: current
unit_of_measurement: A
state_class: measurement
The Error I’m Seeing in the editor.
Some of the data I can get, but not current Temp.
Any thoughts?
Edit,
In the MQTT Intergration I’m only seein 7 Entities,
They are the ones in the second part on the code,
under the Sensor Section.
Other thing I just found is that if I move the yaml to a different file,
as in mqtt.yaml, and put in an include in configuration.yaml, I don’t see the same error showing in the code editor.
The same 7 entities all still appear Ok.
mqtt: !include mqtt,yaml
Hi Phil23,
Strange as your config looks the same as mine but mine not showing an error in file editor.
Where it states value not accepted, Valid … does it say anything else after that ?
Have you tried installing MQTT Explorer on your laptop to monitor all MQTT traffic during operation. it’s what helped me build all them entities.
Have it Working now, but it seems to not be receiving a few topics.
The two I can’t get are FuelUsage & FuelRate as seen here.
Have you tried adding them?
They are showing up correctly in MQTT Explorer.
These are the two blocks of code that are not returning values.
- name: Afterburner Current Usage
unique_id: afterburner_current_usage
state_topic: “AfterburnerFF4E3C/sts/FuelUsage”
unit_of_measurement: mL
state_class: total_increasing
- name: Afterburner Fuel Rate
unique_id: afterburner_fuelrate
state_topic: “AfterburnerFF4E3C/sts/FuelRate”
# unit_of_measurement:
# state_class:
Tried removing the Unit & State_Class, but the Broker is still not passing them on to Home Assistant.