Please update for better compatibility with js-controller 3.3.X

Hi PCL,

thanks for your work, great adapter!
I added the adapter to iobroker and I'm getting all needed values from plant data. But not the status data for my inverter.
Is it possible to add additional inverters for status data?
we have a Growatt 1500-S inverter (Mode: A0B0D1ToPFU1MAS1, Build: G.1.8, Version: ggaa0404) with data logger ShineWIFI-S (Firmware: 1.7.7.7).
Goal is to use the data for our Grafana Dashboard.
Very apreciate your help.

Cheers
yunagear

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Adapter findet keinen Datenlogger

Getestet habe ich Version 3.0.2 und Versoin 3.0.4.

Wechselrichter: MIC 2000TL-X
Datenlogger: Growatt ShineWIFI-X
Node.js: v18.16.0
NPM: 9.5.1

Log:

`

Kann mir jemand sagen was ich falsch mache ?

Describe your inverter

Typ, modell, ... GroWatt Mic 600 TL-X
The enviroment (panels, accu etc.) Trina Solar TSM 395
The modell of the logger Growatt Shine X

Describe the bug
The adapter has intermittent problems logging in to Growatt. I have worked in the settings with the key as well as with username and password.
Until the adapter is restarted, no further connection to Growatt is possible and the "Connection to service or device" gets a yellow triangle.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '...'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:

• Adapter version: <1.1.9>
• JS-Controller version: <4.0.21>
• Node version: <14.18.3>
• Operating system:

Additional context
Add any other context about the problem here.

Admin 5.x Oberfläche :

growatt.0 | 2021-05-26 19:07:27.547 | error | Logout:Error: timeout of 1000ms exceeded
growatt.0 | 2021-05-26 19:09:30.671 | error | Logout:Error: timeout of 1000ms exceeded

Admin 4.x Oberfläche:

growatt.0 | 2021-05-26 20:53:49.956 | error | (20087) Login:{"message":"timeout of 1000ms exceeded","name":"Error","stack":"Error: timeout of 1000ms exceeded\n at createError (/opt/iobroker/node_modules/axios/lib/core/createError.js:16:15)\n

Der Fehler tritt nicht immer auf. Ein Problem auf meiner Seite ?
Der Fehler war bei 1.0.1 nicht vorhanden,

Hi!
Great adapter, thanks for your work.
I've noticed that the credentials needs to be entered again after updating from a build which stored them unencrypted. Otherwise, the login fails.
Maybe the adapter could identify unencrypted passwords and encrypt them accordingly...

Hallo PLCHome, leider weiß ich nicht wie ich am besten Kontakt mit Dir aufnehmen kann und ich bin auch neu in Github, bin aber auf dich gestoßen, weil ich exakt das Problem habe, die Werte meines Growatt Wechselrichters abzugreifen und ich glaube Du könntest mir helfen. Habe versucht über Python mir was zu basteln, komme aber nicht weiter...
Ohne Dich zu belästigen und man kann das hier natürlich auch sofort dann löschen, aber wie kann ich Dich kurz dazu befragen, wo ich die speziellen Werte für meinen Growatt-Account erhalte? Bislang habe ich nur Gesamtwerte wie über response = session.post("https://server.growatt.com/selectPlant/getPlantList", data={"currPage": "1","plantType": "-1","orderType": "2","plantName": "".) Wäre Dir super dankbar, Chrissili

Think about update stable version to 3.0.4

Version: stable=3.0.2 (55 days old) => latest=3.0.4 (30 days old)
Installs: stable=751 (52.89%), latest=106 (7.46%), total=1420
Click to edit

Sentry Issue: IOBROKERGROWATT-B

TypeError: Cannot read property 'xxxxxx' of undefined
  File "C:\Program Files\iobroker\SmartHome\node_modules\growatt\lib\growatt.js", line 1210, in null.<anonymous>
    if (!result[plant.id].devices[devData.sn]) {
  ?, in runMicrotasks

Think about update stable version to 1.1.1

Version: stable=1.0.1 (188 days old) => latest=1.1.1 (105 days old)
Installs: stable=152 (71.7%), latest=53 (25%), total=212
Click to edit

Hi,

first of all: thanks for this great adapter!

im looking for the reading of the current power. i only find growatt.0.xxxxxx.plantData.eTotal which represents the total power reading.

The adapter is also not running correctly for me since 07.08.2022.
From time to time data is synchronized.
Error message when logging in with user/password:

Growatt exception: Error: Request failed with status code 588

Alternative login with key via URL does not work either.
The Growatt server in the web browser can be reached online.
Does anyone have a tip?

Dear Adapter developer,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/PLCHome/ioBroker.growatt

• [E300] Not found on travis. Please setup travis

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

@Apollon77: One personal note:

• an Interval is risky combined with external communication because interval fires independent if the run before was finished ...
• better is Timeouts that are set anew at the end of an action.

• Maybe I should also think about increasing the cycle if an error occurs

From Wildbill
magix said in Test Adapter Growatt v1.0.0:

I noticed when I go back to the adapter settings that all fields are empty again and no more ticks can be set below.
Is that normal?
Is there a way to get the voltage readings?

I noticed the exact same problem today. When I open the adapter's config page with Safari on any of my Apple devices, all the values ​​are empty. This is the case on two Macs as well as on the IPad and IPhone. If I open the config pages of other adapters, I can operate everything normally. If I open the config page of the Growatt adapter with Firefox on the Mac, all the values ​​are there and I can operate everything.
So the problem is only the configuration page of the Growatt adapter in connection with Safari. Everything else works.
Content blockers are disabled, but they can't really be anything if the other sites work.
What is different about the Growatt adapter or where can I start? Can someone test with Apple hardware whether it's the same with Safari?
Greetings, Juergen

After upgrade to Growat Adapter V1.1.12 the field mTotal is missing. It was the total savings in Euro.
In the old Vers. it was in
growatt.0.340069.devices.DHE3A11050.totalData.mTotal

Think about update stable version to 3.1.2

Version: stable=3.0.4 (59 days old) => latest=3.1.2 (15 days old)
Installs: stable=660 (46.35%), latest=83 (5.83%), total=1424
Click to edit

Describe your inverter

Growatt Min2500XH
Arc XH Battery 7kw
shine wifi

Describe the bug
After i upgrade my inverter with a xh battery system i lost some data fields.

this datafields i only see in iobroker now.

I'm getting these errors very frequently. Im Using Growatt adapter v3.2.1.
The adapter seems to work but has frequntly issues to access the server.

`

