Giter VIP home page Giter VIP logo

iobroker.go-e's Introduction

Logo

ioBroker.go-echarger

NPM version Apache 2.0 Downloads Number of Installations (latest) Version of Installations (stable) Known Vulnerabilities NPM Codacy Badge

The go-eCharger Wallbox

Product Image For more details please visit https://go-e.co/

Notice

This Adapter is currently only running with API v1. The new API v2 support is currently pending. Please make sure that in the App you turned on the API v1.

Dieser Adapter unterstützt derzeit die API v1 und benötigt zur vollen funktionalität auch die V2. Bitte stelle sicher, dass in der APP die API v1 und v2 aktiviert wurde.

go-eCharger adapter for ioBroker

EN go-e is an invitation to move electrically. E-mobility is our drive, whereby our core competence is the charging technology for electric cars. From the individual charging station for e-cars to photovoltaic connections to load management of entire buildings, we are providers of holistic system solutions for all requirements of modern e-mobility.

DE go-e ist die Aufforderung, sich elektrisch zu bewegen. e-Mobilität ist unser Antrieb, wobei unsere Kernkompetenz die Ladetechnik für Elektroautos ist. Von der einzelnen Ladestation für e-Autos über Photovoltaik-Anbindung bis hin zum Lastmanagement von ganzen Gebäuden, sind wir Anbieter gesamtheitlicher Systemlösungen für sämtliche Anforderungen der modernen e-Mobilität.

ioBroker-Adapter manual / Quick start guide

The Manual for installation and configuration you can find here: Adapter Manual

Developer manual

Join the adapter Community https://t.me/goECharger

Official API Documentation: https://github.com/goecharger/go-eCharger-API-v1 https://github.com/goecharger/go-eCharger-API-v2

Official Product Support: https://go-e.co/support/

Changelog

1.0.38

  • Bug on Negate Watts if use Go-e charger

1.0.35

  • switch between ioBroker and go-e Hardware logic for PV-Calculation
  • Adding phaseSwitch Buffer to reduce switch on coudy days
  • improved documentation
  • Bug #232
  • Wrong deafult value type

1.0.32

  • Timer for loading

1.0.31

  • Versioning updates

1.0.30

  • added max ampere in settings
  • Added level to switch 1-phase to 3 pahases
  • enables phasesSwitchMode
  • Only possible if V2 is enabled
  • some bugs

1.0.29

  • Bugfixes.

1.0.27

*Enabled foreign Object usage; Full Changelog online: https://github.com/MK-2001/ioBroker.go-e/blob/main/docs/CHANGELOG.md; Issue for Object not found.

1.0.25

  • TempArray resize on FW 054 HW V2; Readme.Adaption; Dependency security updates; Added the options to consider acknowledged value changes of foreign adapters; Added choice of ack of foreign adapters (#125)\n Minor bug for sentry; Error in tme object; Bug in Sentry. Added Catch.

1.0.18

  • First adaption of V3 hardware from go-e; Added switch to disable writing of the temperatures array; write different amont of temperature sensors; Added addtional attributes to ast; Updated several FOSS libs

1.0.15

  • Bug fixes

1.0.10

  • Enabled new Version of hardware updates

Additional moved here

Translations

The most of the translations are coming from https://translator-ui.iobroker.in feel free to contribute, if something went wrong during the translations.

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 2020 MK-2001 [email protected]

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.

Copyright

Copyright (c) 2023 MK-2001 [email protected]

iobroker.go-e's People

Contributors

8mk avatar annekaagoethe avatar apollon77 avatar dependabot[bot] avatar mcm1957 avatar mk-2001 avatar snyk-bot avatar stan23 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

iobroker.go-e's Issues

ECONNREFUSED

Hi,
ich habe mir den Adapter heruntergeladen und in einem Docker Container installiert. Leider bekomme ich im Log folgenden Fehler:

go-e.0 2020-09-13 10:34:39.830 error (994) connect ECONNREFUSED 127.0.0.1:80
go-e.0 2020-09-13 10:33:39.707 info (994) Intervall: 60
go-e.0 2020-09-13 10:33:39.706 info (994) Server: http://192.168.0.161
go-e.0 2020-09-13 10:33:39.682 info (994) starting. Version 0.1.2 in /opt/iobroker/node_modules/iobroker.go-e, node: v12.18.3, js-controller: 3.1.6

Der manuelle Zugriff über "http://192.168.0.161/status" funktioniert und gibt Werte zurück. Hab ich was übersehen oder liegt es an dem Docker Konstrukt, da der Adapter scheinbar versucht auf "127.0.0.1:80" zuzugreifen ?
Bin für jede Hilfe dankbar...

Originally posted by @ND42 in #12 (comment)

Funktionalität PV Überschussladen

Hi ich könnte dir mit einem Script weiterhelfen was man vielleicht mit einbauen könnte.Dieses holt die Werte von meinem Wechselrichter und berechnet danach wieviel das Auto laden darf.

Abschaltung der Automatik

hallo, wäre es machbar einen Datenpunkt für die Ladeautomatik zu erstellen in dem ich das Script Aktiv bzw Inaktiv schalten kann?
Wenn ich mal Laden will und das mit voller Leistung zB.

(1089) Cloud not store temperature array to single value

Hi,

danke das du dich mit dem go-eCharger beschäftigst. Ich habe folgende Warnung im ioBroker Log:

2020-09-20 10:40:45.548 - warn: go-e.0 (1089) Cloud not store temperature array to single values, because of error Cannot read property 'toString' of undefined

Unter Objekte - go-e.0 - temperatures wird eine „maintempereature“ korrekt in °C angezeigt, die IDs die da drunter folgen (tempereature 1 bis 4, sowie tempereatureArray) sind jedoch leer.

Die Meldung wiederholt sich im konfigurierten Intervall, bei mir 1 Minute.

Bin mir nicht sicher ob der Wert der die Warnmeldung hervorruft überhaupt wichtig ist, wüsste aber auch nicht, wo ich etwas konfigurieren könnte, um die Warnung im Log loszuwerden. Irgendeine Idee?

Gruss,
maxe1111

Compatibility check to js-controller 4.0

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!

Charging progress

Hi Guys,
is it possible to see the charging progress?
Is there an attribute to estimate how far is the charging progress?
Br Kuumaur

Temperature Warning

Describe the bug
I get the following warning message:
`

go-e.0 2022-02-21 10:20:16.217 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2022-02-21 10:19:16.201 warn State "go-e.0.temperatures.tempereature6" has no existing object, this might lead to an error in future versions
go-e.0 2022-02-21 10:19:16.199 warn State "go-e.0.temperatures.tempereature5" has no existing object, this might lead to an error in future versions
`

To Reproduce
Steps to reproduce the behavior:
Every minute when the adapter is runnintg

Versions:

  • Adapter version: 1.0.18
  • JS-Controller version: 14.0.12
  • Node version: 14.19.0

Compatibility check and testing for Node.js 14 and 16

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!

Attribute TXI without description

Describe the bug
The attribute txi is currently stored in the objects, but it doesn't store any kind of information about the Value

To Reproduce
Steps to reproduce the behavior:

  1. Install the adapter
  2. navigate to Objects
  3. Read txi (?)

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

Neuste Version

hi die 0.0.2 läuft nicht nach dem installieren.War mal so frei und wollte diese testen.

Adapter aktualisiert keine Datenpunkte

ich habe heute die Wallbox neu bekommen, den Adapter installiert usw. Er verbindet sich zwar (grün und go-e.0.info.connection ist true) aber alle anderen DP werden nicht beschrieben bzw. Änderungen nicht an die WB gesendet.

WB:

  • 11kW home fix
  • Firmware: 050
  • Hardware: V3

im iob-log kommt:

2021-06-16 14:43:35.364 - error: go-e.0 (31042) API response validation error: [{"message":""tmp" is required","path":["tmp"],"type":"any.required","context":{"label":"tmp","key":"tmp"}},{"message":""txi" is required","path":["txi"],"type":"any.required","context":{"label":"txi","key":"txi"}},{"message":""lon" is required","path":["lon"],"type":"any.required","context":{"label":"lon","key":"lon"}},{"message":""mce" is required","path":["mce"],"type":"any.required","context":{"label":"mce","key":"mce"}},{"message":""mcp" is required","path":["mcp"],"type":"any.required","context":{"label":"mcp","key":"mcp"}},{"message":""mcc" is required","path":["mcc"],"type":"any.required","context":{"label":"mcc","key":"mcc"}},{"message":""amx" is not allowed","path":["amx"],"type":"object.unknown","context":{"child":"amx","label":"amx","value":"6","key":"amx"}},{"message":""fsp" is not allowed","path":["fsp"],"type":"object.unknown","context":{"child":"fsp","label":"fsp","value":"0","key":"fsp"}}]

2021-06-16 14:43:35.366 - info: go-e.0 (31042) {"version":"B","tme":"1606211443","rbc":"7","rbt":"2455187","car":"1","amx":"6","amp":"6","err":"0","ast":"0","alw":"1","stp":"0","cbl":"0","pha":"56","fsp":"0","tma":[27,31.875],"dws":"0","dwo":"180","adi":"1","uby":"0","eto":"0","wst":"3","fwv":"050","nrg":[232,231,234,0,0,0,0,0,0,0,0,0,0,0,0,0],"sse":"050345","wss":"wifi","wke":"","wen":"1","cdi":"0","tof":"101","tds":"1","lbr":"255","aho":"0","afi":"6","azo":"0","ama":"16","al1":"6","al2":"8","al3":"12","al4":"14","al5":"16","cid":"255","cch":"65535","cfi":"65280","lse":"1","ust":"0","wak":"","r1x":"2","dto":"0","nmo":"0","sch":"AAAAAAAAAAAAAAAA","sdp":"0","eca":"0","ecr":"0","ecd":"0","ec4":"0","ec5":"0","ec6":"0","ec7":"0","ec8":"0","ec9":"0","ec1":"0","rca":"1","rcr":"","rcd":"","rc4":"","rc5":"","rc6":"","rc7":"","rc8":"","rc9":"","rc1":"","rna":"User 1","rnm":"User 2","rne":"User 3","rn4":"User 4","rn5":"User 5","rn6":"User 6","rn7":"User 7","rn8":"User 8","rn9":"User 9","rn1":"User 10","loe":0,"lot":32,"lom":6,"lop":50,"log":"","lof":0,"loa":0,"lch":0}

Ich vermute, dass es der Adapter die Temperatur unter tmp sucht, go-e hat die aber mittlerweile in das Array tma gepackt. In der offiziellen Doku ist das nicht vermerkt, habe es aber hier gefunden: https://www.loxwiki.eu/pages/viewpage.action?pageId=72122962
Wobei es bei mir anscheinend nur 2 Sensoren statt 4 gibt wie im loxwiki...

Grüße
Schwunkel

Ver. 1.0.7/08: API response validation error

Just updated from 1.0.6 to 1.0.7 with the following error now.
It also continues the info of type number.
After updating from 1.0.7 to 1.0.8 same error, no change:

`

go-e.0 2021-06-10 08:44:51.642 error (13136) API response validation error: {"_original":{"version":"B","tme":"1006210844","rbc":"41","rbt":"3581078625","car":"1","amp":"8","err":"0","ast":"0","alw":"0","stp":"0","cbl":"20","pha":"8","tm
go-e.0 2021-06-10 08:44:24.790 error (13136) API response validation error: {"_original":{"version":"B","tme":"1006210844","rbc":"41","rbt":"3581051769","car":"1","amp":"8","err":"0","ast":"0","alw":"0","stp":"0","cbl":"20","pha":"8","tm
go-e.0 2021-06-10 08:43:51.918 error (13136) API response validation error: {"_original":{"version":"B","tme":"1006210843","rbc":"41","rbt":"3581018811","car":"1","amp":"8","err":"0","ast":"0","alw":"0","stp":"0","cbl":"20","pha":"8","t
go-e.0 2021-06-10 08:43:24.785 error (13136) API response validation error: {"_original":{"version":"B","tme":"1006210843","rbc":"41","rbt":"3580991773","car":"1","amp":"8","err":"0","ast":"0","alw":"0","stp":"0","cbl":"20","pha":"8","t
go-e.0 2021-06-10 08:42:51.631 error (13136) API response validation error: {"_original":{"version":"B","tme":"1006210842","rbc":"41","rbt":"3580958622","car":"1","amp":"8","err":"0","ast":"0","alw":"0","stp":"0","cbl":"20","pha":"8","t
go-e.0 2021-06-10 08:42:43.768 info (13136) State value to set for "go-e.0.settings.ampere_level5" has to be type "number" but received type "string"
go-e.0 2021-06-10 08:42:43.732 info (13136) State value to set for "go-e.0.settings.ampere_level4" has to be type "number" but received type "string"
go-e.0 2021-06-10 08:42:43.723 info (13136) State value to set for "go-e.0.settings.ampere_level3" has to be type "number" but received type "string"
go-e.0 2021-06-10 08:42:43.674 info (13136) State value to set for "go-e.0.settings.ampere_level2" has to be type "number" but received type "string"
go-e.0 2021-06-10 08:42:43.658 info (13136) State value to set for "go-e.0.settings.ampere_level1" has to be type "number" but received type "string"
go-e.0 2021-06-10 08:42:43.652 info (13136) State value to set for "go-e.0.settings.color.led_brightness" has to be type "number" but received type "string"
go-e.0 2021-06-10 08:42:43.646 info (13136) State value to set for "go-e.0.serial_number" has to be type "number" but received type "string"

`

Fehlermeldungen nach Update von IoBroker

Hallo,

folgende Fehlermeldung erhalte ich:

go-e.0 2021-07-11 17:52:28.074 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.1 2021-07-11 17:52:26.224 info ""
go-e.1 2021-07-11 17:52:26.224 error API response validation error: [{"message":""value" must be of type object","path":[],"type":"object.base","context":{"type":"object","label":"value","value":""}}]
go-e.0 2021-07-11 17:52:23.044 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"

Ich hatte die Adapter Admin, Vis, Web und so aktuallisiert und seitdem kommen diese Meldungen.
Grüße

Feature Loading below 6A

Vielleicht wäre das für die nächsten Versione? 1200W für 10min schaltet ein, 400W Bezug und Laden für 10 min und die Box schaltet aus. Werte natürlich variabel.
By Carsten

Add new possibilities from Adapter Version 3

Describe the bug
go-e.co created a new Adapter Design and called it "V3". The resulting firmwares are starting with the identifier of "050" and higher.

Some functionalities:

  • Sich phases during loading process
  • Loading below 6A
  • Mass On-Off

To Reproduce
Steps to reproduce the behavior:

  1. Buy a new Hardware Adapter

** Solution **
To solve this issue a developer needs the new adapter version on his development environment
(In this open source development , that means at his home, as replacement for existing V2 adapter) :-)

1.0.10 still a lot of info

Version 1.0.10 works fine, but still too much info:

`

go-e.0 2021-06-11 08:33:05.962 info (22345) State value to set for "go-e.0.settings.color.led_brightness" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.847 info (22345) State value to set for "go-e.0.firmware_version" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.828 info (22345) State value to set for "go-e.0.max_ampere" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.784 info (22345) State value to set for "go-e.0.electricity_exchange.price_zone" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.766 info (22345) State value to set for "go-e.0.electricity_exchange.finish_hour" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.747 info (22345) State value to set for "go-e.0.electricity_exchange.min_hours" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.670 info (22345) State value to set for "go-e.0.loaded_energy" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.650 info (22345) State value to set for "go-e.0.http_flags" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.628 info (22345) State value to set for "go-e.0.cloud_disabled" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.619 info (22345) State value to set for "go-e.0.wifi.enabled" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.576 info (22345) State value to set for "go-e.0.transmit_interface" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.562 info (22345) State value to set for "go-e.0.wifi.state" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.533 info (22345) State value to set for "go-e.0.cable_ampere_code" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:05.011 info (22345) State value to set for "go-e.0.phases" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:04.997 info (22345) State value to set for "go-e.0.stop_state" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:04.945 info (22345) State value to set for "go-e.0.allow_charging" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:04.924 info (22345) State value to set for "go-e.0.access_state" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:04.890 info (22345) State value to set for "go-e.0.error" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:04.868 info (22345) State value to set for "go-e.0.ampere" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:04.841 info (22345) State value to set for "go-e.0.car" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:04.793 info (22345) State value to set for "go-e.0.reboot_timer" has to be type "number" but received type "string"
go-e.0 2021-06-11 08:33:04.749 info (22345) State value to set for "go-e.0.reboot_counter" has to be type "number" but received type "string"

`

Build not succeed - axios module not found

Describe the bug
During the build process, the axios module can't be found.
Please review the travis logs

To Reproduce
Steps to reproduce the behavior:

  1. Clone the repo
  2. npm test

Expected behavior
Success

Screenshots & Logfiles
Error: Cannot find module 'axios'

Versions:

  • Adapter version: 0.0.1
  • Node version: 12.18.2
  • Operating system: linux

ID „go-e.0.loaded_energy_kwh“ um den Faktor 1000 zu hoch

Hi,

möglicherweise ein kleiner Schönheitsfehler:

Unter Objekte - go-e.0 gibt es die ID „go-e.0.loaded_energy_kwh“. Der Wert steht für die bereits ins Auto geladene Energie und wird auch von der Original go-eCharger App (in kWh) angezeigt.

Der Wert in „go-e.0.loaded_energy_kwh“ ist allerdings nicht der Wert in kWh, sondern in Wh, also Faktor 1000 zu hoch. Oder kann ich das irgendwo konfigurieren ?

Gruss
maxe1111

Some parameters are not writeable by default

Describe the bug
Some parameters, that should be writeable (see API), are defined to be just readable by default.

To Reproduce
Steps to reproduce the behavior:

  1. Install adapter
  2. See writeability of objects in object view
    For example "ust"
    grafik

Expected behavior
All parameters, that are described in the API to be settable, should be writeable by default.

Versions:

  • Adapter version: 1.04
  • JS-Controller version: 3.1.6
  • Node version: v12.20.2
  • Operating system: Linux raspberrypi 5.10.11-v71+ #1399

Additional context
Following parameters are not writeable by default although they should be:

  • wss
  • wke
  • wen
  • tof
  • tds
  • lbr
  • aho
  • afi
  • ama
  • ust
  • wak
  • r1x
  • dto
  • nmo
  • rn[a,m,r,1-9]

Compatibility check to js-controller 3.3 and Admin5 React UI

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!

Think about to fix the issues found by adapter checker

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/MK-2001/ioBroker.go-e

  • [E605] No actual year found in copyright. Please add "Copyright (c) 2022 MK-2001 [email protected]" at the end of README.md

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

Gesamt geladene Energiemenge flasch

Bei mir stimmt der Wert die gesamt geladene Energiemenge (energy_total) nicht mit der Energie Gesamt in der App überein.
Adapter Version 1.0.15
Firmware-Version Go-E Charger: 041.0

Feature allowChargeingForMins

Describe the bug
give the possibility to allow charging just for a given time period.

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:
  • JS-Controller version:
  • Node version:
  • Operating system:

Additional context
Add any other context about the problem here.

cant write single temps - expected 3 elements got only 2..

With update to 051.4 of the Wallbox the adapter with version 1.0.15 I got no temperatures in the objects and this error message:
2021-09-28 22:17:26.593 - debug: go-e.0 (101837) state go-e.0.ampere changed: 16 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.596 - debug: go-e.0 (101837) state go-e.0.amperePV changed: 0 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.599 - debug: go-e.0 (101837) state go-e.0.access_state changed: 1 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.601 - debug: go-e.0 (101837) state go-e.0.allow_charging changed: 0 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.603 - debug: go-e.0 (101837) state go-e.0.stop_state changed: 0 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.649 - debug: go-e.0 (101837) state go-e.0.max_load changed: 50 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.667 - debug: go-e.0 (101837) state go-e.0.settings.ampere_level1 changed: 6 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.669 - debug: go-e.0 (101837) state go-e.0.settings.ampere_level2 changed: 10 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.671 - debug: go-e.0 (101837) state go-e.0.settings.ampere_level3 changed: 12 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.673 - debug: go-e.0 (101837) state go-e.0.settings.ampere_level4 changed: 14 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.674 - debug: go-e.0 (101837) state go-e.0.settings.ampere_level5 changed: 16 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.677 - debug: go-e.0 (101837) state go-e.0.settings.color.idle changed: #ff (ack = true) namespace: go-e.0 2021-09-28 22:17:26.678 - debug: go-e.0 (101837) state go-e.0.settings.color.charging changed: #ffff (ack = true) namespace: go-e.0 2021-09-28 22:17:26.680 - debug: go-e.0 (101837) state go-e.0.settings.color.finish changed: #ff00 (ack = true) namespace: go-e.0 2021-09-28 22:17:26.747 - info: go-e.0 (101837) State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object" 2021-09-28 22:17:26.748 - debug: go-e.0 (101837) Cant write temp single temps. Expected 3 elements got ["18.125","22.875"] 2021-09-28 22:17:26.761 - debug: go-e.0 (101837) state go-e.0.unlock_state changed: 0 (ack = true) namespace: go-e.0 2021-09-28 22:17:56.437 - debug: go-e.0 (101837) Starte Abfrage an: http://192.168.0.124/status 2021-09-28 22:17:56.663 - debug: go-e.0 (101837) Response: 200 - OK with data as object 2021-09-28 22:17:56.663 - debug: go-e.0 (101837) {"version":"B","tme":"2809212217","rbc":"10","rbt":"20814595","car":"1","amx":"0","amp":"16","err":"0","ast":"1","alw":"0","stp":"0","cbl":"0","pha":"56","fsp":"0","tma":[18.125,22.875],"dws":"2457353","dwo":"500","adi":"1","uby":"0","eto":"148","wst":"3","fwv":"051.4","nrg":[234,235,234,0,0,0,0,0,0,0,0,0,0,0,0,0],"sse":"059285","wss":"MITS","wke":"********","wen":"1","cdi":"0","tof":"101","tds":"1","lbr":"149","aho":"0","afi":"6","azo":"1","ama":"16","al1":"6","al2":"10","al3":"12","al4":"14","al5":"16","cid":"255","cch":"65535","cfi":"65280","lse":"1","ust":"0","wak":"********","r1x":"2","dto":"0","nmo":"0","sch":"AAAAAAAAAAAAAAAA","sdp":"0","eca":"0","ecr":"0","ecd":"0","ec4":"0","ec5":"0","ec6":"0","ec7":"0","ec8":"0","ec9":"0","ec1":"0","rca":"1","rcr":"1","rcd":"","rc4":"","rc5":"","rc6":"","rc7":"","rc8":"","rc9":"","rc1":"","rna":"ChipGoE","rnm":"BlueChip","rne":"User 3","rn4":"User 4","rn5":"User 5","rn6":"User 6","rn7":"User 7","rn8":"User 8","rn9":"User 9","rn1":"User 10","loe":0,"lot":32,"lom":6,"lop":50,"log":"","lof":0,"loa":0,"lch":259}

grafik

Akkustand

Wäre es möglich den Akkustand in % anzugeben? Die Powerwall liefert nur den % Wert.

Mini-Bug Version 1.0.15

Es gibt bei mir minütlich eine Fehlermeldung im Log-File:

State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"

Ich habe händisch mit allen zu Verfügung stehenden Formaten versucht, die Fehlermeldung zu unterbinden, ging aber nicht. Bei der Anzeige oben ist die Variable auf "Objekt" gesetzt oder im Code:
{
"_id": "go-e.0.temperatures.tempereatureArray",
"type": "state",
"common": {
"name": "all temperatures (tma)",
"type": "object",
"role": "value.temperature",
"read": true,
"write": false
},
"acl": {
"object": 1636,
"state": 1636,
"file": 1636,
"ownerGroup": "system.group.administrator"
},
"from": "system.adapter.admin.0",
"user": "system.user.admin",
"ts": 1629193551667
}
Da müsste etwas im Quellcode angepasst werden!
Danke dafür

Nachtrag:
Im Log-File des iobrokers findet eine wahre Nachrichtenflut statt - bis der Ladevorgang unterbrochen wird.:

go-e.0 2021-08-17 12:13:00.028 info Set value 0 of id alw
go-e.0 2021-08-17 12:12:51.705 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:34.838 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:34.716 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:34.388 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:34.070 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:32.953 info 200 with message: OK
go-e.0 2021-08-17 12:12:32.845 info 200 with message: OK
go-e.0 2021-08-17 12:12:32.731 info 200 with message: OK
go-e.0 2021-08-17 12:12:32.626 info 200 with message: OK
go-e.0 2021-08-17 12:12:18.691 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:18.645 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:18.535 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:18.176 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:17.659 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:16.516 info 200 with message: OK
go-e.0 2021-08-17 12:12:16.407 info 200 with message: OK
go-e.0 2021-08-17 12:12:16.293 info 200 with message: OK
go-e.0 2021-08-17 12:12:16.151 info 200 with message: OK
go-e.0 2021-08-17 12:12:16.040 info 200 with message: OK
go-e.0 2021-08-17 12:12:09.541 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:09.485 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:09.394 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:09.275 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:09.072 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
go-e.0 2021-08-17 12:12:08.494 info State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"

fehlermeldung im iobroker

habe eine HW V2 mit SW V0.40 und bekomme diesen Fehler

API response validation error: [{"message":""tme" with value "0101-300152" fails to match the required pattern: /^[0-9]{10}$/","path":["tme"],"type":"string.pattern.base","context":{"regex":{},"value":"0101-300152","label":"tme","key":"tme"}}]

ich starte das modul nur sehr selten, da ich zur zeit noch nicht so oft daheim laden muss.
heute ist mir aufgefallen, das ich diese fehlermeldung bekomme und leider gar nichts mit anfangen kann :(

liegt das an meinem Problem, das der Go-E laut FritzBox im WLan ist aber wenn ich in der App schaue steht immer Disconectet?

ausschnitt von meiner fritz box
WLAN-Eigenschaften (2,4 GHz)
Signalstärke-88dBm
max. mögliche Datenrate72 / 72 Mbit/s
aktuelle Datenrate1 / 2 Mbit/s
WLAN-StandardWLAN-b+g+n / Wi-Fi 4
Frequenzband2,4 GHz
Kanalbandbreite20 MHz
Streams1 x 1
WLAN-Eigenschaften
VerschlüsselungWPA2
SignaleigenschaftenSTBC
QoS (Quality of Service)
Repeaterbetriebnein

go-e.0.wifi.state = NO_CONNECTION

würde mich über eine kurze Info sehr freuen
mfg heiko

Describe the bug
A clear and concise description of what the bug is.

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:
  • JS-Controller version:
  • Node version:
  • Operating system:

Additional context
Add any other context about the problem here.

amp is only 100000 times writeable

Describe the bug
In a renewed documentation about firmware 040 is mentioned, that amp (Ampere) in only 100000 times writeable because of the eprom. The introduced a new attribute of amx.

Go E Temperatures has no existing Objekt

Hi, diese Warnmeldungen kommen im Intervall der eingestellten Zeit.

Adapter 1.018

`

host.raspberrypi 2022-01-25 16:39:28.480 info stopInstance system.adapter.go-e.0 (force=false, process=true)
go-e.0 2022-01-25 16:38:55.955 warn State "go-e.0.temperatures.tempereature6" has no existing object, this might lead to an error in future versions
go-e.0 2022-01-25 16:38:55.951 warn State "go-e.0.temperatures.tempereature5" has no existing object, this might lead to an error in future versions
go-e.0 2022-01-25 16:37:55.994 warn State "go-e.0.temperatures.tempereature6" has no existing object, this might lead to an error in future versions
go-e.0 2022-01-25 16:37:55.988 warn State "go-e.0.temperatures.tempereature5" has no existing object, this might lead to an error in future versions
go-e.0 2022-01-25 16:36:56.020 warn State "go-e.0.temperatures.tempereature6" has no existing object, this might lead to an error in future versions
go-e.0 2022-01-25 16:36:56.015 warn State "go-e.0.temperatures.tempereature5" has no existing object, this might lead to an error in future versions
go-e.0 2022-01-25 16:35:56.019 warn State "go-e.0.temperatures.tempereature6" has no existing object, this might lead to an error in future versions
go-e.0 2022-01-25 16:35:56.013 warn State "go-e.0.temperatures.tempereature5" has no existing object, this might lead to an error in future versions
`

Habe jetzt auf Log Stufe Error gestellt, gibt es hierzu eine Lösung habe den go e v2

Gruß

Weiterhin Fehler mit Hardware v3 und 1.0.14

Folgender Log Eintrag in iobroker nach starten des Adapters.

go-e.0 2021-06-19 15:24:05.144 info (75464) {"version":"B","tme":"1906211524","rbc":"15","rbt":"26998952","car":"1","amx":"16","amp":"16","err":"0","ast":"0","alw":"1","stp":"0","cbl":"20","pha":"56","fsp":"0","tma":[33.25,38.875],"dws
go-e.0 2021-06-19 15:24:05.144 error (75464) API response validation error: [{"message":""lon" is required","path":["lon"],"type":"any.required","context":{"label":"lon","key":"lon"}}]

Next Stable Release for Version 2

Funktionen zur Version 2

Schreiben zu allen beschreibbaren Edpunken ermöglichen:

  • await queue.add(() => this.setState("ampere", { val: o.amp, ack: true })); // write
  • await queue.add(() => this.setState("access_state", { val: o.ast, ack: true })); // write
  • await queue.add(() => this.setState("allow_charging", { val: o.alw, ack: true })); // write
  • await queue.add(() => this.setState("stop_state", { val: o.stp, ack: true })); // write
  • await queue.add(() => this.setState("wifi.ssid", { val: o.wss, ack: true })); // write
  • await queue.add(() => this.setState("wifi.key", { val: o.wke, ack: true })); // write
  • await queue.add(() => this.setState("wifi.enabled", { val: o.wen, ack: true })); // write
  • await queue.add(() => this.setState("cloud_disabled", { val: o.cdi, ack: true }));
  • await queue.add(() => this.setState("wifi.hotspot_key", { val: o.wak, ack: true })); // write
  • await queue.add(() => this.setState("http_flags", { val: o.r1x, ack: true })); // write
  • await queue.add(() => this.setState("max_load", { val: (o.dwo / 10), ack: true })); // write
  • await queue.add(() => this.setState("electricity_exchange.min_hours", { val: o.aho, ack: true })); // write
  • await queue.add(() => this.setState("electricity_exchange.finish_hour", { val: o.afi, ack: true })); // write
  • await queue.add(() => this.setState("led_brightness", { val: o.lbr, ack: true })); // write
  • await queue.add(() => this.setState("ampere_level1", { val: o.al1, ack: true })); // write
  • await queue.add(() => this.setState("ampere_level2", { val: o.al2, ack: true })); // write
  • await queue.add(() => this.setState("ampere_level3", { val: o.al3, ack: true })); // write
  • await queue.add(() => this.setState("ampere_level4", { val: o.al4, ack: true })); // write
  • await queue.add(() => this.setState("ampere_level5", { val: o.al5, ack: true })); // write
  • await queue.add(() => this.setState("color.idle", { val: "#" + ("000000" + parseInt(o.cid).toString(16)).slice(6), ack: true })); // write
  • await queue.add(() => this.setState("color.charging", { val: "#" + ("000000" + parseInt(o.cch).toString(16)).slice(6), ack: true })); // write
  • await queue.add(() => this.setState("color.finish", { val: "#" + ("000000" + parseInt(o.cfi).toString(16)).slice(6), ack: true })); // write
  • await queue.add(() => this.setState("time_offset", { val: o.tof, ack: true})); // write
  • await queue.add(() => this.setState("time_daylight_saving", { val: o.tds, ack: true })); // write
    // RFID Name
  • await queue.add(() => this.setState("rfid.badges.1.name", { val: o.rna, ack: true })); // write
  • await queue.add(() => this.setState("rfid.badges.2.name", { val: o.rnr, ack: true })); // write
  • await queue.add(() => this.setState("rfid.badges.3.name", { val: o.rnd, ack: true })); // write
  • await queue.add(() => this.setState("rfid.badges.4.name", { val: o.rn4, ack: true })); // write
  • await queue.add(() => this.setState("rfid.badges.5.name", { val: o.rn5, ack: true })); // write
  • await queue.add(() => this.setState("rfid.badges.6.name", { val: o.rn6, ack: true })); // write
  • await queue.add(() => this.setState("rfid.badges.7.name", { val: o.rn7, ack: true })); // write
  • await queue.add(() => this.setState("rfid.badges.8.name", { val: o.rn8, ack: true })); // write
  • await queue.add(() => this.setState("rfid.badges.9.name", { val: o.rn9, ack: true })); // write
  • await queue.add(() => this.setState("rfid.badges.10.name", { val: o.rn1, ack: true })); // write
  • await queue.add(() => this.setState("led_save_energy", { val: o.lse, ack: true })); // write
  • await queue.add(() => this.setState("unlock_state", { val: o.ust, ack: true })); // write
  • await queue.add(() => this.setState("electricity_exchange.balance_time", { val: o.dto, ack: true })); // write
  • await queue.add(() => this.setState("energy.norway_mode", { val: o.nmo, ack: true })); // write

Feature Get State from Solar Power, House Consumption & House Battery as external States

Describe the bug
Use await this.asyncGetForeignStateVal(this.config.homeBatteryState);

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:
  • JS-Controller version:
  • Node version:
  • Operating system:

Additional context
Add any other context about the problem here.

Ich bekomme seit 2 Tagen plötzlich immer mehr warnmeldungen

Adapter Version 1.04
Node.js
v12.22.1
NPM
6.14.12

go-e.0 2021-05-30 10:01:02.192 warn at processTicksAndRejections (internal/process/task_queues.js:97:5)
go-e.0 2021-05-30 10:01:02.192 warn at runMicrotasks (<anonymous>)
go-e.0 2021-05-30 10:01:02.192 warn at GoE.processStatusObject (/opt/iobroker/node_modules/iobroker.go-e/main.js:318:25)
go-e.0 2021-05-30 10:01:02.192 warn at PQueue.add (/opt/iobroker/node_modules/p-queue/dist/index.js:152:16)
go-e.0 2021-05-30 10:01:02.192 warn at new Promise (<anonymous>)
go-e.0 2021-05-30 10:01:02.192 warn at /opt/iobroker/node_modules/p-queue/dist/index.js:171:18
go-e.0 2021-05-30 10:01:02.192 warn at PQueue._tryToStartAnother (/opt/iobroker/node_modules/p-queue/dist/index.js:105:17)
go-e.0 2021-05-30 10:01:02.192 warn at run (/opt/iobroker/node_modules/p-queue/dist/index.js:157:104)
go-e.0 2021-05-30 10:01:02.192 warn at /opt/iobroker/node_modules/iobroker.go-e/main.js:318:99
go-e.0 2021-05-30 10:01:02.192 warn (31771) Error in go.e: "Cannot read property '0' of undefined"; Stack: TypeError: Cannot read property '0' of undefined
go-e.0 2021-05-30 10:01:02.145 warn (31771) Cloud not store synctime, because of error object null is not iterable (cannot read property Symbol(Symbol.i

Falsche Objekttypen

Hi,
bekomme mit HW V3 folgende Meldungen im Log.

2021-09-19 20:43:05.260 - info: go-e.0 (27577) State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
2021-09-19 20:44:05.242 - info: go-e.0 (27577) State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
2021-09-19 20:45:05.264 - info: go-e.0 (27577) State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
2021-09-19 20:46:05.212 - info: go-e.0 (27577) State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
2021-09-19 20:47:05.244 - info: go-e.0 (27577) State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
2021-09-19 20:48:05.242 - info: go-e.0 (27577) State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object"
2021-09-19 20:49:05.248 - info: go-e.0 (27577) State value to set for "go-e.0.temperatures.tempereatureArray" has to be stringified but received type "object

Wrong date in iobroker

My go-echarger seems to give me a wrong date (today is the 20th of February 2021 14:00. In the json I see "2002211400" for tme which is obviously wrong. That should be "2002201400". I have set "tof":"101","tds":"1" in the go-echarger, which would be correct for timezone Euroe/Berlin I hope.
Nevertheless, in iobroker I see this for the datapoint synctime/tme: Fri Feb 21 2020 14:00:00 GMT+0100 (Mitteleuropäische Normalzeit)
The date is exatly what the go-echarger is delivering, but the weekday is wrong. The 21st should be a Sunday and not Friday. So the go-echarger seems to make a misstake (don't know why, maybe problem with europe.pool.ntp.org? But the adapter also seems to make a misstake by delivering the wrong weekday.

Greetings, Jürgen

Objekt "ast" bzw. "acess state" unvollständig

Laut der go-e API v1 Spezifikation sollte das Objekt "ast" bzw. "acess state" folgende Werte haben können:
0: Offen
1: RFID
2: Strompreis

Im ioBroker lässt sich allerdings nur 0 (open) oder 1 (key required) setzen! In der go-e App gibts sogar noch eine weitere Möglichkeit "Ladetimer". Wenn ich das Objekt bearbeite so dass ich z.B. auch eine 2 setzen kann, dann kommt die aber am Charger nicht an. Ist das ein Bug im Adapter?
API_Doku
ioBroker
App-Einstellungen

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.