Offizielles FHEM Docker Basis Image für verschiedene Plattformen

Begonnen von Loredo, 28 Juli 2018, 21:24:57

Vorheriges Thema - Nächstes Thema

Sidey

Hi,

Packages nachinstallieren ist ein antipattern für Docker und muss jedesmal wenn das Image geladen wird wiederholt werden.


Ich beschäftige mich gerade mit Version 4 des Images.
Darin ist das von dir erwähnte Perl Paket auch installiert:


ghcr.io/fhem/fhem-docker:4.0.0-beta1-bullseye

Gruß Sidey
Signalduino, Homematic, Raspberry Pi, Mysensors, MQTT, Alexa, Docker, AlexaFhem

Maintainer von: SIGNALduino, fhem-docker, alexa-fhem-docker, fhempy-docker

joachimS

Super!
Danke für die Antworten.
docker run -d --name FHEM -p 1883:1883 -p 8083:8083 -v fhem:/opt/fhem -e CPAN_PKGS="XML::Bare" --device=/dev/ttyACM0 fhem/fheminstalliert das XML prereq und SIRD tut nun.
Aber klar, ich warte auf den neuen Container
Gruss
Joachim

(fhem auf Synology DS209, CUL, FS20, FHT, EM, HM, Keymatic, Hue, OpenDTU)

Homalix99

Hallo,
ich habe schon lange Fhem auf Docker am Laufen. Aber jedesmal, wenn der Docker Server neu gestartet wird, ist der Mountpoint zur Fritzbox weg und ich muss diesen innerhalb der Shell im Container wieder händisch einhängen. Bei restart des Fhem containers bleibt der mount erhalten.
Im File post-start.sh (Wird ja nach jedem Start des fhem-containers ausgeführt) ist der mount definiert:
mkdir /mnt/Fritz.Nas
mount -t cifs -o username=fhem,password=##fhembackupusr*,uid=6061,gid=6061,noserverino,sec=ntlmv2 //192.168.3.1/fritz.nas/Generic-FlashDisk-01/FHEM /mnt/Fritz.Nas

Wie kann es funktionieren?

Gruß

Alex

- RPI 4 fhem in Docker, 2 x Arduino Uno, HM-GW, HM-Dev. (Fensterkontakte, HK-Thermostate, div. Aktoren), JeeLink,
- GPIOs, HM-LAN, ESPs (MQTT2)
-Überwachung Fenster/Türen/Licht, HK-Thermostatregelung, Rollosteuerung, Überw. Betriebstemperaturen Heizung, Erfassung Gas/Wasser, PV-Anl., Wetter (WS1600)

Sidey

Wie wäre es, wenn Du den Mountpoint über Docker und nicht innerhalb des Containers verbindest?
docker volume create \
--driver local \
--opt type=cifs \
--opt device=//192.168.3.1/fritz.nas/Generic-FlashDisk-01/FHEM \
--opt o=addr=uxxxxx.your-server.de,username=uxxxxxxx,password=*****,file_mode=0777,dir_mode=0777 \
--name vol-fritzbox

Ich habe es selbst nicht versucht, würde aber vermuten, dass es der empfohlene Weg ist, denn innerhalb von Containern sollte nichts verändert werden was beim Nächsten Laden des Containers auch vorhanden sein soll:


Falls Du compose verwendest, so sollte es damit gehen:
volumes:
  vol-fritzbox:
    driver_opts:
      type: cifs
      o: username={smbuser},password={smbpass},uid={UID for mount},gid={gid for mount},vers=3.0
      device: //192.168.3.1/fritz.nas/Generic-FlashDisk-01/FHEM

Quelle:
https://forums.docker.com/t/how-to-map-lan-network-share-to-docker-volume/97276/2


PS: Das Passwort änderst Du jetzt hoffentlich, nachdem Du es hier veröffentlicht hast.
Signalduino, Homematic, Raspberry Pi, Mysensors, MQTT, Alexa, Docker, AlexaFhem

Maintainer von: SIGNALduino, fhem-docker, alexa-fhem-docker, fhempy-docker

Homalix99

Hallo Sidey,

erstmal danke für Deine Nachricht.
Die Idee das mit Volumes zu lösen hörte sich gut an.
Habe ich soweit hinbekommen, dass zwar der Fhem Container wieder läuft, aber innerhalb des Fhem Containers funktioniert der mount leider nicht.
Folgendes compose-file:
volumes:
  vol-fritzbox:
    driver: local
    driver_opts:
      type: cifs
      o: username=fhem,password=xxxxxxxxx,uid=6061,gid=20,vers=3.0
      device: //192.168.3.1/fritz.nas/Generic-FlashDisk-01/FHEM

services:
    fhem:
        image: fhem/fhem:latest
        restart: always
        container_name: fhem
        hostname: FHEM-Docker
        privileged: true
        ports:
            - "8083:8083"
            - "8084:8084"
            - "7072:7072"
            - "5987:5987"
            - "5060:5060"
            - "5070:5070"
            - "5080:5080"
            - "139:139"
            - "445:445"
            - "1000:1000"
...

        volumes:
            - ./fhem/core/:/opt/fhem/
            - /etc/localtime:/etc/localtime:ro
            - /sys/class/gpio:/sys/class/gpio
            - /sys/devices/platform/soc/fe200000.gpio:/sys/devices/platform/soc/fe200000.gpio
            - /dev/serial/by-id:/dev/serial/by-id
            - vol-fritzbox:/mnt/Fritz.Nas:rw
