ticaki / iobroker.espresense

Connect to ESPresense

ioBroker.espresense

Tests:

espresense adapter for ioBroker

Connect to ESPresense

• MQTT server and clientmodue

• Start own mqtt server activate server mode

• Server ip use only for external mqtt server

• Port, Username & Passowrd of internal or external mqtt Server

• If devices have been added to the configuration, only these will be displayed in the objects.

• The two configuration times are linked, the presence check always runs with the processing of the MQTT messages.

Best practice: Pair the devices to be monitored with espresense and filter the output to avoid unnecessary network traffic.

For help use issue or if u understand german https://forum.iobroker.net/topic/71189/test-adapter-espresense

• The mqtt-server used is a fully compatible MQTT 3.1 and 3.1.1 server, but the adapter only responds to the topic espresense/#

Changelog

0.4.4 (2024-01-18)

• (ticaki) The time period over which incoming Mqtt messages are collected can be configured. min. 1 sec max. (2^31-1) / 1000 sec

0.4.3 (2024-01-14)

• (ticaki) Collect incoming MQTT messages and process them every 5 seconds

0.4.2 (2024-01-05)

• (ticaki) New state for actual distance/conversion factor and calculated distance

0.4.1 (2023-12-30)

• (ticaki) fixed: no names. (2. try)

0.4.0 (2023-12-30)

• (ticaki) fixed: no names.
• (ticaki) Added: global esp32 configuration (retained)

0.3.0 (2023-12-23)

• (ticaki) Breaking Change: move datadir from node_modules/iobroker.espresense/mydp to iobroker-data/espresense.0 (instance). move the files there and use iobroker fix after it.

0.2.1 (2023-12-21)

• (ticaki) fixed: object not exist sometimes.

0.2.0 (2023-12-21)

• (ticaki) Add/Remove Devices

0.1.3 (2023-12-21)

• (ticaki) prepare for lastest

0.1.2 (2023-12-21)

• (ticaki) add common.name to states

0.1.1 (2023-12-20)

• (ticaki) fixed: sometimes adapter crashed after login.

0.1.0 (2023-12-20)

• (ticaki) Added: send configuration datapoints to esp

0.0.3 (2023-12-19)

• (ticaki) Added: Mqtt Server with file db

0.0.2 (2023-12-18)

• (ticaki) initial release

License

MIT License

Copyright (c) 2024 ticaki [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.

iobroker.espresense's Issues

Konfiguration der ESPresense Sensoren wird zerschossen und zwar bei beiden gleichzeitig

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)

Causes very high system load

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%)

Fehlermeldung „.“ am Ende des Namens

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)