Posted on

Product updates Q3 2025

Product ID fixed

Most products are now getting an internal code ID ‘burned’ into the memory of the ESP32 chip during production to identify the product and the batch number of its’ circuit board.
The latest EMS-ESP development firmware 3.7.3 version 15 or higher will detect this ID and fix the board profile accordingly.
Firmware 3.7.3 is not a stable release yet, but as the latest stable 3.7.2 does not have the internal code to look for this ID, all production boards which contain a product ID are loaded with the 3.7.3 dev15 or higher firmware.

In the past, a faulty firmware update could for instance reset the board profile to the default S32, which would render the Ethernet port inoperable. You would then have to log in via WiFi, set the board profile back to E32 V2 and reboot to get the Ethernet port working.
With the product ID fixed inside the ESP32, the firmware will then automatically recover and use the correct board profile.
If you are a developer who likes to play with custom board profiles on a BBQKees Gateway product, you need to take into account that the default EMS-ESP firmware will keep setting the board profile according to the product ID found.

The product ID is burned into the ESP32 chip, so this is persistent over firmware updates and will even survive a full erase of the flash memory.

How can I check if a product ID has been set?

If you visit the Hardware tab on the Status page of the web interface, the ‘Hardware device’ will show the BBQKees logo and will tell you which board revision and batch number it is.
If it does not show the BBQKees logo and give just the ESP32 chip revision, it will not have the product ID fixed.

Alternatively, you can use the terminal to check. Open a terminal on the Gateway via Telnet or serial en type in ‘show’.

If there is no fixed product ID, the model description will be empty. If a product ID was found, it will show the specification. Below on the left a board with product ID and on the right a board without product ID.

What happens when I load new firmware on a BBQKees product without a product ID?

Nothing will happen to the board settings when you update the firmware on an existing BBQKees product without fixed product ID. So it is backwards compatible.
However, if the product ID is set, any firmware from 3.7.3 dev15 and onward will fix the board profile to the one belonging to the product ID. So custom board profiles may be overruled.
If you use a custom board profile on a genuine BBQKees board you are probably a developer yourself so you will know how to change the board profile back to a custom one.

Discontinuation of the EMS Gateway S3

The manufacturer of the grey enclosure of the S3 and S3-LR Gateways has stopped production entirely earlier this year. We purchased all remaining stock we could find but our S3 enclosure inventory is almost depleted now.

Because of this, we were forced to revisit our product portfolio.
The S3 and E32 V2 Gateway models have only slight differences aside from the absence of LAN/Ethernet on the S3. As the more feature-rich Gateway E32 V2 is already our existing main product, we basically have an S3 ‘successor’ at hand.
Designing an completely new S3-like product in a new enclosure from scratch is a huge amount of work. It’s not just selecting an enclosure and fitting the circuit board to this new box, but you need to go through all the regulatory and compliance testing again which is both a pain in the ass and expensive. And after that create new manuals, instructions, design new packaging, incur new GTIN/EAN fees, etc etc.
Therefore we decided to focus solely on the E32 V2 instead of creating an additional successor of the S3.

Over the past 2 years we had plenty of time to refine the existing E32 V2, which will be able to handle all the stuff we can think of in the coming years thanks to its big and future proof 16MB Flash and 8MB PSRAM memory.

Time frame remaining stock

We will discontinue the S3 product line after the current stock has sold. We expect to sell out within a number of weeks or by the end of Q3 2025 at the latest. So if you like to get your hands on a small WiFi-only EMS Gateway you have to decide soon!
There will not be a sale on the remaining S3 or S3 KIT products. Business customers who would to get some S3 before it sells out, just send us an email for a quote.

The previously available S3-LR will not get into new production anymore obviously (we had a number of people on a waiting list).

Warranty and parts availability

The S3 Gateway will still be supported in future EMS-ESP firmware releases and you still get the 2-year BBQKees warranty. We are committed to long term service and are thus keeping an inventory of spare boards and other S3 parts for warranty replacements.

Posted on

Adding DS18B20 temperature sensors to your Gateway (without soldering)

This guide will show you how to easily add some DS18B20 temperature sensors to your BBQKees EMS Gateway.
No soldering skills necessary.

You can add DS18B20 sensors to all BBQKees Gateways ever made by using the small 3-wire JST cable that is supplied with each Gateway order.

The easiest to use are waterproof DS18B20 sensors with a cable. These are cheap and convenient to use.
We do not sell these sensors, they are available at many places online.


You can add a number of these sensors in parallel to a Gateway. The specific number varies depending on the length of the cable and the type of DS18B20 sensor used. But in general 10 sensors is usually not a problem.

Make sure the sensors are all of the same DS18B20 sub-type and do not mix parasitic mode with normal mode wiring.

