endpoints returning a 404

[n2aws]

Hello,

I appreciate the work you've done here. I was originally planning on getting a USB to RS485 adapter, and physically wiring it into my conext gateway.. and then figuring out how to integrate that data with home assistant. In researching this, I stumbled upon your code, and was hoping to use it (obviously tcp would be a lot easier than modbus directly)

looking at your HA example, I see your endpoints are on the gateway itself, using /cc, /inverter, and /battery. However, those all return a 404 error page for me. Is there some setting in the conext gateway you needed to enable? I've been all through the config menu, and can't seem to find anything that seems relevant.

Any suggestions would be appreciated!

(Note, I tested the endpoints manually via a chrome browser and via curl, before trying the code in HA. so this isn't an HA config issue)

[shorawitz]

Hi n2aws!

Sorry for not responding to this sooner. I've been working on a Seplos BMS module now to integrate those into my HA management solution. I think there is a bit of misunderstanding how this works. The endpoints are running in a docker container that is running on the HA host. The docker container app (which uses NGINX as a frontend proxy for HA to communicate with) is the one that queries the ModbusTCP connection on the Gateway. What you can try is the "query.py" app that does communicate directly with the Gateway. If you have the PyModbusTCP module installed, you can use that python script to query the data directly on the Gateway.