Describe the bug
Calling commands like resetting the meter values results in error.

To Reproduce
Steps to reproduce the behavior:

1. Go to objects > warp.0.meter.reset
2. Set value for reset to true
3. Meter values are not reset + error result in protocol

Expected behavior
No error in protocol + meter values in WARP should be resetted.

Screenshots & Logfiles

Versions:

• Adapter version: 1.0.0
• JS-Controller version: 4.0.21
• Node version: 14.19.1
• Operating system: linux (docker)

Hi,

while charging the state shows ERROR(3). The enum is not correct.
The api shows 5 enums and 3 is charging not error. https://www.warp-charger.com/api.html#states_section_states

The enum in warp-api-definitions.ts:
Param.enum('charger_state', { 0: 'NOT_CONNECTED', 1: 'CONNECTED', 2: 'CHARGING', 3: 'ERROR' })

Greetings,
Lars

Zu allererst, vielen Dank für den Adapter, das sieht sehr vielversprechend aus.

Ich habe das Problem das bei beiden wallboxen von mir mit jeweils eigener Instanz der LOG mit folgenden Warn Meldungen voll ist.

Zuerst zum System.
Nodejs 14.19.1
NPM 6.14.16
JS Controller 4.0.21

2x Warp2 Smart

Die Fehler kommen im Sekundentakt bei beiden Wallboxen.

`

warp.0 | 2022-04-05 20:06:46.150 | warn | (7047) Object of state "warp.0.evse.low_level_state.gpio" is missing the required property "common.type"
warp.0 | 2022-04-05 20:06:46.078 | warn | (7047) Object of state "warp.0.evse.low_level_state.voltages" is missing the required property "common.type"
warp.0 | 2022-04-05 20:06:46.066 | warn | (7047) Object of state "warp.0.evse.low_level_state.adc_values" is missing the required property "common.type"
warp.0 | 2022-04-05 20:06:45.140 | warn | (7047) Object of state "warp.0.evse.low_level_state.gpio" is missing the required property "common.type"
warp.0 | 2022-04-05 20:06:45.039 | warn | (7047) Object of state "warp.0.evse.low_level_state.voltages" is missing the required property "common.type"
warp.0 | 2022-04-05 20:06:45.019 | warn | (7047) Object of state "warp.0.evse.low_level_state.adc_values" is missing the required property "common.type"
warp.0

`

Hi,

i have 4 connected warp chargers. And every minute there are warn messages in the log like this;

warp.3 | 2023-05-23 14:34:06.512 | warn | [WarpClient] Unexpected disconnected from WARP charger. Try reconnecting in 60 seconds
warp.3 | 2023-05-23 14:34:06.510 | info | [WarpClient] Connected to WARP charger
warp.3 | 2023-05-23 14:34:06.500 | info | [WarpClient] Try connecting to WARP charger
warp.3 | 2023-05-23 14:34:06.500 | warn | [WarpClient] Try reconnecting
warp.3 | 2023-05-23 14:34:06.495 | info | [WarpClient] Last received keep alive timestamp is older than 40 seconds

Can i solve this? Is there a config for the timeout?

Greetings,
Christian

A new WARP firmware was released (version 2.0.0) with a lot of breaking changes in the API

I want to install the adapter and get this message!
"Invalid version of js controller. Required >=2.0.0. Current 4.0.23"
A little crazy!
4.0.23 is bigger than 2.0.0

When starting the WarpAdapter with version 1.0.1 the message appears that the firmware >= 2.0.0 must be installed.

But the http request returns the requested version:

{"firmware":"2.0.1-624eeb29","config":"2.0.0"}

The following constellation is present in the firmware:

Unfortunately, I have no more idea how to get the adapter to work.

The older version with the 1.9 firmware still worked.

Versions:

• Adapter version: 1.0.1
• JS-Controller version: 4.0.23
• Node version: v14.19.1

Distributor ID: Ubuntu
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Codename: focal

The static init period of 120 seconds from adapter start needs to be improved. Better solution is to remember which objects/devices are already initialized instead of time period.

Notification from ioBroker Check and Service Bot

Dear adapter developer,

I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter warp for common errors and appropiate suggestions to keep this adapter up to date.

Please see the result of the check below.

ioBroker.warp

-

ERRORS:

• ❗ [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommened
• ❗ [E033] @iobroker/adapter-core 2.6.0 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
• ❗ [E036] @iobroker/testing 3.0.2 specified. 4.1.3 is required as minimum, 4.1.3 is recommended. Please update devDependencies at package.json
• ❗ [E162] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.

WARNINGS:

• 👀 [W040] "keywords" within package.json should contain "ioBroker"
• 👀 [W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
• 👀 [W109] Missing suggested translation into uk of "common.desc" in io-package.json.
• 👀 [W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
• 👀 [W130] Many "common.news" found in io-package.json. Repositorybuilder will truncate at 7 news. Please remove old news.
• 👀 [W145] Missing suggested translation into uk of some "common.news" in io-package.json.
• 👀 [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
• 👀 [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
• 👀 [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
• 👀 [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
• 👀 [W522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.

Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

@mcm1957 for evidence

Nightjob detected a change of the official API documentation. https://www.warp-charger.com/api.html had a change:

(changed) Zustände meter/state meter/values meter/phases meter/error_counters meter/all_values Kommandos meter/reset HTTP-Spezifisch meter/history meter/live
(-> into) Zustände meter/state meter/values meter/phases meter/error_counters meter/all_values Kommandos meter/state_update meter/values_update meter/phases_update meter/all_values_update meter/reset Zustände meter/last_reset HTTP-Spezifisch meter/history meter/live
(changed) Zustände nfc/seen_tags Kommandos nfc/inject_tag Konfigurationen nfc/config
(-> into) Zustände nfc/seen_tags Kommandos nfc/inject_tag nfc/inject_tag_start nfc/inject_tag_stop Konfigurationen nfc/config
(changed) Konfiguriert, ob ein angeschlossenes Fahrzeug selbstständig geladen wird. Dieser Wert kann über evse/auto_start_charging_update mit dem selben Payload aktualisiert werden. Achtung: Ein Neustart des Ladecontrollers setzt diesen Wert zurück auf true.
(-> into) Konfiguriert, ob ein angeschlossenes Fahrzeug selbstständig geladen wird. Dieser Wert kann über evse/auto_start_charging_update mit dem selben Payload aktualisiert werden.
(changed) evse/reset_dc_fault_current_state
(-> into) evse/reset_dc_fault_current_state (Nur WARP 2)
(added) + meter/state_update
(added) * Zustände
(changed) type WARP 1:
(-> into) type 2. 2 - SDM630
(changed) meter/phases (Nur WARP 2)
(-> into) meter/phases
(changed) meter/all_values (Nur WARP 2)
(-> into) meter/all_values
(added) meter/state_update
(added) meter/last_reset
(added) + nfc/inject_tag_start
(changed) Täuscht vor, dass ein Tag vom NFC-Leser erkannt wurde. Hiermit kann über die API ein Ladevorgang für einen bestimmten Benutzer gestartet werden. Das vorgetauschte Tag ist immer der letzte Eintrag in nfc/seen_tags
(-> into) Täuscht vor, dass ein Tag vom NFC-Leser erkannt wurde. Hiermit kann über die API ein Ladevorgang für einen bestimmten Benutzer gestartet oder gestoppt werden. Analog zur physischen Verwendung eines Tags wird der Ladevorgang bei Aufruf der API abwechselnd freigegeben oder blockiert. Siehe nfc/inject_tag_start und nfc/inject_tag_stop für genauere Kontrolle. Das vorgetauschte Tag ist immer der letzte Eintrag in nfc/seen_tags
(added)

Warp Adapter erzeugt in kurzem Takt Meldungen über Verbindungsabbrüche im log

Fehlerbeschreibung:
Im log der iobroker Instanz werden regelmäßig und in kurzen Intervallen Verbindungsabbrüche des Adapters gemeldet.

Meldungen:
2024-03-10 12:57:09.068 - info: warp.0 (21993) [WarpClient] Last received keep alive timestamp is older than 40 seconds
2024-03-10 12:57:09.080 - warn: warp.0 (21993) [WarpClient] Try reconnecting
2024-03-10 12:57:09.080 - info: warp.0 (21993) [WarpClient] Try connecting to WARP charger
2024-03-10 12:57:09.094 - info: warp.0 (21993) [WarpClient] Connected to WARP charger
2024-03-10 12:57:09.131 - warn: warp.0 (21993) [WarpClient] Unexpected disconnected from WARP charger. Try reconnecting in 60 seconds
2024-03-10 12:57:54.145 - info: warp.0 (21993) [WarpClient] Last received keep alive timestamp is older than 40 seconds
2024-03-10 12:57:54.151 - warn: warp.0 (21993) [WarpClient] Try reconnecting
2024-03-10 12:57:54.152 - info: warp.0 (21993) [WarpClient] Try connecting to WARP charger
2024-03-10 12:57:54.162 - info: warp.0 (21993) [WarpClient] Connected to WARP charger
2024-03-10 12:57:54.170 - warn: warp.0 (21993) [WarpClient] Unexpected disconnected from WARP charger. Try reconnecting in 60 seconds
2024-03-10 12:58:39.180 - info: warp.0 (21993) [WarpClient] Last received keep alive timestamp is older than 40 seconds
2024-03-10 12:58:39.187 - warn: warp.0 (21993) [WarpClient] Try reconnecting
2024-03-10 12:58:39.188 - info: warp.0 (21993) [WarpClient] Try connecting to WARP charger
2024-03-10 12:58:39.199 - info: warp.0 (21993) [WarpClient] Connected to WARP charger

Systemkomponenten:

• Warp2 über LAN; FW Version: 2.2.1-65ca20dd (erstellt 12.02.2024 14:45:01)
• iobroker auf raspberrypi 4 (8 GB)
  • Node.js: v18.19.1
  • NPM: 10.2.4

Folgende Prüfungen habe ich durchgeführt:

• Eine parallel testweise aktivierte (exklusive) mqtt-Instanz läuft problemlos.
• Die Fehler werden mit und ohne aktivierter mit Authentifizierung am WARP Charger geworfen.
• Im log des Warp Charger wird kein Fehler angezeigt.

Anmerkung:

Hallo Pottio,
eine Korrektur wäre schön, der Adapter ist ansonsten für meinen Bedarf ideal.
Für Fragen und Tests stehe ich gern zur Verfügung!
Grüße - Jürgen