Souci HACS depuis changement d'IP

bentou · Juin 26, 2024, 6:44

Bonjour,

J’ai changé mon plan d’adressage IP,
reparamétré mon HA
changé les adresses des esp
tout marche bien sauf les mises à jour HACS. elles apparaissent, mais il ne se passe rien quand je clique dessus.

Cette erreur provient d'une intégration personnalisée

Enregistreur: custom_components.hacs
Source: custom_components/hacs/base.py:734
intégration: HACS (documentation, problèmes)
S'est produit pour la première fois: 25 juin 2024 à 17:04:51 (45 occurrences)
Dernier enregistrement: 08:33:06

A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/custom-components/ble_monitor/12.11.3/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 0
A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/cyr-ius/hass-livebox-component/2.2.7/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 1
A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/totaldebug/atomic-calendar-revive/v9.7.0/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 0
A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/dougiteixeira/proxmoxve/3.4.2/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 0
A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/cyr-ius/hass-livebox-component/2.2.7/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 0

depuis la console je teste:

config $ wget https://raw.githubusercontent.com/totaldebug/atomic-calendar-revive/v9.7.0/info.md
--2024-06-26 08:39:05--  https://raw.githubusercontent.com/totaldebug/atomic-calendar-revive/v9.7.0/info.md
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 2606:50c0:8002::154, 2606:50c0:8001::154, 2606:50c0:8000::154, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|2606:50c0:8002::154|:443...

tiens, de lipv6 ? je teste en désactivant l’ipv6:

Échec de la modification des paramètres réseau
Can't update config on end0: ipv6.dns: this property is not allowed for 'method=link-local'

et Paf le chien…
un ping sur google.com ne passe pas en ipv6 mais est OK en ipv4:

config $ ping -6 google.com
PING google.com (2a00:1450:4007:81a::200e): 56 data bytes
^C
--- google.com ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
config $ ping -4 google.com
PING google.com (142.250.201.174): 56 data bytes
64 bytes from 142.250.201.174: seq=0 ttl=116 time=2.616 ms
64 bytes from 142.250.201.174: seq=1 ttl=116 time=2.430 ms
64 bytes from 142.250.201.174: seq=2 ttl=116 time=2.461 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 2.430/2.502/2.616 ms
config $

Pulpy-Luke · Juin 26, 2024, 6:53

Salut.

Oui l’ipv6 c’est pas le top sur HA.
Et avec cette config, HACS ne sait pas accéder à internet. Donc soit tu repasses en ipv4 soit il faut finaliser le réseau en ipv6 (dns et passerelle notamment)

bentou · Juin 26, 2024, 6:55

oui, mais comment désactiver l’ipV6 sur HA ?
j’ai pas réussi depuis l’interface graphique et je suis en haos, donc pas grand chose en mode commande.

Pulpy-Luke · Juin 26, 2024, 6:58

Pourtant, c’est écrit en gros

vers

bentou · Juin 26, 2024, 6:59

si je clique sur désactivée:

Échec de la modification des paramètres réseau
Can't update config on end0: ipv6.dns: this property is not allowed for 'method=link-local'

bentou · Juin 26, 2024, 6:59

Pulpy-Luke · Juin 26, 2024, 7:00

Regarde ça

github.com/home-assistant/supervisor

Cant disable IPv6

opened 11:04AM - 11 Jun 24 UTC

closed 07:48PM - 24 Jun 24 UTC

partxxx

bug