...
Ein docker inspect volume zeigt dies:
docker volume inspect  fhem-docker_vol-fritzbox:
[
    {
        "CreatedAt": "2024-02-23T15:57:33+01:00",
        "Driver": "local",
        "Labels": {
            "com.docker.compose.project": "fhem-docker",
            "com.docker.compose.version": "1.29.2",
            "com.docker.compose.volume": "vol-fritzbox"
        },
        "Mountpoint": "/var/lib/docker/volumes/fhem-docker_vol-fritzbox/_data",
        "Name": "fhem-docker_vol-fritzbox",
        "Options": {
            "device": "//192.168.3.1/fritz.nas/Generic-FlashDisk-01/FHEM",
            "o": "username=fhem, password=xxxxxxxxx,uid=6061,gid=20,vers=3.0",
            "type": "cifs"
        },
        "Scope": "local"
    }
]

Nachdem dies nicht funktioniert hat, habe ich die Volume Def.
auf das ursprüngliche Format (hat ja früher funktioniert, nur nicht nach Host restart) abgeändert:
o: username=fhem,password=xxxxxxxxx,uid=6061,gid=20,noserverino,sec=ntlmv2

docker volume inspect  fhem-docker_vol-fritzbox
[
    {
        "CreatedAt": "2023-11-20T11:40:34+01:00",
        "Driver": "local",
        "Labels": {
            "com.docker.compose.project": "fhem-docker",
            "com.docker.compose.version": "1.29.2",
            "com.docker.compose.volume": "vol-fritzbox"
        },
        "Mountpoint": "/var/lib/docker/volumes/fhem-docker_vol-fritzbox/_data",
        "Name": "fhem-docker_vol-fritzbox",
        "Options": {
            "device": "//192.168.3.1/fritz.nas/Generic-FlashDisk-01/FHEM",
            "o": "username=fhem,password=xxxxxxxxx,uid=6061,gid=20,noserverino,sec=ntlmv2",
            "type": "cifs"
        },
        "Scope": "local"
    }
]

Aber leider auch ohne Erfolg
Vielleicht hat noch jemand eine Idee?

VG

Alex
- RPI 4 fhem in Docker, 2 x Arduino Uno, HM-GW, HM-Dev. (Fensterkontakte, HK-Thermostate, div. Aktoren), JeeLink,
- GPIOs, HM-LAN, ESPs (MQTT2)
-Überwachung Fenster/Türen/Licht, HK-Thermostatregelung, Rollosteuerung, Überw. Betriebstemperaturen Heizung, Erfassung Gas/Wasser, PV-Anl., Wetter (WS1600)

Homalix99

Sorry,

funktioniert doch.
War zu ungeduldig und habe zu schnell getestet.
Mein Beitrag Nummer #2014 ist deshalb obsolet.
Vielen Dank nochmals.

VG

Alex
- RPI 4 fhem in Docker, 2 x Arduino Uno, HM-GW, HM-Dev. (Fensterkontakte, HK-Thermostate, div. Aktoren), JeeLink,
- GPIOs, HM-LAN, ESPs (MQTT2)
-Überwachung Fenster/Türen/Licht, HK-Thermostatregelung, Rollosteuerung, Überw. Betriebstemperaturen Heizung, Erfassung Gas/Wasser, PV-Anl., Wetter (WS1600)

Sidey

Zitat von: Homalix99 am 23 Februar 2024, 16:51:17Sorry,

funktioniert doch.
War zu ungeduldig und habe zu schnell getestet.

Prima, welche Variante hat denn funktioniert?
Signalduino, Homematic, Raspberry Pi, Mysensors, MQTT, Alexa, Docker, AlexaFhem

Maintainer von: SIGNALduino, fhem-docker, alexa-fhem-docker, fhempy-docker

volschin

Bin gerade an der v4 Beta 6 des Images. Bei mir schlägt der Healthcheck fehl. Ich musste ihn deaktivieren, dann gibt es keine Probleme. Ich vermute, dass das mit der Telnet-Deaktivierung zusammenhängt.

Weiterhin fiel mir auf, dass ein
- PIDFILE=/run/lock/fhem.pid

Im compose-file auf run/lock/fhem.pid geändert wird. Das ist natürlich nicht Sinn und Zweck.
Eigentlich gehört das PID-file dort auch standardmäßig hin. Gibt es einen Grund, warum das in das log-Verzeichnis geschrieben werden soll?
Intel NUC+Ubuntu 24.04+Docker+FHEM6
HomeMatic: HM-MOD-RPI-PCB+HM-USB-CFG2+hmland+diverse, HUE: Hue-Bridge, RaspBee+deCONZ+diverse
Amzn Dash-Buttons, Siro Rollos
4xRPi, 4xCO20, OWL+USB, HarmonyHub, FRITZ!Box 7690, Echo Dots+Show8, HomeBridge

Sidey

Zitat von: volschin am 14 März 2024, 20:21:07Bin gerade an der v4 Beta 6 des Images. Bei mir schlägt der Healthcheck fehl.

Kannst Du es noch mal mit dem TAG dev-bullseye probieren?

ghcr.io/fhem/fhem-docker:dev-bullseye
Wenn der Fehler dann immer noch existiert, würden mir mehr Details zu deiner FHEMWEB Konfiguration helfen.

