[Projekt] ioGo # Smarthome to go

NightWatcher

@nis yes, in der Tat. Mit der beta 11 werden nun die Einheiten angezeigt. Danke dir, gute Arbeit. 🙂

e-s

@e-s sagte in [Projekt] ioGo # Native Android App:

@nis
Hallo, Gibt es bei den letzten beiden betas irgendwas was genau getestet werden muss oder sollte?

Mir ist noch ein kleiner Fehler aufgefallen, unter instances werden schlecht deinstallierte Adapter noch angezeigt. Also in meinem Fall hatte ich eine Zeit owntracks getestet und später deinstalliert. Dieser taucht auch unter Adapter nicht auf. Unter instances schon. Klickt man dort dann owntracks an, Wird die app unsanft geschlossen.
Werde heute Abend ein issue erstellen.

In beta11 crasht die app nicht mehr. Trotzdem ist owntracks unter instances online, Aber unter Adapter nicht zu finden. Was auch unter Adapter richtig ist, Da er deinstalliert wurde.
Wenn ich jetzt auf instances owntracks gehe, steht da bei den Werten 0 und stop ist auswählbar, passieren tut aber nichts wenn ich drauf klicke.
Ob man sich jetzt die Mühe macht, den Fehler des falschen Anzeigens nach geht oder man gar eine löschfunktion in der app anbietet, Kann ich dir auch nicht sagen.

? Offline

@e-s Du kannst die Instanz einfach löschen. Geh dazu in den Tanzreiter Objekte und aktiviere die Experten Ansicht. Dann kannst du nach "instance" filtern und die kaputten Objekte löschen

e-s

@nis
Das war mir schon klar. Wollte ich aber erst machen wenn die app deswegen nicht mehr crasht.
Deswegen war nur kurz mein gedankenspiel, inwiefern es weiter von der app beachtet werden sollte. Dazu fallen mir 4 Möglichkeiten ein.

Alles bleibt so wie es jetzt ist, der Anwender kann sich überlegen was er macht.
Die app zeigt kaputte Instanzen erst gar nicht an.
Die app weißt den Anwender auf die kaputten Instanzen hin.
Die app bietet die Möglichkeit an, Diese fehlerhaften Einträge zu beseitigen.

? Offline

Bei solchen Themen verfolge bisher den Ansatz:

Die App soll nicht abstürzen
Die App korrigiert keine fehlerhaften Objekte automatisch/manuell (das sind einfach zu viele verschieden mögliche Fehlerquellen)

@e-s sagte in [Projekt] ioGo # Native Android App:

@nis
Das war mir schon klar. Wollte ich aber erst machen wenn die app deswegen nicht mehr crasht.
Deswegen war nur kurz mein gedankenspiel, inwiefern es weiter von der app beachtet werden sollte. Dazu fallen mir 4 Möglichkeiten ein.

Alles bleibt so wie es jetzt ist, der Anwender kann sich überlegen was er macht.

Nein, die App soll nicht abstürzen

Die app zeigt kaputte Instanzen erst gar nicht an.

Ja, das könnte der iogo-adapter übernehmen

Die app weißt den Anwender auf die kaputten Instanzen hin.

Ja, das könnte man ins Log des iogo-adapters packen

Die app bietet die Möglichkeit an, Diese fehlerhaften Einträge zu beseitigen.

Nein, das wird nicht machbar sein

Kannst du mal bitte Screenshot von den Instanzen im Tabreiter Objekte und das RAW eines der Objekte posten.

e-s

@nis
Mache ich heute Abend. Zu 1. Die app stürzt jetzt nicht mehr ab. Also der fehler ist zumindest behoben. Ich meinte nur, das man eben nur derzeit fehlerhafte Instanzen sehen kann, diese werden aber weder ignoriert oder als fehlerhaft angezeigt. Was m. E. So auch OK ist, Da es andere Probleme gibt, die wichtiger sind.

? Offline