### Describe the issue you are experiencing I set up an "automatic" IPv6 than i… would like to disable it and got this message " Can't update config on enu1: ipv6.dns: this property is not allowed for 'method=link-local' " ### What operating system image do you use? odroid-xu4 (Hardkernel ODROID-XU4) ### What version of Home Assistant Operating System is installed? 6.6.29-haos ### Did you upgrade the Operating System. Yes ### Steps to reproduce the issue 1. Enable IPv6 automatic 2. save 3. Try to disable ... ### Anything in the Supervisor logs that might be useful for us? ```txt 2024-06-11 12:40:23.268 ERROR (MainThread) [supervisor.host.network] Can't update config on enu1: ipv6.dns: this property is not allowed for 'method=link-local' 2024-06-11 12:40:42.826 INFO (MainThread) [supervisor.host.network] Updating local network information ``` ### Anything in the Host logs that might be useful for us? ```txt 2024-06-11 10:43:44.120 homeassistant NetworkManager[444]: <info> [1718102624.1201] audit: op="connection-update" uuid="e99e701e-8502-3562-9685-32611aba8642" name="Supervisor enu1" result="fail" reason="ipv6.dns: this property is not allowed for 'method=link-local'" IP Address: 2001:4c4e:1506:a300:4663:dc94:6c57:a6af/64, fe80::9d40:e75a:5430:ab19/64 Gateway: fe80::da07:b6ff:fe76:c7fc Method: auto Name Servers: ::1 ``` ### System information ## System Information version | core-2024.6.1 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.2 os_name | Linux os_version | 6.6.29-haos arch | armv7l timezone | Europe/Budapest config_dir | /config <details><summary>Home Assistant Community Store</summary> GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1392 Downloaded Repositories | 2 HACS Data | pending </details> <details><summary>Home Assistant Cloud</summary> logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | pending can_reach_cloud | ok </details> <details><summary>Home Assistant Supervisor</summary> host_os | Home Assistant OS 12.3 -- | -- update_channel | stable supervisor_version | supervisor-2024.06.0 agent_version | 1.6.0 docker_version | 25.0.5 disk_total | 56.3 GB disk_used | 5.9 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | odroid-xu4 supervisor_api | ok version_api | pending installed_addons | File editor (5.8.0), chrony (3.0.1), Terminal & SSH (9.14.0), ESPHome (2024.5.5), AdGuard Home (5.1.1), Mosquitto broker (6.4.1), Zigbee2MQTT (1.38.0-1), Silicon Labs Flasher (0.2.3) </details> <details><summary>Dashboards</summary> dashboards | 1 -- | -- resources | 0 views | 1 mode | storage </details> <details><summary>Recorder</summary> oldest_recorder_run | 7 June 2024 at 20:28 -- | -- current_recorder_run | 11 June 2024 at 12:17 estimated_db_size | 51.09 MiB database_engine | sqlite database_version | 3.44.2 </details> ### Additional information _No response_

bentou · Juin 26, 2024, 7:03

Ah oui, en automatique, c’est quasiment instantané comme réaction…

je devais être en statique depuis toujours et comme j’avais pas de connexion, je l’ai jamais vu…

bentou · Juin 26, 2024, 7:13


       ▄██▄           _   _                                    
     ▄██████▄        | | | | ___  _ __ ___   ___               
   ▄████▀▀████▄      | |_| |/ _ \| '_ ` _ \ / _ \              
 ▄█████    █████▄    |  _  | (_) | | | | | |  __/              
▄██████▄  ▄██████▄   |_| |_|\___/|_| |_| |_|\___|          _   
████████  ██▀  ▀██      / \   ___ ___(_)___| |_ __ _ _ __ | |_ 
███▀▀███  ██   ▄██     / _ \ / __/ __| / __| __/ _` | '_ \| __|
██    ██  ▀ ▄█████    / ___ \\__ \__ \ \__ \ || (_| | | | | |_ 
███▄▄ ▀█  ▄███████   /_/   \_\___/___/_|___/\__\__,_|_| |_|\__|
▀█████▄   ███████▀

Welcome to the Home Assistant command line.

System information
  IPv4 addresses for end0:  192.168.1.25/24
  IPv6 addresses for end0:  2a01:cb00:fb:df00:0000:0000:0000:ba1/64, fdf8:91e9:2bf8:0000:0000:0000:0000:af7d/64, fe80::3bba:0000:0000:a749/64
  IPv4 addresses for wlan0: 

  OS Version:               Home Assistant OS 12.4
  Home Assistant Core:      2024.6.4

  Home Assistant URL:       http://homeassistant.local:8123
  Observer URL:             http://homeassistant.local:4357
~ $ ping -6 google.com
PING google.com (2a00:1450:4007:81a::200e): 56 data bytes
64 bytes from 2a00:1450:4007:81a::200e: seq=0 ttl=249 time=3.156 ms
64 bytes from 2a00:1450:4007:81a::200e: seq=1 ttl=249 time=3.103 ms
64 bytes from 2a00:1450:4007:81a::200e: seq=2 ttl=249 time=3.049 ms
64 bytes from 2a00:1450:4007:81a::200e: seq=3 ttl=249 time=2.769 ms
64 bytes from 2a00:1450:4007:81a::200e: seq=4 ttl=249 time=5.624 ms
^C
--- google.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 2.769/3.540/5.624 ms

et mes upgrades sont passés crème.