O home assistant parou de funcionar DENOVO

Olha eu de novo com este assunto.
Não sei o que fiz de errado, mas vou procurar ser o mais claro possível.

Tenho duas haspberry PI 3B+

Eu estava usando a versão hassos_rpi3-2.11 e fui atualizar para a hassos_rpi3-2.12

Parou de funcionar não consegui nem mesmo visualizar nada pelo endereo
http://hassio.local:8123.

Basicamente tinha instalado o configurator, SSH server, duckDNS e mosquito broquer.

Como já era uma instalação antiga, resolvi partir para uma instalação do zero., já que tenho backup dos ficheiros, deveria ser rápido e fácil.

Mas o que esta acontecendo, consigo instalar o hassio no cartão SD, e depois do boot,
consigo instalar os addons, e configurar os ficheiros.

Mas depois do reboot, o sistema não mostra a página de visão geral. fica como se estivesse carregando, mas não carrega nunca.

resolvi fazer uma instalação mais sinples, sem o duckdns e o sshserver.
Simplifiquei também a quantidade de dispositivos, para apenas um módulo no arquivo configuration.yalm.
quando testo a configuração, não aparece nenhum erro. mas a página de visão geral não carrega mesmo assim.

uffa. não sei o que acintece. alguém sabe o porque o hassio parece tão instável?

Já viste os logs? Tens a certeza que o IP não alterou?

Além daquilo que o @tmarquespt disse experimentaste limpar a cache do browser?

Ainda não consegui fazer funcionar.
vou colocar minha configurações aqui, assim se eu estiver fazendo coisa errada, alguém poderá me mostrar. mas já estou cansado.

as configurações do mosquito broker