Zitat von: volschin am 14 März 2024, 20:21:07Weiterhin fiel mir auf, dass ein
- PIDFILE=/run/lock/fhem.pid

Im compose-file auf run/lock/fhem.pid geändert wird. Das ist natürlich nicht Sinn und Zweck.

In welchem Compose File meinst Du?
Oder meinst Du entry.sh ?
Signalduino, Homematic, Raspberry Pi, Mysensors, MQTT, Alexa, Docker, AlexaFhem

Maintainer von: SIGNALduino, fhem-docker, alexa-fhem-docker, fhempy-docker

volschin

#2019
Zitat von: Sidey am 14 März 2024, 21:20:52Kannst Du es noch mal mit dem TAG dev-bullseye probieren?

ghcr.io/fhem/fhem-docker:dev-bullseye
Wenn der Fehler dann immer noch existiert, würden mir mehr Details zu deiner FHEMWEB Konfiguration helfen.
Das behebt das Problem.

Zitat von: volschin am 14 März 2024, 20:21:07Weiterhin fiel mir auf, dass ein
- PIDFILE=/run/lock/fhem.pid

Im compose-file auf run/lock/fhem.pid geändert wird. Das ist natürlich nicht Sinn und Zweck.

In welchem Compose File meinst Du?
Oder meinst Du entry.sh ?
[/quote]
In meinem docker-compose.yaml. In der Readme ist ja beschrieben, dass man den Pfad über environment setzen kann. In FHEM taucht dann stattdessen das run/lock/fhem.id auf, also ohne den führenden / für Root.
Intel NUC+Ubuntu 24.04+Docker+FHEM6
HomeMatic: HM-MOD-RPI-PCB+HM-USB-CFG2+hmland+diverse, HUE: Hue-Bridge, RaspBee+deCONZ+diverse
Amzn Dash-Buttons, Siro Rollos
4xRPi, 4xCO20, OWL+USB, HarmonyHub, FRITZ!Box 7690, Echo Dots+Show8, HomeBridge

Sidey

Zitat von: volschin am 15 März 2024, 08:36:59In meinem docker-compose.yaml. In der Readme ist ja beschrieben, dass man den Pfad über environment setzen kann. In FHEM taucht dann stattdessen das run/lock/fhem.id auf, also ohne den führenden / für Root.

Habe ich verstanden, ich bevorzuge es, die Themen zur beta Version hier zu diskutieren, dort dann auch mehr zu dem Pidfile Problem, welches ich noch nicht in Gänze gelöst habe:
https://forum.fhem.de/index.php?topic=137309.new#new
Signalduino, Homematic, Raspberry Pi, Mysensors, MQTT, Alexa, Docker, AlexaFhem

Maintainer von: SIGNALduino, fhem-docker, alexa-fhem-docker, fhempy-docker

rallye

#2021
Hallo zusammen! Lange Zeit habe ich mich um meinen FHEM nicht gekümmert, da er wunderbar lief. Eventuell mal ein "update" mit "shutdown restart". Das war's. Nun kommt bald die Schwimmbadsaison und ich habe eine neue Heizanlage. Und beides möchte ich mit der "Überproduktion" meiner PV-Anlage steuern. Das hat mit dem Schwimmbad letztes Jahr super funktioniert, doch ein habe ich entdeckt, dass mein FHEMpy.fusionsolar keine Verbindung mehr bekommt (login failed). Wie gesagt: seit letztem Sommer nichts ernsthaft geändert. Ich habe mein FHEM im Docker und natürlich FusionSolar auch. Das sieht so aus:
version: '3.8'
services:
#
#
##### ----- portainer ----- #################################################
  portainer:
    image: portainer/portainer-ce:latest
    container_name: portainer
    ports:
      - "9443:9443"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /opt/portainer/data:/data
#
    restart: unless-stopped
#
##### ----- fhem ----- ########################################################
  fhem:
    image:  ghcr.io/fhem/fhem-docker:3-bullseye
    container_name: fhem
    restart: always
    volumes:
      - /opt/fhem/:/opt/fhem/
    environment:
      FHEM_UID: 999
      FHEM_GID: 20
      TZ: Europe/Vienna
    networks:
      fhem_net:
        ipv4_address: 172.16.57.2
    ports:
      - "8083:8083"
      - "1883:1883"
#      - "1885:1885"
      - "8883:8883"
      - "8084:8084"
#
##### ----- FHEMpy FusionSolar ----- ###########################################
  fhempy-fusionsolar:
    image: ghcr.io/fhem/fhempy-docker_fusionsolar:releases-1.4-beta
    container_name: FHEMpy-fusionsolar
    hostname: fhempy-fusionsolar
    restart: always
    networks:
      fhem_net:
        ipv4_address: 172.16.57.4

#
##### ----- FHEMpy google_weather ----- ########################################
  fhempy-googleweather:
    image: ghcr.io/fhem/fhempy-docker_google_weather:releases-1.4-beta
    container_name: FHEMpy-google_weather
    hostname: fhempy-googleweather
    restart: always
    networks:
      fhem_net:
        ipv4_address: 172.16.57.5
##### ----- network definitions ----- ##########################################
networks:
  fhem_net:
    driver: bridge
    ipam:
      driver: default
      config:
        - subnet: 172.16.57.0/24
          gateway: 172.16.57.1
#
#
##### ----- volume definitions ----- ###########################################
volumes:
  portainer_data:
    name: portainer_data
    external: true
Ich habe noch mosquitto, sonsos, minidlna, ... die habe ich aber hier weggelassen

Die Definition für fhempy.fusionsolar sieht so aus:
defmod FHEMpy.fusionsolar BindingsIo fhempy-fusionsolar:15733 fhempy
attr FHEMpy.fusionsolar devStateIcon {      my $attr_ver = "1.1.0";;;;      my $status_img = "10px-kreis-gruen";;;;      my $status_txt = "connected";;;;      my $ver = ReadingsVal($name, "version", "-");;;;      my $ver_available = ReadingsVal($name, "version_available", $ver);;;;      my $update_icon = "";;;;      my $refresh_img = "refresh";;;;      my $refresh_txt = "Update fhempy";;;;      if ($ver_available ne $ver) {        $refresh_img = "refresh\@orange";;;;        $refresh_txt = "Version ".$ver_available." available for update";;;;      }      if (ReadingsVal($name, "state", "disconnected") eq "disconnected") {        $status_img = "10px-kreis-rot";;;;        $status_txt = "disconnected";;;;      }      $update_icon = "<a  href=\"/fhem?cmd.dummy=set $name update&XHR=1\" title=\"Start ".$ver_available." update\">".FW_makeImage($refresh_img, $refresh_txt)."</a>";;;;      my $restart_icon = "<a  href=\"/fhem?cmd.dummy=set $name restart&XHR=1\" title=\"Restart fhempy\">".FW_makeImage("control_reboot")."</a>";;;;      "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a> ".$ver." </a>".$update_icon.$restart_icon."</div>"    }
attr FHEMpy.fusionsolar group fhempy
attr FHEMpy.fusionsolar icon file_json-ld2
attr FHEMpy.fusionsolar room fhempy

setstate FHEMpy.fusionsolar opened
setstate FHEMpy.fusionsolar 2024-04-03 17:18:04 hostname fhempy-fusionsolar
setstate FHEMpy.fusionsolar 2024-04-03 17:18:04 os posix
setstate FHEMpy.fusionsolar 2024-04-03 17:18:04 python 3.10.12
setstate FHEMpy.fusionsolar 2024-04-03 17:18:04 release 6.1.21-v8+
setstate FHEMpy.fusionsolar 2024-04-03 17:38:52 state opened
setstate FHEMpy.fusionsolar 2024-04-03 17:18:04 system Linux
setstate FHEMpy.fusionsolar 2024-04-03 17:18:04 version 0.1.538
setstate FHEMpy.fusionsolar 2024-04-03 17:38:57 version_available 0.1.730
setstate FHEMpy.fusionsolar 2024-04-03 17:38:57 version_release_notes <html><a href="https://github.com/fhempy/fhempy/releases" target="_blank">Release Notes</a></html>


und hier die Definition für meine Solaranlage:
defmod PV_Lohr fhempy fusionsolar USERID PASSWORT eu5
attr PV_Lohr userattr mqttAlias:textField-long mqttDefaults:textField-long mqttDisable:both,incoming,outgoing mqttForward:all,none mqttPublish:textField-long mqttSubscribe:textField-long
attr PV_Lohr IODev FHEMpy.fusionsolar
attr PV_Lohr comment folgende Werte in kW:\
active_power:    derzeitige Leistung der PV-Anlage\
electrical_load: derzeitige Verbrauch im Haus\
grid_power:      derzeitige Bilanz PV-Netz (positiver Wert: Entnahme, negativer Wert: Einspeisung)\
from_grid_power: derzeitige Entnahme aus dem öffentlichen Netz\
to_grid_power:   derzeitige Einspeisung\
\
folgende Werte in kWh:\
daily_energy:           heutiger Energieertrag aus Solaranlage\
daily_self_use_energy:  heutige Eigennutzung aus Solarenergie\
daily_use_energy:       heutiger Gesamtenergieverbrauch (Netz plus Solar)\
daily_grid_use_energy:  heutiger Energiebezug aus dem öffentlichen Netz (wird als userReadings aus\
                        daily_use_enegy-daily_self_use_energy berechnet)\
daily_to_grid_energy:   heutiger Energieeinspeisung ins öffentliche Netz (wird als userReadings aus\
                        daily_enegy-daily_self_use_energy berechnet)
attr PV_Lohr group fusionsolar
attr PV_Lohr icon measure_photovoltaic_inst
attr PV_Lohr room fhempy
attr PV_Lohr userReadings daily_to_grid_energy {ReadingsVal("PV_Lohr","daily_energy",0)-ReadingsVal("PV_Lohr","daily_self_use_energy",0)}, daily_grid_use_energy {ReadingsVal("PV_Lohr","daily_use_energy",0)-ReadingsVal("PV_Lohr","daily_self_use_energy",0)}