@MGK sagte in [Projekt] ioGo # Native Android App:

@nis
Die gelöschten Funktionen werden aber immer noch angezeigt.

Es gibt eine Verbesserung in Version 0.4.5 des Adapters, dieser macht nun einen kompletten Abgleich beim Start und löscht Objekte remote die es lokal nicht mehr gibt.

johni

ich weiß nicht ob schon geklärt oder gefragt wurde... ist es möglich einen kamera stream einzubinden? rtsp oder http?

? Offline

@johni hat noch keiner gefragt, gerne mit Beschreibung einen issue in github aufmachen, oder einen neuen Thread für das Thema eröffnen

crunchip

@nis gerade beta 12 geladen
sieht soweit gut aus, was mir jetzt noch aufgefallen ist, das zwar die Favoriten erhalten bleiben, aber wenn ich mir den Zeitstempel anseh, ist dieser von gestern bzw vorgestern.
in meinem Fall lass ich mir Räume mit eingeschalteten Lichtern, offene Fenster und Türen anzeigen. Dementsprechend wird auch nicht der Aktuelle Status angezeigt.

e-s

@crunchip
Also ich habe bei mir ein paar Zählerstände, Türen, Licht usw drin, und lastchange als Untertitel. Funktioniert bei mir schon immer ohne Probleme.
Nimm als Rolle mal sensor.door, Dann wird auch offen und geschlossen angezeigt.

crunchip

@e-s hab es per web und per adapter sync. bei beiden das gleiche.
Ja es aktualisiert ja auch alle schalter, states, etc.
nur eben diese drei nicht.

crunchip

@e-s das mit der rolle, hatte ich schon drin, ist nach dem Update wieder verschwunden

e-s

@crunchip
Wenn da die Anzahl der Türen nicht angezeigt wird, Dann wird glaube ich es nur helfen wenn du die raw der States mal zeigst. Da wird irgendwas nicht passen. Stimmen denn die Zeitstempel wenn du unter Objekte schaust.

crunchip

@e-s zeitstempel 18.20 passt, letzte Änderung 16.07 Fenster geöffnet, passt

{
  "common": {
    "type": "string",
    "name": "Räume mit offenen Fenster",
    "desc": "Namen der Räume, in denen Fenster offen sind",
    "def": " ",
    "role": "value",
    "custom": {
      "iot.0": {
        "smartName": false
      }
    }
  },
  "native": {},
  "type": "state",
  "from": "system.adapter.javascript.0",
  "ts": 1548092547514,
  "_id": "javascript.0.Status.Fenster.Raum",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  },
  "user": "system.user.admin"
}

crunchip

hat das so seine Richtigkeit? Ich weiss, sind zwar nur Warnungen, kommt mir trotzdem ein wenig komisch vor.

$ ./iobroker upgrade iogo
Update iogo from @0.4.4 to @0.4.5
NPM version: 6.9.0
npm install iobroker.iogo@0.4.5 --production --save --prefix "/opt/iobroker" (System call)
npm WARN
 @typescript-eslint/eslint-plugin@1.12.0 requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.npm WARN @typescript-eslint/parser@1.12.0 requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.

npm WARN
 optional
 SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})


npm install --production (System call) in "/opt/iobroker/node_modules/iobroker.iogo"
npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm 
WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN
 tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, writenpm
 WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN
 tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm
 WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm
 WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar
 ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN
 tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN 
tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN
 tar ENOSPC: no space left on device, write
npm ERR! cb() never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://npm.community>

got /opt/iobroker/node_modules/iobroker.iogo/admin
upload [3] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/words.js words.js application/javascript
Update "system.adapter.iogo.0"
upload [2] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/iogo.png iogo.png image/png
upload [1] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/index_m.html index_m.html text/html
upload [0] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/index.html index.html text/html
Adapter "iogo" updated
process exited with code 0

? Offline

