Stand-alone usage

[bublath]

Hi,
Thanks for putting all the efforts into decoding the protocol.
You mention that it could be possible to run without a controller. So do I get it right that it could work just the the TAP (no CCA)?
Just wondering if you have plans to enhance this anytime soon. I just bought a TAP and hooked it up and (probably as expected) the "observe" does not get any data (not even sure I have A and B correct as my USB adapter did not label it). At least it should have power as the red LED is on.
If there would be a beta to try it out, I would be happy to help.

Jörg

[willglynn]

The next step there would be to add a poll subcommand, which would do everything observe does plus:

1. Enumerate gateway(s) on the RS-485 interface,
2. Request a node table from each gateway, and
3. Receive packets from each gateway

I think this would be enough to receive telemetry from an already-configured mesh network.

Reconfiguring an existing system or configuring a system from scratch would require significantly more experimentation. I haven't seen a controller do that at all, much less do that in enough different ways to understand what everything means.

[bublath]

So you're saying to properly set up everything, a controller would still be needed (at least until the full protocoll is understood)?
What if there only is one gateway? I don't have that many panels equipped and believe the one gateway I have, should be able to receive them all. Would that require any special configuration or could the gateway be triggered to send everything it has?

[willglynn]

My install has a bunch of optimizers. The optimizers definitely need to know how they're wired, both in series and in parallel, to function correctly. That information came from the controller, and I don't know how that's structured or communicated.

Shutdown devices probably don't need nearly as much configuration but I suspect there is still some. The PV configuration packets suggest that PV modules are configured with a gateway's PAN ID. I wager that 1) controllers affirmatively create that association during the commissioning process and 2) this happens even for the simplest devices.

I think the poll subcommand described above would be sufficient to receive telemetry without a CCA, but it would not be sufficient to configure a system from scratch.

Note also that Tigo's warranty requires that you run one of their controllers:

In order for this Limited Warranty to apply during the full Warranty Period, Tigo requires all system components to be connected to the Internet and to maintain such connection throughout the Warranty Period. Tigo shall have the right to update the Equipment through remote firmware upgrades, without further notice. If this Limited Warranty is not able to be honored during the full Warranty Period because of failure to comply with this Internet connection requirement, Tigo will still honor the Limited Warranty for 5 years from the Warranty Start Date.

[as-cmi]

About tigo's warranty: my install is MINE and I decide wether or not it will be online and when!
That's why I use taptap first: my whole rig is offline.
To me it is not a thing to have inside my lan a black box explicitly controlled by someone on the other side of the world.

Available to re-initialize my setup and share all the traffic between cca and tap if it helps!

[litinoveweedle]

Don't want to be the devil's advocate, but their extended warranty offer is just deal for your data. You are free to take it or leave it.

It would be even a fair deal, if they wouldn't artificially block local data access, crippled their cloud API and let you pay extra to get your data back. So with tap tap I can now have both - connected Tigo to cloud for warranty and reliable local access. Today I just switched my Home Assistant to the taptap-mqtt bridge so let's see.

[willglynn]

Yes, I agree; I bothered decoding the protocol so that I can have data without putting any Tigo controller on my network.

[Sn0w3y]

Okay, i need to set my POV here - i just started to Disassemble some of the Files running on my Tigo CCA and found some interesting things aswell.

My Question on this Topic is aswell - could we somehow help you to make a "new Configuration" of the CCA and System so we see which things the CCA sends to the TAP ?

[bublath]

Has someone succeeded to send something to the TAP and getting a reply?
I would assume that the "ping" or "enumarate" requests mentioned in the documentation should trigger something on a "lone" TAP.
However, I tried to send some data over the ttyUSB and all I ever receive back is an echo of what I sent. Not even sure if my cabling is right, as swapping A and B does not make any difference, while disconnecting A or B also stops the echoing.
Any hints and an example program for the "ping" would be appreciated.