setstate PV_Lohr login failed, no more retry
setstate PV_Lohr 2023-12-03 11:55:30 active_power 0.0
setstate PV_Lohr 2023-12-03 11:55:30 battery_charge_capacity 0
setstate PV_Lohr 2023-12-03 11:55:30 battery_discharge_capacity 0
setstate PV_Lohr 2023-12-03 11:55:30 battery_power 0
setstate PV_Lohr 2023-12-03 11:55:30 battery_soc 0
setstate PV_Lohr 2023-12-03 11:55:30 co2_saved 1987.6850000000002
setstate PV_Lohr 2023-12-03 11:55:30 daily_energy 0.0
setstate PV_Lohr 2024-04-03 17:40:51 daily_grid_use_energy 2.75
setstate PV_Lohr 2023-12-03 11:55:30 daily_self_use_energy 0.0
setstate PV_Lohr 2023-12-03 11:55:30 daily_self_use_ratio 0.00
setstate PV_Lohr 2023-12-03 11:55:30 daily_self_use_solar_ratio --
setstate PV_Lohr 2024-04-03 17:40:51 daily_to_grid_energy 0
setstate PV_Lohr 2023-12-03 11:55:30 daily_use_energy 2.75
setstate PV_Lohr 2023-12-03 11:55:30 electrical_load 0.232
setstate PV_Lohr 2023-12-03 11:55:30 from_grid_power 0.232
setstate PV_Lohr 2023-12-03 11:55:30 grid_connected_time 2023-07-26 11:10:27
setstate PV_Lohr 2023-12-03 11:55:30 grid_frequency 0.0
setstate PV_Lohr 2023-12-03 11:55:30 grid_phase_a_current 0.0
setstate PV_Lohr 2023-12-03 11:55:30 grid_phase_a_voltage 0.0
setstate PV_Lohr 2023-12-03 11:55:30 grid_phase_b_current 0.0
setstate PV_Lohr 2023-12-03 11:55:30 grid_phase_b_voltage 0.0
setstate PV_Lohr 2023-12-03 11:55:30 grid_phase_c_current 0.0
setstate PV_Lohr 2023-12-03 11:55:30 grid_phase_c_voltage 0.0
setstate PV_Lohr 2023-12-03 11:55:30 grid_power 0.232
setstate PV_Lohr 2023-12-03 11:55:30 installed_capacity 10.5600
setstate PV_Lohr 2023-12-03 11:55:30 inverter_output_power 0.0
setstate PV_Lohr 2023-12-03 11:55:30 mppt_1_dc_cumulative_energy 2201.63
setstate PV_Lohr 2023-12-03 11:55:30 mppt_2_dc_cumulative_energy 2123.36
setstate PV_Lohr 2023-12-03 11:55:30 output_reactive_power 0.0
setstate PV_Lohr 2023-12-03 11:55:30 power_factor 0.0
setstate PV_Lohr 2023-12-03 11:55:30 pv1_input_current 0.0
setstate PV_Lohr 2023-12-03 11:55:30 pv1_input_voltage 0.0
setstate PV_Lohr 2023-12-03 11:55:30 pv2_input_current 0.0
setstate PV_Lohr 2023-12-03 11:55:30 pv2_input_voltage 0.0
setstate PV_Lohr 2024-04-03 17:40:51 state login failed, no more retry
setstate PV_Lohr 2023-12-03 11:55:30 station NE=36213689
setstate PV_Lohr 2023-12-03 11:55:30 string_output_power 0.0
setstate PV_Lohr 2023-12-03 11:55:30 to_grid_power 0
setstate PV_Lohr 2023-12-03 11:55:30 total_current_day_energy 0.0
setstate PV_Lohr 2023-12-03 11:55:30 total_current_month_energy 0.03
setstate PV_Lohr 2023-12-03 11:55:30 total_current_year_energy 4184.6
setstate PV_Lohr 2023-12-03 11:55:30 total_input_power 0.0
setstate PV_Lohr 2023-12-03 11:55:30 total_lifetime_energy 4184.6


Seit mir unbekannter Zeit erhalte ich ein "login failed" und ich bekomme keine aktuellen Werte mehr. Mit einem Restart von FHEMpy.fusionsolar erhalte ich folgenden Log-Eintrag:
2024.04.03 17:57:27 1: ws:fhempy-fusionsolar:15733 disconnected, waiting to reappear (FHEMpy.fusionsolar)
2024.04.03 17:57:27 1: BindingsIo (FHEMpy.fusionsolar): ERROR during connection setup: fhempy-fusionsolar: Connection refused (111)
2024.04.03 17:57:39 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/10_BindingsIo.pm line 558.
2024.04.03 17:57:39 1: ws:fhempy-fusionsolar:15733 reappeared (FHEMpy.fusionsolar)
Connection refused könnte ein falsches PW sein - ich habe es aber nicht geändert und daher kann ich das ausschließen (ich habe das login mit meinen Daten in das WI soeben erfolgreich durchgeführt).

Hat jemand eine Idee? Danke

NB: google-weather mit fhempy funktioniert klaglos
RaspiPi v4, HM-LGW, 6x HM-TC-IT-WM-W-EU, 11x HM-CC-RT-DN, 1x HUE Bridge, 4x HUE-RC, 5x HUE White&Color, 15xHUE White, 3xHM-LC-SW1-FM, 1xHM-LC-SW2-FM, 1x ConBeeII, 15x Shelly1, 5xShellyplug, Aquara: 2x Temp-Sensor, 1x Vibrationssensor, 2x Lichtsensor, 19x Tür/Fenstersensor

Sidey

@rallye

Was steht denn im Log vom `fhempy-fusionsolar` container?

Es gab an dem fusionsolar code auch Aktualisierungen, aber ich habe gerade gesehen, dass seit Dezember die Container dafür nicht mehr erzeugt werden.
Signalduino, Homematic, Raspberry Pi, Mysensors, MQTT, Alexa, Docker, AlexaFhem

