NEWS
Test Adapter alpha-ess v3.0.1
-
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
-
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
@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 werdenJa, 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/issuesSorry, da sind mir leider die Hände gebunden :(
-
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.
-
Leider gibt es schon das nächste Problem:
https://github.com/alphaess-developer/alphacloud_open_api/issues/59 -
Aktuelle Version v3.0.1 Veröffentlichungsdatum 22.12.2024 Github Link Verfügbar im ioBroker Stable Repository Hallo,
dieser Adapter ist wahrscheinlich nur für einen sehr kleinen Anwenderkreis interessant.
Die Firma Alpha ESS vertreibt Photovoltaikanlagen mit Batteriespeicher (auf Wunsch mit USV). Die neueren Modelle haben ein Modbus Interface, mit dem sich die meisten Daten auslesen lassen.
Will man eine Alpha-ESS Wallbox steuern oder hat man ein älteres Modell, steht dieser Weg leider nicht zur Verfügung. Alpha ESS bietet zusätzlich noch eine Cloud API,die (derzeit) leider nicht offiziell dokumentiert ist,mit der sich insbesondere die Konfigurationsdaten der Anlage auslesen und teilweise auch modifizieren lassen.Der vorliegende Adapter kann sowohl Echtzeitdaten als auch Konfigurationsdaten zyklisch auslesen und auch zu schreiben.
Seit Version V2.0.0 wird jetzt ausschließlich die offizielle Alpha-ESS API "OpenAPI" unterstützt. Wer sie nutzen will, muss sich und seine Anlage unter https://open.alphaess.com registrieren. Die inoffizielle "Closed API" wurde von Alpha-ESS am 2.12.2023 (wieder einmal) geändert und daher funktionierte diese Zugangsart nicht mehr. Da Alpha-ESS das bereits angekündigt hatte und dazu aufgerufen hatte, auf die "Open API" umzusteigen, habe ich die "Closed API" jetzt aus dem Adapter entfernt.
Das State Attribut Quality wird entsprechend des aktuellen Status gesetzt:
Quality meaning 0x00 OK and up to date 0x01 value not updated due to unknown reason, see debug log 0x02 problem with online connection for this data point 0x12 adapter disconnected or stopped 0x44 API returned error or internal error, see debug log Mehr Info findet ihr in der README des Adapters
Viel Spaß
Gaspode@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
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. -
@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?@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 PortalNä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.
-
@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 -
@gaspode
Hallo,
das Achnowledged Signal war das Problem.
Richtig gemacht und schon gehts.
Danke für die Unterstützung.
Armin -
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.
-
Aktuelle Version v3.0.1 Veröffentlichungsdatum 22.12.2024 Github Link Verfügbar im ioBroker Stable Repository Hallo,
dieser Adapter ist wahrscheinlich nur für einen sehr kleinen Anwenderkreis interessant.
Die Firma Alpha ESS vertreibt Photovoltaikanlagen mit Batteriespeicher (auf Wunsch mit USV). Die neueren Modelle haben ein Modbus Interface, mit dem sich die meisten Daten auslesen lassen.
Will man eine Alpha-ESS Wallbox steuern oder hat man ein älteres Modell, steht dieser Weg leider nicht zur Verfügung. Alpha ESS bietet zusätzlich noch eine Cloud API,die (derzeit) leider nicht offiziell dokumentiert ist,mit der sich insbesondere die Konfigurationsdaten der Anlage auslesen und teilweise auch modifizieren lassen.Der vorliegende Adapter kann sowohl Echtzeitdaten als auch Konfigurationsdaten zyklisch auslesen und auch zu schreiben.
Seit Version V2.0.0 wird jetzt ausschließlich die offizielle Alpha-ESS API "OpenAPI" unterstützt. Wer sie nutzen will, muss sich und seine Anlage unter https://open.alphaess.com registrieren. Die inoffizielle "Closed API" wurde von Alpha-ESS am 2.12.2023 (wieder einmal) geändert und daher funktionierte diese Zugangsart nicht mehr. Da Alpha-ESS das bereits angekündigt hatte und dazu aufgerufen hatte, auf die "Open API" umzusteigen, habe ich die "Closed API" jetzt aus dem Adapter entfernt.
Das State Attribut Quality wird entsprechend des aktuellen Status gesetzt:
Quality meaning 0x00 OK and up to date 0x01 value not updated due to unknown reason, see debug log 0x02 problem with online connection for this data point 0x12 adapter disconnected or stopped 0x44 API returned error or internal error, see debug log Mehr Info findet ihr in der README des Adapters
Viel Spaß
Gaspode@gaspode
Hallo,
vielen Dank für diesen Super-Adapter für einen kleinen Kreis von Nutzern.
Das Einrichten hat mit deiner Anleitung sofort Funktioniert :+1:Einzig scheinen mir Datenpunkte zu fehlen, die bei anderen Nutzern (vgl. Kommentare) offenbar da sind.
Insbesondere diese fehlen mir in der Version 2.0.2 ...
ppv1, ppv2: [W]
Summe der PV Leistungpbat: [W]
Ladeleistung (-) bzw. Entladeleistung (+) der Batteriesoc: [%]
Batteriestand -
@gaspode
Hallo,
vielen Dank für diesen Super-Adapter für einen kleinen Kreis von Nutzern.
Das Einrichten hat mit deiner Anleitung sofort Funktioniert :+1:Einzig scheinen mir Datenpunkte zu fehlen, die bei anderen Nutzern (vgl. Kommentare) offenbar da sind.
Insbesondere diese fehlen mir in der Version 2.0.2 ...
ppv1, ppv2: [W]
Summe der PV Leistungpbat: [W]
Ladeleistung (-) bzw. Entladeleistung (+) der Batteriesoc: [%]
Batteriestand@andreas-s
So sollten die Echtzeitwerte aussehen:
Sind die anderen alle da uns passen? Welches Alpha-ESS Gerät hast du denn? Ist das Gerät korrekt in der Alpha-Cloud registriert?
Ansonsten kannst du gerne mal ein Log vom Adapterstart und einen Screenshot deiner Adapterkonfiguartion posten.
-
@andreas-s
So sollten die Echtzeitwerte aussehen:
Sind die anderen alle da uns passen? Welches Alpha-ESS Gerät hast du denn? Ist das Gerät korrekt in der Alpha-Cloud registriert?
Ansonsten kannst du gerne mal ein Log vom Adapterstart und einen Screenshot deiner Adapterkonfiguartion posten.
@gaspode
Hi,
also obwohl die Instanz gut aussieht, scheint im Protokoll einiges doch nicht sauber zu gehen.
Laut Monitoring Seite heißt mein Modell SMILE-S6-HV-INV sollte aber die gleichen Werte haben.
alpha-ess.0 2024-04-16 19:34:35.943 info Got terminate signal TERMINATE_YOURSELF alpha-ess.0 2024-04-16 19:34:36.245 info terminating alpha-ess.0 2024-04-16 19:34:36.246 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason alpha-ess.0 2024-04-16 19:34:36.448 info terminating host.iob2022 2024-04-16 19:34:36.853 info instance system.adapter.alpha-ess.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.iob2022 2024-04-16 19:34:57.266 info "system.adapter.alpha-ess.0" enabled host.iob2022 2024-04-16 19:34:57.528 info instance system.adapter.alpha-ess.0 started with pid 1155099 alpha-ess.0 2024-04-16 19:34:59.496 info starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.alpha-ess, node: v18.19.0, js-controller: 5.0.19 alpha-ess.0 2024-04-16 19:35:00.452 error Alpha ESS Api returns an error! Group: Realtime alpha-ess.0 2024-04-16 19:35:00.452 info Error code: 6005 - This appId is not bound to the SN (#1) alpha-ess.0 2024-04-16 19:35:00.453 error Adapter won't try again to fetch any data. alpha-ess.0 2024-04-16 19:35:01.041 error Alpha ESS Api returns an error! Group: Energy alpha-ess.0 2024-04-16 19:35:01.042 info Error code: 6005 - This appId is not bound to the SN (#2) alpha-ess.0 2024-04-16 19:35:01.042 error Adapter won't try again to fetch any data. alpha-ess.0 2024-04-16 19:35:01.606 error Alpha ESS Api returns an error! Group: Settings_Charge alpha-ess.0 2024-04-16 19:35:01.607 info Error code: 6005 - This appId is not bound to the SN (#3) alpha-ess.0 2024-04-16 19:35:01.609 error Adapter won't try again to fetch any data. alpha-ess.0 2024-04-16 19:35:02.194 error Alpha ESS Api returns an error! Group: Settings_Discharge alpha-ess.0 2024-04-16 19:35:02.197 info Error code: 6005 - This appId is not bound to the SN (#4) alpha-ess.0 2024-04-16 19:35:02.198 error Adapter won't try again to fetch any data. alpha-ess.0 2024-04-16 19:35:03.552 info Initialized states for : Summary alpha-ess.0 2024-04-16 19:35:03.623 info Wallbox data disabled! Adapter won't fetch Wallbox data. According states deleted.Das sind die Datenpunkte in den Objekten
-
@gaspode
Hi,
also obwohl die Instanz gut aussieht, scheint im Protokoll einiges doch nicht sauber zu gehen.
Laut Monitoring Seite heißt mein Modell SMILE-S6-HV-INV sollte aber die gleichen Werte haben.alpha-ess.0 2024-04-16 19:34:35.943 info Got terminate signal TERMINATE_YOURSELF alpha-ess.0 2024-04-16 19:34:36.245 info terminating alpha-ess.0 2024-04-16 19:34:36.246 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason alpha-ess.0 2024-04-16 19:34:36.448 info terminating host.iob2022 2024-04-16 19:34:36.853 info instance system.adapter.alpha-ess.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.iob2022 2024-04-16 19:34:57.266 info "system.adapter.alpha-ess.0" enabled host.iob2022 2024-04-16 19:34:57.528 info instance system.adapter.alpha-ess.0 started with pid 1155099 alpha-ess.0 2024-04-16 19:34:59.496 info starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.alpha-ess, node: v18.19.0, js-controller: 5.0.19 alpha-ess.0 2024-04-16 19:35:00.452 error Alpha ESS Api returns an error! Group: Realtime alpha-ess.0 2024-04-16 19:35:00.452 info Error code: 6005 - This appId is not bound to the SN (#1) alpha-ess.0 2024-04-16 19:35:00.453 error Adapter won't try again to fetch any data. alpha-ess.0 2024-04-16 19:35:01.041 error Alpha ESS Api returns an error! Group: Energy alpha-ess.0 2024-04-16 19:35:01.042 info Error code: 6005 - This appId is not bound to the SN (#2) alpha-ess.0 2024-04-16 19:35:01.042 error Adapter won't try again to fetch any data. alpha-ess.0 2024-04-16 19:35:01.606 error Alpha ESS Api returns an error! Group: Settings_Charge alpha-ess.0 2024-04-16 19:35:01.607 info Error code: 6005 - This appId is not bound to the SN (#3) alpha-ess.0 2024-04-16 19:35:01.609 error Adapter won't try again to fetch any data. alpha-ess.0 2024-04-16 19:35:02.194 error Alpha ESS Api returns an error! Group: Settings_Discharge alpha-ess.0 2024-04-16 19:35:02.197 info Error code: 6005 - This appId is not bound to the SN (#4) alpha-ess.0 2024-04-16 19:35:02.198 error Adapter won't try again to fetch any data. alpha-ess.0 2024-04-16 19:35:03.552 info Initialized states for : Summary alpha-ess.0 2024-04-16 19:35:03.623 info Wallbox data disabled! Adapter won't fetch Wallbox data. According states deleted.Das sind die Datenpunkte in den Objekten
@andreas-s said in Test Adapter alpha-ess v2.0.1:
Error code: 6005 - This appId is not bound to the SN
Du musst den Smile auch korrekt registrieren und an den Account binden:
-
@andreas-s said in Test Adapter alpha-ess v2.0.1:
Error code: 6005 - This appId is not bound to the SN
Du musst den Smile auch korrekt registrieren und an den Account binden:
@gaspode
Ich war der festen Überzeugung, es wie beschrieben gemacht zu heben.
Ich musste doch auch in der Instanz bei den Einstellungen das AppSecret mit eingeben.
Eine Überprüfung brachte Gewissheit, die Anlage war doch nicht zugefügt :face_with_rolling_eyes:Es geht nun auch perfekt mit dem Modell SMILE-S6-HV-INV
Vielen Dank
-
@gaspode
Ich war der festen Überzeugung, es wie beschrieben gemacht zu heben.
Ich musste doch auch in der Instanz bei den Einstellungen das AppSecret mit eingeben.
Eine Überprüfung brachte Gewissheit, die Anlage war doch nicht zugefügt :face_with_rolling_eyes:Es geht nun auch perfekt mit dem Modell SMILE-S6-HV-INV
Vielen Dank
@andreas-s said in Test Adapter alpha-ess v2.0.1:
Es geht nun auch perfekt mit dem Modell SMILE-S6-HV-INV
Freut mich. Viel Spaß mit dem Adapter und Danke für die Rückmeldung.
-
... der Adapter Vers. 2.0.2 ist GELB und zeigt schon den ganzen Tag (wiederholt) diese Fehler ...
alpha-ess.0 2024-07-02 20:43:51.309 error Error prforming get request getLastPowerData?sysSn=ALB00xxxxxxx: AxiosError: timeout of 10000ms exceeded alpha-ess.0 2024-07-02 20:42:00.019 error Unknown error occurred: null (#4) Group:Summary alpha-ess.0 2024-07-02 20:42:00.016 error Error prforming get request getSumDataForCustomer?sysSn=ALB&queryDate=2024-07-02: AxiosError: timeout of 10000ms exceededNoch jemand ? Was tun ?
-
... der Adapter Vers. 2.0.2 ist GELB und zeigt schon den ganzen Tag (wiederholt) diese Fehler ...
alpha-ess.0 2024-07-02 20:43:51.309 error Error prforming get request getLastPowerData?sysSn=ALB00xxxxxxx: AxiosError: timeout of 10000ms exceeded alpha-ess.0 2024-07-02 20:42:00.019 error Unknown error occurred: null (#4) Group:Summary alpha-ess.0 2024-07-02 20:42:00.016 error Error prforming get request getSumDataForCustomer?sysSn=ALB&queryDate=2024-07-02: AxiosError: timeout of 10000ms exceededNoch jemand ? Was tun ?
@raspiuser said in Test Adapter alpha-ess v2.0.1:
... der Adapter Vers. 2.0.2 ist GELB und zeigt schon den ganzen Tag (wiederholt) diese Fehler ...
War wohl ein temporäres Problem der Alpha-ESS Cloud und hat sich inzwischen wieder beruhigt.
Support us
799
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge