This repository has been moved to iobroker-community-adapters organisation.

https://github.com/iobroker-community-adapters/ioBroker.solaredge

Do NOT open new issues here, but go to repository mentioned above.

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!

We saw your adapter and if it is ready please request that it is added to the repository. With this it becomes available for all users. Please consult https://github.com/ioBroker/ioBroker.repositories#add-a-new-adapter-to-the-latest-repository and the following sections for more details.
If you need help, contact us in the forum https://forum.iobroker.net/ or in the developer chat https://github.com/iobroker-community-adapters/info .

Thank you for your support.

• think about to upgrade dependencies
• add "request" package as dependecy if you use it (see testing failures)
• enter news in all languages (see translate tools in dev-best-practices in readme of this repo)
• add the default values of your two config vars to native section in io-package
• you set the values using default value of the created objects? this will not work and should never update the value on next run;
• also ideally use async/await then you also do not need that kill-timer.
• also https://github.com/92lleo/ioBroker.solaredge/blob/master/main.js#L146 will not work if the system is a bit slower ...

See ioBroker/ioBroker.repositories#1153

Dear Adapter develop,

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!

see https://forum.iobroker.net/topic/67687/solaredge-adapter-update-auf-1-0

Adapter Release 1.0.1:

Adapter does not always stop.
Problem seems to be caused by any axios exception.

2023-10-01 04:34:47.584 - info: modbus.0 (937) Connected to slave 192.168.2.85
2023-10-01 04:34:49.192 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:35:00.091 - info: host.IOBroker instance system.adapter.solaredge.0 started with pid 19372
2023-10-01 04:35:02.963 - info: solaredge.0 (19372) starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.solaredge, node: v18.18.0, js-controller: 5.0.12
2023-10-01 04:35:24.343 - error: solaredge.0 (19372) Cannot read data from solaredge cloud: Error: getaddrinfo EAI_AGAIN monitoringapi.solaredge.com
2023-10-01 04:35:50.192 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:36:48.629 - info: modbus.0 (937) Disconnected from slave 192.168.2.85
2023-10-01 04:36:51.169 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:37:52.165 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:38:53.208 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:39:54.169 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:40:00.013 - warn: host.IOBroker instance system.adapter.solaredge.0 already running with pid 19372
2023-10-01 04:40:55.165 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:41:48.631 - info: modbus.0 (937) Connected to slave 192.168.2.85
2023-10-01 04:41:56.189 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:42:57.167 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:43:49.694 - info: modbus.0 (937) Disconnected from slave 192.168.2.85
2023-10-01 04:43:58.191 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:44:59.200 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:45:00.007 - warn: host.IOBroker instance system.adapter.solaredge.0 already running with pid 19372
2023-10-01 04:46:00.178 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:47:01.163 - info: smartmeter.0 (1042) Received 10 values, 5 updated
2023-10-01 04:48:02.204 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:48:49.696 - info: modbus.0 (937) Connected to slave 192.168.2.85
2023-10-01 04:49:03.193 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:50:00.008 - warn: host.IOBroker instance system.adapter.solaredge.0 already running with pid 19372
2023-10-01 04:50:04.169 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:50:50.741 - info: modbus.0 (937) Disconnected from slave 192.168.2.85
2023-10-01 04:51:05.170 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:52:06.163 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:53:07.170 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:54:08.223 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:55:00.008 - warn: host.IOBroker instance system.adapter.solaredge.0 already running with pid 19372
2023-10-01 04:55:09.152 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:55:50.743 - info: modbus.0 (937) Connected to slave 192.168.2.85
2023-10-01 04:56:10.210 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:57:11.154 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:57:51.781 - info: modbus.0 (937) Disconnected from slave 192.168.2.85
2023-10-01 04:58:12.147 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 04:59:13.169 - info: smartmeter.0 (1042) Received 10 values, 6 updated
2023-10-01 05:00:00.009 - warn: host.IOBroker instance system.adapter.solaredge.0 already running with pid 19372
2023-10-01 05:00:00.070 - info: host.IOBroker instance system.adapter.daswetter.0 started with pid 3130

Admin v6.10.4
node: v18.18.0
js-controller: 5.0.12
NPM 9.8.1

