Extending the test framework

[proddy]

EMS-ESP always had an offline simulation mode, so compiling and running on a PC without an ESP attached. It's built using the makefile (customized for linux only as it used gcc and GNUmake).

This mode is useful for seeing how telegrams are parsed and which MQTT publish topics would be triggered. It's done via the test command on the console. I've now extended this to the web API so it can also run on the ESP8266/ESP32. So in theory if you power up an ESP (without the EMS bus connected) and issue commands like http://ems-esp/api?device=system&cmd=test&data=boiler it will simulate all the incoming telegrams for a specific boiler. It's useful to testing devices that we don't have to see how they behave in the Web, like solar, mixing, gateway, heatpump units etc

It's only for debugging, so make sure you have the EMSESP_TEST flag set in pio_local.ini like

[common]
debug_flags = -DEMSESP_TEST

[proddy]

only problem is that is causes the ESP8266 to crash! so still experimental....

[proddy]

Ok, seems to work on both ESP8266 and ESP32. Some tests are:

http://ems-esp/api?device=system&cmd=test&data=boiler (add a Nefit Trendline boiler)
http://ems-esp/api?device=system&cmd=test&data=thermostat (adds a FW120 thermostat with HC1 - HC3)
http://ems-esp/api?device=system&cmd=test&data=gateway (adds a KM200 and a RC310 thermostat)
http://ems-esp/api?device=system&cmd=test&data=solar (adds a SM100)
http://ems-esp/api?device=system&cmd=test&data=heatpump (adds an Enviline and FW120 thermostat)
http://ems-esp/api?device=system&cmd=test&data=mixer (adds a controller and MM100, MM200, MM100)
http://ems-esp/api?device=system&cmd=test&data=general (adds a Trendline boiler and a CR100 thermostat)
http://ems-esp/api?device=system&cmd=test&data=general2 (adds a GB072 and a RC310 thermostat)

In the console the other tests to be run in standalone mode are:
render, devices, double, unknown, web, fr120, tc100, km, solar200, cr100, rx, tx, poll, cmd, mqtt, offset

[proddy]

in 2.1.1b3