so far so good. If you will see power reports events in the observe mode, set logging level in the taptap ha addon config to debug, start it, keep it running for minute and post the logs.
@litinoveweedle exactly the same like yesterday after sunset: only info about the gateway.
[2025-10-27T08:40:52Z INFO taptap] opening source connection...
[2025-10-27T08:40:52Z INFO taptap] source opened, entering read loop
[2025-10-27T08:40:59Z INFO taptap] gateway version observed: GatewayID(0x1201) = "Gateway Version G3.64 \rAug 29 2013\r06:21:18\rES-GW-H150.4.10S0.12\r"
[2025-10-27T08:41:29Z INFO taptap] gateway version observed: GatewayID(0x1201) = "Gateway Version G3.64 \rAug 29 2013\r06:21:18\rES-GW-H150.4.10S0.12\r"
[2025-10-27T08:42:14Z INFO taptap] gateway version observed: GatewayID(0x1201) = "Gateway Version G3.64 \rAug 29 2013\r06:21:18\rES-GW-H150.4.10S0.12\r"
[2025-10-27T08:42:29Z INFO taptap] gateway version observed: GatewayID(0x1201) = "Gateway Version G3.64 \rAug 29 2013\r06:21:18\rES-GW-H150.4.10S0.12\r"
[2025-10-27T08:42:59Z INFO taptap] gateway version observed: GatewayID(0x1201) = "Gateway Version G3.64 \rAug 29 2013\r06:21:18\rES-GW-H150.4.10S0.12\r"
My prognosis is, that Tigo changed power report packet structure. With my tin hat on, I would guess that they felt threatened by few users using the taptap.
For others, I would suggest to block Tigo cloud access for your CCA until this is resolved to avoid Tigo forcing you firmware upgrade.
Did anyone seen this FW also on the green box CCA?
Or is this related only to the new device types?
To continue, I will need to see taptap peek-bytes results capturing let say 1min.
This is how previously power report packet lokked like:
FF 7E 07 92 01 01 49 00 FE 04 BB 9C 7F 31
This packet is typically long and lot of those are produced during the day, it shall be easy to detectā¦
So if you post or PM me the peek-byte output we shall be able to see what is going on. Other possibility is to give me remove access to your Modbus converter - in that case PM me.
Thank you. So it seems that your installations is not a probably never be supported, as it uses old version of the communication protocol, which is not implemented in the taptap. I am sorry.
I was confused by the recent but unrelated upgrade of the other type (green) Tigo CCA to FW 4.0
Try BobSilvioās implementation. He has a Tigo Local and Tigo Cloud implementation.
It also seems like heās been working on taptap (RS485 sniffing) @litinoveweedle although he is choosing to use an ESP32 as an intermediary instead of an RS485 to IP solution. Maybe some synergies between the two projects?
Unfortunately, the local option doesnāt work, and the cloud version requires a ā¬20 yearly fee. The one Iām using seems to work without that fee.
Iām mainly using the Tigo data to check if thereās any issue with an individual panel, since I monitor power and energy at the inverter level. So a 5-minute poll from the Tigo cloud is quite fine for me.
So this is probably a rather dumb question (please pardon me for being a noob) @litinoveweedle how do we make use of the 0.2 taptap features with the module/serial number detection? Iām guessing we have to wait for the updated HASSIO addon (itās currently version 0.1.7)ā¦is that right?
Great project, but unfortunately I do not get results (yet) ā¦
My setup consists of 44 TIGOs, 2 TAPs, the green CCA and a Waveshare rs485 to Eth(B) and the hardware seems to perform as expected: taptap peek-bytes and peek-frames deliver a continuous data stream (day & night) taptap activity would provide data during the night (only very few @ day)
However: taptap observe does not provide any data
Trying to run taptap observe with persistent-file gives me an error message āunexpected argument āpersistent-fileā not foundā
(in home-assistant all my panels are reported unavailable, here I guess that the configuration in terms of Panel ID vs Panel Name might be incorrect as I had to changeout some TIGOs and change the string configuration, but ā¦
that should not matter ?)
Any ideas, any further information to asses the situation
There is already development working release of the taptap HA addon published here:
this is my development HACS repo.
The latest release contains both node identification using serials and also taptap fix for the Tigo protocol changes introduced by the Tigo CCA FW 4.X.X
If you do not want to use my dev repo (which is unstable and without any guarantees) you will need to wait day or two for the standard release.