@copystring Danke für die Info. Und an dieser Stelle auch mal vielen Dank für deine Arbeit. Echt top was du da in sehr kurzer Zeit hinbekommen hast
NEWS
Best posts made by M-A Hueb
-
RE: Roborock Adapter tester gesucht
-
RE: [Tutorial] VIS Fritzbox Status & Up/Downloadanzeige
Hallo,
habe jetzt über diesen Thread drübergelesen und ahbe das ganze auch mit einer 6591 am laufen. Was immer noch auftritt ist, dass wenn die 4GB grenze beim Up/Download erreicht wird springt der wert auf 0 zurück. Gibt es hierfür eine Lösung?
-
RE: Roborock Adapter tester gesucht
@copystring vielen Dank für deine Mühe. Du hast in echt kurzer Zeit ein super Ergebnis erzielt
-
RE: TTS mit HomePod
@wildbill Dank dir. Hatte es auf steuere. das problem lies sich durch einen Reboot beheben
-
RE: Test ioBroker unter Windows installieren - 2022 Edition
@jb_sullivan Also bei mir braucht das einfach kurz bis iobroker stop durch ist:
-
RE: Roborock Adapter tester gesucht
@copystring Hindernisserkennung passt bei mir.
Zonenerstellung auf Touch geräten tut auch -
RE: HowTo: Zusatz-Programme fuer jarvis v3
@mcu Ich danke dir für deine Geduld. in einem privaten Fenster funktioniert es. ich leere jetzt mal alle Caches. Vielen Dank
Und so wie du es gemacht hast passt es
-
RE: Test Adapter sureflap v1.0.x GitHub
Guten Morgen,
seit gestern Mittag 15:51 Uhr funktioniert der Adaptert nicht mehr.
Adapter steht auf Logstufe Debug. Das steht im Log. Logindaten habe ich verifiziert. Das passt, es werden die Katzen aufgelistet.
Wenn man in die Sureflap-App schaut passt alles.
An was kann das liegen?
Latest posts made by M-A Hueb
-
RE: Test ioBroker unter Windows installieren - 2023 Edition
@mcm57 Das Problem hier war VOR dem Problem das sich die Adapter nicht installieren liesen. Beide Themen mittlerweile behoben, da ich ja iobroker neu installiert habe und die Daten aus der alten Installation migriert habe.
Du warst nur schneller wie ich. Wollte gerade hier auch erledigt schreiben. -
RE: Unable to verify the first certificate
Hat sich erledigt.
Es lag am Virenscanner. der hat die Zertifikatskette zerschossen -
RE: Unable to verify the first certificate
@mcm57 meine Versionen sind in meiner Signatur. Admin 6.13.16.
iob diag gibt unter windows das hier zurück:C:\ioBroker>iob diag iobroker [command] Commands: iobroker setup Setup ioBroker iobroker start [all|<adapter>.<instance>|<adapter>] Starts the js-controller or a specified adapter instance or all instances of an adapter iobroker stop [<adapter>.<instance>|<adapter>] stops the js-controller or a specified adapter instance or all instances of an adapter iobroker restart [<adapter>.<instance>|<adapter>] Restarts js-controller or a specified adapter instance or all instances of an adapter [aliases: r] iobroker debug <adapter>[.<instance>] Starts a Node.js debugging session for the adapter instance iobroker info Shows the host info iobroker logs [<adapter>] Monitor log iobroker add <adapter> [desiredNumber] Add instance of adapter [aliases: a] iobroker install <adapter> Installs a specified adapter [aliases: i] iobroker rebuild [<module>] Rebuild all native modules or path iobroker url <url> [<name>] Install adapter from specified url, e.g. GitHub iobroker del <adapter> Remove adapter and all instances from this host [aliases: delete] iobroker del <adapter>.<instance> Remove adapter instance [aliases: delete] iobroker update [<repositoryUrl>] Update repository and list adapters iobroker upgrade Upgrade management iobroker upload [all|<adapter>] Upload management [aliases: u] iobroker object Object management [aliases: o] iobroker state State management [aliases: s] iobroker message <adapter>[.instance] <command> [<message>] Send message to adapter instance/s iobroker list <type> [<filter>] List all entries, like objects iobroker chmod <mode> <file> Change file rights iobroker chown <user> <group> <file> Change file ownership iobroker touch <file> Touch file iobroker rm <file> Remove file iobroker file File management iobroker user User commands iobroker group group management iobroker host <hostname> Set host to given hostname iobroker set <adapter>.<instance> Change settings of adapter config iobroker license <license.file or license.text> Update license by given file iobroker cert Certificate management iobroker clean <yes> Clears all objects and states iobroker backup Create backup iobroker restore <backup name or path> Restore a specified backup iobroker validate <backup name or path> Validate a specified backup iobroker status [all|<adapter>.<instance>] Status of ioBroker or adapter instance [aliases: isrun] iobroker repo [<name>] Show repo information iobroker uuid Show uuid of the installation [aliases: id] iobroker unsetup Reset license, installation secret and language iobroker fix Execute the installation fixer script, this updates your ioBroker installation iobroker nodejs-update [<major-version>] Upgrade the Node.JS installation to the current LTS iobroker multihost Multihost management iobroker compact compact group management iobroker plugin Plugin management iobroker vendor <passphrase> [<vendor.json>] Update the vendor information using given passphrase iobroker version [<adapter>] Show version of js-controller or specified adapter [aliases: v] Options: --help Show help [boolean]
-
RE: Unable to verify the first certificate
Angefangen hat das ganze am 17.04 19:37Uhr
17 Apr 2024 19:39:24.911 bring.0: Error polling all lists: Cannot get lists: Error: unable to verify the first certificate 17 Apr 2024 19:39:14.292 midea.0: Error: unable to verify the first certificate 17 Apr 2024 19:39:14.244 midea.0: Error: unable to verify the first certificate 17 Apr 2024 19:39:14.243 midea.0: Error: unable to verify the first certificate 17 Apr 2024 19:39:01.078 solaredge.0: Cannot read data from solaredge cloud: Error: unable to verify the first certificate 17 Apr 2024 19:38:59.963 sureflap.0: Error: Request error: 'Error: unable to verify the first certificate'. Retrying in 60 seconds 17 Apr 2024 19:38:18.678 nuki-extended.0: getWebApi(): Error retrieving smartlocks: Error: unable to verify the first certificate 17 Apr 2024 19:38:18.678 nuki-extended.0: getWebApi(): Error retrieving notifications: Error: unable to verify the first certificate 17 Apr 2024 19:38:15.008 midea.0: Error: unable to verify the first certificate 17 Apr 2024 19:38:14.964 midea.0: Error: unable to verify the first certificate 17 Apr 2024 19:38:14.964 midea.0: Error: unable to verify the first certificate 17 Apr 2024 19:38:01.119 solaredge.0: Cannot read data from solaredge cloud: Error: unable to verify the first certificate 17 Apr 2024 19:37:59.610 sureflap.0: Error: Request error: 'Error: unable to verify the first certificate'. Retrying in 60 seconds
-
RE: Unable to verify the first certificate
@homoran
habe mittlerweile iobroker testehalber neu installiert.
Beim Versuch die Adapter nachzuziehen kommen diese Meldungenadmin.0 2024-04-18 13:00:33.803 warn Cannot update news: unable to verify the first certificate admin.0 2024-04-18 13:00:32.747 warn Cannot update rating: unable to verify the first certificate admin.0 2024-04-18 13:00:32.643 warn Cannot check node.js versions: Error: unable to verify the first certificate admin.0 2024-04-18 13:00:32.580 warn Active repository "stable" cannot be read admin.0 2024-04-18 13:00:32.580 warn Repository cannot be read: Active repo - stable admin.0 2024-04-18 13:00:32.568 info Use link "http://127.0.0.1:8081" to configure. admin.0 2024-04-18 13:00:32.567 info http server listening on port 8081 admin.0 2024-04-18 13:00:32.566 info socket.io server listening on port 8081 admin.0 2024-04-18 13:00:32.535 info received all objects admin.0 2024-04-18 13:00:32.489 info requesting all objects admin.0 2024-04-18 13:00:32.475 info starting. Version 6.13.16 in C:/ioBroker/node_modules/iobroker.admin, node: v18.20.2, js-controller: 5.0.19 host.Server 2024-04-18 13:00:31.455 info instance system.adapter.admin.0 started with pid 14264 host.Server 2024-04-18 13:00:31.410 info starting 3 instances host.Server 2024-04-18 13:00:31.408 info 3 instances found host.Server 2024-04-18 13:00:31.223 info added notifications configuration of host host.Server 2024-04-18 13:00:31.215 info Node.js version has changed from unknown to 18.20.2 host.Server 2024-04-18 13:00:31.209 info connected to Objects and States host.Server 2024-04-18 13:00:31.087 info ip addresses: 192.168.1.1 fe80::2c0e:4633:31a7:9837 192.168.176.1 fe80::4973:a07e:3bf7:ada3 192.168.44.1 host.Server 2024-04-18 13:00:31.087 info hostname: Server, node: v18.20.2 host.Server 2024-04-18 13:00:31.087 info Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker host.Server 2024-04-18 13:00:31.085 info iobroker.js-controller version 5.0.19 js-controller starting
-
Unable to verify the first certificate
Hallo,
seit heute morgen wird mein Log mit Meldungen zugemüllt:
unable to verify the first certificate
Adapter lassen sich auch nicht mehr updaten.
Wie lässt sich das abstellen? -
RE: Test ioBroker unter Windows installieren - 2023 Edition
Nach dem Update mit dem iobroker.installer3.0.1 startet mein iobroker nicht mehr. er meldet das was beim Fixer fehlgeschlagen ist.
Logs anbei
installNodeJs.log installIoBrokerFix.log
Was läuft hier falsch?
Wenn ich manuell über die CMD starten will komtm Systemfehler 1067
Was kann ich machen? -
RE: [Tutorial] SolarEdge -> Modbus -> ioBroker -> Grafana
Ich nutze auch die Anleitung.
Mit dem hausverbrauch habe ich Allerdings ein Problem.
Und zwar ist es so, mit steigender PV-Leistung auch mein Hausverbrauch steigt.
Vorhanden ist ein Solaredege WR SE7K + BYD Batterie, sowie 1 kleine Balkonanlage die über FritzDect ausgewertet wird.
So sieht mein Blockly aus.
ACTUAL ist der aktuelle Wert meines Stromzählers.
AC Leistungswert und Total Real Power sind die Daten vom WR mit Modbus ausgelesen und mit SF verrechnet.
Power ist der Wert von dem Fritzstecker.
Wo liegt meine Fehler?und noch ne 2te Frage:
Habt ihr über Modbus auch manchmal so harte Peaks drin?
Das habe ich seit dem letzten Firmware-Update des Solaredge-WR
-
RE: Neuer Adapter für Roborock-Staubsauger
Hallo,
der Adapter in Version 0.4.4 lief bei mir bisher gut. Seit kurzem kommen immer diese Meldungen:roborock.0 2024-01-10 08:59:11.402 warn MQTT connection close. roborock.0 2024-01-10 08:59:11.401 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:59:11.318 warn MQTT connection reconnect. roborock.0 2024-01-10 08:59:10.308 warn MQTT connection close. roborock.0 2024-01-10 08:59:10.307 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:59:10.213 warn MQTT connection reconnect. roborock.0 2024-01-10 08:59:09.202 warn MQTT connection close. roborock.0 2024-01-10 08:59:09.201 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:59:09.116 warn MQTT connection reconnect. roborock.0 2024-01-10 08:59:08.114 warn MQTT connection close. roborock.0 2024-01-10 08:59:08.114 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:59:08.023 warn MQTT connection reconnect. roborock.0 2024-01-10 08:59:07.015 warn MQTT connection close. roborock.0 2024-01-10 08:59:07.014 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:59:06.928 warn MQTT connection reconnect. roborock.0 2024-01-10 08:59:05.926 warn MQTT connection close. roborock.0 2024-01-10 08:59:05.925 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:59:05.831 warn MQTT connection reconnect. roborock.0 2024-01-10 08:59:04.815 warn MQTT connection close. roborock.0 2024-01-10 08:59:04.814 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:59:04.723 warn MQTT connection reconnect. roborock.0 2024-01-10 08:59:03.717 warn MQTT connection close. roborock.0 2024-01-10 08:59:03.717 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:59:03.624 warn MQTT connection reconnect. roborock.0 2024-01-10 08:59:02.612 warn MQTT connection close. roborock.0 2024-01-10 08:59:02.611 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:59:02.526 warn MQTT connection reconnect. roborock.0 2024-01-10 08:59:02.236 warn Failed to execute get_water_box_custom_mode on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 1492 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:59:02.236 warn Failed to execute get_carpet_clean_mode on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 3508 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:59:02.235 warn Failed to execute get_carpet_mode on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 6269 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:59:02.235 warn Failed to execute get_timer on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 2650 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:59:02.235 warn Failed to execute get_server_timer on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 7166 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:59:02.235 warn Failed to execute get_network_info on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 5932 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:59:02.235 warn Failed to execute get_consumable on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 1395 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:59:02.235 warn Failed to execute get_room_mapping on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 4413 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:59:02.235 warn Failed to execute get_status on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 2318 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:59:01.524 warn MQTT connection close. roborock.0 2024-01-10 08:59:01.524 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:59:01.423 warn MQTT connection reconnect. roborock.0 2024-01-10 08:59:01.423 warn MQTT connection reconnect. roborock.0 2024-01-10 08:59:00.417 warn MQTT connection close. roborock.0 2024-01-10 08:59:00.417 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:59:00.287 warn MQTT connection reconnect. roborock.0 2024-01-10 08:58:59.284 warn MQTT connection close. roborock.0 2024-01-10 08:58:59.284 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:58:59.196 warn MQTT connection reconnect. roborock.0 2024-01-10 08:58:58.191 warn MQTT connection close. roborock.0 2024-01-10 08:58:58.190 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:58:58.103 warn MQTT connection reconnect. roborock.0 2024-01-10 08:58:57.100 warn MQTT connection close. roborock.0 2024-01-10 08:58:57.098 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:58:57.007 warn MQTT connection reconnect. roborock.0 2024-01-10 08:58:56.001 warn MQTT connection close. roborock.0 2024-01-10 08:58:56.000 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:58:55.911 warn MQTT connection reconnect. roborock.0 2024-01-10 08:58:54.900 warn MQTT connection close. roborock.0 2024-01-10 08:58:54.899 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:58:54.814 warn MQTT connection reconnect. roborock.0 2024-01-10 08:58:53.809 warn MQTT connection close. roborock.0 2024-01-10 08:58:53.807 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:58:53.716 warn MQTT connection reconnect. roborock.0 2024-01-10 08:58:52.712 warn MQTT connection close. roborock.0 2024-01-10 08:58:52.711 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:58:52.617 warn MQTT connection reconnect. roborock.0 2024-01-10 08:58:52.251 warn Failed to execute get_water_box_custom_mode on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 1528 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:58:52.216 warn Failed to execute get_carpet_clean_mode on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 7189 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:58:52.213 warn Failed to execute get_carpet_mode on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 4261 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:58:52.213 warn Failed to execute get_timer on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 8435 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:58:52.213 warn Failed to execute get_server_timer on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 6361 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:58:52.213 warn Failed to execute get_network_info on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 2819 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:58:52.213 warn Failed to execute get_consumable on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 1083 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:58:52.212 warn Failed to execute get_room_mapping on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 6224 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:58:52.208 warn Failed to execute get_status on robot 1j8J6Jlg0k7jyRe1SieBV5 Error: Request with id 5920 timed out after 10 seconds for response.102 roborock.0 2024-01-10 08:58:51.614 warn MQTT connection close. roborock.0 2024-01-10 08:58:51.613 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:58:51.529 warn MQTT connection reconnect. roborock.0 2024-01-10 08:58:50.516 warn MQTT connection close. roborock.0 2024-01-10 08:58:50.514 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized roborock.0 2024-01-10 08:58:50.429 warn MQTT connection reconnect. roborock.0 2024-01-10 08:58:49.422 warn MQTT connection close. roborock.0 2024-01-10 08:58:49.421 error MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized
-
RE: jarvis v3.1.x - just another remarkable vis
Hallo zusammen,
ich wünsche erstmal ein frohes neues Jahr.
Ich würde gerne in Jarvis meinen Pelletstand eingeben, da dieser bisher leider nicht via Modbus auslesbar ist.
Gibt es in Jarvis die Möglichkeit das InputAction Element so einzuschränken, dass man nur Zahlen eingeben kann?