Cannot authorize. Instructions unclear.

[Redsandro]

I'm trying to set up manual smart charging with my Zaptec Go using this integration. I can see power consumption and such, but I cannot figure out how to "Authorize charging" from the app.

To minimize ambiguity, Here's what I am trying to do:

1. Authenticate myself locally using RFID key fob.
2. Start charging at night using HA/Zaptec when electricity is cheap.

readme.md:

If the installation is configured for native authentication it is possible to authorize charging from Home Assistant using the "Authorize charging" button.

I've tried multiple configurations and I cannot get this to work. I'm missing something. At the same time, some things are unclear.

1. Are Authorization and Authentication two distinct different actions, or are they used interchangeably?
2. Is this supposed to work exclusively in online mode, offline mode, or both?

"Offline mode" (as used by Zaptec) is also ambiguous, because it is not actually offline. I can read all the data from my Zaptec Go using this integration.

Here is my problem. In "Offline mode", charging upon authentication starts immediately. So I disable "Offline mode", and then charging never starts. It is always "waiting to charge". I can hit all the buttons from the integration, but it never starts.

[steinmn]

Authorization and Authentication are used interchangeably. The "Authorize charging"-button performs the same action as using the RFID key fob, so if you have already authenticated with RFID, the "Authorize charging"-button does nothing since you are already authenticated.

Please consult the Prevent charging auto start-section in the readme. If you want to use the RFID, you will need to adjust available current to 0 when you don't want to charge.

I'm afraid I have no idea what you are referring to with "Offline mode", but it's been a while since I've touched the Zaptec app/portal.

[Redsandro]

Thank you for these insights. So if I am not mistaken, "Authorize charging"-button should work in offline mode Stand-alone mode.

I'm afraid I have no idea what you are referring to with "Offline mode"

Apologies, I was mistaken (or they renamed it); it is called Stand-alone mode in the English language of the app.

In the offline Stand-alone mode, the key fob authorizes charging and that's it. In Online mode, the key fob will authenticate you as in being allowed to charge so the charger changes to "waiting to charge" and then I guess the Zaptec Cloud will authorize the final charging, depending on conditions and services. I have never gotten this to work properly, but in theory this allows Zaptec to defer charging until electricity is cheap or have other third parties manage charging for you.

So on one hand, according to the Zaptec app, "online" mode (the non-stand-alone mode) is required for third party services, and I don't know if it means services connected to the Zaptec cloud, or also this HA integration. On the other hand I have never managed to charge in "online" mode - it will permanently stay "waiting to charge" no matter what - and I have exclusive used "Stand-alone mode". I can still read power usage and such using this integration, but I can't authorize charging with this integration in Stand-alone mode. Only the RFID fob works.

I have contacted Zaptec. They have upgraded my firmware to the latest version and reset my cloud settings (?). But there is no change. I get the subjective feeling that there is a remnant of a third party service blocking charging on "online" mode, but Zaptec customer service has assured me they see no such problem in my account.

Can you confirm that I should technically be able to start charging with this integration if the Zaptec Go is in "stand-alone" mode as well? Is there anything else that strikes you as something worth looking into? I probably have tunnel vision by now.

[sveinse]

Can you confirm that I should technically be able to start charging with this integration if the Zaptec Go is in "stand-alone" mode as well? Is there anything else that strikes you as something worth looking into? I probably have tunnel vision by now.

I've never tested this setup. I'm not sure what to expect in stand-alone mode for the HA Zaptec integration. Given the statement that off-line mode "third-party services connected to Zaptec are turned off", I'm inclined to assume that this HA Zaptec integration will be disabled. The HA integration doesn't communicate directly to the charger locally (Zaptec doesn't provide the means to do so), instead it depends on the services provided by Zaptec cloud. If the Zaptec cloud cuts off the connection to the charger in "stand-alone" mode, there is nothing we can do.

[steinmn]

Based on #366, I think we can conclude that the HA integration cannot control a charger that is in stand-alone mode.

[no-gram]

My experiences with stand-alone mode match the behavior described here:

https://help.zaptec.com/hc/en-GB/article/use-stand-alone-mode-for-troubleshooting-and-unstable-internet

When plugging in the charger the charging started immediately. The charging status was updated correctly through the integration and I could stop and start the charging. I was however not able to prevent auto start by setting the "Available current" to 0 at the Installation-level.

[Redsandro]

Update: So while I cannot start charging by pressing "authenticate", I can stop and restart charging with the charging toggle.

That means @sveinse's inclined assumption "that this HA Zaptec integration will be disabled" is wrong, and @steinmn's plausible conclusion that "the HA integration cannot control a charger that is in stand-alone mode" is wrong.

As for @no-gram, I guess your experience is closest to mine, except mine doesn't autostart as it is configured to require authentication.

This is all very interesting and confusing: The HA integration can control and monitor the charger, but it cannot authenticate using the authentication button. Interesting but problematic because I wanted HA to decide when to charge. I guess technically I can make an automation for HA to stop charging when it starts charging, and then restart charging again at the desired hour.

[sveinse]

This is interesting indeed. This Zaptec integration in HA doesn't communicate directly with the charger, and we're completely at the mercy what the Zaptec Portal API is providing us of features. If certain things are working in stand-alone, while others are not, is at the exclusive control by Zaptec centrally. (Unfortunately. We would have loved local control. But that's a different discussion.) I know I'm deflecting the answer, but I'm not able provide any insights to this, nor have the ability to do something about it, I'm afraid.