{
  "logins": [
    {
      "username": "username_mqtt",
      "password": "meu_pass_mqtt"
    }
  ],
  "anonymous": false,
  "customize": {
    "active": false,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}

o log do broker

[10:05:46] INFO: Setup mosquitto configuration
[10:05:46] WARNING: SSL not enabled - No valid certs found!
[10:05:46] INFO: Found local users inside config
[10:05:46] INFO: Initialize Hass.io Add-on services
[10:05:46] INFO: Initialize Home Assistant discovery
[10:05:46] INFO: Start Mosquitto daemon
1563455146: mosquitto version 1.6.3 starting
1563455146: Config loaded from /etc/mosquitto.conf.
1563455146: Loading plugin: /usr/share/mosquitto/auth-plug.so
1563455146:  ├── Username/password checking enabled.
1563455146: |-- *** auth-plug: startup
1563455146:  ├── TLS-PSK checking enabled.
1563455146:  └── Extended authentication not enabled.
1563455146: Opening ipv4 listen socket on port 1883.
1563455146: Opening ipv6 listen socket on port 1883.
1563455146: Opening websockets listen socket on port 1884.
1563455147: Warning: Mosquitto should not be run as root/administrator.

secret.yaml


# Use this file to store secrets like usernames and passwords.
# Learn more at https://home-assistant.io/docs/configuration/secrets/
some_password: welcome

latitude: -26.703375
longitude: -42.497417

darksky_key: aqui_tenho_minha chave_numérica

configuration.yaml

homeassistant:
  # Name of the location where Home Assistant is running
  name: Casa
  # Location required to calculate the time the sun rises and sets
  latitude: !secret latitude
  longitude: !secret longitude
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 0
  # metric for Metric, imperial for Imperial
  unit_system: metric
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: America/Sao_Paulo
  # Customization file
  customize: !include customize.yaml

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Discover some devices automatically
discovery:

# Sensors
sensor:
  # Weather prediction
  #- platform: yr
  
  - platform: darksky
    api_key: !secret darksky_key
    monitored_conditions:
    #- summary
   # - nearest_storm_distance
    #- wind_speed
    #- wind_bearing
    #- temperature
    #- humidity
    #- pressure
    #- visibility
    #- ozone
    
  - platform: systemmonitor
    resources:
    - type: disk_use_percent
      arg: /home
    - type: memory_use_percent
    - type: processor_use

mqtt:
  broker: !secret broker_ip
  username: !secret user_mqtt
  password: !secret password_mqtt
  
light 1:
      platform: mqtt
      name: sala de aula
      icon: mdi:lightbulb
      state_topic: 'iead/switch_1/status'
      command_topic: 'iead/switch_1/switch'
      optimistic: false
      qos: 1
      availability_topic: "iead/switch_1/lwt"
      payload_on: "ON"
      payload_off: "OFF"
      payload_available: "ONLINE" 
      payload_not_available: "OFFLINE"
      retain: false
           
light 2:
      platform: mqtt
      name: Iluminação da entrada
      icon: mdi:lightbulb
      state_topic: 'iead/light_1/status'
      command_topic: 'iead/light_1/set'
      optimistic: false
      qos: 1
      availability_topic: "iead/light_1/lwt"
      payload_on: "ON"
      payload_off: "OFF"
      payload_available: "ONLINE"
      payload_not_available: "OFFLINE"
      retain: true
      
      
light 3:
      platform: mqtt
      name: Iluminação da rampa
      icon: mdi:lightbulb
      state_topic: 'iead/light_4/status'
      command_topic: 'iead/light_4/set'
      optimistic: false
      qos: 1
      availability_topic: "iead/light_4/lwt"
      payload_on: "ON"
      payload_off: "OFF"
      payload_available: "ONLINE"
      payload_not_available: "OFFLINE"
      retain: true
      
light RGB 1:
      platform: mqtt
      name: 'iead RGB light'
      state_topic: 'iead/rgb1/light/status'
      command_topic: 'iead/rgb1/light/switch'
      brightness_state_topic: 'iead/rgb1/brightness/status'
      brightness_command_topic: 'iead/rgb1/brightness/set'
      rgb_state_topic: 'iead/rgb1/rgb/status'
      rgb_command_topic: 'iead/rgb1/rgb/set'
      availability_topic: "iead/rgb1/light/lwt"
      payload_available: "ONLINE"
      payload_not_available: "OFFLINE"
      brightness_scale: 100
      optimistic: false
      
      
      


# Text to speech
tts:
  - platform: google_translate
  
http:
  base_url: 192.168.15.5:8123   
  api_password: supervalorizacao
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
  ip_ban_enabled: True
  login_attempts_threshold: 150

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml


tenho poucos dispositivos instalados mesmo.

mas por que parou não sei.

Sem logs ninguém vai adivinhar o que se passa…

tas a usar as platformas mal porque usares light 1: light 2: light 3: ??
o name é que vai defenir o nome do light que vai criar que será

 light.iluminação_da_rampa 
 light.Iluminação_da_entrada
 light.sala _de_aula 
 
light:
  - platform: mqtt
    name: sala de aula
    icon: mdi:lightbulb
    state_topic: 'iead/switch_1/status'
    command_topic: 'iead/switch_1/switch'
    optimistic: false
    qos: 1
    availability_topic: "iead/switch_1/lwt"
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "ONLINE" 
    payload_not_available: "OFFLINE"
    retain: false
           

  - platform: mqtt
    name: Iluminação da entrada
    icon: mdi:lightbulb
    state_topic: 'iead/light_1/status'
    command_topic: 'iead/light_1/set'
    optimistic: false
    qos: 1
    availability_topic: "iead/light_1/lwt"
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "ONLINE"
    payload_not_available: "OFFLINE"
    retain: true
    
      

  - platform: mqtt
    name: Iluminação da rampa
    icon: mdi:lightbulb
    state_topic: 'iead/light_4/status'
    command_topic: 'iead/light_4/set'
    optimistic: false
    qos: 1
    availability_topic: "iead/light_4/lwt"
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "ONLINE"
    payload_not_available: "OFFLINE"
    retain: true
      

  - platform: mqtt
    name: 'iead RGB light'
    state_topic: 'iead/rgb1/light/status'
    command_topic: 'iead/rgb1/light/switch'
    brightness_state_topic: 'iead/rgb1/brightness/status'
    brightness_command_topic: 'iead/rgb1/brightness/set'
    rgb_state_topic: 'iead/rgb1/rgb/status'
    rgb_command_topic: 'iead/rgb1/rgb/set'
    availability_topic: "iead/rgb1/light/lwt"
    payload_available: "ONLINE"
    payload_not_available: "OFFLINE"
    brightness_scale: 100

é claro que nao pode reinciar ate limpares erros

Descobri que o HA estava em um endereço ip errado.
Corrigi isto com as configurações que se coloca no pen drive.

Olhando o log do broker percebo que os 3 pontos de luz que tenho estão se comunicando com o broker:
este é o log do broker:

[22:48:20] INFO: Setup mosquitto configuration
[22:48:20] WARNING: SSL not enabled - No valid certs found!
[22:48:20] INFO: Found local users inside config
[22:48:21] INFO: Initialize Hass.io Add-on services
[22:48:21] INFO: Initialize Home Assistant discovery
[22:48:21] INFO: Start Mosquitto daemon
1563500901: |-- *** auth-plug: startup
1563500901: mosquitto version 1.6.3 starting
1563500901: Config loaded from /etc/mosquitto.conf.
1563500901: Loading plugin: /usr/share/mosquitto/auth-plug.so
1563500901:  ├── Username/password checking enabled.
1563500901:  ├── TLS-PSK checking enabled.
1563500901:  └── Extended authentication not enabled.
1563500901: Opening ipv4 listen socket on port 1883.
1563500901: Opening ipv6 listen socket on port 1883.
1563500901: Opening websockets listen socket on port 1884.
1563500901: Warning: Mosquitto should not be run as root/administrator.
1563500902: New connection from 192.168.15.18 on port 1883.
[INFO] found wilson on local database
1563500905: New client connected from 192.168.15.18 as iluminação da rampa (p2, c1, k15, u'wilson').
1563500905: New connection from 192.168.15.17 on port 1883.
1563500905: New connection from 192.168.15.15 on port 1883.
1563500905: New client connected from 192.168.15.17 as office_rgb_light (p2, c1, k15, u'wilson').
1563500905: New client connected from 192.168.15.15 as chaveamento_tipo_1 (p2, c1, k15, u'wilson').
1563500917: Socket error on client iluminação da rampa, disconnecting.
1563500922: New connection from 192.168.15.18 on port 1883.
1563500922: New client connected from 192.168.15.18 as iluminação da rampa (p2, c1, k15, u'wilson').
1563501074: New connection from 172.30.32.1 on port 1883.
[INFO] found homeassistant on local database
1563501077: New client connected from 172.30.32.1 as auto-40193E0E-18CF-CA6F-7FB0-E925F622DC08 (p2, c1, k60, u'homeassistant').


e mesmo assim não consigo que nada apareça na visão geral do HA.

acredito que o problema esteja em configuration.yaml.

o que fiz para teste:

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123


  
  light:
      platform: mqtt
      name: 'iead RGB light'
      state_topic: 'iead/rgb1/light/status'
      command_topic: 'iead/rgb1/light/switch'
      brightness_state_topic: 'iead/rgb1/brightness/status'
      brightness_command_topic: 'iead/rgb1/brightness/set'
      rgb_state_topic: 'iead/rgb1/rgb/status'
      rgb_command_topic: 'iead/rgb1/rgb/set'
      availability_topic: "iead/rgb1/light/lwt"
      payload_available: "ONLINE"
      payload_not_available: "OFFLINE"
      brightness_scale: 100
      optimistic: false

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

e a lâmpada rgb não aparece.

não sei mais o que fazer.

instalei a versão mais recente em uma raspberry pi 3B+

o log do sistema é este:

19-07-19 03:12:22 INFO (MainThread) [__main__] Initialize Hass.io setup
19-07-19 03:12:23 INFO (MainThread) [__main__] Setup HassIO
19-07-19 03:12:23 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/armv7-hassio-supervisor with version 169
19-07-19 03:12:23 INFO (SyncWorker_0) [hassio.docker.supervisor] Connect Supervisor to Hass.io Network
19-07-19 03:12:24 INFO (SyncWorker_0) [hassio.docker.interface] Cleanup images: ['homeassistant/armv7-hassio-supervisor:163']
19-07-19 03:12:25 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.systemd1 on /org/freedesktop/systemd1
19-07-19 03:12:25 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
19-07-19 03:12:25 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.hostname1 on /org/freedesktop/hostname1
19-07-19 03:12:26 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
19-07-19 03:12:26 INFO (MainThread) [hassio.utils.gdbus] Introspect de.pengutronix.rauc on /
19-07-19 03:12:26 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: de.pengutronix.rauc - /
19-07-19 03:12:26 INFO (MainThread) [hassio.host.info] Update local host information
19-07-19 03:12:26 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
19-07-19 03:12:26 INFO (MainThread) [hassio.host.services] Update service information
19-07-19 03:12:26 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
19-07-19 03:12:27 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
19-07-19 03:12:27 INFO (MainThread) [hassio.host.services] Reload local service hassos-apparmor.service

19-07-19 03:12:27 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1
19-07-19 03:12:27 INFO (SyncWorker_1) [hassio.docker.interface] Attach to homeassistant/raspberrypi3-homeassistant with version landingpage
19-07-19 03:12:27 INFO (MainThread) [hassio.hassos] Detect HassOS 2.12 on host system
19-07-19 03:12:27 INFO (SyncWorker_2) [hassio.docker.hassos_cli] Found HassOS CLI homeassistant/armv7-hassio-cli with version 11
19-07-19 03:12:27 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/a0d7b954 repository
19-07-19 03:12:27 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/core repository
19-07-19 03:12:27 INFO (MainThread) [hassio.store] Load add-ons from store: 59 all - 59 new - 0 remove
19-07-19 03:12:27 INFO (MainThread) [hassio.addons] Found 0 installed add-ons
19-07-19 03:12:27 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
19-07-19 03:12:30 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files
19-07-19 03:12:30 INFO (MainThread) [hassio.discovery] Load 0 messages
19-07-19 03:12:30 INFO (MainThread) [hassio.ingress] Load 0 ingress session
19-07-19 03:12:30 INFO (MainThread) [__main__] Run Hass.io
19-07-19 03:12:30 INFO (MainThread) [hassio.misc.dns] Start DNS port forwarding for host add-ons

19-07-19 03:12:30 INFO (MainThread) [hassio.api] Start API on 172.30.32.2
19-07-19 03:12:30 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
19-07-19 03:12:30 INFO (MainThread) [hassio.addons] Phase 'system' start 0 add-ons
19-07-19 03:12:30 INFO (MainThread) [hassio.addons] Phase 'services' start 0 add-ons
19-07-19 03:12:30 INFO (SyncWorker_5) [hassio.docker.interface] Restart homeassistant/raspberrypi3-homeassistant
19-07-19 03:12:36 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-07-19 03:12:36 INFO (MainThread) [hassio.addons] Phase 'application' start 0 add-ons
19-07-19 03:12:36 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
19-07-19 03:12:36 INFO (MainThread) [hassio.core] Hass.io is up and running
19-07-19 03:12:36 INFO (MainThread) [hassio.homeassistant] Setup Home Assistant
19-07-19 03:12:36 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.96.1.
19-07-19 03:19:19 INFO (SyncWorker_0) [hassio.docker.interface] Tag image homeassistant/raspberrypi3-homeassistant with version 0.96.1 as latest
19-07-19 03:19:19 INFO (MainThread) [hassio.homeassistant] Home Assistant docker now installed
19-07-19 03:19:19 INFO (MainThread) [hassio.homeassistant] Start Home Assistant
19-07-19 03:19:19 INFO (SyncWorker_19) [hassio.docker.interface] Stop homeassistant application
19-07-19 03:19:21 INFO (SyncWorker_19) [hassio.docker.interface] Clean homeassistant application

19-07-19 03:19:22 INFO (SyncWorker_19) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.96.1
19-07-19 03:19:42 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-07-19 03:19:42 INFO (SyncWorker_4) [hassio.docker.interface] Cleanup images: ['homeassistant/raspberrypi3-homeassistant:landingpage']
19-07-19 03:33:40 INFO (MainThread) [hassio.addons] Create Home Assistant add-on data folder /data/addons/data/core_configurator
19-07-19 03:33:40 INFO (SyncWorker_19) [hassio.docker.interface] Pull image homeassistant/armv7-addon-configurator tag 3.4.
19-07-19 03:34:44 INFO (SyncWorker_19) [hassio.docker.interface] Tag image homeassistant/armv7-addon-configurator with version 3.4 as latest
19-07-19 03:37:30 INFO (SyncWorker_4) [hassio.docker.addon] Start Docker add-on homeassistant/armv7-addon-configurator with version 3.4
19-07-19 03:37:49 INFO (MainThread) [hassio.addons] Create Home Assistant add-on data folder /data/addons/data/core_mosquitto
19-07-19 03:37:49 INFO (SyncWorker_11) [hassio.docker.interface] Pull image homeassistant/armv7-addon-mosquitto tag 5.0.

19-07-19 03:38:02 INFO (SyncWorker_11) [hassio.docker.interface] Tag image homeassistant/armv7-addon-mosquitto with version 5.0 as latest
19-07-19 03:38:31 INFO (SyncWorker_12) [hassio.docker.addon] Start Docker add-on homeassistant/armv7-addon-mosquitto with version 5.0
19-07-19 03:38:33 INFO (MainThread) [hassio.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
19-07-19 03:38:33 INFO (MainThread) [hassio.discovery] Send discovery to Home Assistant mqtt from core_mosquitto
19-07-19 03:38:33 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
19-07-19 03:38:33 INFO (MainThread) [hassio.discovery] Discovery 37b9fcf6b0234ec6b21fd94ba79be3ec message send
19-07-19 03:45:29 INFO (SyncWorker_12) [hassio.docker.interface] Restart homeassistant/raspberrypi3-homeassistant
19-07-19 03:45:52 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-07-19 03:54:10 INFO (SyncWorker_0) [hassio.docker.interface] Restart homeassistant/raspberrypi3-homeassistant
19-07-19 03:54:37 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance

Tens de te organizar e ser claro nos pedidos de ajuda.

Pedi.te os logs e para confirmares o IP logo ao início porque nem conseguias abrir o HA.

Agora parece-me que o teu problema é que não sabes configurar o lovelace., E para isso não interessam os logs.

Começa lá de novo e diz o que se passa caso contrário ninguém percebe qual é verdadeiramente o teu problema.

a lampada nao poderá funcionar porque indentation do código esta toda mal, e obviamente tu nao usas as ferramentas que o HA te oferece para verificares errors, neste caso o check config…
se usares o que tens ai em cima da te erro…

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123


  
  light:
      platform: mqtt
      name: 'iead RGB light'
      state_topic: 'iead/rgb1/light/status'
      command_topic: 'iead/rgb1/light/switch'
      brightness_state_topic: 'iead/rgb1/brightness/status'
      brightness_command_topic: 'iead/rgb1/brightness/set'
      rgb_state_topic: 'iead/rgb1/rgb/status'
      rgb_command_topic: 'iead/rgb1/rgb/set'
      availability_topic: "iead/rgb1/light/lwt"
      payload_available: "ONLINE"
      payload_not_available: "OFFLINE"
      brightness_scale: 100
      optimistic: false

2

se usares da maneira correta…

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123


  
light:
  - platform: mqtt
    name: 'iead RGB light'
    state_topic: 'iead/rgb1/light/status'
    command_topic: 'iead/rgb1/light/switch'
    brightness_state_topic: 'iead/rgb1/brightness/status'
    brightness_command_topic: 'iead/rgb1/brightness/set'
    rgb_state_topic: 'iead/rgb1/rgb/status'
    rgb_command_topic: 'iead/rgb1/rgb/set'
    availability_topic: "iead/rgb1/light/lwt"
    payload_available: "ONLINE"
    payload_not_available: "OFFLINE"
    brightness_scale: 100
    optimistic: false

ja nao tens erros…
1

tens andado preocupado com logs etc… quando o problema real é a própria maneira de inserção de código…uma coisa de cada vez…
se tens o código todo arranjado na maneira que te postei em cima porque nao poes te como está lá?
copy e paste

Realmente não estamos nos entendendo.

Eu sempre procuro estudar e tentar tudo antes de recorrer ao forum.

O fato é que muita coisa estranha esta acontecendo.

Eu sempre verificava a validação dos códigos antes, mas agora nesta última versão do HA o botão de verificação não aparece.

Existe sim uma instabilidade no HA.

Com relação a formatação do código, acho que na hora de colar o código aqui, posso ter errado na formatação, mas a formatação do arquivo esta, ou estava correta, porque era o que usava antes desta quebra.

Deixando o passado de lado e começando tudo de novo, hoje por volta das duas da manhã consegui colocar a lâmpada RGB para funcionar. ou seja o problema esta na forma como escrevo o arquivo configuration.yaml. OK. existe algum manual, onde eu possa aprender mais sobre isto. Porque na página web do HA, vejo mais é exemplos de outros usuários, gostaria de aprender mais sobre esta configuração de uma forma mais formal.

convém sempre ver o que á de novo com as novas updates, nao é so fazer update…
em cada update á sempre muitas breaking changes que convém ler para se preparar

a partir da 0.96.0 para aceder a isso tem de habilitar advance mode

para abilitar tem de ir á nova side bar…
1
depois vai la ver nova opcao Advanced mode
2
habilta opcao e vai encontrar o check config onde teve sempre

Em termos de manuais so o site do HA, google, youtube
existe muita informação disponível por ai espalhada

É isso mesmo, estou estudando por aqui, e já consegui resolver.

Olhem como ficou, agora vou melhorar aos poucos.

Acho que podemos encerrar este tópico.

obrigado.

edita ai a foto tas a mostrar o teu duckdns moranda !!!
ja te editei a foto…


Copyright © 2017-2020. Todos os direitos reservados
CPHA.pt - info@cpha.pt


FAQ | Termos de Serviço/Regras | Política de Privacidade