deg0nz / mmm-vartaess Goto Github PK

For me the batterie Status does not Update, it only switches between "Unknown" and "Error". The other Values are gathered properly so the plugin shows the right value for that.

Logs show the following:
[06.02.2022 18:13.16.614] [LOG] [VartaESS Data Fetcher (ID: 42)] Modbus read error:
[06.02.2022 18:13.16.666] [LOG] [VartaESS Data Fetcher (ID: 42)] {"name":"TransactionTimedOutError","message":"Timed out","errno":"ETIMEDOUT"}
[06.02.2022 18:13.19.751] [LOG] [VartaESS Data Fetcher (ID: 42)] Connected.
[06.02.2022 18:14.49.647] [LOG] [VartaESS Data Fetcher (ID: 42)] Modbus read error:
[06.02.2022 18:14.49.674] [LOG] [VartaESS Data Fetcher (ID: 42)] {"name":"TransactionTimedOutError","message":"Timed out","errno":"ETIMEDOUT"}
[06.02.2022 18:14.58.721] [LOG] [VartaESS Data Fetcher (ID: 42)] Modbus read error:
[06.02.2022 18:14.58.767] [LOG] [VartaESS Data Fetcher (ID: 42)] {"name":"TransactionTimedOutError","message":"Timed out","errno":"ETIMEDOUT"}
[06.02.2022 18:15.01.915] [LOG] [VartaESS Data Fetcher (ID: 42)] Connected.
[06.02.2022 18:21.13.686] [LOG] [VartaESS Data Fetcher (ID: 42)] Modbus read error:
[06.02.2022 18:21.13.702] [LOG] [VartaESS Data Fetcher (ID: 42)] {"name":"TransactionTimedOutError","message":"Timed out","errno":"ETIMEDOUT"}
[06.02.2022 18:21.16.789] [LOG] [VartaESS Data Fetcher (ID: 42)] Connected.
[06.02.2022 18:26.18.359] [LOG] [VartaESS Data Fetcher (ID: 42)] Modbus read error:
[06.02.2022 18:26.18.433] [LOG] [VartaESS Data Fetcher (ID: 42)] {"name":"TransactionTimedOutError","message":"Timed out","errno":"ETIMEDOUT"}
[06.02.2022 18:26.21.575] [LOG] [VartaESS Data Fetcher (ID: 42)] Connected.
[06.02.2022 18:33.24.333] [LOG] [VartaESS Data Fetcher (ID: 42)] Modbus read error:
[06.02.2022 18:33.24.395] [LOG] [VartaESS Data Fetcher (ID: 42)] {"name":"PortNotOpenError","message":"Port Not Open","errno":"ECONNREFUSED"}
[06.02.2022 18:33.27.714] [LOG] [VartaESS Data Fetcher (ID: 42)] Connected.

If I try to read the data manually with the tool "modbus-cli" I get the correct value:
~/modbus-cli/bin $ python3 modbus 192.168.20.9:502 1065
Parsed 0 registers definitions from 1 files
1065: 4 0x4

My config is as follows:
module: 'MMM-VartaESS',
position: "bottom_right",
config: {
ip: "192.168.20.9", // Entering the IP of the power converter is mandatory
header: "Hausbatterie",
clientId: 42,
uodateInterval: 60000
}

I already experimented with different update interval and clientId, as you can see.

Any idea how to fix that?

(atm I'm connecting to the batterie through a VPN, so maybe the timeout for connection kicks in? But all the other values work...)

After you hinted me to my typo in the config, it seams that with another value for the update interval it is not working anymore:

Logs:
[15.02.2022 14:03.18.069] [LOG] [VartaESS Data Fetcher (ID: 41)] {"name":"PortNotOpenError","message":"Port Not Open","errno":"ECONNREFUSED"}
[15.02.2022 14:03.23.209] [LOG] [VartaESS Data Fetcher (ID: 41)] Connected.

Config:
{
module: 'MMM-VartaESS',
position: "bottom_right",
config: {
ip: "192.168.20.9", // Entering the IP of the p$
header: "Hausbatterie",
updateInterval: 5000,
clientId: 41
}
}

Hi - I have installed the module together with MMM-EnergyMonitor. I have a Varta Element that is running on 192.168.1.102 and port 502. The fetcher does not seem to fetch any data or log any errors. All I get when starting a simple config.js with just MMM-VartaESS and MMM-EnergyMonitor in it is (from MagicMirror Console):

Initializing MagicMirror².
translator.js:128 Loading core translation file: translations/en.json
translator.js:146 Loading core translation fallback file: translations/en.json
loader.js:184 Load script: modules/MMM-VartaESS/MMM-VartaESS.js
module.js:501 Check MagicMirror² version for module 'MMM-VartaESS' - Minimum version: 2.1.0 - Current version: 2.20.0
module.js:503 Version is ok!
module.js:509 Module registered: MMM-VartaESS
loader.js:155 Bootstrapping module: MMM-VartaESS
loader.js:160 Scripts loaded for: MMM-VartaESS
loader.js:203 Load stylesheet: modules/MMM-VartaESS/MMM-VartaESS.css
loader.js:162 Styles loaded for: MMM-VartaESS
translator.js:107 MMM-VartaESS - Load translation: translations/en.json
loader.js:164 Translations loaded for: MMM-VartaESS
loader.js:184 Load script: modules/MMM-EnergyMonitor/MMM-EnergyMonitor.js
module.js:501 Check MagicMirror² version for module 'MMM-EnergyMonitor' - Minimum version: 2.17.0 - Current version: 2.20.0
module.js:503 Version is ok!
module.js:509 Module registered: MMM-EnergyMonitor
loader.js:155 Bootstrapping module: MMM-EnergyMonitor
loader.js:160 Scripts loaded for: MMM-EnergyMonitor
loader.js:203 Load stylesheet: modules/MMM-EnergyMonitor/MMM-EnergyMonitor.css
loader.js:203 Load stylesheet: modules/MMM-EnergyMonitor/fontawesome.css
loader.js:162 Styles loaded for: MMM-EnergyMonitor
translator.js:107 MMM-EnergyMonitor - Load translation: translations/en.json
loader.js:164 Translations loaded for: MMM-EnergyMonitor
loader.js:203 Load stylesheet: css/custom.css
MMM-VartaESS.js:43 MMM-VartaESS started.
MMM-EnergyMonitor.js:49 MMM-EnergyMonitor started.
main.js:501 All modules started!

I can see the visualisation of the energy flows of MMM-EnergyMonitor in the MagicMirror window (all with 0 W) but no sign that VartaFetcher.js would fetch any data or log any (connection) errors.

What can I try as the next step?

Many thanks