Maintainer von: SIGNALduino, fhem-docker, alexa-fhem-docker, fhempy-docker

rallye

#2023
@Sidey

Anbei die Info:
um 11:47:07 habe ich das Image restartend. FHEM macht 3 login-Versuche, danach bleibt es auf "failed" stehen

2024-04-04 05:47:49,888 - INFO     - websockets.server: connection closed
2024-04-04 05:48:40,143 - INFO     - websockets.server: connection failed (200 OK)
2024-04-04 05:48:40,161 - INFO     - websockets.server: connection closed
.
.
.
.
2024-04-04 11:44:44,535 - INFO     - websockets.server: connection failed (200 OK)
2024-04-04 11:44:44,544 - INFO     - websockets.server: connection closed
2024-04-04 11:45:34,729 - INFO     - websockets.server: connection failed (200 OK)
2024-04-04 11:45:34,733 - INFO     - websockets.server: connection closed
2024-04-04 11:46:24,898 - INFO     - websockets.server: connection failed (200 OK)
2024-04-04 11:46:24,902 - INFO     - websockets.server: connection closed
2024-04-04 11:47:07,755 - INFO     - fhempy.lib.fhem_pythonbinding: Shutdown initiated...
2024-04-04 11:47:07,760 - INFO     - fhempy.lib.fhem_pythonbinding: All modules successfully undefined!
2024-04-04 11:47:07,762 - INFO     - websockets.server: server closing
2024-04-04 11:47:17,924 - INFO     - websockets.server: connection closed
2024-04-04 11:47:17,925 - INFO     - websockets.server: server closed
2024-04-04 11:47:17,928 - INFO     - fhempy.lib.fhem_pythonbinding: Exit 0
2024-04-04 11:47:25,694 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.538...
2024-04-04 11:47:25,744 - INFO     - fhempy.lib.pkg_installer: Attempting install of async-upnp-client==0.31.2
2024-04-04 11:47:27,282 - ERROR    - fhempy.lib.pkg_installer: Unable to install package async-upnp-client==0.31.2: ERROR: Could not find a version that satisfies the requirement async-upnp-client==0.31.2 (from versions: none)
ERROR: No matching distribution found for async-upnp-client==0.31.2
2024-04-04 11:47:27,285 - INFO     - fhempy.lib.pkg_installer: Attempting install of async-upnp-client==0.31.2
2024-04-04 11:47:28,788 - ERROR    - fhempy.lib.pkg_installer: Unable to install package async-upnp-client==0.31.2: ERROR: Could not find a version that satisfies the requirement async-upnp-client==0.31.2 (from versions: none)
ERROR: No matching distribution found for async-upnp-client==0.31.2
2024-04-04 11:47:28,791 - INFO     - fhempy.lib.pkg_installer: Attempting install of async-upnp-client==0.31.2
2024-04-04 11:47:30,647 - ERROR    - fhempy.lib.pkg_installer: Unable to install package async-upnp-client==0.31.2: ERROR: Could not find a version that satisfies the requirement async-upnp-client==0.31.2 (from versions: none)
ERROR: No matching distribution found for async-upnp-client==0.31.2
2024-04-04 11:47:30,649 - INFO     - fhempy.lib.fhem_pythonbinding: Advertise fhempy on local network with 172.16.57.4:15733
2024-04-04 11:47:33,679 - WARNING  - asyncio: Executing <Task pending name='Task-1' coro=<async_main() running at /usr/local/lib/python3.10/site-packages/fhempy/lib/fhem_pythonbinding.py:613> wait_for=<Future pending cb=[Task.task_wakeup()] created at /usr/local/lib/python3.10/asyncio/base_events.py:429> cb=[_run_until_complete_cb() at /usr/local/lib/python3.10/asyncio/base_events.py:184] created at /usr/local/lib/python3.10/asyncio/tasks.py:636> took 3.030 seconds
2024-04-04 11:47:34,052 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-04-04 11:47:34,160 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2024-04-04 11:47:38,180 - INFO     - websockets.server: connection open
2024-04-04 11:47:38,183 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 172.16.57.2
2024-04-04 11:47:38,332 - WARNING  - asyncio: Executing <Task pending name='Task-16' coro=<send_latest_release() running at /usr/local/lib/python3.10/site-packages/fhempy/lib/fhem.py:295> wait_for=<Future pending cb=[shield.<locals>._outer_done_callback() at /usr/local/lib/python3.10/asyncio/tasks.py:864, Task.task_wakeup()] created at /usr/local/lib/python3.10/asyncio/base_events.py:429> created at /usr/local/lib/python3.10/asyncio/tasks.py:337> took 0.123 seconds
2024-04-04 11:47:38,969 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/pubkey: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/pubkey) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:47:38 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:47:39,304 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action?service=/unisess/v1/auth?service%3D%252Fnetecowebext%252Fhome%252Findex.html&decision=1&actionErrors=465&timeStamp=1712231258939&nonce=4d11bb026f23bdf5abb85bcb0c126913) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:47:39 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:47:39,306 - ERROR    - PV_Lohr: Failed to get data: 'FusionSolarRestApi' object has no attribute 'api_base'
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/fhempy/lib/fusionsolar/fusionsolar_api.py", line 211, in login
    url = self.api_base + "/unisess/v1/auth/session"