first of call: great to offer this iobroker adapter to get full control over the SE production details (values and parameters (=addresses). Thanx a lot to the effords of the developer.

What ate the planned next steps to enhance to range of data pulling from the SE portal?

Could this topic be used to ask additional ibroker users what their ideas for enhancement are?

What ist link to the existing iobroker modbus approach, where the users are tapping into the jungle of address clarirication and not all details of the SE euqipment (e.g.optimizers) could be not accessed via Modbis and rather have to pull datas from the SE portal?

This adapter starts at every quater (xx:00:00 / xx:15:00 / xx:30:00 / xx:45:00).

This can lead to high load peaks at the target web service is this adapter is used by a higher number oif users. So scheduled adapter should distribute the load using random delays or other measurements to avaoid synchronized polls.

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!

Just got my SolarEdge installed and was looking for an adapter - glad this one exists. It is pretty basic as of now.

I guess you have seen the API docs here?
https://www.solaredge.com/sites/default/files//se_monitoring_api.pdf

Would allow much more data to be pulled from them. I would especially be interessted in current power readings to decide if there is spare power for some devices or not.

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/92lleo/ioBroker.solaredge

• [E154] common.dependencies must contain {"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
• Please check your pull request to latest: ioBroker/ioBroker.repositories#1153

I have also found warnings that may be fixed if possible.

• [W400] Cannot find "solaredge" in latest repository

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

Is there a way to retrieve the status of an attached battery (which the monitor displays) via the adapter?
Could any information on errors which the monitor displays, be retrieved?

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/92lleo/ioBroker.solaredge

• [E101] io-package.json must have at least empty "native" attribute
• [E300] Not found on travis. Please setup travis

I have also found warnings that may be fixed if possible.

• [W400] Cannot find "solaredge" in latest repository

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

I use your adapter Solaredge Monitoring (0.1.1) in ioBroker.
Unfortunately, I don't get any data. The objects only have the folder with my location ID.

I set up an NUC with Ubuntu. Can it be because of that?

The following entry is in the log file:

solaredge.0 2021-03-13 07:50:01.263 info (1940) Terminated (NO_ERROR): Without reason
solaredge.0 2021-03-13 07:50:01.258 info (1940) cleaned everything up...
solaredge.0 2021-03-13 07:50:01.257 info (1940) Done, stopping...
solaredge.0 2021-03-13 07:50:01.256 info (1940) Current power for 1810xxx: 990 W
solaredge.0 2021-03-13 07:50:00.562 info (1940) api key: 39NS...
solaredge.0 2021-03-13 07:50:00.562 info (1940) site id: 1810xxx
solaredge.0 2021-03-13 07:50:00.550 info (1940) start. Version 0.1.1 in /opt/iobroker/node_modules/iobroker.solaredge, node: v12.21.0, js-controller: 3.2.16

This repeats every 5 minutes. The Current Power value changes correctly.

Do you have a tip for me?

The adapter starts more then one time after there are problems with network.

Log:
`2023-10-25 01:30:12.345 - info: ical.0 (17065) starting. Version 1.13.3 in /opt/iobroker/node_modules/iobroker.ical, node: v18.18.2, js-controller: 5.0.14
2023-10-25 01:30:17.514 - info: smartmeter.0 (974) Received 10 values, 6 updated
2023-10-25 01:30:19.365 - info: ical.0 (17065) Terminated (NO_ERROR): Without reason
2023-10-25 01:30:19.901 - info: host.IOBroker instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
2023-10-25 01:30:22.189 - error: solaredge.0 (16782) Cannot read data from solaredge cloud: "
HTTP Status 500 – Internal Server Error

Type Status Report

Description The server encountered an unexpected condition that prevented it from fulfilling the request.
Apache Tomcat/8.5.46
"
2023-10-25 01:32:08.108 - info: sonoff.0 (991) Client [Lampe_Flur] reconnected. Old secret 1698190266954_9251. New secret 1698190328107_6534
2023-10-25 01:32:19.496 - info: smartmeter.0 (974) Received 10 values, 6 updated
2023-10-25 01:33:08.937 - info: sonoff.0 (991) Client [Lampe_Flur] reconnected. Old secret 1698190328107_6534. New secret 1698190388935_7820
2023-10-25 01:33:20.526 - info: smartmeter.0 (974) Received 10 values, 6 updated`

After this error the adapter try to start a second time:
2023-10-25 01:45:04.067 - warn: host.IOBroker instance system.adapter.solaredge.0 already running with pid 16782

I need to kill the pid first. Then it works again until the same behavior starts again after a few hours or days.

There is already a discussion here:
https://forum.iobroker.net/topic/67687/solaredge-adapter-update-auf-1-0/3?_=1698862931949

Versions:

• Adapter version: 1.01
• JS-Controller version: 18.18.2
• Node version: 9.8.1
• Operating system: Raspbian OS

Please let us know whther this adapter is still maintained by you.

Firsz of all lets say THANK YOU for spending time an knowledge and providing this adapter to users.

But as far as I can see there's a newer release with several changes available at npm. The corresponding PR (August 2023) has not yet been merged or commented by you.

If you do not have time or interest to maintain this adapter, we would kindly ask to transfer ist to iobroker-community-adapters area. Of course you can have access to the adapter (incl. rights to modify etc.) if interested. This would allow other developers to do required changes for good user experiance in future.

Please let us know about your plan / wishes

THANKs
Martin (mcm1957)

Think about adding version 1.0.1 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=1.0.1 (30 days old)
Installs: stable=0 (0%), latest=43 (11.29%), total=381
Click to edit

I think this work is great. Thank you for your time and love in this project!!

I'm new in the iobroker unit.... is there a reason, why i can't fouund it indise iobroker, in the adapter list?
IS the adapter up-to-date or is the project down?

thank you for your anser
best regards jumbo