FoxESS Community - Owners & Installers Forum

Is it possible to bind a site to multiple installers?

No a user can only be bound to 1 installer, but an agent can have multiple installers.

What's the difference between agent and installer? Is there a hierarchy, Agent>Installer>Site or Installer>Agent>Site?
This is what I see from the Agent login I created and bind my site to. Looks like my Installer no longer has access, which I'm fine with as they just did a basic setup and any questions I had referred my to Fox ESS support (whcih don't repsond to tickets in Australia, only phone calls when you can get through).

brunofabre wrote: ↑Fri Jan 16, 2026 1:32 am What's the difference between agent and installer? Is there a hierarchy, Agent>Installer>Site or Installer>Agent>Site?
This is what I see from the Agent login I created and bind my site to. Looks like my Installer no longer has access, which I'm fine with as they just did a basic setup and any questions I had referred my to Fox ESS support (whcih don't repsond to tickets in Australia, only phone calls when you can get through).

The site is bound by the datalogger and so whichever account the datalogger is in the device on that site will show there.

I'm intrigued that you managed to take over the account as an agent, normally an installer would be part of an agent account and the only way to re-allocate a site would be to get Fox to release the site from the installer and then re-bind it - so that suggests your installer never created an agent account.

From what I can tell the hierarchy is User(Site), Installer, Agent, Fox, the Agent can be bound to sites (many) or installers (many). An installer can be bound to sites (many), bound to the site by Installer code, or the installer can be bound to an Agent (1 off).

There's not a big functional difference between Agent and Installer other than an installer can have many distinct sites, whereas the Agent can have many distinct Installers and/or sites. The agent gets access to a few more data reports but functionally very similar to installer.

Above all of this is Fox who can access any system with far more tools and firmware at their disposal.

Thanks Dave. I'm guessing that the Solar Distributor is Fox ESS. That confirms that my installer no longer has access to my site.
From the User Manual, there is a concept of a Company (Agent) which contain Admin and Installers. Would there be any difference between an Admin and a Installer?

Appreciate all your help.

Dave Foster wrote: ↑Fri Jan 16, 2026 11:35 am

brunofabre wrote: ↑Fri Jan 16, 2026 1:32 am What's the difference between agent and installer? Is there a hierarchy, Agent>Installer>Site or Installer>Agent>Site?
This is what I see from the Agent login I created and bind my site to. Looks like my Installer no longer has access, which I'm fine with as they just did a basic setup and any questions I had referred my to Fox ESS support (whcih don't repsond to tickets in Australia, only phone calls when you can get through).

The site is bound by the datalogger and so whichever account the datalogger is in the device on that site will show there.

If i purchase a separate data logger can i register the new logger to another installer? It doesnt check inverter or battery serial number?

greensolar wrote: ↑Tue Mar 17, 2026 6:23 am If i purchase a separate data logger can i register the new logger to another installer? It doesnt check inverter or battery serial number?

There's a way to do it without buying a new data logger.

https://foxess.evilbunny.org/doku.php?i ... er_account

I dont want to replace my current installer, i will need him for warranty purposes. i want to use an additional wifi dongle which will be bound to a different installer.

is this possible?

greensolar wrote: ↑Tue Mar 17, 2026 9:29 am I dont want to replace my current installer, i will need him for warranty purposes. i want to use an additional wifi dongle which will be bound to a different installer.

is this possible?

I think your only option would be using a modbus connection and it seems to be a DIY path.

I'm not sure your warranty states your installer must have remote access.