AttributeError: 'FusionSolarRestApi' object has no attribute 'api_base'
2024-04-04 11:47:49,887 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/pubkey: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/pubkey) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:47:49 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:47:50,118 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action?service=/unisess/v1/auth?service%3D%252Fnetecowebext%252Fhome%252Findex.html&decision=1&actionErrors=465&timeStamp=1712231269634&nonce=5d535579432c27acb8a7231cbd050464) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:47:50 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:47:50,121 - ERROR    - PV_Lohr: Failed to get data: 'FusionSolarRestApi' object has no attribute 'api_base'
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/fhempy/lib/fusionsolar/fusionsolar_api.py", line 211, in login
    url = self.api_base + "/unisess/v1/auth/session"
AttributeError: 'FusionSolarRestApi' object has no attribute 'api_base'
2024-04-04 11:48:00,613 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/pubkey: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/pubkey) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:00 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:00,855 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action?service=/unisess/v1/auth?service%3D%252Fnetecowebext%252Fhome%252Findex.html&decision=1&actionErrors=465&timeStamp=1712231280588&nonce=23eec50232a2ec255190764360361a63) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:00 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:00,857 - ERROR    - PV_Lohr: Failed to get data: 'FusionSolarRestApi' object has no attribute 'api_base'
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/fhempy/lib/fusionsolar/fusionsolar_api.py", line 211, in login
    url = self.api_base + "/unisess/v1/auth/session"
AttributeError: 'FusionSolarRestApi' object has no attribute 'api_base'
2024-04-04 11:48:11,109 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/pubkey: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/pubkey) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:11 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:11,320 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action?service=/unisess/v1/auth?service%3D%252Fnetecowebext%252Fhome%252Findex.html&decision=1&actionErrors=465&timeStamp=1712231291083&nonce=873a9d1ceb2f812a709911d64005f589) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:11 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:11,322 - ERROR    - PV_Lohr: Failed to get data: 'FusionSolarRestApi' object has no attribute 'api_base'
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/fhempy/lib/fusionsolar/fusionsolar_api.py", line 211, in login
    url = self.api_base + "/unisess/v1/auth/session"
AttributeError: 'FusionSolarRestApi' object has no attribute 'api_base'
2024-04-04 11:48:14,242 - INFO     - websockets.server: connection failed (200 OK)
2024-04-04 11:48:14,248 - INFO     - websockets.server: connection closed
2024-04-04 11:48:21,607 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/pubkey: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/pubkey) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:21 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:21,821 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action?service=/unisess/v1/auth?service%3D%252Fnetecowebext%252Fhome%252Findex.html&decision=1&actionErrors=465&timeStamp=1712231301574&nonce=36cecccb994d956a5cd7dda4be825fbb) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:21 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:21,822 - ERROR    - PV_Lohr: Failed to get data: 'FusionSolarRestApi' object has no attribute 'api_base'
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/fhempy/lib/fusionsolar/fusionsolar_api.py", line 211, in login
    url = self.api_base + "/unisess/v1/auth/session"
AttributeError: 'FusionSolarRestApi' object has no attribute 'api_base'
2024-04-04 11:48:34,885 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/pubkey: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/pubkey) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:34 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:35,110 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action?service=/unisess/v1/auth?service%3D%252Fnetecowebext%252Fhome%252Findex.html&decision=1&actionErrors=465&timeStamp=1712231314854&nonce=25249f50cd9662eff93cb3fc9226a868) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:35 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:35,112 - ERROR    - PV_Lohr: Failed to get data: 'FusionSolarRestApi' object has no attribute 'api_base'
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/fhempy/lib/fusionsolar/fusionsolar_api.py", line 211, in login
    url = self.api_base + "/unisess/v1/auth/session"
AttributeError: 'FusionSolarRestApi' object has no attribute 'api_base'
2024-04-04 11:48:45,395 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/pubkey: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/pubkey) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:45 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:45,669 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action?service=/unisess/v1/auth?service%3D%252Fnetecowebext%252Fhome%252Findex.html&decision=1&actionErrors=465&timeStamp=1712231325374&nonce=275595dbd3a929ea8e463d237e13e54f) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:45 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:45,671 - ERROR    - PV_Lohr: Failed to get data: 'FusionSolarRestApi' object has no attribute 'api_base'
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/fhempy/lib/fusionsolar/fusionsolar_api.py", line 211, in login
    url = self.api_base + "/unisess/v1/auth/session"
AttributeError: 'FusionSolarRestApi' object has no attribute 'api_base'
2024-04-04 11:48:55,931 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/pubkey: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/pubkey) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:55 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:56,133 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action?service=/unisess/v1/auth?service%3D%252Fnetecowebext%252Fhome%252Findex.html&decision=1&actionErrors=465&timeStamp=1712231335910&nonce=37233f5db5b161ed4a6b3e53f176e606) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:48:56 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:48:56,135 - ERROR    - PV_Lohr: Failed to get data: 'FusionSolarRestApi' object has no attribute 'api_base'
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/fhempy/lib/fusionsolar/fusionsolar_api.py", line 211, in login
    url = self.api_base + "/unisess/v1/auth/session"
