Tigo optimizer local monitoring - without cloud now possible!

Hello,

base on the taptap project which reverse engineered protocol between Tigo TAP and CCA components I was able to create mqtt bridge and package it as a Home Assistant addon TapTap.

So now we can detailed information from the Tigo photovoltaic optimizer modules locally - without Tigo cloud and with refresh time of 10s. :wink:

Implementation requires:

  • Modbus RS485 to Ethernet convertor (like for example WaveShare models
  • MQTT broker (like mosquitto addon)
  • MQTT integration

As Addon uses HomeAssisatant MQTT auto discovery feature, it will setup all provided sensors automatically in the HA.

Any feedback is welcome.

3 Likes

Hey there, I have a waveshare RS485 to WiFi/ETH device and trying to configure it in HA

Please can you elaborate more on the settings to configure like what I should be putting in for the following:
taptap_module_ids*
taptap_module_names*

Maybe some screen shots of the waveshare setup and the config would help as you instructions are not that clear

These are the errors I am getting
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-taptap: starting
s6-rc: info: service init-taptap successfully started
s6-rc: info: service taptap: starting
[17:13:33] INFO: Starting taptap…
s6-rc: info: service taptap successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Reading config file: /etc/taptap/config.ini
Invalid config entry: TAPTAP/ADDRESS
[17:13:33] INFO: Service taptap exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service taptap: stopping
s6-rc: info: service taptap successfully stopped
s6-rc: info: service init-taptap: stopping
s6-rc: info: service init-taptap successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Just some comments,
taptap_address = Waveshare IP
taptap_port = Waveshare Port

Hi, sorry for issue - there was malformed translation YAML and therefore no help was displayed in addon configuration page. I fixed it and also provided detailed DOCS page. Also new version of the taptap-mqtt is now included in the latest release 0.1.1. You can check it out.

1 Like

Thank you, will play again and see how it works out

Thank you very much for this! it works great, and now I don’t have to rely on Tigo API! For future folks:

  1. add the repo to HA add-on store:
  1. Search the HA add-on store for TapTap, install it.

  2. Follow the configuration instructions

Hello, good to hear @josher-mi that it works! Some users struggle with the setup as it is not easy - wiring is required, MQTT prerequisites, add-on settings etc. So any hint where additional more detailed description/docs could be helpful is very welcome.

1 Like

I was thrown off by the docs page here:

https://github.com/litinoveweedle/hassio-addons/blob/38cee27eb0190208d590f52b80fb6e05122164ac/taptap/DOCS.md

Basically the doc directs us to install the ‘example’ add-on, which generates random quotes.

Maybe replace this (pictured) above section with a few bullets like…

  1. explain how to add your repo to the add-on store (and include the actual repo url)

  2. Explain how to search for TapTap in the add-on store, and then how to install it and add config, and finally start it.

  3. Show how to verify that the HA MQTT broker is getting messages from the converter.

  4. because it’s so simple, describe how to install the MQTT add-on AND integration. Probably many folks find MQTT a little intimidating :laughing:

I felt the rest of the instructions were spot on!

I also think pictures speak volumes :slightly_smiling_face:

This is what a working waveshare converter looks like:

Today was announced new custom integration without need any device or cloud:

I was using local web access to the Tigo CCA whole last year, even wrote similar rest API based integration. However to my knowledge latest Tigo version of the CCA firmware completely closed local web server access, so this method is not feasible anymore for upgraded devices or new installations (where there is mandatory step to first upgrade the firmware to be able to contiue with commissioning).

integration is based on 3.8.3-ct-3

yr version?

Hi @Bobsilvio , I’ve checked you integration. It are actually uses:

URL: http://IP/cgi-bin/summary_data
credentials: Tigo:$olar

That very well known credentials are no longer valid for new FW - as Tigo probably realized that people start using this loophole more and more. I just re-checked this access on the two installations which were commissioned at the end of the last year and it really doesn’t work. I am not on the site so I have no idea which version of the FW is installed there (and I do not know other way to get FW than from the mobile app when using local BT connection).

Also at least on the older FW (can’t say for the new one) you needed either reverse proxy or logging into CCA using SSH modifying iptables rules to circumvent source IP address restriction (to IP 10.11.1.1) for the webserver access.

So instead battling those limitations with every new FW I decided to go for taptap - as it is much more hard for Tigo to close the physical Modbus tapping access.

EDIT:

just rechecked (saw the message on the same forum were were learned about the Tigo) and I can actualy get http://IP/summary/ page from the CCA. So the isue was probably my fault not providing summary_data GET params. So your integration shall work :wink:

my CCA was installed 10 days ago, and it contains the latest firmware

http://xxx/cgi-bin/mobile_api?cmd=DEVICE_INFO&dev=1&ver=1

I don’t think you have a firmware higher than 3.8.3

maybe you have a different cca? not the black and green one?

EDIT: OK thanks