@crunchip sieht irgenwie aus wie Dateisystem kaputt oder Voll. Aber das ist absolut nicht mein Fachgebiet :-(

crunchip

@nis hmm, naja mal sehn, läuft ja ohne Fehlermeldung

crunchip

@crunchip @nis nach langem suchen und keinen Fehler gefunden, hab ich den Adapter neu gestartet, bzw die neue version 0.4.5 drauf.
Meine drei state´s werden jetzt wieder aktualisiert, sind jedoch aus den Favoriten am Handy wieder verschwunden.

hast du ne Idee was da noch falsch ist bei mir

iogo.0	2019-09-13 20:35:58.255	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"71"}
iogo.0	2019-09-13 20:35:58.249	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"71"}
iogo.0	2019-09-13 20:35:58.245	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"71"}
iogo.0	2019-09-13 20:35:58.234	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"71"}
iogo.0	2019-09-13 20:35:48.074	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"71"}
iogo.0	2019-09-13 20:35:48.071	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"71"}
iogo.0	2019-09-13 20:35:48.068	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"71"}
iogo.0	2019-09-13 20:35:48.057	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"71"}
iogo.0	2019-09-13 20:35:37.851	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:37.849	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:37.847	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:37.828	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:27.650	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:27.647	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:27.642	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:27.627	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:17.410	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:17.408	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:17.404	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:17.392	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:07.209	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:07.206	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:07.200	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:35:07.189	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:57.034	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:57.031	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:57.028	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:57.021	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:46.894	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:46.891	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:46.882	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:46.865	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:36.693	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:36.691	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:36.689	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:36.678	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:26.505	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:26.503	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:26.499	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:26.485	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"70"}
iogo.0	2019-09-13 20:34:16.325	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:34:16.318	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:34:16.316	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:34:16.304	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:34:06.141	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:34:06.139	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:34:06.133	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:34:06.119	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:55.949	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:55.946	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:55.936	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:55.922	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:45.760	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:45.757	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:45.754	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:45.744	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:35.579	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:35.577	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:35.574	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:35.564	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:28.451	info	Object iogo.0.f4Oce5GiBFM.token created
iogo.0	2019-09-13 20:33:28.449	info	Object iogo.0.f4Oce5GiBFM.token created
iogo.0	2019-09-13 20:33:28.449	info	Object iogo.0.f4Oce5GiBFM.token created
iogo.0	2019-09-13 20:33:28.448	info	Object iogo.0.f4Oce5GiBFM.token created
iogo.0	2019-09-13 20:33:28.441	warn	setObject iogo.0.f4Oce5GiBFM.token (type=state) property native missing!
iogo.0	2019-09-13 20:33:28.422	warn	setObject iogo.0.f4Oce5GiBFM.token (type=state) property native missing!
iogo.0	2019-09-13 20:33:28.417	warn	setObject iogo.0.f4Oce5GiBFM.token (type=state) property native missing!
iogo.0	2019-09-13 20:33:28.409	warn	setObject iogo.0.f4Oce5GiBFM.token (type=state) property native missing!
iogo.0	2019-09-13 20:33:25.397	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:25.394	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:25.389	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:25.379	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:15.211	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:15.208	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:15.205	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:15.195	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:05.626	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:05.624	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:05.621	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
iogo.0	2019-09-13 20:33:05.603	info	state update received: {"ack":false,"id":"iogo.0.f4Oce5GiBFM.akku","lc":0,"q":0,"ts":0,"val":"69"}
socketio.0	2019-09-13 20:33:05.469	info	==>Connected system.user.admin from ::ffff:192.168.178.111

e-s

@nis
auf beta12 und 0.4.5 sind alle instances Probleme bei mir weg. Dabei ist zwar die Startseite wieder leer, aber dafür sind die Anzahl von States, instances und Adapter scheinbar alle jetzt richtig, waren vorher alle viel zu viel.

Community Forum

NEWS

[Projekt] ioGo # Smarthome to go

Support us

565

32.6k

82.3k

1.3m