iobroker.stromgedacht v1.1.0

ioBroker.stromgedacht

Tests:

stromgedacht adapter for ioBroker

Reads the values from Strom Gedacht API provided by „StromGedacht, TransnetBW GmbH“. It could be used to check if there is more green energy in the system, so intensive consumers could be used

Disclaimer

The API used by this adapter is provided by „StromGedacht, TransnetBW GmbH“. Images of Stromgedacht do belong to „StromGedacht, TransnetBW GmbH“.

Settings

this adapter needs just two settings. | setting | description | |---------|-------------| | zipcode | needed for the API, it's the select mechanism for the region| | hoursInFuture | a value between 1 and 48, the power prediction for the requested time. 48h is the maximum provided by the stromgedacht api |

How to use?

Right now the data is available in two forms.

Available as to and from

For each Stromgedacht State there is a State available in the Object tree. These state objects hava a begin and end Timestamp:

These timestamps can be used for using in your own scriptings.

For visualization there is now also a timeseries state object for the complete forecast and also for each different state.

These timesamps can be used in a visualization. For example using the Apex-Chard Card for the Lovelace visualization.

the following config can be use:

type: custom:apexcharts-card
graph_span: 2d
span:
    start: hour
header:
    show: true
    title: Stromgedacht
    show_states: false
    colorize_states: true
yaxis:
    - show: false
      min: 0
series:
    - entity: sensor.forecast_states_supergruen_timeseries
      name: Supergrün
      type: column
      color: green
      data_generator: |
          return JSON.parse(entity.state);
    - entity: sensor.forecast_states_gruen_timeseries
      name: Grün
      type: column
      color: blue
      data_generator: |
          return JSON.parse(entity.state);
    - entity: sensor.forecast_states_orange_timeseries
      name: Orange
      type: column
      color: orange
      data_generator: |
          return JSON.parse(entity.state);
    - entity: sensor.forecast_states_rot_timeseries
      name: Rot
      type: column
      color: red
      data_generator: |
          return JSON.parse(entity.state);

Developer manual

This section is intended for the developer. It can be deleted later.

Scripts in package.json

Several npm scripts are predefined for your convenience. You can run them using npm run <scriptname> | Script name | Description | |-------------|-------------| | build | Compile the TypeScript sources. | | watch | Compile the TypeScript sources and watch for changes. | | test:ts | Executes the tests you defined in *.test.ts files. | | test:package | Ensures your package.json and io-package.json are valid. | | test:integration | Tests the adapter startup with an actual instance of ioBroker. | | test | Performs a minimal test run on package files and your tests. | | check | Performs a type-check on your code (without compiling anything). | | coverage | Generates code coverage using your test files. | | lint | Runs ESLint to check your code for formatting errors and potential bugs. | | translate | Translates texts in your adapter to all required languages, see @iobroker/adapter-dev for more details. | | release | Creates a new release, see @alcalzone/release-script for more details. |

Configuring the compilation

The adapter template uses esbuild to compile TypeScript and/or React code. You can configure many compilation settings either in tsconfig.json or by changing options for the build tasks. These options are described in detail in the @iobroker/adapter-dev documentation.

Publishing the adapter

Using GitHub Actions, you can enable automatic releases on npm whenever you push a new git tag that matches the form v<major>.<minor>.<patch>. We strongly recommend that you do. The necessary steps are described in .github/workflows/test-and-release.yml.

Since you installed the release script, you can create a new release simply by calling:

npm run release

Additional command line options for the release script are explained in the release-script documentation.

To get your adapter released in ioBroker, please refer to the documentation of ioBroker.repositories.

Test the adapter manually with dev-server

Since you set up dev-server, you can use it to run, test and debug your adapter.

You may start dev-server by calling from your dev directory:

dev-server watch

The ioBroker.admin interface will then be available at http://localhost:8081/

Please refer to the dev-server documentation for more details.

Changelog

1.1.0 (2024-02-25)

• adding new feature to retrieve JSON for net load, renewable Energy, residual Load and super green threshold

1.0.0 (2024-02-19)

• using the official logo with thanks to „StromGedacht, TransnetBW GmbH“
• terminology bugfix: instead of yellow use orange, yellow was removed from underlying API

0.2.0 (2024-01-05)

• timeseries are now also logged to InfluxDB-Adapter, if configured.

0.1.1 (2024-01-05)

• trying to make sure the adapter is restarted every hour

0.1.0 (2024-01-03)

• code cleanup
• adding timeseries
• adding sample to readme about how to visualize
• itests now functional

0.0.6 (2023-12-30)

• experimenting with exit of adapter itself
• fixing integration test

0.0.5 (2023-12-29)

• Fixing integration tests, partially
• Integration tests don't fully functional, only one test can be run, because adapter isn't stopped in time

0.0.4 (2023-12-27)

• scheduler is not rescheduled due to already running instance.

0.0.3 (2023-12-27)

• fixing integration tests by making them fail again. Problem is due to missing connection to database
• debug log messages are now in debug level
• trying to run as scheduled instance

0.0.2 (2023-12-22)

• 0.0.2 - more tests and integration tests

0.0.1 (2023-12-22)

• initial release

License

							 Apache License
					   Version 2.0, January 2004
					http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

   "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

   "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

   "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

   "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

   "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

   "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

   "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

   "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

   "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

   "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

   (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

   (b) You must cause any modified files to carry prominent notices stating that You changed the files; and

   (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

   (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

   You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

  To apply the Apache License to your work, attach the following
  boilerplate notice, with the fields enclosed by brackets "[]"
  replaced with your own identifying information. (Don't include
  the brackets!)  The text should be enclosed in the appropriate
  comment syntax for the file format. We also recommend that a
  file or class name and description of purpose be included on the
  same "printed page" as the copyright notice for easier
  identification within third-party archives.

Copyright 2023-2024 anierbeck

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.