ciddi89 / iobroker.device-watcher Goto Github PK

View Code? Open in Web Editor NEW

19.0 2.0 12.0 7.24 MB

Watchdog for adapter/instances and devices/services.

License: MIT License

JavaScript 100.00%

iobroker smarthome watchdog device-watcher home-automation notifications device devices lists

iobroker.device-watcher's Introduction

ioBroker.device-watcher

Version:

Tests:

Sentry

This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers. For more details and for information how to disable the error reporting see Sentry-Plugin Documentation! Sentry reporting is used starting with js-controller 3.0.

Documentation

🇬🇧 Documentation
🇩🇪 Dokumentation

Discussion and Questions

ioBroker Forum
ioBroker Discord Channel

Device-Watcher adapter for ioBroker

This is a watchdog for devices/services and adapter/instances. The adapter looks for the different information about the datapoints and create JSON & HTML lists of them:

Devices/Services:

devices with battery,
devices with low battery,
devices with link quality,
updates for devices,
devices offline and
all devices

Adapter/Instances:

all instances
deactivated instances
instances with error
available adapter updates

It's also counting them in the same categories. You can use the lists and states for Grafana, Jarvis etc for example.

Supported adapters:

Alexa2	APC UPS	Ble
Deconz	Enocean	ESP Home
euSec	FritzDect	fullyBrowser
Harmony	Ham	Home Connect
Homematic IP	Homematic RPC	HS100
Philips Hue	Philips Hue Extended	Innogy Smarthome
Jeelink	Lupusec	Max! Cube
Meross	MiHome	MiHome Vacuum
MQTT Client Zigbee2Mqtt	MQTT Nuki	MusicCast
Netatmo	Nuki Extended	Nut
Ping	Roomba	Shelly
Smartgarden	Sonoff	Sonos
Sureflap	Switchbot Ble	Tado
Tapo	Tradfri	Unifi
Wled	Yeelight	Zigbee
Zigbee2MQTT	Zwave

A list with more information about the supported adapters can be found here: in German or in English.
If one adapter is missing, feel free to open an request issue to add it.

Notifications:

The adapter has different possibilities to send notifications:

A device is no longer reachable or reachable again
A device has reached the low battery level or the low bat state is true
When an update is available for a device (shelly and unifi)
Time based a list of offline devices
Time based a list of low batterie devices
Time based a list of devices which can be updated

Currently supported notification services are:

Telegram
Pushover
WhatsApp
Email
Jarvis
Lovelace
Signal
SynoChat
and also an datapoint with the last notification, so you can use it for other services which aren't supported.

Blacklist

Is it neccessary to ignore a specifice device, you can add it in the blacklist and the device-watcher will ignore it. It's possible to select:

Ignore in notifications
Ignore in main list
Ignore in adapter own list

Here are some images how the lists can be look like in Grafana:

Credits

This adapter would not have been possible without the great work of Christian Behrends [email protected] who implemented the initial releases of this adapter.

Changelog

WORK IN PROGRESS

(ciddi89) Fixed #362: Ecovacs Deebot use connectionUptime dp as timeselector

2.12.1 (2024-05-09)

(ciddi89) Added: #341 Support for Zigbee battery_state datapoint

2.12.0 (2024-04-05)

(mcm1957) Adapter requires nodeJS >= 18 and js-controller >= 5 now
(mcm1957) Adpter has been migrated to iobroker-community-adapters organisation
(mcm1957) Dependencies have been updated

2.11.0 (2024-03-18)

(ciddi89) Added #323: Support for Ring Cameras

2.10.5 (2024-02-29)

(ciddi89) Fixed #262 & #292: Phantom Messages

2.10.4 (2024-02-26)

(ciddi89) Added: Option to set language for messages and tables
(ciddi89) Fixed #312: Schedule messages were not emptied after they were sent
(ciddi89) Fixed: Too many messages were sent about online / offline devices when an instance was started or ended

2.10.3 (2024-01-27)

(ciddi89) Fixed #299: blacklisted devices was shown in html-list

2.10.2 (2024-01-20)

(ciddi89) Fixed: typeError for available adapter update messages
(ciddi89) Fixed: Lists for updatable adapter

2.10.1 (2024-01-15)

(ciddi89) Fixed: several bugs from last version
(ciddi89) Added: finished translations

2.10.0 (2024-01-13)

(ciddi89) Fixed: Batterie value for shelly plus Gen2 devices #282
(ciddi89) Added: Option to display the last signal strength value when the device is offline #282
(ciddi89) Added: Translation for JSON lists, HTML lists and notifications #245
(ciddi89) Other: clean up code

2.9.14 (2024-01-04)

(ciddi89) Fixed: This schould fixed the bugs with high cpu and ram load, finally. Sorry about the last two buggy versions.

2.9.13 (2024-01-03)

(ciddi89) Fixed: Issues from v2.9.12 #283
(ciddi89) Fixed: High CPU usage at object and state changes #283

2.9.12 (2024-01-02)

(ciddi89) Fixed: Changed handling for state changes and subscriptions #283

2.9.11 (2023-12-12)

(ciddi89) Fixed: Fullybroswer >v3 use id not common name

2.9.10 (2023-12-11)

(ciddi89) Fixed: Fullybroswer >v3 devicename
(ciddi89) Fixed: Fullybroswer >v3 wifi signal

2.9.9 (2023-12-07)

(ciddi89) Fixed: Write log message of selected adapters only on startup

2.9.8 (2023-11-26)

(ciddi89) Fixed: Added additional check for instance states #262
(ciddi89) Fixed: Execute adapter even if no device adapter is selected

2.9.7 (2023-11-23)

(ciddi89) Added: Support for Wifilight
(ciddi89) Fixed: Multiple messages if Sonoff devices reachable #244

2.9.6 (2023-11-12)

(ciddi89) Fixed: Admin jsonConfig schema
(ciddi89) Changed: Admin jsonConfig to json5
(ciddi89) Added: Support for Tuya devices with online state
(ciddi89) Other: cleaned up files

2.9.5 (2023-11-03)

(ciddi89) Added: if available use deviceName datapoint for sonoff devices
(arteck) Fixed: Changed zwave to zwave2
(ciddi89) Fixed: minor bugfixes
(ciddi89) Added: FullyBrowser > v3

2.9.4 (2023-10-16)

(ciddi89) Added: Fallback for HmIp-eTRV-2 batterie devices #218
(@mango1402) Fixed: Proxmox VM/CT online status #241
(ciddi89) Updated: Dependencies

2.9.3 (2023-07-21)

(ciddi89) Dropped: Node v14.x support and added: Node v20.x support
(ciddi89) Fixed: last seen of Ping devices
(ciddi89) Fixed: Connection messages of devices without instance connection datapoint
(ciddi89) Fixed: Data & Lists of instances wasn't refreshed correctly
(ciddi89) Fixed: Tradfri state alive must be false for device offline state

2.9.2 (2023-05-19)

(ciddi89) Fixed: Instance name in schedule notifications for faulty instances
(ciddi89) Fixed: Ignore null values in update datapoints of devices
(ciddi89) Updated: Dependencies

2.9.1 (2023-04-27)

(ciddi89) Removed: Function for error handling (not neccessary)

2.9.0 (2023-04-26)

(ciddi89) Fixed: Deactivated instances were not displayed in the daily message about deactivated instances
(ciddi89) Added: Viessmann devices, Homekit-Controller devices
(ciddi89) Improvements: Text of overview messages

2.8.5 (2023-04-20)

(ciddi89) Fixed: Error that instances can not be added to the blacklist because of the popup message #172
(ciddi89) Fixed: That messages have been sent when the instance has briefly jumped from Enabled to Disabled and back to Enabled #173

2.8.4 (2023-04-16)

(ciddi89) Fixed: Functions for instance status completely renewed (#170)
(ciddi89) Added: Popup message when the instance is not running and the user tries to select a device/instance in the settings tables (#170)

2.8.3 (2023-04-13)

(ciddi89) Fixed: Multiple push messages when restarting an instance (#170)

2.8.2 (2023-04-13)

(ciddi89) Fixed: Don't handle id's which ends with fullstop
(ciddi89) Added: Possibility for the user to select the global deactivation time for instances

2.8.1 (2023-04-09)

(ciddi89) Added: Possibility for the user to select the global error time for instances

2.8.0 (2023-04-04)

(ciddi89) Added: Support for LOQED Smart Lock
(ciddi89) Added: Option to add user/group api key for Pushover
(ciddi89) Added: Option to send notification if an instance was stopped
(ciddi89) Added: Option to send shedule notifications with overview of stopped instances
(ciddi89) Fixed: Issue if notifications was send of stopped instance but the option wasn't choosen
(ciddi89) Fixed: Ignore battery values 0% if they were not smaller than 5% before

2.7.1 (2023-03-26)

(ciddi89) Added: Support for Ecovacs-Deebot
(ciddi89) Updated: Dependencies
(ciddi89) Improvements: Small fixes

2.7.0 (2023-03-13)

(ciddi89) Added: Fully-MQTT
(ciddi89) Added: Notification Service Matrix
(ciddi89) Added: List and number of active instances
(ciddi89) Added: HTML lists for instances/adapters
(ciddi89) Added: HM-RPC device update pending datapoint
(ciddi89) Added: User can define reporting time for error instances
(ciddi89) Fixed: Send notification about adapter updates only if there are new ones
(ciddi89) Improvements: Hide notification services only if no instance is choosen
(ciddi89) Improvements: Some small code changes to avoid error messages

2.6.1 (2023-02-26)

(ciddi89) Added: Signal adapter for notifications
(ciddi89) Added: Raw-List with all data of devices
(ciddi89) Added: FHEM TFA sensors #137
(ciddi89) Improvement: Objecthandling of devices/instances
(ciddi89) Improvement: Adapter update data
(ciddi89) Fixed: HM-CC-RT-DN battery #128
(ciddi89) Added/Changed: some texts in instance config

2.6.0 (2023-02-06)

(ciddi89) Fixed: Instance error list and count was not reset
(ciddi89) Fixed: Made working notification for adapter update
(ciddi89) Added: Delete objects automatically if it is not selected in settings.
(ciddi89) Enhancement: Check if general device connected state is true for more then few seconds to prevent multiple device status messages
(ciddi89) Added: Proxmox Adapter (#123)
(ciddi89) Fixed: Delete/Add data of new or deleted instance without restart (#125)
(ciddi89) Fixed: Delete/Add data of new or deleted devices without restart (#125)
(ciddi89) Enhancement: Schedule and State notifications
(ciddi89) Enhancement: Some code improvements

2.5.0 (2023-01-27)

(ciddi89) Add Feature: Possibility to watch instances
(ciddi89) Change: Folder strukur. Instances and devices have got their own folders because of the overview. Please delete the instance folder and restart the instance.

2.4.1 (2023-01-14)

(ciddi89) send online and offline notifications only, if the connection to device (zigbee stick etc.) is longer then few seconds. Should prevent multiple messages at a stroke
(ciddi89) fixed issue that all devices was listed even though only batterie devices was selected

2.4.0 (2023-01-10)

(ciddi89) make onStateChanges only, when device instance is alive
(ciddi89) Homeconnect and Smartgarden Adapter added

2.3.1 (2023-01-05)

(ciddi89) changed HMRPC lowbat to lowbat_alarm
(ciddi89) changed HMRPC unreach to unreach_alarm
(ciddi89) fixed nuki mqtt selector
(ciddi89) added shelly charge datapoint to identify battery devices better
(ciddi89) fixed lowbat issues
(ciddi89) added lowbat support for HMRPC: HM-CC-RT-DN
(ciddi89) added additionally timeSelector for each adapter for better support

2.3.0 (2023-01-03)

(ciddi89) sorting for device selection in the blacklist added
(ciddi89) Devices can now also be blacklisted in adapter own list
(ciddi89) booleans for lowbat, offline and upgradable added (#105)
(ciddi89) euSec adapter added (#73)

2.2.2 (2022-12-29)

(ciddi89) some translation added
(ciddi89) datapoints will be written in intervall
(ciddi89) improvements of lists
(ciddi89) some other small improvements

2.2.1 (2022-12-28)

(ciddi89) Innogy Smarthome added
(ciddi89) Lists for each adapter are working again

2.2.0 (2022-12-27)

(Scrounger) Yamaha MusicCast adapter added
(ciddi89) send update message on state change
(Scrounger) datapoints and scheduled notification for updateable devices added
(ciddi89) reaction for state changes of battery datapoints added
(ciddi89) send message and write lists directly if one device has low battery
(ciddi89) send message and write lists directly if on device is going online or offline

2.1.0 (2022-12-19)

(Scrounger) optionally show adapter name in notification
(ciddi89) optionally receive a message when an update for an device is available #87
(Scrounger) update message for shelly adapter added
(Scrounger) Yamaha MusicCast adapter added
(ciddi89) update message for unifi devices added
(ciddi89) fixed devices are not reported in case battery is 0% #86
(ciddi89) SynoChat added #85
(ciddi89) MQTT NukiHub, MQTT-Clien Zigbee2MQTT added (#82)

2.0.3 (2022-11-26)

fixed issue with localCompare
added tapo
(Scrounger) added fullyBrowser adapter
(Scrounger) added Sure Flap adapter
fixed low bat messages

2.0.2 (2022-11-12)

added status to battery list
batt devices which are offline are now still included in the battery list
small improvements of translations
offline time settings: you can use 0 instead of -1 (it will be the new standard)
improvements of adaptername
fixed issues #66 & #67
repaired blacklist notifications
added handling for blacklist object

2.0.1 (2022-11-02)

If the device is offline, set signal strength to '0%'
If the device is offline, set battery to ' - '
repair some small issues in the lists

2.0.0 (2022-11-01)

added Lupusec, HS100 adapter, Zigbee2MQTT and MaxCube
changed name of Homematic to HM-RPC
made a completly makeover of the blacklist
clean up the code and shorten some

1.1.0 (2022-10-03)

removed indicatoren for daily sent messages
changed selector for shelly devices
added Zigbee2MQTT adapter
added cron function to use own time for daily overview messages

1.0.1 (2022-09-30)

added WLED, Ikea Tradfri, Roomba, HmIp, Tado, Netatmo, Yeelight-2, Unifi, Nut and Meross adapter
fixed battery message
corrected and repaired some issues of last contact time
added support for old HM devices
some small refactoring of code
changed shelly selector from dp rssi to dp online

1.0.0 (2022-09-03)

** BREAKING CHANGE ** If you update from version <= 0.3.0, remove the old instance first before you update to >= 1.0.0. After that you can create a new instance.
changed mode from shedule to daemon, please take aware from the advice above
added Logitech Harmony Hub
small bugfixes (own function for blacklist, fix for memory leak etc.)

0.3.0 (2022-08-10)

removed channelnumber in Homematic devices name
added function to create html list
added german and english documentation

0.2.4 (2022-07-31)

many changes of code, comments and error handling

0.2.2 (2022-07-28)

fixed translations
added sentry
added nuki battery state

0.2.1 (2022-07-27)

removed test states

0.2.0 (2022-07-24)

added function to create data of each adapter

0.1.2 (2022-07-22)

improved overview of admin ui
added option in admin ui to create own folders for each adapter (!!not working yet!!)

0.1.1 (2022-07-22)

changed wrong type of datapoint lastCheck
added possibility to choose own offline time for each adapter
added Whatsapp notification services
improved sonoff devices
added row with online and offline status in table allDevices
added alexa2 and esphome devices
Added priority for pushover notifications

0.0.8 (2022-07-05)

added own notes field for blacklist
added ping, switchbot ble, mihome, sonos, fritzdect, hue, hue extended and nuki extended
some improvements of code

0.0.6 (2022-06-10)

added Homematic, Deconz, Zwave
added Email notification
added count and list for low battery devices
changes Log state dp to last notification state dp
Using available state instead of link quality state for zigbee devices
Show the correct time of last contact instead the minutes if the time is under 100minutes
small bugfixes

0.0.5 (2022-06-05)

added admin translations

0.0.3 (2022-06-05)

added Shelly and Sonoff Devices

0.0.2 (2022-06-05)

Release for testing

0.0.1 (2022-05-01)

initial release

License

MIT License

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.device-watcher's People

Contributors

Stargazers

Watchers

Forkers

arteck o0shojo0o apollon77 scrounger iobrokertranslator mcm1957 garfonso mango1402 linxxx213 iobroker-archive iobroker-archive dklinger

iobroker.device-watcher's Issues

Error catched and sent to Sentry, error: [[writeDatapoints]] error: Cannot read property 'localeCompare' of undefined

Hi,

i receive this Error in the logs:

Error catched and sent to Sentry, error: [[writeDatapoints]] error: Cannot read property 'localeCompare' of undefined

Fresh installed adapter
Plattform: linux
RAM: 7.7 GB
Node.js: v14.19.3(14.21.1 / 16.18.1)
NPM: 6.14.17(8.19.2)
Admin v6.2.23

The HTML Report will not be generated. What can i do to fix this problem?
Regards
Sebastian

You might be interested in (Lovelace embedding)

I have created a small script which creates HTML data points from your adapters for me to embed them in Lovelace.
https://github.com/o0shojo0o/iob.Device-Watcher_ToHTML

save method is not available

bandicam.2022-07-29.07-11-46-392.mp4

Aktuelle Version schmeißt warnings

Describe the bug
der Adapter "device-watcher" beendet sich nach seiner Ausführung nicht (Schedule) und verursacht somit warnings im Log.

To Reproduce
Steps to reproduce the behavior:

Stop oder kill den Prozess "device-watcher"
Starte den Adapter "device-watcher" neu, dann sieht das ganze so aus:
auf das erste Scheduling warten und der Adapter sieht anschließend so aus:
es gibt zudem folgende Log Einträge:

host.iobroker | 2022-09-20 12:30:08.119 | warn | instance system.adapter.device-watcher.0 already running with pid 291357
host.iobroker | 2022-09-20 12:15:04.112 | warn | instance system.adapter.device-watcher.0 already running with pid 291357
host.iobroker | 2022-09-20 11:46:43.650 | error | instance system.adapter.device-watcher.0 terminated with code 156 START_IMMEDIATELY_AFTER_STOP)
host.iobroker | 2022-09-20 11:45:04.079 | warn | instance system.adapter.device-watcher.0 already running with pid 254312

Adapter Versions:

Verfügbare Version: 1.0.0
Installierte Version: 1.0.0

Additional context
PlatformBetriebssystem:linux
Architektur:x64
Node.js:v16.17.0
NPM:8.15.0
Aktive Instanzen:33
Pfad:/opt/iobroker/
_nodeCurrent:16.17.0
_npmCurrent:8.15.0

VG
Bernd

Blacklist for Sonoff not working

i used it to watch my sonoff (tasmota) devices, and i have set one to the blacklist
but it comes the message that is offline

have i the wrong datapoint?
thanks

Zigbee lights state

Hi there,

Nice work on that adapter.

I was thinking if it was possible to add states from certain devices like zigbee lights. (on/off). In a second step this states could be written into an array in case of power grid failure. (My iob is connected to an USV). When power is back those states are written back to each zigbee light. Currently my house is shinning like a xmas tree after power failure. :-) Cheers

zigbee2mqtt

Hallo!
Ich würde gerne den device-watcher für meine zigbee-Geräte einsetzen. Alle meine zigbee-Geräte laufen unter zigbee2mqtt. Im ioBroker kommuniziere ich dann über MQTT-Client mit den Geräten. Funktioniert alles perfekt.
Der device-watcher findet nur die vom Adapter Ping verwalteten Geräte. Die Zibbee-Geräte findet er nicht.
Protokoll:

Hardcopy von

Mache ich etwas falsch oder habe ich eine falsche Erwartungshaltung?
Protokoll.pdf
iobroker.current.log.txt

checkbox is not available

bandicam.2022-07-29.07-11-59-237.mp4

HM Devices Fault_Reporting

Describe the bug
ioBroker-Forum:
https://forum.iobroker.net/topic/55426/test-adapter-device-watcher-v2-x-x-github-latest/943?_=1672848027466

leere HM (ohne IP) Komponenten bei denen die CCU das zwar wusste, der low_bat Datenpunkt trotzdem durchgehend auf false stand, dafür der Fault_Reporting auf 6 (aka. LOWBAT).

Tapo-Adapter wäre super

TA2K arbeitet gerade an einem neuen Adapter für die TP100 etc. von TP-Link.
https://github.com/TA2k/ioBroker.tapo
Die sind recht beliebt, da sie beim großen A für einen unschlagbaren Preis zu bekommen sind.

Der Screenshot ist alles andere als optimal, da der Entwickler z.Zt. noch alles liest was er irgendwie erwischen kann.
Die einzelnen Geräte hängen im Baum direkt unter der Instanz.

Ach übrigens: Danke für Deine Arbeit!

Offline Zeit funktioniert nicht

Describe the bug
Die Einstellung Offline Zeit wird bei einer Änderung der Werte nicht gespeichert (das Feld speichern wird nicht aktiv, wenn ein anderer Wert noch geändert wird ist zwar speichern aktiv, aber die Werte setzen sich wieder auf -1 zurück)

To Reproduce
Steps to reproduce the behavior:

Go to 'Expert Settings'
Click on 'Offline-Zeit'

Expected behavior
die Werte sollten gespeichert werden

Screenshots & Logfiles

Current states (xx Tagen) als offline Gerät

Ich lasse mir die Meldung via Telegram senden. Folgendes wird gesendet:

Folgende 2 Geräte sind seit einiger Zeit nicht erreichbar:
Current states (39 Tagen)
Temperatursensor Garage (48 Stunden)

Woher kommt "Current states"? Kann man den ausblenden?

Vielen Dank für den Adapter.

HmIP Geräte werden nicht gefunden

Bosch Smart Home Bridge - Support

Hello,

it would be nice, if support for the Bosch devices could be added.
The datapoint have no Online or last seens status. Therefore - i think - it should be looked for last timestamp or similar

If you need anything for this, please let me know.

Homeatic Last Contact Fehlerhaft

Hallo,
ich habe hier ein HM-Sec-SCo Fenster Kontakt.
Der funktioniert auch wunderbar, nur der Adapter sagt mir, das der letzte Kontakt über 300 Tage her ist.

{"Device":"Fenster Büro:0","Adapter":"Homematic","Battery":" - ","Signal strength":"0%","Last contact":"338 Tagen","Status":"Online"}

Der State Datenpunkt hatte die letzte Änderung vor 2 Tagen.

Was ließt der Adapter hier genau aus? Der Rest wie Battery und Signalstärke stimmt. Das wird nicht geliefert in Homematic.

Adapter Version ist 0.2.4

Sollten noch Daten gebraucht werden, dann einfach melden.

Add option to blacklists devices in lists for each adapter

Add option in blacklist menu to blacklist devices in lists of each adapter

working battery devices are not reported in case battery is 0%

yes, this sounds a bit strange - but i do have sensors which are still happily running with a reported battery of 0% (zigbee).
They do have been reported by device-watcher as long as they still had 1% - and then they dropped out of the list. Datapoint "available" is "true".
adapter version: 2.0.3

ah, not worth a separate issue - perhaps you could swap the string "Niedriege" to "Niedrige" ;-) - or, even better, allow to enter a string for the report.
Thanks for the adapter - really useful!

Feature: Notification if update available

Describe the solution you'd like
It would be great if the adapter would also check for updates and send a notification.
Think that actually fits great to this adapter, what do you think?

kein Ergebnis

Es werden offensichtlich keine Adapter ausgelesen
Alle Listen sind leer:
[{"Device":"--keine--","Adapter":"","Battery":""}]

Es werden keine Datenpunkte aktualisiert - ausgenommen ist lastCheck: hier wird der Timestamp eingetragen

Wenn weitere Infos benötigt werden, bitte melden

Tado Adapter

Es währe super wenn auch der Tado-Adapter abgefragt werden könnte.

was will mir der adapter damit sagen

Geräte bleiben offline

Admin 5
Node-js 16.40
Controler 4.0.23
Shelly Geräte werden seit 12h als Offline gemeldet, obwohl sie erreichbar sind.
Nicht erreichbar waren sie tatsächlich, aber nur eine kurze zeit nicht.

Exception on instance start

Describe the bug
Device Watcher does not start, due to an exception. See log. Fully deterministic.

To Reproduce
Directly on instance start.

Screenshots & Logfiles

host.mediapc	2022-11-06 13:08:32.260	error	instance system.adapter.device-watcher.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
device-watcher.0	2022-11-06 13:08:31.696	error	Cannot read properties of undefined (reading 'captureException')
device-watcher.0	2022-11-06 13:08:31.696	error	TypeError: Cannot read properties of undefined (reading 'captureException') at DeviceWatcher.errorReporting (/opt/iobroker/node_modules/iobroker.device-watcher/main.js:1823:38) at DeviceWatcher.onReady (/opt/iobroker/node_modules/iobroker.device-watcher/main.js:207:9)
device-watcher.0	2022-11-06 13:08:31.695	error	unhandled promise rejection: Cannot read properties of undefined (reading 'captureException')
device-watcher.0	2022-11-06 13:08:31.695	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

Versions:

Adapter version: 2.0.1
JS-Controller version: 4.0.23
Node version: 16.18.1
Operating system: Ubuntu 22.04

Zigbee Devices zeigen keine Signalstärke mehr an

Hallo,

ich bekomme die "Signalstärke" der zigbee Devices nicht mehr Angezeigt. Ich habe den Adapter, sowohl Stable als auch aktuell von github getestet.

Ich habe auch den adapter gestoppt und die Objekte gelöscht und neu anlegen lassen, Signalstärke fehlt bei den zigbee's.

Beispiel, anhand eines zigbee Tasters:

Am Beispiel aus der Liste "zigbee.listAll":

{"Device":"DG_Schlafzimmer [Remote]","Adapter":"Zigbee","Battery":"100%","Signal strength":" - ","Last contact":"06:39 Uhr","Status":"Online"}

Gesamte Liste der zigbee devices.
zigbee.listAll.zip

VG
Bernd

[JsonConfig] Cannot read file: Not exists

Fresh installed, this screen is everything I could see. Admin etc. @ latest. Already tried other browser and reinstallation... No changes at all.

Log (debug) is clean:

device-watcher.0	2022-12-24 21:16:42.059	warn	No adapter selected. Please check the instance configuration!
device-watcher.0	2022-12-24 21:16:42.058	debug	Adapter device-watcher was started
device-watcher.0	2022-12-24 21:16:42.049	info	starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.device-watcher, node: v14.16.0, js-controller: 4.0.23
device-watcher.0	2022-12-24 21:16:41.927	debug	Plugin sentry Initialize Plugin (enabled=true)

Feature: own structured devices

Describe the solution you'd like
Could you implement something that one can use e.g. also own devices / structures. So for example I have a few mqtt devices that I would like to monitor with the adapter.
My idea would be that you can e.g. create your own structures via the adapter config per json:

	meineStruktur: {
		Selektor: 'meineStruktur.*.rssi',
		adapterID: 'meineStruktur',
		adapter: 'meineStruktur',
		battery: '.battery',
		rssiState: '.rssi',
		reach: 'none',
		isLowBat: 'none',
	}

Add HM-RPC CuxD Devices

Describe the bug
CuxD Devices are not found.

Additional context
LaCrosse Temperatur/Feuchte-Sensoren, welche über Cuxd an die CCU2 angebunden sind, werden nicht erkannt. [...]
Der RSS_PEER Wert ist bei allen Sensoren auf 0, bringt also nichts, den zu verwenden. Aber die Batterieüberwachung

Please support HomeConnect

Which adapter should be implement:
iobroker.homeconnect
https://github.com/iobroker-community-adapters/ioBroker.homeconnect

The following information is important to add the adapter correctly, if possible add a json or screenshot with the information:
Every HomeConnect device has a connected state, e.g.
homeconnect.0.SIEMENS-SX758X06TE-68A40E117A96.general.connected
homeconnect.0.SIEMENS-TI9575X9FU-68A40E57624D.general.connected
None of the other states (update, battery,...) are available.

Thanx in advance

Adapter meldet trotz deinstallation weiter states über telegram

Describe the bug
Ich hatte den 0.3.0 adapter installiert, da ein sonoff gerät sich gern mal abmeldet nervten die nachrichten etwas. also instanz deaktiviert, nachrichten kamen weiter, instanz und adapter gelöscht, iob neustart und nachrichten kommen immer noch.
die version 1.0.0 installiert, alles abgewählt und neu gestartet aber die nachrichten kommen weiterthin. wie bekomme ich das wieder in den griff?
das man bei dem update auf 1.0.0 den vorhergehenden vorher löschen muss hab ich leider zu spät gelesen

Erweiterung Doku Syntax Grafana für Influx2/ Flux

Influx2 hat die neue Sprache Flux.
Daraus ergibt sich folgende neue Syntax

Query
`from(bucket: "iobroker")

|> range(start: v.timeRangeStart, stop: v.timeRangeStop)
|> filter(fn: (r) => r["_measurement"] == "device-watcher.0.listAll")
|> filter(fn: (r) => r["_field"] == "value")`

3 Transformations (siehe Attachment)

Lupusec: offlineList bzw. -count

Zunächst mal: Vielen Dank für die schnelle Implementierung des Lupusec-Adapters.
Ich frage mich allerdings, wie die Liste offlineList zustande kommt.

Meine Geräte sind alle online und eine Möglichkeit an "last contact" heranzukommen kann ich in den Objektdaten gar nicht erkennen.
Ich denke nicht, dass man dafür den Wert "ts" an den Datenpunkten heranziehen kann. Der dürfte lediglich den Zeitpunkt der letzten Änderung darstellen. Wenn ein Gerät aber z.B. seit Monaten fehlerfrei läuft, wird sich dieser Wert kaum ändern.

Der Wert "cond_ok" kann Werte von 0 (Fehler) und 1 (OK) annehmen.

Gruß
Bernd

Add Synology Chat to notification service

Describe the solution you'd like
For the notification of offline or battery problems, you can choose which service you would like to be informed about, I would like to have the additional option Synochat, because I don't use Telegram or WhatsApp,

Additional context
https://github.com/phoeluga/ioBroker.synochat

with kind regards
Bernd

Laut Log werden Geräte nur als "undefined" angezeigt.

Laut Log werden Geräte nur als "undefined" angezeigt.
Dementsprechend helfen die Pushnachrichten auch nicht sooo viel. ;)
Sieht man auch im Log:

Im Datenpunkt werden die Geräte aber korrekt angezeigt:

[{"Device":"Küche","Adapter":"Zigbee","Last_contact":"45 Stunden"}]

Originally posted by @firebowl in https://github.com/ciddi89/ioBroker_device_watchdog/issues/2

Boolean Status

I use the adapter to display various information in my visualization.

For the topics lowBattery, offline and upgradable I would like to have another Boolean data point. This should show true if a device appears in the list.

device-watcher Displays information where it shouldn't be

Describe the bug
I have the following configuration at my test environment,
As shown, I activate Zwave but without using or have Zwave Adapter installed, but I get 3 objects shown as zwave devices.

Screenshots & Logfiles
Adapter configuration:

And I get this objects at device-watcher.0

The shown devices are from zigbee2mqqt, see .json below

[{"Device":"","Adapter":"Zigbee2MQTT","Battery":"100%","Status":"Online"},{"Device":"","Adapter":"Zigbee2MQTT","Battery":"100%","Status":"Online"},{"Device":"BWM","Adapter":"Zigbee2MQTT","Battery":"74%","Status":"Offline"}]

Versions:

Adapter version: 2.2.1
JS-Controller version: 4.0.24
Node version: v18.12.1
Operating system: arch-linux

Additional context
I did the test also with my productive system, I have only the zigbee Adapter installed, but also activate at device-watcher the zigbee2mqtt and zigbee2mqtt shows the same information as zigbee

Direct link to device

Describe the solution you'd like
Currently I use my own scripts which do kind of what this adapter is doing. Maybe I'll switch to the adapter to clean up things a bit.
But this adapter needs to have a list where you can directly click on a link which goes directly to the device.
See this example:

The link points to http://zigbee2mqtt:8080/?#/device/0x842e14fffe01d883/info for example
Should also be possible for shelly devices with web interface and maybe other devices.

MQTT Nuki find only devices for instance 0

Describe the bug
MQTT Nuki find only devices for instance 0

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '...'
Scroll down to '....'
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.

Sonoff-Tasmota-Geräte unter Sonoff Adapter in Quality Liste?

Version 1.1

Bug? keine Sonoff-Tasmota-Geräte tauchen in der Quality Liste auf!

Ich weiß nicht ob das ein Bug ist , aber sollten bei Anwahl von Sonoff in der Quality Liste nicht alle Tasmota Geräte auftauchen
mit der Anzeige der Wlan Qualität ... oder habe ich da was falsch verstanden?

Bei der Offline-Liste tauchen die Sonoff-Tasmota-Geräte mit auf!

Gruß Klaus

add support for nuki-extended adapter devices

Hi,

probably it's possible to add nuki-extended adapter. There are different things that can be connected to the nuki bridge and I have two of them.

One of the devices has just the batteryCritical State and one has batter berrtyChargeState with the percentage.

warn, error: [[createDataOfAllAdapter]] error: Cannot read properties of undefined (reading 'de')

iobroker Update device-watcher from @1.1.0 to @2.0.1
seit dem Update habe ich kontinuierlich diese Meldung
`

warn	Error catched and sent to Sentry, error: [[createDataOfAllAdapter]] error: Cannot read properties of undefined (reading 'de')

Lupusec Adapter Integration wäre super

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Enocean

Wäre es auch möglich enocean mit aufzunehmen damit er die Sensoren auch überwacht?

Tradfri + HmIP

Bitte den Tradfri-Netzwerk-Gateway und HmIP (AP) adaptieren :-)

Max! Cube Adapter hinzufügen

Hallo,

könntest Du den Max! Cube Adapter integrieren?
Das sind in meinem Fall eq-3 Heizkörperthermostate und ein Fensterkontakt.

Please add the jeelink adapter.

Is your feature request related to a problem? Please describe.
Please add the jeelink adapter.

Describe the solution you'd like
All data points are re-set approximately every 10 seconds, yes really that often!

Additional context

{
  "type": "state",
  "common": {
    "name": "Battery Low",
    "type": "boolean",
    "role": "indicator.lowbat"
  },
  "native": {},
  "from": "system.adapter.jeelink.0",
  "user": "system.user.admin",
  "ts": 1638137687685,
  "_id": "jeelink.0.LaCrosse_TR_Sensor_TempHum.lowBatt",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  }
}

Eufy Homebase Support

Would be great if also the cameras from Eufy could be added
All values are added with the adapter eusec

WLED

WLED als 'Supported adapter' wäre auch cool :)

Add sorting for device selection in the blacklist

Is your feature request related to a problem? Please describe.
da_Woody can't find his device fast enough

Describe the solution you'd like
A sorted list of all devices in the dropdown menu of the blacklist

Zigbee TuYa Thermostat has only batterLow indicator

Is your feature request related to a problem? Please describe.
The TuYa TS0601_thermostat (Zigbee) does not output the battery state in % or volt but only batterLow indicator.
More Information

Describe the solution you'd like
Solution like Zwave or Homematic

Additional context

{
  "type": "state",
  "common": {
    "name": "Battery Status Low",
    "type": "boolean",
    "read": true,
    "write": false,
    "role": "indicator.lowbat",
    "custom": {
      "influxdb.0": {
        "enabled": true,
        "storageType": "",
        "aliasId": "",
        "changesOnly": true,
        "debounce": 0,
        "changesRelogInterval": 60,
        "changesMinDelta": 0,
        "retention": "63072000",
        "maxLength": 10
      }
    }
  },
  "native": {},
  "_id": "zigbee.0.847127fffe11df7a.battery_low",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  },
  "from": "system.adapter.admin.0",
  "user": "system.user.admin",
  "ts": 1630530366536
}

Tasmota Ethrnet Device taucht nicht auf

Describe the bug
Tasmota Ethernet Device Olimex ESP32-POE-ISO wird nicht gelistet. Das Wifi am Device ist halt deaktiviert weil er am LAN hängt

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '...'
Scroll down to '....'
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: 0.0.8
JS-Controller version: 4.0.23
Node version: 14.14.0
Operating system: Ubuntu 19.04

Additional context
Add any other context about the problem here.