Error all entities unavailable

[enes-oerdek]

Error all entities unavailable

[enes-oerdek]

Sorry for the inconvenience. Issue should be resolved. Please restart your HA or reload the integration, in order to update the sensors. I will leave this issue open for a while in order to observe the backend.

[MVerBerkmoes]

It came back after following the directions above, but now, all sensors are down with the same error. 😩

[enes-oerdek]

Issue should be resolved. That external service is now also running on the backend. Availability should improve.

[jooslouw]

Same problem here since yesterday. I get the same log file error (obviously with my walletID in the 500 Server Error line). I also updated to the latest version 2.4.3. I tried downgrading back to 2.4.2 without luck.
These were the chain of events:
I was on HASS 2023.7
I updated the Helium integration to version 2.4.3 via HACS
The Helium entities became unavailable after the restart.
I then upgraded my HASS to 2023.8
Helium entities still unavailable, then downgraded to 2.4.2
Helium entities still unavailable, then upgraded back to 2.4.3

[bttfw]

Same

[datascope11]

Same error here. Started occurring for me 8/8/2023 around ~1:30pm EST... Tried updating the component, but same result.

[pbvdven]

Yes its working again. Thanks

[jooslouw]

Working again after reloading the Helium integration. Thanks

[roelvandermade]

Hi the issue clearly seems to be the backend, I noticed you are using a backend you maybe created yourself? There are several publically available official Solana API services, wouldn't it make it more sense to use one of those to get the required data?

[enes-oerdek]

Hi the issue clearly seems to be the backend, I noticed you are using a backend you maybe created yourself? There are several publically available official Solana API services, wouldn't it make it more sense to use one of those to get the required data?

Unfortunately, it is not sufficient to just grab data from the api, and sometimes external services have costs. I am running a very simple backend server, which costs me 3$ per month where I can provide all the needed calculations and processes to get the required data. Everything is heavily cached.

Actually the currently existing issue is due to an external service no longer working. This integration is dependend on this endpoint: https://github.com/lthiery/hnt-explorer
https://hnt-explorer.herokuapp.com/v1/positions/vehnt

I will work on running this service as well on this integration's backend, to have better availability. Sorry again for the inconvenience.

[roelvandermade]

Hi the issue clearly seems to be the backend, I noticed you are using a backend you maybe created yourself? There are several publically available official Solana API services, wouldn't it make it more sense to use one of those to get the required data?

Unfortunately, it is not sufficient to just grab data from the api, and sometimes they cost money. I am running a very simple backend server, which costs me 3$ per month where I can provide all the needed calculations and processes to get the required data. Actually the currently existing issue is due to an external service no longer working. This integration is dependend on this endpoint: https://github.com/lthiery/hnt-explorer https://hnt-explorer.herokuapp.com/v1/positions/vehnt

I will work on running this service as well on this integration's backend, to have better availability. Sorry again for the inconvenience.

Aha, clear. Yeah those external dependancies aren't the greatest to rely on ;-)
If you need any help server-side (config/tuning/etc.), let me know.

thanks!

[roelvandermade]

Issue should be resolved. That external service is now also running on the backend. Availability should improve.

so I noticed indeed, great work & thanks!

[jooslouw]

Issue should be resolved. That external service is now also running on the backend. Availability should improve.

Excellent! Thanks Enes for the effort and great work. Much appreciated.

[enes-oerdek]

You are very welcome. Thanks again for raising the issue. I will close this issue. In case you face other issues, please create a new issue.