Givtcp REST API Path

[dulochpark]

In the Predbat documentation and yaml file, the URL for the Givtcp REST API is http://homeassistant.local:6345

The URL for using Givtcp 3.0 in Home Assistant is http://homeassistant.local:8099/REST1

I've had Predbat installed in Home Assistant since September and it was only by chance that I read the documentation for Givtcp and I saw that the 6345 port is for docker containers and 8099/REST1 was for Home Assistant.

Can you please put this into the YAML file and documentation? It would help people like me that rarely RTFM and I guess the majority of people run Predbat in Home Assistant rather Docker these days.

Thanks!
Craig

[gcoan]

Thanks for raising this

I'm using GivTCP v3 with Home Assistant and have my apps.yaml set to:

  givtcp_rest:
    - 'http://192.168.1.69:6345'
    - 'http://192.168.1.69:6346'

(two inverters)

This works fine for me.

Do you know what the difference is with port 8099 vs 6345 and why one should be used in preference to the other - is there anything in the givtcp documentation?

[dulochpark]

Hello!

I found the details below in this Givtcp document - http://192.168.68.71:8123/hassio/addon/533ea71a_givtcp/info
Obviously the 192.168.68.71 is my local Home Assistant address

GivTCP provides a REST API for data output and control. REST service is available at: http://ipaddress:8099/ Each available inverter exposes its REST interface on the following endpoints:

/REST1/
/REST2/
/REST3/
/REST4/
/REST5/ You can call REST1/api to discover what api calls are available to you.
If Docker is running in Host mode then the REST service is available on port 6345

[springfall2008]

The 8099 port appears to work as well, maybe they supported the old and new methods