ticaki / iobroker.espresense Goto Github PK

The adapter causes very high system load.

System:
Proxmox host (3 node cluster), i7-12650H, 16 cores, 32 GB RAM, storage via NFS from a QNAP
iobroker 4 Cores, 16 GB RM
The only VM on that Proxmox host

————

After installing and using the adapter, my iobroker incl. the Proxmox host almost “died”.
CPU-temp of the host went up to above 70 degrees celsius

Top gives back:
Espresence up to 23% system load (average approx. 19%)
is-controller 75% (min. 64%) system load

————

After stopping Espresence..
CPU-temp going down to approx. 45-50 degrees celcius

Top:
js-controller max. 31% system load (average 23%)

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 espresense for common errors and appropiate suggestions to keep this adapter up to date.

Please see the result of the check below.

ioBroker.espresense

-

ERRORS:

• ❗ [E033] @iobroker/adapter-core 3.0.4 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
• ❗ [E162] js-controller 3.3.22 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"
• 👀 [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.

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

Ich habe dann einen zusätzlichen iTag auf diese Weise konfiguriert. Danach liefen die Sensoren nicht mehr und befanden sich im Bootloop. Ich überprüfte die Konfiguration der Sensoren, nachdem ich zuerst die MQTT- und ESPresense-Adapter gestoppt und alle Datenpunkte dieser Adapter gelöscht hatte. Nachdem ich die Adapter wieder startete, kamen die Sensoren aus dem Bootloop.

Die Basis-Konfigurationen der Adapter waren unverändert, aber die Einstellungen waren bei allen Sensoren komplett zerstört. Da standen so Werte wie "Null" drin. Ich musste diese Einstellungen wieder korrigieren, danach begannen sie wieder, MQTT-Daten zu senden, nur leider nicht mehr so wie vorher. Einige iTags wurden nicht mehr erkannt. Erst ein erneutes Flashen der Sensoren hat alle Problem behoben. Das heißt, es werden auch noch Sensorkonfigurationsdaten zerstört, die über die Einstellungen nicht verändert/angepast werden können.

(ÄTZEND)

Adapterversion 0.4.1
Node 18.17.1
Js-controller 5.0.17

Adapter installiert und 1 x ESPresence-Sensor per MQTT (ext. MQTT auf iobroker) angebunden.

Er schreibt mir das Log im Sekundentakt voll:

espresense.0
2024-01-02 06:10:32.389	error	Error: The id "rooms.wohnzimmer." is invalid. Ids are not allowed to end in "." 

Ich habe aber nirgendwo den Punkt definiert … in ESPresence selber heißt das Teil nur „Wohnzimmer“
Siehe auch Post im Forum : Link

VG,
Eric (eric2905)