Boot loop if internet access is blocked

[1337-gitter]

On startup, the glow tries to access glow-energy.io (I assume to check for firmware updates). On my network, IOT devices like the glow are located within a separate VLAN which doesn't have access to the internet. In this situation, the glow performs constant resets and cannot be used at all.
I can resolve the situation if I grant internet access to the glow. In this case, everything works like a charm.

Is there a way to disable the connection to glow-energy.io or would it be possible to make it more robust?

Kind regards,
André

[klaasnicolaas]

I would keep it easy for yourself and give the glow access to the internet, so that it continue to receive firmware updates.

An alternative is to create a custom firmware for your glow. I'm not sure if just adopting is enough to disable the http_request update or if you actually need to create your own YAML config from the ground up and customize it.

./Klaas

[1337-gitter]

Sorry, but I'm not so familiar with ESPHome.
Can I use !remove? But which part of updates.yaml should I remove?
If I use !extend, could I set 'timeout' of http_request to 0 to avoid blocking?

Thanks,
André

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[1337-gitter]

I would be glad to receive an answer to my questions.

[klaasnicolaas]

You could indeed use !remove to remove a piece of config.

Might start with removing the http_request under ota, something like:

ota:
  - id: !remove ota_http_request

or

http_request: !remove
update: !remove

./Klaas