UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Johrei]

Hallo zusammen,
leider bekomme ich keine Echtzeitdaten angezeigt der Ordner bleibt leer

• Anlage auf Openapi alphaess registriert
• Adapter unter der Version 2.0
• Entwickler ID und Secret eingetragen
• SN der Anlage eingetragen

kann mir jemand bitte helfen?

[Gaspode]

@johrei said in Test Adapter alpha-ess v2.0.0:

kann mir jemand bitte helfen?

Was sagt denn das Log?

[Johrei]

Hier das Log bei einem Adapter Neustart

[Thomas Braun]

@johrei

Bitte logs nie als Screenshot sondern immer in Textform in CodeTags eingebettet hier rein.
Und nodejs auf Stand halten.

iob stop
iob fix
iob nodejs-update

[Johrei]

2024-01-02 23:52:11.254 - info: host.johannes-MINI-S stopInstance system.adapter.alpha-ess.0 (force=false, process=true)
2024-01-02 23:52:11.257 - info: alpha-ess.0 (551183) Got terminate signal TERMINATE_YOURSELF
2024-01-02 23:52:11.336 - info: host.johannes-MINI-S stopInstance system.adapter.alpha-ess.0 send kill signal
2024-01-02 23:52:11.434 - info: alpha-ess.0 (551183) terminating
2024-01-02 23:52:11.434 - info: alpha-ess.0 (551183) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-01-02 23:52:11.758 - info: alpha-ess.0 (551183) terminating
2024-01-02 23:52:12.001 - info: host.johannes-MINI-S instance system.adapter.alpha-ess.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-01-02 23:52:14.388 - info: host.johannes-MINI-S instance system.adapter.alpha-ess.0 started with pid 552101
2024-01-02 23:52:14.984 - info: alpha-ess.0 (552101) starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.alpha-ess, node: v18.19.0, js-controller: 5.0.17
2024-01-02 23:52:15.819 - info: alpha-ess.0 (552101) Initialized states for : Realtime
2024-01-02 23:52:16.981 - info: alpha-ess.0 (552101) Initialized states for : Energy
2024-01-02 23:52:17.536 - info: alpha-ess.0 (552101) Initialized states for : Settings_Charge
2024-01-02 23:52:18.059 - error: alpha-ess.0 (552101) Alpha ESS Api returns an error! Group: Settings_Discharge
2024-01-02 23:52:18.060 - info: alpha-ess.0 (552101) Error code: 6053 - The request was too fast, please try again later (#1)
2024-01-02 23:52:18.882 - info: alpha-ess.0 (552101) Initialized states for : Summary
2024-01-02 23:52:18.904 - info: alpha-ess.0 (552101) Wallbox data disabled! Adapter won't fetch Wallbox data. According states deleted.

Hoffe du meintest so

danke Update hat super funktioniert leider ohne Erfolg

[Thomas Braun]

@johrei sagte in Test Adapter alpha-ess v2.0.0:

leider ohne Erfolg

Ja doch. Deine Basis ist jetzt wieder auf Stand und wird aus dem richtigen Repo gespeist.
CodeTags verbergen sich übrigens hinter dem </> Icon.
Text dann zwischen die Anführungszeichen kopieren.
Oder Text markieren und dann auf das Icon klicken.

[Johrei]

Bekomme aber dennoch keine Datenpunkte im Verzeichnis Realtime angezeigt.

[Gaspode]

@johrei said in Test Adapter alpha-ess v2.0.0:

Bekomme aber dennoch keine Datenpunkte im Verzeichnis Realtime angezeigt.

Das ist seltsam. Das Log sieht bis auf den bekannten Fehler auf Alpha-ESS Seite (Settings_Discharge) gut aus.

Schalte mal die Log Stufe auf Debug und poste nochmal.

[Johrei]

2024-01-03 10:05:18.088 - info: host.johannes-MINI-S instance system.adapter.alpha-ess.0 started with pid 694018
2024-01-03 10:05:18.451 - debug: alpha-ess.0 (694018) Redis Objects: Use Redis connection: 127.0.0.1:9001
2024-01-03 10:05:18.473 - debug: alpha-ess.0 (694018) Objects client ready ... initialize now
2024-01-03 10:05:18.473 - debug: alpha-ess.0 (694018) Objects create System PubSub Client
2024-01-03 10:05:18.474 - debug: alpha-ess.0 (694018) Objects create User PubSub Client
2024-01-03 10:05:18.522 - debug: alpha-ess.0 (694018) Objects client initialize lua scripts
2024-01-03 10:05:18.524 - debug: alpha-ess.0 (694018) Objects connected to redis: 127.0.0.1:9001
2024-01-03 10:05:18.550 - debug: alpha-ess.0 (694018) Redis States: Use Redis connection: 127.0.0.1:9000
2024-01-03 10:05:18.563 - debug: alpha-ess.0 (694018) States create System PubSub Client
2024-01-03 10:05:18.563 - debug: alpha-ess.0 (694018) States create User PubSub Client
2024-01-03 10:05:18.630 - debug: alpha-ess.0 (694018) States connected to redis: 127.0.0.1:9000
2024-01-03 10:05:18.681 - info: alpha-ess.0 (694018) starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.alpha-ess, node: v18.19.0, js-controller: 5.0.17
2024-01-03 10:05:18.747 - debug: alpha-ess.0 (694018) Used API: Open API
2024-01-03 10:05:18.747 - debug: alpha-ess.0 (694018) config appID: alphaf45842ae84000000
2024-01-03 10:05:18.747 - debug: alpha-ess.0 (694018) config systemId: AL200101000000
2024-01-03 10:05:18.747 - debug: alpha-ess.0 (694018) config oAIntervalRealtime: 30
2024-01-03 10:05:18.748 - debug: alpha-ess.0 (694018) config oAIntervalEnergyMins: 5
2024-01-03 10:05:18.748 - debug: alpha-ess.0 (694018) config oAIntervalSettingsChargeMins 5
2024-01-03 10:05:18.748 - debug: alpha-ess.0 (694018) config oAIntervalSettingsDischargeMins 5
2024-01-03 10:05:18.748 - debug: alpha-ess.0 (694018) config oAIntervalSummaryMins: 5
2024-01-03 10:05:18.748 - debug: alpha-ess.0 (694018) config oAIntervalWallboxMins: 5
2024-01-03 10:05:18.748 - debug: alpha-ess.0 (694018) config oAEnableRealtime: true
2024-01-03 10:05:18.748 - debug: alpha-ess.0 (694018) config oAEnableEnergy: true
2024-01-03 10:05:18.748 - debug: alpha-ess.0 (694018) config oAEnableSettingsCharge: true
2024-01-03 10:05:18.748 - debug: alpha-ess.0 (694018) config oAEnableSettingsCharge: true
2024-01-03 10:05:18.748 - debug: alpha-ess.0 (694018) config oAEnableSettingsDischarge: true
2024-01-03 10:05:18.749 - debug: alpha-ess.0 (694018) config oAEnableSummary: true
2024-01-03 10:05:18.749 - debug: alpha-ess.0 (694018) config oAEnableWallbox: false
2024-01-03 10:05:18.749 - debug: alpha-ess.0 (694018) config updateUnchangedStates: true
2024-01-03 10:05:18.797 - debug: alpha-ess.0 (694018) oAIntervalRealtime: 30
2024-01-03 10:05:18.804 - debug: alpha-ess.0 (694018) Fetching Realtime data...
2024-01-03 10:05:19.538 - info: alpha-ess.0 (694018) Initialized states for : Realtime
2024-01-03 10:05:19.538 - debug: alpha-ess.0 (694018) Timeout with interval 30000 ms started for group Realtime
2024-01-03 10:05:19.538 - debug: alpha-ess.0 (694018) oAIntervalEnergyMins: 300
2024-01-03 10:05:19.581 - debug: alpha-ess.0 (694018) Set state Energy.Battery_charge_today to val: 0; q: 2; ack: true
2024-01-03 10:05:19.584 - debug: alpha-ess.0 (694018) Set state Energy.Battery_discharge_today to val: 0; q: 2; ack: true
2024-01-03 10:05:19.586 - debug: alpha-ess.0 (694018) Set state Energy.Charging_pile to val: 0; q: 2; ack: true
2024-01-03 10:05:19.588 - debug: alpha-ess.0 (694018) Set state Energy.Grid_charge to val: 0; q: 2; ack: true
2024-01-03 10:05:19.590 - debug: alpha-ess.0 (694018) Set state Energy.Grid_consumption_today to val: 3.58; q: 2; ack: true
2024-01-03 10:05:19.592 - debug: alpha-ess.0 (694018) Set state Energy.Grid_feed_in_today to val: 0.73; q: 2; ack: true
2024-01-03 10:05:19.594 - debug: alpha-ess.0 (694018) Set state Energy.Generation_today to val: 1.1; q: 2; ack: true
2024-01-03 10:05:19.596 - debug: alpha-ess.0 (694018) Fetching Energy data...
2024-01-03 10:05:20.125 - debug: alpha-ess.0 (694018) Skipped object Energy.sysSn
2024-01-03 10:05:20.125 - debug: alpha-ess.0 (694018) Skipped object Energy.theDate
2024-01-03 10:05:20.126 - debug: alpha-ess.0 (694018) Created object Energy.eCharge
2024-01-03 10:05:20.127 - debug: alpha-ess.0 (694018) Created object Energy.epv
2024-01-03 10:05:20.127 - debug: alpha-ess.0 (694018) Created object Energy.eOutput
2024-01-03 10:05:20.128 - debug: alpha-ess.0 (694018) Created object Energy.eInput
2024-01-03 10:05:20.128 - debug: alpha-ess.0 (694018) Created object Energy.eGridCharge
2024-01-03 10:05:20.129 - debug: alpha-ess.0 (694018) Created object Energy.eDischarge
2024-01-03 10:05:20.129 - debug: alpha-ess.0 (694018) Created object Energy.eChargingPile
2024-01-03 10:05:20.130 - info: alpha-ess.0 (694018) Initialized states for : Energy
2024-01-03 10:05:20.174 - debug: alpha-ess.0 (694018) Received object Energy.eCharge with value 0
2024-01-03 10:05:20.178 - debug: alpha-ess.0 (694018) Received object Energy.epv with value 1.1
2024-01-03 10:05:20.180 - debug: alpha-ess.0 (694018) Received object Energy.eOutput with value 0.73
2024-01-03 10:05:20.183 - debug: alpha-ess.0 (694018) Received object Energy.eInput with value 3.58
2024-01-03 10:05:20.185 - debug: alpha-ess.0 (694018) Received object Energy.eGridCharge with value 0
2024-01-03 10:05:20.187 - debug: alpha-ess.0 (694018) Received object Energy.eDischarge with value 0
2024-01-03 10:05:20.189 - debug: alpha-ess.0 (694018) Received object Energy.eChargingPile with value 0
2024-01-03 10:05:20.189 - debug: alpha-ess.0 (694018) Timeout with interval 300000 ms started for group Energy
2024-01-03 10:05:20.189 - debug: alpha-ess.0 (694018) oAIntervalSettingsChargeMins: 300
2024-01-03 10:05:20.233 - debug: alpha-ess.0 (694018) Set state Settings_Charge.Battery_Charging_enabled to val: false; q: 2; ack: true
2024-01-03 10:05:20.236 - debug: alpha-ess.0 (694018) Set state Settings_Charge.Charging_period_1_start to val: 00:00; q: 2; ack: true
2024-01-03 10:05:20.238 - debug: alpha-ess.0 (694018) Set state Settings_Charge.Charging_period 1_end to val: 00:00; q: 2; ack: true
2024-01-03 10:05:20.240 - debug: alpha-ess.0 (694018) Set state Settings_Charge.Charging_period_2_start to val: 00:00; q: 2; ack: true
2024-01-03 10:05:20.242 - debug: alpha-ess.0 (694018) Set state Settings_Charge.Charging_period_2_end to val: 00:00; q: 2; ack: true
2024-01-03 10:05:20.245 - debug: alpha-ess.0 (694018) Set state Settings_Charge.Charging_stopps_at_SOC to val: 100; q: 2; ack: true
2024-01-03 10:05:20.247 - debug: alpha-ess.0 (694018) Fetching Settings_Charge data...
2024-01-03 10:05:20.780 - debug: alpha-ess.0 (694018) Created object Settings_Charge.gridCharge
2024-01-03 10:05:20.781 - debug: alpha-ess.0 (694018) Subscribed State: Settings_Charge.Battery_Charging_enabled
2024-01-03 10:05:20.783 - debug: alpha-ess.0 (694018) Created object Settings_Charge.timeChaf1
2024-01-03 10:05:20.783 - debug: alpha-ess.0 (694018) Subscribed State: Settings_Charge.Charging_period_1_start
2024-01-03 10:05:20.784 - debug: alpha-ess.0 (694018) Created object Settings_Charge.timeChae1
2024-01-03 10:05:20.785 - debug: alpha-ess.0 (694018) Subscribed State: Settings_Charge.Charging_period 1_end
2024-01-03 10:05:20.785 - debug: alpha-ess.0 (694018) Created object Settings_Charge.timeChaf2
2024-01-03 10:05:20.786 - debug: alpha-ess.0 (694018) Subscribed State: Settings_Charge.Charging_period_2_start
2024-01-03 10:05:20.787 - debug: alpha-ess.0 (694018) Created object Settings_Charge.timeChae2
2024-01-03 10:05:20.787 - debug: alpha-ess.0 (694018) Subscribed State: Settings_Charge.Charging_period_2_end
2024-01-03 10:05:20.788 - debug: alpha-ess.0 (694018) Created object Settings_Charge.batHighCap
2024-01-03 10:05:20.789 - debug: alpha-ess.0 (694018) Subscribed State: Settings_Charge.Charging_stopps_at_SOC
2024-01-03 10:05:20.789 - info: alpha-ess.0 (694018) Initialized states for : Settings_Charge
2024-01-03 10:05:20.839 - debug: alpha-ess.0 (694018) Received object Settings_Charge.gridCharge with value 0
2024-01-03 10:05:20.843 - debug: alpha-ess.0 (694018) Received object Settings_Charge.timeChaf1 with value 00:00
2024-01-03 10:05:20.847 - debug: alpha-ess.0 (694018) Received object Settings_Charge.timeChae1 with value 00:00
2024-01-03 10:05:20.851 - debug: alpha-ess.0 (694018) Received object Settings_Charge.timeChaf2 with value 00:00
2024-01-03 10:05:20.854 - debug: alpha-ess.0 (694018) Received object Settings_Charge.timeChae2 with value 00:00
2024-01-03 10:05:20.856 - debug: alpha-ess.0 (694018) Received object Settings_Charge.batHighCap with value 100
2024-01-03 10:05:20.857 - debug: alpha-ess.0 (694018) Timeout with interval 300000 ms started for group Settings_Charge
2024-01-03 10:05:20.857 - debug: alpha-ess.0 (694018) oAIntervalSettingsDischargeMins: 300
2024-01-03 10:05:20.904 - debug: alpha-ess.0 (694018) Fetching Settings_Discharge data...
2024-01-03 10:05:21.448 - error: alpha-ess.0 (694018) Alpha ESS Api returns an error! Group: Settings_Discharge
2024-01-03 10:05:21.448 - info: alpha-ess.0 (694018) Error code: 6053 - The request was too fast, please try again later (#1)
2024-01-03 10:05:21.496 - debug: alpha-ess.0 (694018) Timeout with interval 300000 ms started for group Settings_Discharge
2024-01-03 10:05:21.496 - debug: alpha-ess.0 (694018) oAIntervalSummaryMins: 300
2024-01-03 10:05:21.541 - debug: alpha-ess.0 (694018) Set state Summary.Generation_today to val: 1.1; q: 2; ack: true
2024-01-03 10:05:21.545 - debug: alpha-ess.0 (694018) Set state Summary.Generation_total to val: 34506.2; q: 2; ack: true
2024-01-03 10:05:21.548 - debug: alpha-ess.0 (694018) Set state Summary.Income_today to val: 0.18; q: 2; ack: true
2024-01-03 10:05:21.551 - debug: alpha-ess.0 (694018) Set state Summary.Income_total to val: 5543.9; q: 2; ack: true
2024-01-03 10:05:21.553 - debug: alpha-ess.0 (694018) Set state Summary.Self_consumption_total to val: 31.2; q: 2; ack: true
2024-01-03 10:05:21.555 - debug: alpha-ess.0 (694018) Set state Summary.Self_sufficiency_total to val: 32.4; q: 2; ack: true
2024-01-03 10:05:21.558 - debug: alpha-ess.0 (694018) Set state Summary.Trees_plantet_total to val: 5907.9; q: 2; ack: true
2024-01-03 10:05:21.560 - debug: alpha-ess.0 (694018) Set state Summary.CO2_reduction_total to val: 29675.3; q: 2; ack: true
2024-01-03 10:05:21.562 - debug: alpha-ess.0 (694018) Set state Summary.Currency to val: Euro; q: 2; ack: true
2024-01-03 10:05:21.564 - debug: alpha-ess.0 (694018) Set state Summary.Consumption_today to val: 3.95; q: 2; ack: true
2024-01-03 10:05:21.567 - debug: alpha-ess.0 (694018) Set state Summary.Grid_feed_in_today to val: 0.73; q: 2; ack: true
2024-01-03 10:05:21.569 - debug: alpha-ess.0 (694018) Set state Summary.Grid_consumption_today to val: 3.58; q: 2; ack: true
2024-01-03 10:05:21.571 - debug: alpha-ess.0 (694018) Set state Summary.Battery_charge_today to val: 0; q: 2; ack: true
2024-01-03 10:05:21.573 - debug: alpha-ess.0 (694018) Set state Summary.Battery_discharge_today to val: 0; q: 2; ack: true
2024-01-03 10:05:21.575 - debug: alpha-ess.0 (694018) Fetching Summary data...
2024-01-03 10:05:22.768 - debug: alpha-ess.0 (694018) Created object Summary.epvtoday
2024-01-03 10:05:22.769 - debug: alpha-ess.0 (694018) Created object Summary.epvtotal
2024-01-03 10:05:22.770 - debug: alpha-ess.0 (694018) Created object Summary.eload
2024-01-03 10:05:22.770 - debug: alpha-ess.0 (694018) Created object Summary.eoutput
2024-01-03 10:05:22.770 - debug: alpha-ess.0 (694018) Created object Summary.einput
2024-01-03 10:05:22.771 - debug: alpha-ess.0 (694018) Created object Summary.echarge
2024-01-03 10:05:22.772 - debug: alpha-ess.0 (694018) Created object Summary.edischarge
2024-01-03 10:05:22.772 - debug: alpha-ess.0 (694018) Created object Summary.todayIncome
2024-01-03 10:05:22.773 - debug: alpha-ess.0 (694018) Created object Summary.totalIncome
2024-01-03 10:05:22.774 - debug: alpha-ess.0 (694018) Created object Summary.eselfConsumption
2024-01-03 10:05:22.775 - debug: alpha-ess.0 (694018) Created object Summary.eselfSufficiency
2024-01-03 10:05:22.776 - debug: alpha-ess.0 (694018) Created object Summary.treeNum
2024-01-03 10:05:22.778 - debug: alpha-ess.0 (694018) Created object Summary.carbonNum
2024-01-03 10:05:22.779 - debug: alpha-ess.0 (694018) Created object Summary.moneyType
2024-01-03 10:05:22.780 - info: alpha-ess.0 (694018) Initialized states for : Summary
2024-01-03 10:05:22.830 - debug: alpha-ess.0 (694018) Received object Summary.epvtoday with value 1.1
2024-01-03 10:05:22.833 - debug: alpha-ess.0 (694018) Received object Summary.epvtotal with value 34506.2
2024-01-03 10:05:22.835 - debug: alpha-ess.0 (694018) Received object Summary.eload with value 3.95
2024-01-03 10:05:22.837 - debug: alpha-ess.0 (694018) Received object Summary.eoutput with value 0.73
2024-01-03 10:05:22.839 - debug: alpha-ess.0 (694018) Received object Summary.einput with value 3.58
2024-01-03 10:05:22.841 - debug: alpha-ess.0 (694018) Received object Summary.echarge with value 0
2024-01-03 10:05:22.843 - debug: alpha-ess.0 (694018) Received object Summary.edischarge with value 0
2024-01-03 10:05:22.845 - debug: alpha-ess.0 (694018) Received object Summary.todayIncome with value 0.18
2024-01-03 10:05:22.847 - debug: alpha-ess.0 (694018) Received object Summary.totalIncome with value 5543.9
2024-01-03 10:05:22.851 - debug: alpha-ess.0 (694018) Received object Summary.eselfConsumption with value 0.31193
2024-01-03 10:05:22.853 - debug: alpha-ess.0 (694018) Received object Summary.eselfSufficiency with value 0.32433
2024-01-03 10:05:22.855 - debug: alpha-ess.0 (694018) Received object Summary.treeNum with value 5907.8901
2024-01-03 10:05:22.857 - debug: alpha-ess.0 (694018) Received object Summary.carbonNum with value 29675.332
2024-01-03 10:05:22.859 - debug: alpha-ess.0 (694018) Received object Summary.moneyType with value Euro
2024-01-03 10:05:22.859 - debug: alpha-ess.0 (694018) Timeout with interval 300000 ms started for group Summary
2024-01-03 10:05:22.859 - debug: alpha-ess.0 (694018) oAIntervalWallboxMins: 300
2024-01-03 10:05:22.859 - info: alpha-ess.0 (694018) Wallbox data disabled! Adapter won't fetch Wallbox data. According states deleted.
2024-01-03 10:05:22.875 - debug: alpha-ess.0 (694018) Watchdog interval started!

Hier das Log als Debug
die letzten Ziffern bei App ID und System ID habe ich abgeändert.

Evtl. werden ja auch keine Realtime Daten von meiner Anlage angeboten ist ein 8 Jahre alter Storion Eco ES5

Auf der Weboberfläche steht bei Echtzeit auch das die Daten nur alle 5 Minuten geholt werden

[Gaspode]

@johrei said in Test Adapter alpha-ess v2.0.0:

Evtl. werden ja auch keine Realtime Daten von meiner Anlage angeboten ist ein 8 Jahre alter Storion Eco ES5
Auf der Weboberfläche steht bei Echtzeit auch das die Daten nur alle 5 Minuten geholt werden

Ja, das ist dann leider so. Im Log sieht man, dass die API keine Werte liefert. Wollte gerade fragen, welche Anlage du hast.
Evtl. hilft ein Feature Request hier: https://github.com/alphaess-developer/alphacloud_open_api/issues

Sorry, da sind mir leider die Hände gebunden :(

[Gaspode]

​Gute Nachrichten:

ElevenFan hat den nervigen Bug beim Lesen der Discharge Settings Daten korrigiert. Außerdem dürfen die Werte jetzt alle 10 Minuten geschrieben werden, nicht nur alle 24 Stunden.

Da leider der Lese-Timeout etwas erhöht wurde (auf 10 Sekunden), wird es demnächst eine neu Version 2.0.1 (zunächst im Beta Repository) geben, die sicher stellen soll, dass es beim Rücklesen nach dem Schreiben von Werten keine Fehlermeldung gibt. In dieser Version wird vor dem Rücklesen mindestens 11 Sekunden gewartet.

[Gaspode]

Leider gibt es schon das nächste Problem:
https://github.com/alphaess-developer/alphacloud_open_api/issues/59

[Armin 2]

@gaspode
Ich benutze den alpha-Ess V2.0.2
mit IO-Broker auf Raspery 5
Ich möchte besonders die Werte:
alpha-ess.0.Settings_Charge.Battery_Charging_enabled
alpha-ess.0.Settings_Charge.Charging_stopps_at_SOC
alpha-ess.0.Settings_Discharge.Discharging_Cutoff_SOC
schreiben.
Wenn ich den Wert im IO-Broker oder über Nodered setze
werden die Werte immer wieder ?? von Alpha?? überschrieben.
Was mache ich falsch.
An eine Schreibbegenzung alle 10 Minuten habe ich mich gehalten.

[Gaspode]

@armin-2
Hmm, kann ich dir gerade nicht sagen. Ich hab gerade testweise Settings_Charge.Charging_stopps_at_SOC gesetzt und das hat funktioniert und der neue Wert war auch im Alpha-ESS Portal zu sehen.
Wie schreibst du denn die Werte genau?

[Armin 2]

@gaspode Im iobroker

alpha-ess.0.Settings_Charge.Charging_stopps_at_SOC
Fenster Wert Schreiben:
Wert 30
WERT SETZEN
Im Protokoll
alpha-ess.0
2024-01-22 17:22:07.729 info Written values fror group Settings_Charge
Wert bleibt gesetzt.
Auch im Alpha Portal

Nächster Versuch:
17:44 Wert aus Node-Red 33
Wert ist im iobroker auch 33
Im Alpha Portal wird der Wert nicht gesetzt.

Es wird im Portokol kein INFO "Written values fror group Settings_Charge" gesetzt.

Wert wird nach ca. 5 Minuten wieder auf den alten Wert gesetzt.

[Gaspode]

@armin-2
Also direkt im Admin geht es?

Bin jetzt nicht so der NodeRed Fachmann, das Problem scheint dann ja eher dort zu liegen. Klingt so, als würdest du beim Schreiben per Node-Red das Attribut "Bestätigt" bzw. "Acknowledged" auf True setzen. Das würde erklären, warum der Adapter erst gar nicht versucht, zu schreiben.
Details dazu findest du hier: https://forum.iobroker.net/topic/61876

[Armin 2]

@gaspode
Hallo,
das Achnowledged Signal war das Problem.
Richtig gemacht und schon gehts.
Danke für die Unterstützung.
Armin

[Gaspode]

@armin-2 said in Test Adapter alpha-ess v2.0.1:

das Achnowledged Signal war das Problem.
Richtig gemacht und schon gehts.

Alles klar, Danke für die Rückmeldung :)

[Hehabela]

Hallo,
kann mir jemand eine Info geben, was die beiden Zeichen (Lampenschirm) bei Charging_Start und Stop bedeuten?

[Gaspode]

@hehabela

Das sind States mit der Rolle "Button", d.h. zu Deutsch "Knöpfe" bzw. "Taster".

States mit dieser Rolle zeigen keinen Zustand an, sie sind dafür da, dass man "draufdrücken" kann und dadurch eine Aktion auslöst. Das "Ergebnis" spiegelt sich im State "Status" wider, der wechselt z.B. von 1 auf einen anderen Wert, wenn das Starten geklappt hat.