Think about update stable version to 1.1.1

Version: stable=1.0.1 (98 days old) => latest=1.1.1 (15 days old)
Installs: stable=118 (71.08%), latest=34 (20.48%), total=166
Click to edit

Adapter V 1.1.17
After Update to Admin 6.2.17
I get new error massages.

Sentry Issue: IOBROKERGROWATT-7

        }
    }
    /**
     * Is Called to get Data
     */
    async growattLogout() {
>>        this.log.debug('Enter growattLogout');
        let allTimeDiff = getTime();
        delete(this.connectTime)
        let growatt = this.growatt
        delete(this.growatt)
        if (typeof growatt  !== 'undefined') {
            if (growatt.isConnected()) {
                await growatt.logout().catch(e => {});


TypeError: Cannot read property 'debug' of undefined
  File "/opt/iobroker/node_modules/iobroker.growatt/main.js", line 226, in Growatt.growattLogout
    this.log.debug('Enter growattLogout');
  File "/opt/iobroker/node_modules/iobroker.growatt/main.js", line 118, in Growatt.onUnload
    this.growattLogout();
  File "events.js", line 314, in Growatt.emit
  File "domain.js", line 483, in Growatt.EventEmitter.emit
  File "/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js", line 8749, in process.stop
    this.emit('unload', finishUnload);
...
(2 additional frame(s) were not displayed)

environment
production
handled
no
installedFrom
[email protected]
jsControllerVersion
3.3.22
level
error
mechanism
onunhandledrejection
nodejsVersion
v12.22.5
osPlatform
linux
plugin-sentry
1.1.10
release
1.1.7
skippedNormalization
True
version
1.1.7

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/PLCHome/ioBroker.growatt

• [E300] Not found on travis. Please setup travis

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Please update test-and-release.yml and add tests for node 20.

Unless you know that your adapter does not work with node 20 please extend tests to include node 20 as node 20 has been released as official version now

If you adapter hat problems with node 20, please consider fixing them in the near future

--- English below ---

Hallo,
vielen Dank erstmal für diesen tollen Adapter! Habe ihn erfolgreich am Laufen zusammen mit InfluxDB/Grafana.
Ein Problem jedoch, was ich mit den so gewonnenen Daten habe ist, dass sie mal mehr, mal weniger lückenhaft sind. Das kommt durch eine instabile WiFi Verbindung, was sowohl meinen Homeserver, als auch den Logger vom Inverter betrifft. In der Growatt Weboberfäche, bzw. auch in der App stelle ich fest, dass Datenlücken (wenn z.B. der Logger einen Tag lang keine Internetverbindung hatte) automatisch nachsynchronisiert und gefüllt werden, sobald der Logger wieder eine Verbindung hat.
Dieses Verhalten würde ich gerne mit dem ioBroker Adapter auch realisieren. Frage: Ist dies überhaupt möglich? Es gibt ja zumindest API Kommandos dafür und die "HistoryLast" Option macht schon etwas Hoffnung, kann ja aber keine vergangenen Daten liefern.
Mein Wunsch wäre, einen Button "Synchronize All" zu haben, der bis zu einem wählbaren Startzeitpunkt (Option), z.B. seit Start der Anlage, alle Daten synchronisiert - das wäre zur einmaligen, manuellen Ausführung. Und zum zweiten einen Button "Synchronize Recent", der einen kürzeren Zeitraum synchronisiert (z.B. automatisch 1x am Tag den letzten Tag, oder manuell: letzte Stunde).
Oder ist das gar nicht möglich, wäre dann https://github.com/PLCHome/growatt die richtige Adresse, Daten manuell holen mit Requests und anschließend Daten manuell zur influxDB hinzufügen?

Danke schon mal für eine Erklärung / Einschätzung!

Hello,
thanks a lot for this great adapter! I have it successfully running in an InfluxDB/Grafana setup.
However, one problem I face with the obtained data is that it is sometimes more, sometimes less patchy. This is due to an unstable WiFi connection, which affects both my home server and the logger from the inverter. In the Growatt web interface and in the app, I notice that data gaps (e.g. if the logger has not had an internet connection for a day) are automatically synchronized and filled as soon as the logger has a connection again.
I would like to realize this behavior with the ioBroker adapter as well. Question: Is this possible at all? There are at least API commands for this and the "HistoryLast" option gives some hope, but but it's name is misleading since it is not meant to provide past data, as I have read.
My wish would be to have a button "Synchronize All", which synchronizes all data up to a selectable start time (option), e.g. since start of the plant - this would be for a one-time, manual execution. And secondly a button "Synchronize Recent", which synchronizes a shorter period (e.g. automatically once a day the last day, or manually: last hour).
Or is that not possible at all, would https://github.com/PLCHome/growatt be the right address then, get data manually with requests and then add data manually to influxDB?

Thanks already for an explanation / estimation!

I installed the Growatt ( solar inverter ) adapter to visualize various solar statistics.
That worked fine until yesterday 7.8.2022 - in the morning I noticed that the object data points are no longer updated, but the solar system / inverter is running, I can see that in the original app.

So I restarted the instance, logged in again etc, everything is green, only the data updates are not coming.
Then instance deleted and created again - also nothing.
Then deleted the aapter and deleted the Growatt object tree, which was then only available at the top level anyway, without relevant data points.

I then reinstalled the adapter & created a new instance, logged in with user & PW, everything is green, but no data points are created at all now.
Two weeks ago with the first installation everything went smoothly.

A) Does anyone know the basic problem that adapters no longer create data points, is that an adapter problem, or is something new in ioBroker?

b) Does anyone happen to be using the Growatt adapter and is everything still working as expected there?

IoBroker, adapter etc is all up to date.

The Logfile shows the following:

2022-08-07 20:30:07.732 - info: growatt.0 (1443194) Got terminate signal TERMINATE_YOURSELF

2022-08-07 20:30:07.734 - info: host.PI4-Kaki-Home stopInstance system.adapter.growatt.0 send kill signal
2022-08-07 20:30:07.739 - info: growatt.0 (1443194) terminating
2022-08-07 20:30:07.741 - info: growatt.0 (1443194) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-08-07 20:30:08.314 - info: host.PI4-Kaki-Home instance system.adapter.growatt.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-08-07 20:30:08.706 - info: host.PI4-Kaki-Home instance system.adapter.growatt.0 started with pid 1444891
2022-08-07 20:30:10.603 - info: growatt.0 (1444891) starting. Version 1.1.15 in /opt/iobroker/node_modules/iobroker.growatt, node: v14.20.0, js-controller: 4.0.23
2022-08-07 21:14:40.856 - error: growatt.0 (1444891) Growatt exception: Error: Request failed with status code 502

Describe your inverter

Typ, modell, ...
The enviroment (panels, accu etc.)
The modell of the logger

Describe the bug
Since a few weeks the message "An adapter instance crashes frequently at startup and was stopped for this reason. The log file must be checked before restarting the instance."

To Reproduce
...

Expected behavior
...

Screenshots & Logfiles

Versions:

• Adapter version: 1.1.13
• JS-Controller version: 3.3.19
• Node version: v14.18.1
• Operating system: linux

Additional context
Logfile from yesterday:
2022-04-25 00:00:00.042 - info: sourceanalytix.0 (24936) Reset start values for : growatt.0.596464.devices.GAH0A4404V.deviceData.eToday 2022-04-25 00:00:00.076 - info: sourceanalytix.0 (24936) Memory values before reset : {"stateDetails":{"alias":"","consumption":false,"costs":true,"deviceName":"growatt__0__596464__devices__GAH0A4404V__deviceData__eToday","financialCategory":"costs","headCategory":"consumed","meter_values":false,"name":"eToday","stateType":"ElectricityDay","stateUnit":"W","useUnit":"kWh"},"calcValues":{"start_day":4.541879066556176,"start_month":4.107167118639509,"start_quarter":4.107167118639509,"start_week":4.362427721195068,"start_year":3.1692590253338797,"valueAtDeviceInit":null,"valueAtDeviceReset":null,"cumulativeValue":4.5500703593339535,"previousReadingWatt":0.8,"previousReadingWattTs":1650837577532},"prices":{"basicPrice":"15","unitPrice":"0.27"}} 2022-04-25 00:00:00.214 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.previousWeek.07_Sunday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.261 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.currentWeek.07_Sunday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.282 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.previousWeek.01_Monday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.291 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.currentWeek.01_Monday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.314 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.previousWeek.02_Tuesday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.361 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.currentWeek.02_Tuesday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.381 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.previousWeek.03_Wednesday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.430 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.currentWeek.03_Wednesday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.448 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.previousWeek.04_Thursday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.455 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.currentWeek.04_Thursday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.482 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.previousWeek.05_Friday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.531 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.currentWeek.05_Friday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.549 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.previousWeek.06_Saturday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.556 - warn: sourceanalytix.0 (24936) State "sourceanalytix.0.growatt__0__596464__devices__GAH0A4404V__deviceData__eToday.currentYear.meterReadings.currentWeek.06_Saturday" has no existing object, this might lead to an error in future versions 2022-04-25 00:00:00.585 - info: sourceanalytix.0 (24936) Memory values after reset : {"stateDetails":{"alias":"","consumption":false,"costs":true,"deviceName":"growatt__0__596464__devices__GAH0A4404V__deviceData__eToday","financialCategory":"costs","headCategory":"consumed","meter_values":false,"name":"eToday","stateType":"ElectricityDay","stateUnit":"W","useUnit":"kWh"},"calcValues":{"start_day":4.5500703593339535,"start_month":4.107167118639509,"start_quarter":4.107167118639509,"start_week":4.5500703593339535,"start_year":3.1692590253338797,"valueAtDeviceInit":null,"valueAtDeviceReset":null,"cumulativeValue":4.5500703593339535},"prices":{"basicPrice":"15","unitPrice":"0.27"}} 2022-04-25 00:00:00.586 - info: sourceanalytix.0 (24936) Current value of state : {"val":0.8,"ack":true,"ts":1650837577532,"q":0,"from":"system.adapter.growatt.0","user":"system.user.admin","lc":1650814228270} 2022-04-25 16:03:09.259 - info: growatt.0 (25959) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:03:22.872 - warn: growatt.0 (25959) Growatt login: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:05:58.297 - info: growatt.0 (25959) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:07:44.956 - info: growatt.0 (25959) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:08:29.542 - info: growatt.0 (25959) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:09:04.758 - info: growatt.0 (25959) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:09:42.355 - info: growatt.0 (25959) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:27:19.228 - info: growatt.0 (25959) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:38:26.666 - info: growatt.0 (25959) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:40:32.176 - info: growatt.0 (25959) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:41:12.454 - info: growatt.0 (25959) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:45:49.763 - info: growatt.0 (25959) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 16:54:46.020 - error: growatt.0 (25959) Growatt exception: Error: timeout of 60000ms exceeded 2022-04-25 16:54:46.028 - error: growatt.0 (25959) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-04-25 16:54:46.028 - error: growatt.0 (25959) unhandled promise rejection: Cannot read property 'captureException' of undefined 2022-04-25 16:54:46.029 - error: growatt.0 (25959) TypeError: Cannot read property 'captureException' of undefined at Growatt.growattData (/opt/iobroker/node_modules/iobroker.growatt/growattMain.js:354:45) 2022-04-25 16:54:46.030 - error: growatt.0 (25959) Cannot read property 'captureException' of undefined 2022-04-25 16:54:46.036 - info: growatt.0 (25959) terminating 2022-04-25 16:54:46.038 - warn: growatt.0 (25959) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-04-25 16:54:46.668 - error: host.ioBroker instance system.adapter.growatt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-04-25 16:54:46.673 - info: host.ioBroker Restart adapter system.adapter.growatt.0 because enabled 2022-04-25 16:55:16.751 - info: host.ioBroker instance system.adapter.growatt.0 started with pid 28931 2022-04-25 16:55:18.408 - info: growatt.0 (28931) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2022-04-25 16:55:18.491 - info: growatt.0 (28931) starting. Version 1.1.13 in /opt/iobroker/node_modules/iobroker.growatt, node: v14.18.1, js-controller: 3.3.19 2022-04-25 16:56:13.247 - info: growatt.0 (28931) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 17:16:15.660 - info: growatt.0 (28931) Growatt relogin on session failed: Error: The server sent an unexpected response: /error.do?errorMess=errorNoLogin 2022-04-25 21:05:46.247 - error: growatt.0 (28931) Growatt exception: Error: timeout of 60000ms exceeded 2022-04-25 21:05:46.269 - error: growatt.0 (28931) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-04-25 21:05:46.270 - error: growatt.0 (28931) unhandled promise rejection: Cannot read property 'captureException' of undefined 2022-04-25 21:05:46.272 - error: growatt.0 (28931) TypeError: Cannot read property 'captureException' of undefined at Growatt.growattData (/opt/iobroker/node_modules/iobroker.growatt/growattMain.js:354:45) 2022-04-25 21:05:46.273 - error: growatt.0 (28931) Cannot read property 'captureException' of undefined 2022-04-25 21:05:46.290 - info: growatt.0 (28931) terminating 2022-04-25 21:05:46.293 - warn: growatt.0 (28931) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-04-25 21:05:46.924 - error: host.ioBroker instance system.adapter.growatt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-04-25 21:05:46.928 - info: host.ioBroker Restart adapter system.adapter.growatt.0 because enabled 2022-04-25 21:06:17.001 - info: host.ioBroker instance system.adapter.growatt.0 started with pid 6509 2022-04-25 21:06:18.757 - info: growatt.0 (6509) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2022-04-25 21:06:18.821 - info: growatt.0 (6509) starting. Version 1.1.13 in /opt/iobroker/node_modules/iobroker.growatt, node: v14.18.1, js-controller: 3.3.19 2022-04-25 21:09:18.956 - error: growatt.0 (6509) Growatt exception: Error: timeout of 60000ms exceeded 2022-04-25 21:09:18.963 - error: growatt.0 (6509) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-04-25 21:09:18.963 - error: growatt.0 (6509) unhandled promise rejection: Cannot read property 'captureException' of undefined 2022-04-25 21:09:18.964 - error: growatt.0 (6509) TypeError: Cannot read property 'captureException' of undefined at Growatt.growattData (/opt/iobroker/node_modules/iobroker.growatt/growattMain.js:354:45) 2022-04-25 21:09:18.964 - error: growatt.0 (6509) Cannot read property 'captureException' of undefined 2022-04-25 21:09:18.971 - info: growatt.0 (6509) terminating 2022-04-25 21:09:18.972 - warn: growatt.0 (6509) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-04-25 21:09:19.586 - error: host.ioBroker instance system.adapter.growatt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-04-25 21:09:19.591 - info: host.ioBroker Restart adapter system.adapter.growatt.0 because enabled 2022-04-25 21:09:49.634 - info: host.ioBroker instance system.adapter.growatt.0 started with pid 7015 2022-04-25 21:09:51.293 - info: growatt.0 (7015) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2022-04-25 21:09:51.351 - info: growatt.0 (7015) starting. Version 1.1.13 in /opt/iobroker/node_modules/iobroker.growatt, node: v14.18.1, js-controller: 3.3.19 2022-04-25 21:11:21.485 - error: growatt.0 (7015) Growatt exception: Error: timeout of 60000ms exceeded 2022-04-25 21:11:21.495 - error: growatt.0 (7015) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-04-25 21:11:21.496 - error: growatt.0 (7015) unhandled promise rejection: Cannot read property 'captureException' of undefined 2022-04-25 21:11:21.497 - error: growatt.0 (7015) TypeError: Cannot read property 'captureException' of undefined at Growatt.growattData (/opt/iobroker/node_modules/iobroker.growatt/growattMain.js:354:45) 2022-04-25 21:11:21.498 - error: growatt.0 (7015) Cannot read property 'captureException' of undefined 2022-04-25 21:11:21.508 - info: growatt.0 (7015) terminating 2022-04-25 21:11:21.511 - warn: growatt.0 (7015) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-04-25 21:11:22.177 - error: host.ioBroker instance system.adapter.growatt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-04-25 21:11:22.182 - info: host.ioBroker Restart adapter system.adapter.growatt.0 because enabled 2022-04-25 21:11:22.182 - warn: host.ioBroker Do not restart adapter system.adapter.growatt.0 because restart loop detected

Think about update stable version to 3.2.3

Version: stable=3.2.1 (161 days old) => latest=3.2.3 (15 days old)
Installs: stable=1125 (72.35%), latest=80 (5.14%), total=1555

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!
Do not close this issue manually as a new issue will be created if condition for update still exists
@mcm1957 for evidence

Think about update stable version to 0.0.15

Version: stable=0.0.14 (33 days old) => latest=0.0.15 (30 days old)
Installs: stable=25 (67.57%), latest=10 (27.03%), total=37
Click to edit

Hi,

Is it possible, to make the Timeout configurable ?
So we can try any other Timeout e.g. 6.000 ms.
Today the adapter won't runnig with an Timeout of 5.000 ms.

Problems with data types.
The type of data is recognized by a regular expression and then converted.
Maybe I should query the type and convert the value, using the regular expression only at the beginning.

Secure config against zero

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

Is it possible to expand the Adapter so that we could write/set data?
My problem: the Growatt SPH always stays in "normal mode" and uses between 100 and 150 Watt also when batteries are empty and PV Level is at zero. My hope: to find a way to send the SPH into standby mode via iobroker and hopefully then he needs less energy for its own

Describe your inverter

modell: Growatt MIN 4600TL-XH
Growatt_ARK-2.5_High-Voltage-HV_5.1kWh
Shine WiFi

Describe the bug
connection failed

I've been trying to solve the above problem for about 1.5 days, now I have to report here in the forum.
First of all, I'm an ioBroker beginner trying to fix an error message.
I already have progress to make via the ioBroker forum
https://forum.iobroker.net/topic/62536/growatt-exception-error-result-3/78?loggedin=true
but I can't get any further there despite brilliant support.

What happened? Since January 27th, 2023, no more data has been transmitted from ioBroker to my FHEM because none of the adapters can connect to the server (server.growatt.com).
I have ioBroker installed on a Rasp Pi, which is connected directly to the router using a LAN cable

Screenshots & Logfiles
`

Der Growatt-Adapter-Version 2.0.0.
JS-Controller-Version 4.0.24
Node-Version 16.19.0
Operating system: linux

The server address used is server.growatt.com - login by user and password
I am able to ping the server from the Rasp Pi.
An adapter and instance uninstallation and reinstallation did not lead to a positive result.

What's to do?
...
...
...
6 hours later: I look at the adapter again ... and it's green!
I don't know why and I miss my time - the 2 days - in which I was looking for the error in vain. Now I wait and close the issue. If the error comes again, I'll report back.