I don't think that's a viable position for a vendor to state publicly. I'm suggesting for your sake that you try not to describe your public relations strategy in public, especially in a case like this.
That said, I'm distinguishing two kinds of paths to go down in this regard, and Zero and DigiNow have chosen a particular path that yields the current ecosystem, where the interaction starts with some unhealthy elements, and then there's a feedback loop that tends to say that the lesson is not to interact, inform, or make claims.
The reason I avoid documenting DigiNow's chargers is that I have an NDA with them and performed work under contract for V1, which makes me extra careful with information gained via that channel. I also learned very quickly that information that seemed trustworthy was quickly forgotten or uprooted, because no one wrote anything down to ensure consistency except for me, which meant that the information was constantly shifting and hard to verify.
This is not a personal criticism, so much as a process criticism. I started a process with SuperCharger V1 that led to the wiki. DigiNow diverged from that and still remains in the murky realm of technicians talking shop off the record in inscrutable ways, which I manage to mine extremely gradually for verifiable information I can turn into something legitimate.
I find DigiNow's efforts overall to be commendable as this is a difficult space for any vendor to thrive in. But there are many ways in which DigiNow's efforts have been hobbled by its own perspective, and I want to be clear that it, like Zero, may find itself in a difficult position when a wider audience with different expectations starts paying attention to this space.
But I'll say this particularly: on the road, I do not find DigiNow's offerings to be particularly reassuring over the course of its life. V2.5's protocol is a tentative step in the direction of maturity, but it's only documented in a Google Document that I wrote after painstaking back and forth trying to get what was said verbally confirmed in several different ways because it was hard to interpret.
And even armed with this document and some ad hoc tooling, there's plenty I can't reliably diagnose myself. As a sometimes test engineer for DigiNow's products, I've been under-informed the entire time, and I should be trusted far more than has been shown.