-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: json: cannot unmarshal number into Go struct field ResultData.result_data.org_id of type string #39
Comments
same issue as here...? |
@ottovdv Yes. Seems to be the same error. However, I can't temporarily adjust the file because it is in the addon. |
I have changed the file on my PC but not in the Addon. |
I have the same issue |
Same here |
same since yesterday. |
I also notice that this add-on stops working very often. Most of the time it starts working again after a reboot. But now it's dead completely. Can't seem to get it working again. Same issue as described above |
Mick has commented on the HA forum that the update to iSolarCloud changed a field which broke the add on, and that he's looking into it. |
all good with 3.0.7. thank you. |
Works now! thanks! |
Good morning,
I get the following error message after starting the addon:
Error: json: cannot unmarshal number into Go struct field ResultData.result_data.org_id of type string
Usage:
GoSungrow api login [flags]
Examples:
GoSungrow api login
Flags: Use "GoSungrow help flags" for more info.
Additional help topics:
ERROR: json: cannot unmarshal number into Go struct field ResultData.result_data.org_id of type string
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: