No entiteiten in HA about homeassistant-fusionsolar

[tobyknobi]

Hi tijd. Just letting you know. The problem is solved. The installer forgot 1 thing Thanks for your help and your integration Groetjes Toby Op di 25 apr. 2023 19:14 schreef Toby Eleveld ***@***.***>:

…

Thanks you. I had the same issues. But I didn't know it on my end or installers end. Or home assistant end. I thank you for your time and quick response Toby Op di 25 apr. 2023 16:56 schreef Tijs Verkoyen ***@***.***>: > I'm pretty sure everything is fine at my end, as I am using the > integration on a daily base. > If have checked with your credentials again: > > - Login: works > - Retrieving the stations does not work. Not by calling getStationList > nor stations. The error I get is: Invalid access to current interface!. > Which indicates that there is something wrong with the rights for your > credentials. > > This has nothing to do with your Home Assistant installation. > > If your installer can't resolve the issue, I suggest you contact > ***@***.*** > > — > Reply to this email directly, view it on GitHub > <#84 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AXV5BXSJZ6RL5IYW65CYE6DXC7Q3DANCNFSM6AAAAAAW2PTALQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[tijsverkoyen]

Do you use the same credentials anywhere else?
Have you checked the logs in Home Assistant?
Are you willing to share your credentials with me via email fusionsolar [at] verkoyen [dot] eu

[tobyknobi]

Yes I am willing to share with you my info

[tobyknobi]

Traceback (most recent call last): File "/config/custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py", line 54, in get_station_list response = self._do_call(url, json) File "/config/custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py", line 189, in _do_call raise FusionSolarOpenApiErrorInvalidAccessToCurrentInterfaceError(json_data[ATTR_MESSAGE]) custom_components.fusion_solar.fusion_solar.openapi.openapi_api.FusionSolarOpenApiErrorInvalidAccessToCurrentInterfaceError: Invalid access to current interface! During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 304, in _async_setup_platform await asyncio.shield(task) File "/config/custom_components/fusion_solar/sensor.py", line 750, in async_setup_entry stations = await hass.async_add_executor_job(api.get_station_list) File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) File "/config/custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py", line 57, in get_station_list return self.stations() File "/config/custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py", line 85, in stations response = self._do_call(url, json) File "/config/custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py", line 189, in _do_call raise FusionSolarOpenApiErrorInvalidAccessToCurrentInterfaceError(json_data[ATTR_MESSAGE]) custom_components.fusion_solar.fusion_solar.openapi.openapi_api.FusionSolarOpenApiErrorInvalidAccessToCurrentInterfaceError: Invalid access to current interface!

[tobyknobi]

have send you an email with credencials and stop the integration on HA

[tijsverkoyen]

Jep, thx. I will try to test this week.

[tijsverkoyen]

I think your installer forgot to give you access to the Plant list call.
Both /thirdData/stations and /thirdData/getStationList calls return in a 401 - Invalid access to current interface!

[tijsverkoyen]

I will close this issue. Feel free to reopen it if it is not resolved after your installer has checked that you have access.

[tobyknobi]

Thanks! Oke Op wo 12 apr. 2023 15:24 schreef Tijs Verkoyen ***@***.***>:

…

I will close this issue. Feel free to reopen it if it is not resolved after your installer has checked that you have access. — Reply to this email directly, view it on GitHub <#84 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXV5BXXECEIVE3B2LHY65L3XA2UJFANCNFSM6AAAAAAW2PTALQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[tobyknobi]

Hi there tijs, If you have time can you check if it works on your side? All setting in Northbound should be good. I am not a professional on API systems. But I need to know if there is something wrong with my home assistant Installation. Does it matter if kiosk mode is on? Regards Toby Op wo 12 apr. 2023 15:37 schreef Toby Eleveld ***@***.***>:

…

Thanks! Oke Op wo 12 apr. 2023 15:24 schreef Tijs Verkoyen ***@***.***>: > I will close this issue. Feel free to reopen it if it is not resolved > after your installer has checked that you have access. > > — > Reply to this email directly, view it on GitHub > <#84 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AXV5BXXECEIVE3B2LHY65L3XA2UJFANCNFSM6AAAAAAW2PTALQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[tijsverkoyen]

I'm pretty sure everything is fine at my end, as I am using the integration on a daily base.
If have checked with your credentials again:

• Login: works
• Retrieving the stations does not work. Not by calling getStationList nor stations. The error I get is: Invalid access to current interface!. Which indicates that there is something wrong with the rights for your credentials.

This has nothing to do with your Home Assistant installation.

If your installer can't resolve the issue, I suggest you contact [email protected].

[tobyknobi]

Thanks you. I had the same issues. But I didn't know it on my end or installers end. Or home assistant end. I thank you for your time and quick response Toby Op di 25 apr. 2023 16:56 schreef Tijs Verkoyen ***@***.***>:

…

I'm pretty sure everything is fine at my end, as I am using the integration on a daily base. If have checked with your credentials again: - Login: works - Retrieving the stations does not work. Not by calling getStationList nor stations. The error I get is: Invalid access to current interface!. Which indicates that there is something wrong with the rights for your credentials. This has nothing to do with your Home Assistant installation. If your installer can't resolve the issue, I suggest you contact ***@***.*** — Reply to this email directly, view it on GitHub <#84 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXV5BXSJZ6RL5IYW65CYE6DXC7Q3DANCNFSM6AAAAAAW2PTALQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[tobyknobi]

Well solved. I do get entities. But it stays on unknown everything. Or do I have to wait a bit longer Regards Toby Op di 2 mei 2023 14:11 schreef Toby Eleveld ***@***.***>:

…

Hi tijd. Just letting you know. The problem is solved. The installer forgot 1 thing Thanks for your help and your integration Groetjes Toby Op di 25 apr. 2023 19:14 schreef Toby Eleveld ***@***.***>: > Thanks you. > > I had the same issues. > But I didn't know it on my end or installers end. Or home assistant end. > > I thank you for your time and quick response > Toby > > Op di 25 apr. 2023 16:56 schreef Tijs Verkoyen ***@***.*** > >: > >> I'm pretty sure everything is fine at my end, as I am using the >> integration on a daily base. >> If have checked with your credentials again: >> >> - Login: works >> - Retrieving the stations does not work. Not by calling >> getStationList nor stations. The error I get is: Invalid access to >> current interface!. Which indicates that there is something wrong >> with the rights for your credentials. >> >> This has nothing to do with your Home Assistant installation. >> >> If your installer can't resolve the issue, I suggest you contact >> ***@***.*** >> >> — >> Reply to this email directly, view it on GitHub >> <#84 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AXV5BXSJZ6RL5IYW65CYE6DXC7Q3DANCNFSM6AAAAAAW2PTALQ> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

[tijsverkoyen]

no you should not. Do you see anything in the logs?

[tobyknobi]

I only see this in debug mode aceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 250, in _async_refresh self.data = await self._async_update_data() File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 206, in _async_update_data return await self.update_method() File "/config/custom_components/fusion_solar/sensor.py", line 655, in async_update_station_year_kpi_data response = await hass.async_add_executor_job(api.get_kpi_station_year, station_codes) File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) File "/config/custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py", line 125, in get_kpi_station_year response = self._do_call(url, json) File "/config/custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py", line 194, in _do_call raise FusionSolarOpenApiAccessFrequencyTooHighError( custom_components.fusion_solar.fusion_solar.openapi.openapi_api.FusionSolarOpenApiAccessFrequencyTooHighError: Access frequency to high. failCode: 407, message: ACCESS_FREQUENCY_IS_TOO_HIGH i will go to my installer on friday and take a look in there system . if he maybe has forgotten some more regards toby Op wo 3 mei 2023 08:20 schreef Tijs Verkoyen ***@***.***>:

…

no you should not. Do you see anything in the logs? — Reply to this email directly, view it on GitHub <#84 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXV5BXULIP6NJUNL2V4W6RLXEH2J7ANCNFSM6AAAAAAW2PTALQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[tobyknobi]

I do need to say. After a restart of the docker container. There are no more fusion messages. In the log (also debug) All clean. So there must be that the installer has forgotten something. Op wo 3 mei 2023 21:27 schreef Toby Eleveld ***@***.***>:

…

I only see this in debug mode aceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 250, in _async_refresh self.data = await self._async_update_data() File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 206, in _async_update_data return await self.update_method() File "/config/custom_components/fusion_solar/sensor.py", line 655, in async_update_station_year_kpi_data response = await hass.async_add_executor_job(api.get_kpi_station_year, station_codes) File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) File "/config/custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py", line 125, in get_kpi_station_year response = self._do_call(url, json) File "/config/custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py", line 194, in _do_call raise FusionSolarOpenApiAccessFrequencyTooHighError( custom_components.fusion_solar.fusion_solar.openapi.openapi_api.FusionSolarOpenApiAccessFrequencyTooHighError: Access frequency to high. failCode: 407, message: ACCESS_FREQUENCY_IS_TOO_HIGH i will go to my installer on friday and take a look in there system . if he maybe has forgotten some more regards toby Op wo 3 mei 2023 08:20 schreef Tijs Verkoyen ***@***.***>: > no you should not. Do you see anything in the logs? > > — > Reply to this email directly, view it on GitHub > <#84 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AXV5BXULIP6NJUNL2V4W6RLXEH2J7ANCNFSM6AAAAAAW2PTALQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >