Getting er_invalid_appkey repeatedly, new installation #125
Comments
|
Please see this gist which deals with several scenarios for running GoSungrow. It sounds like you will need to follow the steps in Part 2 of the gist. Each "part" winds up at the configuration instructions which includes info about the app key. |
|
Hi Paraphraser I ran into some more errors due to other issues with the Home Assistant Server which I've been able to update and resolve and I appear to be making some progress but am stuck at this point I am now getting this error after it appears to login to both iSolarCloud and my Home Assistant instance correctly Error: network Error : non-CONNACK first packet received Again thank you for your assistance with the earlier Full Log |
|
Can't be 100% sure but one possible explanation is that this error is talking about TCP handshaking where "connections" are established via packets with the SYN flag set, then SYN+ACK, then ACK. Then, as the client and server exchange packets, you expect to see ACK (ie "acknowledgement") packets at regular intervals confirming reception. It might mean that something other than an ACK came back when an ACK was expected. That's all at layer four of the OSI model. Alternatively, the layer 7 protocol (aka "the API") between GoSungrow and iSolarCloud might have its own definition of ACK and the error might be talking about something missing or out-of-sequence at that level. All I can really say is:
I mention firewalls because any time packets go missing a misconfigured firewall is a likely suspect. Go anything that fits the bill? |
|
Hi
Nothing stands out, can I please check what API Key you are using?
Regards, Glenn
…On Sat, 21 Dec 2024 at 22:51, Phill ***@***.***> wrote:
Can't be 100% sure but one possible explanation is that this error is
talking about TCP handshaking where "connections" are established via
packets with the SYN flag set, then SYN+ACK, then ACK. Then, as the client
and server exchange packets, you expect to see ACK (ie "acknowledgement")
packets at regular intervals confirming reception.
It *might* mean that something other than an ACK came back when an ACK
was expected.
That's all at layer four of the OSI model.
Alternatively, the layer 7 protocol (aka "the API") between GoSungrow and
iSolarCloud might have its own definition of ACK and the error might be
talking about something missing or out-of-sequence at that level.
All I can really say is:
1. It isn't happening to me (Home Assistant running as a guest on
Proxmox-VE) so it probably isn't either *systemic* or a temporary
glitch affecting the AU gateway (that's my gateway too).
2. I have a bog standard Netcomm router from my ISP (AussieBroadband)
and the only firewalling occurring is whatever is baked into that. I don't
have device-level firewalls enabled anywhere.
I mention firewalls because any time packets go missing a misconfigured
firewall is a likely suspect. Go anything that fits the bill?
—
Reply to this email directly, view it on GitHub
<#125 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BN35VFHU7NCIAVFOWPHXHPD2GVP3JAVCNFSM6AAAAABUAKRHRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGEYTENJWGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
"B0455FBE7AA0328DB57B59AA729F05D8" but previous experience (other issues) suggests there's no relationship between app key and gateway server. Some people reported using this "B0" key then having to switch to the "ANDROID" key. There was a theory the switch of appkey might be triggered by logging in via the web GUI but I tried that and wasn't forced to switch. 🤷♂️ |
|
Hey Phil
Just letting you know I had another look at this and found the issue.
I had mistakenly assumed that the MQTT login was my Home Assistant login
which of course is not true. I have a better understanding of HA now and
recognised the issue straight away.
After resetting those MQTT settings and using the Android key from the
article you pointed me to I can now confirm it's all working beautifully.
Thank you so much for your assistance and patience, really appreciate it.
…On Sun, 22 Dec 2024 at 08:30, Phill ***@***.***> wrote:
"B0455FBE7AA0328DB57B59AA729F05D8" but previous experience (other issues)
suggests there's no relationship between app key and gateway server. Some
people reported using this "B0" key then having to switch to the "ANDROID"
key. There was a theory the switch of appkey might be triggered by logging
in via the web GUI but I tried that and wasn't forced to switch.
🤷♂️
—
Reply to this email directly, view it on GitHub
<#125 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BN35VFFZFZLEGXBCAXWHQYT2GXTYXAVCNFSM6AAAAABUAKRHRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGI2TMOJVGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi All
Would appreciate some assistance with trying to resolve this issue, has been happening since I've installed the addin. I've just restarted the Home Assistant server after it being offline for a while
Troubleshooting I've done
checked access to the host: augateway.isolarcloud.com
Restarted the Server and the Host VM
Other Integrations are working fine
Checked my login details, although this appears to be an API Key issue
Do I have to check for a new API key somewhere?
Any assistance would be greatly appreciated.
Error in logs
[06:07:03] INFO: Login to iSolarCloud using gateway https://augateway.isolarcloud.com ...
Error: appkey is incorrect 'er_invalid_appkey'
Complete log with my details removed
[06:07:02] INFO: Setting up GoSungrow config ...
[06:07:03] INFO: Writing GoSungrow config ...
Using config file '/data/.GoSungrow/config.json'
New config:
+-------------------+------------+---------------------------+--------------------------------+-----------------------------------+
| FLAG | SHORT FLAG | ENVIRONMENT | DESCRIPTION | VALUE (* = DEFAULT) |
+-------------------+------------+---------------------------+--------------------------------+-----------------------------------+
| --config | | GOSUNGROW_CONFIG | GoSungrow: config file. | /data/.GoSungrow/config.json |
| --debug | | GOSUNGROW_DEBUG | GoSungrow: Debug mode. | true |
| --quiet | | GOSUNGROW_QUIET | GoSungrow: Silence all | false * |
| | | | messages. | |
| --timeout | | GOSUNGROW_TIMEOUT | Web timeout. | 1m0s |
| --user | -u | GOSUNGROW_USER | SunGrow: api username. | |
| --password | -p | GOSUNGROW_PASSWORD | SunGrow: api password. | |
| --appkey | | GOSUNGROW_APPKEY | SunGrow: api application key. | 93D72E60331ABDCDC7B39ADC2D1F32B3 |
| | | | | * |
| --host | | GOSUNGROW_HOST | SunGrow: Provider API URL. | https://augateway.isolarcloud.com |
| | | | | * |
| --token-expiry | | GOSUNGROW_TOKEN_EXPIRY | SunGrow: last login. | 2023-05-22T19:55:05 |
| --save | -s | GOSUNGROW_SAVE | Save output as a file. | false * |
| --dir | | GOSUNGROW_DIR | Save output base directory. | * |
| --mqtt-user | | GOSUNGROW_MQTT_USER | HASSIO: mqtt username. | |
| --mqtt-password | | GOSUNGROW_MQTT_PASSWORD | HASSIO: mqtt password. | |
| --mqtt-host | | GOSUNGROW_MQTT_HOST | HASSIO: mqtt host. | core-mosquitto |
| --mqtt-port | | GOSUNGROW_MQTT_PORT | HASSIO: mqtt port. | 1883 |
| --modbus-user | | GOSUNGROW_MODBUS_USER | Modbus username. | * |
| --modbus-password | | GOSUNGROW_MODBUS_PASSWORD | Modbus password. | * |
| --modbus-host | | GOSUNGROW_MODBUS_HOST | Modbus host. | * |
| --modbus-port | | GOSUNGROW_MODBUS_PORT | Modbus port. | 502 * |
+-------------------+------------+---------------------------+--------------------------------+-----------------------------------+
[06:07:03] INFO: Login to iSolarCloud using gateway https://augateway.isolarcloud.com ...
Error: appkey is incorrect 'er_invalid_appkey'
Usage:
GoSungrow api login [flags]
Examples:
GoSungrow api login
Flags: Use "GoSungrow help flags" for more info.
Additional help topics:
ERROR: appkey is incorrect 'er_invalid_appkey'
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
The text was updated successfully, but these errors were encountered: