How to test the config without a Marstek device

[bt43a]

Hey,
I just installed the B2500-meter as a docker container und configured a tasmota device as input. Now I want to test my config before the marstek is delivered, but don't know how to do this. Probably a stupid question, but is there any web interface or command to check, if it is correctly reading the tasmota?

Docker protocol:

INFO:b2500-meter:startet b2500-meter application
INFO:b2500-meter:Device Types: ['shellypro3em_old', 'shellypro3em_new' ]
INFO:b2500-meter: Device IDs: ['shellypro3em-ec4609c439c1', 'shellypro3em-ec4609c439c1']
INFO:b2500-meter: Skip Test: False
INFO:b2500-meter: Starting health check service ...
INFO:b2500-meter:Health check service started on 0.0.0.0:52500
INFO:b2500-meter: Health check service started successfully
INFO:b2500-meter: Shelly emulator listening on UDP port 1010 ...

config.ini

[GENERAL]
DEVICE_TYPE = shellypro3em
SKIP_POWERMETER_TEST = False
DISABLE_SUM_PHASES = False
DISABLE_ABSOLUTE_VALUES = False
POLL_INTERVAL = 1
THROTTLE_INTERVAL = 0

[TASMOTA]
IP = 192.168.0.158
#USER = tasmota_user
#PASS = tasmota_pass
JSON_STATUS = StatusSNS
JSON_PAYLOAD_MQTT_PREFIX = LK13BE
JSON_POWER_MQTT_LABEL = Power_curr

[tomquist]

There’s no Webinterface. You can set the log level to debug to see the result of the self-test during startup. This will tell you whether the Tasmota could be read successfully.

[bt43a]

Thanks for the quick reply, sadly I have no idea how to set the log level, could you give me some more help?

[tomquist]

You can change the log level by setting the environment variable LOG_LEVEL to DEBUG.

[bt43a]

Thanks, I've now set the environmental var, but still getting the same logging level.
Maybe my synology NAS isn't playing well with this container.

But when I'm intentionally setting a wrong MQTT Label I'm getting a
ERROR:b2500-meter:Failed to test powermeter after 4 attempts: 'Power_currx'
So the initial config seems to be already fine, as it's throwing no Errors :)

One last question: The Tasmota vars are all labeled "MQTT", isn't this just a http JSON request?

[tomquist]

Yes, it’s using the HTTP API but technically the value you have to provide is the MQTT label that gets requested via HTTP