EMS-ESP version 2.0
New Features in v2
- Supports both ESP8266 and ESP32
- New MQTT option to support Home Assistant MQTT Discovery (https://www.home-assistant.io/docs/mqtt/discovery/)
- A new web interface using React and TypeScript that's now secure as each URL endpoint is protected by issuing a JWT which is then sent using Bearer Authentication.
- In the Access Point mode there is a web Captive Portal
-
A new console. As in version 1.9 it works with both Serial and Telnet but now with a more intuitive Linux shell like behavior. It supports multiple connections and has basic security to prevent any changes to EMS-ESP. A full list of commands is below, here are the key ones:
helplists the commands and keywords. This works in each context.exitwill exit the console or exit the current context. CTRL-D does the same.CTRL-Ufor UndoTABfor auto-complete- Some specific commands are behind contexts. Think of this as a sub-menu. e.g.
system,thermostat. The path will always show you which context you are in.$is the root. suwill switch to super-user or Admin. The default password is "ems-esp-neo" and can be changed withpasswdfrom the system menu or via the Web UI (called secret password). When in Admin mode the command prompt switches from$to#.- Some settings can be changed in the console. The
setcommand will list them. showshows the data specific to the which context you're in. From the root it will show you all the EMS device information and any external temperature sensors. From a context it will be more specific to that context, e.g.show mqttfromsystemwill list MQTT subscriptions and show the status and queue.logsets the logging level.log offdisables logging. Uselog debugfor debugging commands and actions. This will be reset next time the console is opened.watchwill output the incoming Rx telegrams directly to the console. You can also put on a watch on a specific EMS device ID or telegram ID. Also choose to output as verbose text or raw data bytes. these in its 'raw' data format and also watch a particular ID.
-
There is no "serial mode" anymore like with version 1.9. When the Wifi cannot connect to the SSID it will automatically enter a "safe" mode where the Serial console is automatically activated (note Serial is always available on the ESP32 because it has multiple UARTs). The EMS-ESP will blink fast when in Serial mode. Connect via a USB with baud 115200 to see the serial console. Note in this mode the EMS will be disconnect so there will be no incoming traffic. Use only for debugging or changing settings.
-
The onboard LED behaves like in 1.9. A solid LED means good connection and EMS data is coming in. A slow pulse means either the WiFi or the EMS bus is not connected yet. A very fast pulse is when the system is booting up and configuring itself, which typically takes 5 seconds.
Uploading the firmware
-
If you're not using PlatformIO, use the command-line and Python. You can download Python from https://www.python.org/downloads/. Make sure you also get:
esptool, install using the commandpip install esptool- and for OTA updates later,
espotafrom https://github.com/esp8266/Arduino/blob/master/tools/espota.py usingpython espota.py --debug --progress --port 8266 --auth ems-esp-neo -i ems-esp.local -f <firmware.bin>
-
Grab the latest firmware binary from https://github.com/proddy/EMS-ESP/releases/tag/travis-v2-build
-
Uploading directly via USB.
For ESP8266:
esptool.py -p <COM PORT> -b 921600 write_flash 0x00000 <firmware.bin>note: if this fails try a lower speed like115200instead of921600.For ESP32:
esptool.py --chip esp32 --port "COM6" --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x1000 XX\.platformio\packages\framework-arduinoespressif32\tools\sdk\bin\bootloader_dio_40m.bin 0x8000 XX\.pio\build\esp32\partitions.bin 0xe000 XX\.platformio\packages\framework-arduinoespressif32\tools\partitions\boot_app0.bin 0x10000 <firmware.bin> -
Uploading over WiFi:
espota.py --debug --progress --port 8266 --auth ems-esp-neo -i <IP address> -f <firmware.bin>
Setting EMS-ESP up for the first time
- Connect to the Access Point called ems-esp using the WPA password
ems-esp-neo. When you see the captive portal sign-in with usernameadminand passwordadmin. Set the WiFi credentials and go back to http://ems-esp - First thing to check is if Tx is working and that you have a connect to the EMS bus. If it's showing an error try changing the Tx Mode from the settings page. Then check the Status (no need to restart EMS-ESP).
The Console
Connecting to the console will give you more insight into the EMS bus traffic, MQTT queues and the actual device information. The console is reachable via Telnet (port 22) or via the Serial port if using an USB (on baud 115200). To change any settings in the console you must be admin (use su with the default password ems-esp-neo). On an ESP8266 the Serial port is disabled by default unless it's unable to connect to the WiFi.
The call command is to execute a command. The command names ([cmd]) are the same as the MQTT command listed in the next section.
(* = available in su/Admin mode)
common commands available in all contexts:
exit
help
log [level]
watch <on | off | raw> [ID]
su
(from the root)
system (enters a context)
boiler (enters a context)
thermostat (enters a context)
set
fetch
scan devices [deep] *
send telegram <"XX XX ..."> *
set bus_id <device ID> *
set tx_mode <n> *
show
show devices
show ems
show values
show mqtt
system
set
show
format *
show users *
passwd *
restart *
set wifi hostname <name> *
set wifi password *
set wifi ssid <name> *
wifi reconnect *
pin <gpio> [data] *
boiler
read <type ID> *
call [cmd] [data] *
thermostat
set
set master [device ID] *
read <type ID> *
call [cmd] [data] [heating circuit] *
MQTT commands
Breaking change: The MQTT base has been removed in version 2. The hostname is only used as prefixed to the topic, e.g. ems-esp/status.
All commands must be written as {"cmd":<cmd> ,"data":<data>, "id":<n>}.
The id can be replaced with hc for some devices. cmd and data must be enclose in quotes as a string.
*boiler_cmd*
comfort <hot, eco, intelligent>
flowtemp <degrees>
wwtemp <degrees>
boilhyston <degrees> (negative value)
boilhystoff <degrees> (positive value)
burnperiod <minutes>
burnminpower <%>
burnmaxpower <%>
pumpdelay <minutes>
*thermostat_cmd*
--- without hc ---
wwmode <off | on | auto>
calinttemp <degrees>
minexttemp <degrees>
building <light | medium | heavy>
language <n> (0=de, 1=nl, 2=fr, 3=it) only RC30
display <n> (0=int temp, 1= int set, 2=ext. temp, 3=burner, 4=ww, 5=mode, 6=time, 7=date, 8=smoke) only RC30
clockoffset <seconds> (only RC30)
--- with hc ---
mode <auto | night | day | nofrost | heat | eco>
temp <degrees>
nighttemp <degrees>
daytemp <degrees>
nofrosttemp <degrees>
ecotemp <degrees>
heattemp <degrees>
summertemp <degrees>
designtemp <degrees>
offsettemp <degrees>
holidaytemp <degrees>
remotetemp <degrees>
control <0 | 1 | 2>
pause <hours>
party <hours>
holiday <dd.mm.yyyy-dd.mm.yyyy>
date <NTP | hh:mm:ss-dd.mm.yyyy-dw-dst>
*system_cmd*
send <"0B XX XX ..">
pin <gpio> <on|off|1|0|true|false>
Basic Design Principles
- The core services like telnet, logging and shell are based off the libraries from @nomis. I also adopted his general design pattens such as making everything as asynchronous as possible so that no one operation should starve another operation of it's time to execute (https://isocpp.org/wiki/faq/ctors#static-init-order).
- All EMS devices (e.g. boiler, thermostat, solar modules, mixing units etc) are derived from a factory base class and each class handles its own registering of telegram and mqtt handlers. This makes the EMS device code easier to manage and we can extend with new telegrams types and features.
- For debugging there is an offline mode where the code can be compiled and executed standalone without uploading to an ESP controller. Use
make(based off GNUMakefile).
Customizing the Web UI
The Web is based off Rick's awesome esp8266-react framework. These are the files that are modified:
interface:
.envproject name and project path to ems-esp.env.developmentCORS URL
interface/public:
app/manifest.jsonems-esp nameindex.htmlems-esp nameapp/icon.png256x256 PNGfavicon.icoreplaced
interface/src:
CustomMuiTheme.tsxcolors for dark modeinterface/src/wifi/WifiSettingsController.tsxrename esp8266-react
interface/src/project:
ProjectRouting.tsxremoved demo, added paths to ems-esp/status, ems-esp/settings and *DemoProject.tsxremove /demo/ and changed title, renamed to EMSESP.tsxProjectMenu.tsxtitle change, added /ems-esp/settingsDemoInformation.tsxremoved filetypes.tsadd variables- added all custom files starting with EMSESP*
interface/src/mqtt:
types.tsadded mqtt_failsMqttStatusForm.tsxadded MQTT Publish ErrorsMqttStatus.tsadded function mqttPublishHighlightMqttSettingsForm.tsxadded publish time, qos, format
interface/src/authentication:
AuthenticationWrapper.tsxcommented out features.security because we added versionAuthenticationContext.tsxadded versionMqttSettingsForm.tsxadded publish time, qos, format
interface/src/components:
MenuAppBar.tsxadded version to toolbar
interface/src/system:
types.tsadded uptime and free_memSystemStatusForm.tsxadded system uptime, % free mem
lib/framework:
SystemStatus.hadded #include <LittleFS.h>, #include <uuid/log.h>, #include "../../src/system.h"SystemStatus.cppadded LittleFS.info(fs_info); root["uptime"], root["free_mem"]- Commented out all
Serial.print's in all files MqttStatus.hadded #include "../../src/mqtt.h"MqttStatus.cppadded root["mqtt_fails"]SecuritySettingsService.cppadded version to the JWT payloadSecuritySettingsService.h#include "../../src/version.h"WiFiSettingsService.cppadded WiFi.setOutputPower(20.0f), moved setHostnameOTASettingsService.hadded #include "../../src/system.h"OTASettingsService.cppadded call to emsesp::System::upload_status(true)features.ini: -D FT_NTP=0platformio.iniusing our own versionfactory_settings.inimodified withems-esp-neoas password andems-espeverywhere else