EPEver2MQTT icon indicating copy to clipboard operation
EPEver2MQTT copied to clipboard

[HELP] Configuration of working parameters of epever (Solar Station Monitor)

Open miky2k opened this issue 1 year ago • 5 comments

A clear and concise description of what the problem is.

I'm using five epever tracer and all of them is administered through a bridge (serialTCP) by tasmota and linux host with python tcpmodbus client. Sometimes i use in windows solar station monitor to change some parameters and i create virtual com port with com2tcp. I don't' understand yif our firmware accept a connection to act as serialTCP bridge , or if is it possible to configure epever charge controller parameters from (webserial or HA interface).

Additional context

No response

miky2k avatar Aug 26 '24 10:08 miky2k

actual only output control settings are supported, the firmware doesnt have a tcp bridge function. https://github.com/softwarecrash/EPEver2MQTT/wiki/Output-Control

softwarecrash avatar Aug 27 '24 07:08 softwarecrash

Add access to serial stream through tcp port is feasible ? For configuration purpose.

miky2k avatar Aug 27 '24 07:08 miky2k

Add access to serial stream through tcp port is feasible ? For configuration purpose.

not as simple as its sounds, detection is tcp bridge open-disable the workers or build a switching for it... the main problem is the tcp bridges librarys are all verry big and need a lot of cpu time, but the epever project is near the limits without loosing functions like webOTA and other. added it to ideas to check it later, at the moment i doenst have the time for it, must check if it makeable with the prog space

softwarecrash avatar Aug 27 '24 07:08 softwarecrash

but the epever project is near the limits without loosing functions like webOTA and other.

I use tasmota with tcpbridge,modubus,OTA,Webserver,MQTT, SSL and TLS and other peripherals stuff at same time in the same soc, i fell is not a problem of cpu or memory but choice optimized libraries.

miky2k avatar Sep 02 '24 08:09 miky2k

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] avatar Oct 03 '24 02:10 github-actions[bot]

This issue was closed because it has been inactive for 14 days since being marked as stale.

github-actions[bot] avatar Oct 17 '24 02:10 github-actions[bot]