ioBroker.solarmanpv

Tests:

solarmanpv adapter for ioBroker

Reading data from balcony power plant

Getting started

This adapter is used to display data of a balcony power plant, which is provided by a inverter "Bosswerk MI600" in ioBroker. This inverter is compatible with others in the Deye family.

I assume that the plant is monitored by the app "Solarman" so far. This adapter gets the data from this cloud.

First you have to ask Solarman support [email protected] for the needed Credentials (app_id & app_secret) must be requested. There may still be a query of the type, "I need to ask what platform are you using? What is your role? Are you an individual, O&M provider, manufacturer, or distributor? Can you give me your email address for the API?". In my case, another query then came: "Why are you applying for API?". I politely answered this question as well and was sent the necessary data the next day.

On the admin page the 4 fields have to be according to the description. This adapter is created as a "scheduled" adapter. Since the data in the cloud is updated only about every 6 minutes, it does not make to start the adapter more frequently.

Since version 0.3.0, in contrast to the previous versions, a blacklist is made possible. This means that "all" values supplied by the Api are read in and the user can filter out the values that are not needed via the blacklist. The corresponding data points can be deleted, which makes the number of objects clearer.

Since 16.04.2023 Solarman has switched to a new platform - version 0.4.0. Further adaptations of the api, as far as they exist, have not been made.

In versions 0.5.2 to 0.6.x, only developer adjustments were made.

In version 0.7.0, the node-js was raised to the recommended version 20.x and the js-controller >6 was made a prerequisite. Email and app-secret are encrypted. Therefore, both values must be entered again after an update!

In version 0.7.1, only minor adjustments were made to the instance view.

Potentially sensitive data such as “activeToken” should be encrypted, but this does not work reliably. Therefore, this was rolled back in version 0.7.3.

Compatibility

• Tested with Node.js 22
• Tested with js-controller 7
• Incorrectly typed existing ioBroker states are repaired automatically during the next adapter run
• Manual deletion of existing objects is not required

Changelog

0.7.5 (2026-07-13)

• Fix dynamic state type handling
• Automatically repair incorrect ioBroker state types
• Improved compatibility with js-controller 7
• Better handling of string based Solarman values

0.7.4 (2026-05-29)

• (raschy) Bump axios from 1.13.6 to 1.16.1
• (raschy) Removed the unused 'paket' module
• (raschy) NodeJS >= 22.x is required

0.7.3 (2025-11-04)

• (raschy) Bump axios from 1.12.2 to 1.13.1
• (raschy) Token encryption revoked
• (raschy) Dependencies updated according to Dependabot on November 24

0.7.2 (2025-10-01)

• (raschy) Bump axios from 1.11.0 to 1.12.2

0.7.1 (2025-04-25)

• (raschy) jsonConfig customized

Older changelogs can be found there

License

MIT License

Copyright (c) 2022-2026 raschy [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.