WIFI, MQTT, REST API added to Sensorbox-2 -- PLEASE TEST

[dingo35]

I am looking for Sensorbox-2 users who are willing and able to test my new firmware version.

The new firmware version now also supports WiFi, MQTT, REST API, automatic time zone configuration, in fact pretty much everything I could take over from the SmartEVSE is now included. In addition, the "takeover" is designed in such a way that large parts of the code will be shared with the SmartEVSE, so that maintenance remains bearable.

This means that the Sensorbox-2 can also be used without a modbus connection to the SmartEVSE.

I only have one major problem: at my current location I do not have a 3x230V 50Hz grid available, which means I cannot test the core functionality.

3a59ad9c04.zip

(You can flash easily by going to http://ipaddress-of-your-sensorbox/update).

To configure wifi please look at the docs:
https://github.com/dingo35/Sensorbox-2/blob/master/docs/configuration.md

[dingo35]

Additional info:
Backup your original firmware:
esptool.py read_flash 0x00000 0x400000 backup.bin

Flash my firmware.bin:
esptool.py --port /dev/ttyUSB0 -b 115200 write_flash 0x10000 firmware.bin

and again on:
esptool.py --port /dev/ttyUSB0 -b 115200 write_flash 0x1C0000 firmware.bin

so both OTA0 and OTA1 parititons have the same version.

Restore your backup:

Flash your backup:
esptool.py write_flash 0x00000 backup.bin

[dingo35]

I solved two bugs:
-the backup wifi login procedure via USB command line did not work, fixed now. ESPTouch always worked....
-currents were reported 10x too low ...

Fixed:
613aad7aa.zip

[Bl4ckr4v3n]

I flashed 613aad7 on both partitions through USB, but I have no idea whether is was successful, is there a way to check the current firmware version?
FYI: I connected the unit back to the smartEVSE and it looks to be functioning (car not yet connected however), no errors and P1 data is visible on the display.
However I'd expect to see the additional WiFi functionality and I don't see any, so it feels to me as if the original firmware is still there.

[dingo35]

You should see a new device asking for a DHCP lease on your Access Point; if you surf to that ip address it shows you a screen with a.o. serialnr and firmware version.

You should also see it present on your mDNS ; on linux do "avahi-browse -a"

[dingo35]

By the way, did you follow the procedure to log your Sensorbox onto your wifi?

[Bl4ckr4v3n]

Well, the procedure implies you have a WiFi option on the evse screen, which is not there on the smartEVSE v2. I don't know if the WiFi is disabled by default, but otherwise I'd need to switch it on through serial or the like.

[dingo35]

No, you can activate wifi on the Sensorbox-2 via the ESPtouch procedure or the USB procedure.

Especially if your SmartEVSEv2 does not support wifi, it will bring you:

1. More options on your sensorbox webserver screen
2. MQTT feed of your Sensorbox currents to your MQTT broker
3. Easy firmware update of your Sensorbox via /update
4. REST API access to your Sensorbox currents

[Bl4ckr4v3n]

I tried all day to figure this out, but I guess I look in the wrong places. It should go in some kind of discovery mode AFAIK, but I can't detect or trigger this.
All SmartEVSE manuals point to the display to switch it on, both for the ESPtouch and USB procedures. But with a SmartEVSE V2 without the Wifi menu it's not possible to activate the smart config function from there.
It still looks as if the wifi is completely down, I don't detect any client or AP activity with my network monitors.

[dingo35]

We are talking SENSORBOX here, not SmartEVSE.
As stated, here is the procedure:
To configure wifi please look at the docs:
https://github.com/dingo35/Sensorbox-2/blob/master/docs/configuration.md

[Bl4ckr4v3n]

I overlooked that one, sorry...
Nevertheless USB procedure should be the same, but my sensorbox doesn't stop spitting the serial telegrams after hitting enter.
Now I tried the ESPtouch procedure also, but that doesn't give anything as well unfortunately.
It still feels like it didn't take the new firmware, although it flashed both partitions without errors.
Would it be possible that the ESP reverts the old partition to the newly flashed partition during the reboots?
(I presume that the message 'hard resetting via RTS pin' at the end of every flash means it's rebooting)
i.e. is there command to flash both partitions in one run to make sure it doesn't fallback to the old firmware?

[Bl4ckr4v3n]

I combined the commands like this:
esptool.py --port /dev/ttyUSB0 -b 115200 write_flash 0x10000 firmware.bin 0x1C0000 firmware.bin
Unfortunately still the same result, no connection on the ESPtouch app and in the serial connection it keeps spitting telegrams which 'Enter' doesn't stop.

[dingo35]

Ok thx for your efforts, Im working on some modifications so Ill be back here!

[Bl4ckr4v3n]

Any update on the modifications in the last month?

[dingo35]

You might have noticed we released v2.1.0 ; thanks for your efforts!