Prerequisites and parts

  • BBQKees EMS Gateway
  • 3-wire JST ZH cable
  • DS18B20 waterproof sensors with cable
  • 3 Wago 221 splicing connector with levers or f.i. a ‘lusterklemme’
  • Wire stripper
Parts for adding DS18B20 sensors

Step 1: Strip the wires on the JST cable

You need to strip the wires on the JST cable by about 10mm. If the wire ends are soldered, it’s better to cut them off at the point of the wire insulation before stripping. This will make stripping the wires easier.

Stripping JST cable
Stripped JST cable

Step 2: Strip the wires on the DS18B20 sensors

Strip them 10mm, or at least the same length as you stripped the JST cable.

Step 3: Tie the wire ends together

Tie the wire ends together. Tie each color separately. So all yellow wires together, all black wires together and all red wires together.
If there are too many cables, you can also do 2 or 3 cables each time.

Tied cables

Step 4: Put each wire color in a separate Wago clamp

This step is where you could make the most errors so be careful here.

You need to insert each cable bundle of it’s own color into a separate Wago clamp.
DO NOT put any other wire color in the same clamp as this will cause shortcuts.

Wire ends in Wago clamps
End result DS18B20 sensors in Wago clamps

Step 5: Insert the JST plug into the EMS Gateway

Insert the JST plug into the JST connector in the Gateway. You need to keep the flat part of the plug at the top. Make sure it is fully inserted. See the image below for the correct orientation.

It’s best to turn off the Gateway before doing this. If the Gateway does not boot afterwards, you made a shortcut in the wiring.

Inserting the JST cable

Step 6: Check the EMS-ESP web interface and rename the sensors

If everything went correct, you will see the sensors appearing in the Sensors tab in the web interface.

Sensors tab EMS-ESP web interface

Each DS18B20 sensor has it’s own unique address identifier. These identifiers are displayed.
You can click on one to rename it.
After you rename a sensor, it is also renamed in MQTT and Home Assistant etc.

Renaming sensors

If you added a bunch of sensors at the same time, it can be hard to distinguish them.
You can heat each sensor separately with f.i. a hair dryer or heat gun and see which one gets hotter.

And that’s it!

Posted on

Updated guide on integrating an EMS Gateway into your Home Assistant

I have updated the guide on how to connect an EMS gateway into Home Assistant.
The old guide was a bit outdated, and as most EMS Gateway customers use Home Assistant as their Home automation, up to date guides are necessary.

Logo wordmark Home Assistant

It uses a fresh install of Home Assistant version 2025.2.1 installed as HA OS on a Raspberry Pi as a starting point. So only the initial Home Assistant setup has been done. Creating a HA user and that’s it before we configure anything else.

Steps

In short these are the steps you need to take to get all the EMS entities into Home Assistant in a few minutes:

  • Log into Home Assistant
  • Create a new user in Home Assistant for MQTT
  • Install the MQTT integration in Home Assistant
  • Connect the EMS Gateway to the bus and log into the web interface
  • Configure the MQTT settings in the Gateway
  • BOOM! all entities will show up in Home Assistant within a few minutes.

See the following link to the wiki: https://bbqkees-electronics.nl/wiki/home-automations/home-assistant-configuration.html

Posted on

28 October 2024: Firmware 3.7.0 release now available

After 6 months and 47 beta versions EMS-ESP32 firmware 3.7.0 has finally been released. It packs hundreds of improvements, new features and bug fixes.

Updating to 3.7.0 from 3.7.0dev

If you were already on a development version of 3.7.0, you can update the firmware via the update feature of the web interface.

Updating from 3.6.4 or 3.6.5 to 3.7.0

If you are currently on 3.6.4 or 3.6.5, you cannot update via the web interface directly.

Clicking on the bin file will result in an error. This is because after 3.6.5 the firmware bin file naming scheme has changed, so the 3.6.5 firmware is looking for a bin file on the Github repository that does not exist.

In this case go to the releases page of the firmware repository and download the correct bin file.

You can use the table here for getting the right file.

After you have downloaded this file to your computer, you can upload it via the EMS-ESP web interface.

After the reboot of the Gateway, press F5 to clear the browser cache otherwise there may still be some left overs of the old interface in the cache, causing strange UI combinations of both the old and the new user interface.

Possible issue with updating to 3.7.0 with the E32 V2

In some cases after the new firmware upload, the Ethernet interface of the E32 V2 may be disabled. Don’t worry, it’s not dead. In these cases the board profile of the firmware has accidentally defaulted to the S32 Gateway, which has no Ethernet.

To correct this, log in to the ems-esp WiFi network, go to settings and change the board profile to E32 V2. Then save and reboot and Ethernet will become alive again.