AttributeError: 'FusionSolarRestApi' object has no attribute 'api_base'
2024-04-04 11:49:04,455 - INFO     - websockets.server: connection failed (200 OK)
2024-04-04 11:49:04,463 - INFO     - websockets.server: connection closed
2024-04-04 11:49:11,879 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/pubkey: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/pubkey) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:49:11 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:49:12,099 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action?service=/unisess/v1/auth?service%3D%252Fnetecowebext%252Fhome%252Findex.html&decision=1&actionErrors=465&timeStamp=1712231351849&nonce=594bbf965ef634b8f9a5c8c2dbcdd986) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:49:12 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:49:12,100 - ERROR    - PV_Lohr: Failed to get data: 'FusionSolarRestApi' object has no attribute 'api_base'
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/fhempy/lib/fusionsolar/fusionsolar_api.py", line 211, in login
    url = self.api_base + "/unisess/v1/auth/session"
AttributeError: 'FusionSolarRestApi' object has no attribute 'api_base'
2024-04-04 11:49:22,379 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/pubkey: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/pubkey) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:49:22 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:49:22,585 - DEBUG    - PV_Lohr: response from https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action: <ClientResponse(https://eu5.fusionsolar.huawei.com/unisso/v3/validateUser.action?service=/unisess/v1/auth?service%3D%252Fnetecowebext%252Fhome%252Findex.html&decision=1&actionErrors=465&timeStamp=1712231362350&nonce=293d8ee7e9fc2cf700fd1118b83380d3) [200 OK]>
<CIMultiDictProxy('Server': 'product only', 'Date': 'Thu, 04 Apr 2024 11:49:22 GMT', 'Content-Type': 'application/json;charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache,no-store,must-revalidate,max-age=0', 'Pragma': 'no-cache', 'x-xss-protection': '1;mode=block', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'x-frame-options': 'SAMEORIGIN', 'strict-transport-security': 'max-age=31536000 ; includeSubDomains', 'x-content-type-options': 'nosniff', 'x-download-options': 'noopen', 'content-security-policy': "script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src 'self';form-action 'self'", 'upcase-conversion-headers': 'accessSession', 'Content-Encoding': 'gzip')>
2024-04-04 11:49:22,587 - ERROR    - PV_Lohr: Failed to get data: 'FusionSolarRestApi' object has no attribute 'api_base'
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/fhempy/lib/fusionsolar/fusionsolar_api.py", line 211, in login
    url = self.api_base + "/unisess/v1/auth/session"
AttributeError: 'FusionSolarRestApi' object has no attribute 'api_base'
2024-04-04 11:49:54,686 - INFO     - websockets.server: connection failed (200 OK)
2024-04-04 11:49:54,691 - INFO     - websockets.server: connection closed
2024-04-04 11:50:44,832 - INFO     - websockets.server: connection failed (200 OK)
2024-04-04 11:50:44,837 - INFO     - websockets.server: connection closed
2024-04-04 11:51:38,257 - INFO     - websockets.server: connection failed (200 OK)
2024-04-04 11:51:38,262 - INFO     - websockets.server: connection closed
.
.
.
.
Für mich als Laien sieht es so aus als wäre bei async-upnp-client das Problem!!??
2024-04-04 11:47:25,744 - INFO     - fhempy.lib.pkg_installer: Attempting install of async-upnp-client==0.31.2

Dass seit Dezember keine Container mehr erzeugt werden ist sehr unangenehm. Was könnte ich hier beitragen um wieder einen aktuellen zu bekommen? Bin verwundert dass es sonst niemanden gibt der das Problem hat

Danke für die Hilfe

LG Rallye
RaspiPi v4, HM-LGW, 6x HM-TC-IT-WM-W-EU, 11x HM-CC-RT-DN, 1x HUE Bridge, 4x HUE-RC, 5x HUE White&Color, 15xHUE White, 3xHM-LC-SW1-FM, 1xHM-LC-SW2-FM, 1x ConBeeII, 15x Shelly1, 5xShellyplug, Aquara: 2x Temp-Sensor, 1x Vibrationssensor, 2x Lichtsensor, 19x Tür/Fenstersensor

Sidey

Zitat von: rallye am 03 April 2024, 22:35:31Dass seit Dezember keine Container mehr erzeugt werden ist sehr unangenehm. Was könnte ich hier beitragen um wieder einen aktuellen zu bekommen? Bin verwundert dass es sonst niemanden gibt der das Problem hat

Wenn Du magst, kannst Du das Script anpassen, was identifiziert, welche Modul Images erzeugt werden sollen. :)
Ich tippe mal, dass ich nicht damit gerechnet hatte, dass es Module gibt, die selbst keine Abhängigkeiten angeben.
Da ich alles in einer Schleife verarbeite, wird vermutlich der Eintrag für den leeren Datensatz fehlen und somit erfolgt keine Verarbeitung.

Alternativ, könnte man auch den Autor von fhempy überzeugen, dass eine Abhängigkeit angegeben wird, wenn sie vorhanden ist unabhängig davob ob sie in einem anderen System schon geführt wird :)
Der ist ggf. auch der bessere Ansprechpartner für das Anmeldeproblem, wird aber höchstwahrscheinlich vorschlagen, das ganze erst mal mit der aktuellsten Version zu probieren.

Zusammengefasst, brauchts eine Anpassung im Build Prozess der Images.
Signalduino, Homematic, Raspberry Pi, Mysensors, MQTT, Alexa, Docker, AlexaFhem

Maintainer von: SIGNALduino, fhem-docker, alexa-fhem-docker, fhempy-docker