Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. [Projekt] ioGo # Smarthome to go

    NEWS

    • ioBroker 10-Jahres Community Treffen - ein kleiner ReCap

    • Tester für Responsive Initiative gesucht

    • 50€: Mach mit bei einer Smarthome Studie mit ioBroker!

    [Projekt] ioGo # Smarthome to go

    This topic has been deleted. Only users with topic management privileges can see it.
    • ?
      A Former User @mpenno last edited by

      @mpenno du hast einen state vom type=number den wert "true" zugewiesen. Bei Verwendung des web Adapter musst du bei nach der Ursache suchen.

      Ich versuche zudem das logging für diesen Fall in Zukunft zu verbessern

      M 1 Reply Last reply Reply Quote 0
      • ?
        A Former User @crunchip last edited by

        @crunchip dann war wahrscheinlich noch ein command pending und wurde beim starten nachgearbeitet. Denke das ist nicht wirklich ein Fehler, da ein wechseln zwischen web und iogo eher unüblich ist. Oder sehe ich dies falsch?

        crunchip 1 Reply Last reply Reply Quote 0
        • crunchip
          crunchip Forum Testing Most Active @Guest last edited by

          @nis das ist der start, die warnings von allen state´s...nur ein auszug
          10a574ef-cdaf-469c-8a55-c0ac89a2add9-image.png
          das ist das ende, incl. das stoppen des Adapters

          2019-09-02 17:24:18.427 - warn: iogo.0 Value of state system.adapter.iogo.0.cputime has wrong type
2019-09-02 17:24:18.427 - warn: iogo.0 Value of state system.adapter.iogo.0.connected has wrong type
2019-09-02 17:24:18.427 - warn: iogo.0 Value of state system.adapter.iogo.0.alive has wrong type
2019-09-02 17:24:19.349 - info: iogo.0 database initialized with 805 states
2019-09-02 17:24:38.496 - info: host.IoBroker object change system.adapter.iogo.0
2019-09-02 17:24:38.501 - info: iogo.0 cleaned everything up...
2019-09-02 17:24:38.498 - info: host.IoBroker stopInstance system.adapter.iogo.0
2019-09-02 17:24:38.498 - info: host.IoBroker stopInstance system.adapter.iogo.0 killing pid 3096
2019-09-02 17:24:38.636 - error: Caught by controller[0]: (node:3096) UnhandledPromiseRejectionWarning: FirebaseError: 3 INVALID_ARGUMENT: maximum 500 writes allowed per request
2019-09-02 17:24:38.636 - error: Caught by controller[0]: at new FirestoreError (/opt/iobroker/node_modules/iobroker.iogo/node_modules/@firebase/firestore/dist/index.node.cjs.js:354:28)
2019-09-02 17:24:38.636 - error: Caught by controller[0]: at ClientDuplexStream. (/opt/iobroker/node_modules/iobroker.iogo/node_modules/@firebase/firestore/dist/index.node.cjs.js:22142:19)
2019-09-02 17:24:38.637 - error: Caught by controller[0]: at ClientDuplexStream.emit (events.js:198:13)
2019-09-02 17:24:38.637 - error: Caught by controller[0]: at ClientDuplexStream._emitStatusIfDone (/opt/iobroker/node_modules/iobroker.iogo/node_modules/grpc/src/client.js:234:12)
2019-09-02 17:24:38.637 - error: Caught by controller[0]: at ClientDuplexStream._receiveStatus (/opt/iobroker/node_modules/iobroker.iogo/node_modules/grpc/src/client.js:211:8)
2019-09-02 17:24:38.637 - error: Caught by controller[0]: at Object.onReceiveStatus (/opt/iobroker/node_modules/iobroker.iogo/node_modules/grpc/src/client_interceptors.js:1306:15)
2019-09-02 17:24:38.645 - error: Caught by controller[0]: at InterceptingListener._callNext (/opt/iobroker/node_modules/iobroker.iogo/node_modules/grpc/src/client_interceptors.js:568:42)
2019-09-02 17:24:38.647 - error: Caught by controller[0]: at InterceptingListener.onReceiveStatus (/opt/iobroker/node_modules/iobroker.iogo/node_modules/grpc/src/client_interceptors.js:618:8)
2019-09-02 17:24:38.647 - error: Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.iogo/node_modules/grpc/src/client_interceptors.js:1123:18
2019-09-02 17:24:38.647 - error: Caught by controller[0]: (node:3096) UnhandledPromiseRejectionWarning: 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(). (rejection id: 1)
2019-09-02 17:24:38.648 - error: Caught by controller[0]: (node:3096) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
2019-09-02 17:24:38.648 - info: host.IoBroker instance system.adapter.iogo.0 terminated with code 156 ()
          ? 3 Replies Last reply Reply Quote 0
          • crunchip
            crunchip Forum Testing Most Active @Guest last edited by crunchip

            @nis hmm möglich, hatte das Licht an und wieder ausgeschaltet...nach ca ner halben minute später, dann den Adapter erst gestartet...woher sollte dann der Befehl des wieder einschaltens kommen? Am Handy hatte ich ja noch gar nichts umgestellt.

            ? 1 Reply Last reply Reply Quote 0
            • ?
              A Former User @crunchip last edited by

              @crunchip perfekt, schau ich nachher Mal genau an

              1 Reply Last reply Reply Quote 0
              • N
                NightWatcher @Guest last edited by

                @nis klar, sehr gerne:

                modbus.0.holdingRegisters.13290_Temperatur_Sensor Büro.json

                ? 1 Reply Last reply Reply Quote 0
                • ?
                  A Former User @NightWatcher last edited by

                  @NightWatcher da ist ein Leerzeichen in der ID des States, das würde ich mal entfernen und sehen ob es dann klappt

                  N 1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User @crunchip last edited by

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

                    woher sollte dann der Befehl des wieder einschaltens kommen?

                    Die werden alle unterwegs gepuffert und dann nacheinander abgearbeitet. Die Zeitspanne ist relativ egal dabei.

                    1 Reply Last reply Reply Quote 0
                    • ?
                      A Former User @crunchip last edited by

                      @crunchip es gibt ein Limit von 500 Befehlen je Request in einer von mir genutzen Librarys. Mit deinen 850 States hast du das Limit locker gesprengt "iogo.0 database initialized with 805 states". Ich werde das umschreiben müssen, damit es auch für >500 States funktioniert...

                      crunchip 1 Reply Last reply Reply Quote 0
                      • ?
                        A Former User @crunchip last edited by

                        @crunchip probier mal bitte die aktuelle Version von GitHub und teste ob deine 800+ States in der App auftauchen

                        crunchip 1 Reply Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @Guest last edited by crunchip

                          @nis das hab ich auch gelesen, is eher die frage, warum so viele.

                          1. hab ich nichts geändert
                          2. sind das nur ein paar Lichtschalter, Steckdosen, Xiaomi Sensoren, Strom/Gas Werte und Spritkosten
                            sind da die state´s von der gesamten Iobroker Installation gemeint?
                          ? 1 Reply Last reply Reply Quote 0
                          • crunchip
                            crunchip Forum Testing Most Active @Guest last edited by

                            @nis das fehlt bei mir auch

                            {
  "_id": "sonoff.0.rasensprenger.AM2301_Temperature",
  "common": {
    "type": "number",
    "role": "value.temperature",
    "read": true,
    "write": false,
    "unit": "°C",
    "name": "rasensprenger AM2301  Temperature",
    "custom": {
      "iot.0": {
        "smartName": {
          "smartType": "THERMOSTAT"
        }
      }
    }
  },
  "native": {},
  "type": "state",
  "from": "system.adapter.sonoff.0",
  "ts": 1538864470950,
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  },
  "user": "system.user.admin"
}

                            {
  "_id": "mihome.0.devices.sensor_ht_158d000221a574.humidity",
  "common": {
    "name": "Noel Humidity",
    "role": "value.humidity",
    "unit": "%",
    "write": false,
    "read": true,
    "type": "number",
    "min": 0,
    "max": 100
  },
  "type": "state",
  "native": {},
  "from": "system.adapter.mihome.0",
  "ts": 1536998122958,
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  },
  "user": "system.user.admin"
}
                            1 Reply Last reply Reply Quote 0
                            • crunchip
                              crunchip Forum Testing Most Active @Guest last edited by

                              @nis gerade probiert

                              Caught	2019-09-02 21:34:08.947	error	by controller[0]: (node:12186) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process wit
Caught	2019-09-02 21:34:08.947	error	by controller[0]: (node:12186) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecti
Caught	2019-09-02 21:34:08.947	error	by controller[0]: at /opt/iobroker/node_modules/grpc/src/client_interceptors.js:1123:18
Caught	2019-09-02 21:34:08.947	error	by controller[0]: at InterceptingListener.onReceiveStatus (/opt/iobroker/node_modules/grpc/src/client_interceptors.js:618:8)
Caught	2019-09-02 21:34:08.947	error	by controller[0]: at InterceptingListener._callNext (/opt/iobroker/node_modules/grpc/src/client_interceptors.js:568:42)
Caught	2019-09-02 21:34:08.947	error	by controller[0]: at Object.onReceiveStatus (/opt/iobroker/node_modules/grpc/src/client_interceptors.js:1306:15)
Caught	2019-09-02 21:34:08.947	error	by controller[0]: at ClientDuplexStream._receiveStatus (/opt/iobroker/node_modules/grpc/src/client.js:211:8)
Caught	2019-09-02 21:34:08.947	error	by controller[0]: at ClientDuplexStream._emitStatusIfDone (/opt/iobroker/node_modules/grpc/src/client.js:234:12)
Caught	2019-09-02 21:34:08.947	error	by controller[0]: at ClientDuplexStream.emit (events.js:198:13)
Caught	2019-09-02 21:34:08.947	error	by controller[0]: at ClientDuplexStream.<anonymous> (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:22177:19)
Caught	2019-09-02 21:34:08.947	error	by controller[0]: at new FirestoreError (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:354:28)
Caught	2019-09-02 21:34:08.946	error	by controller[0]: (node:12186) UnhandledPromiseRejectionWarning: FirebaseError: 3 INVALID_ARGUMENT: maximum 500 writes allowed per request
iogo.0	2019-09-02 21:34:08.896	info	listener removed
iogo.0	2019-09-02 21:34:08.895	info	triggered listener removed
iogo.0	2019-09-02 21:34:08.893	info	signed out
iogo.0	2019-09-02 21:34:08.887	info	listener removed
iogo.0	2019-09-02 21:34:08.875	info	triggered listener removed
host.IoBroker	2019-09-02 21:34:08.872	info	stopInstance system.adapter.iogo.0 killing pid 12186
host.IoBroker	2019-09-02 21:34:08.872	info	stopInstance system.adapter.iogo.0
iogo.0	2019-09-02 21:34:08.874	info	cleaned everything up...
                              ? 1 Reply Last reply Reply Quote 0
                              • ?
                                A Former User @crunchip last edited by

                                @crunchip tritt der Fehler beim Stoppen der Instanz auf? Bitte etwas mehr Details was du gemacht hast

                                crunchip 1 Reply Last reply Reply Quote 0
                                • crunchip
                                  crunchip Forum Testing Most Active @Guest last edited by crunchip

                                  @nis ja, das kommt, wenn ich den Adapter stoppe, genau das selbe wie vorhin schon gepostet
                                  hab nur den Adapter gestartet, kurz gewartet und dann wieder beendet

                                  ? 1 Reply Last reply Reply Quote 0
                                  • ?
                                    A Former User @crunchip last edited by

                                    @crunchip Und viel wichtiger, wie sieht es beim Start aus?

                                    crunchip 1 Reply Last reply Reply Quote 0
                                    • crunchip
                                      crunchip Forum Testing Most Active @Guest last edited by crunchip

                                      @nis

                                      2019-09-02 21:33:36.135 - info: host.IoBroker object change system.adapter.iogo.0
2019-09-02 21:33:36.156 - info: host.IoBroker instance system.adapter.iogo.0 started with pid 12186
2019-09-02 21:33:37.805 - info: iogo.0 starting. Version 0.4.3 in /opt/iobroker/node_modules/iobroker.iogo, node: v10.16.0
2019-09-02 21:33:37.920 - info: iogo.0 triggered listener removed
2019-09-02 21:33:38.592 - info: iogo.0 licence key found. licence valid until 2020-08-27 20:38:10
2019-09-02 21:33:38.593 - info: iogo.0 logged in as: qwertz <= please keep this uid as your secret
2019-09-02 21:33:38.605 - info: iogo.0 states from remote database removed
2019-09-02 21:33:38.624 - info: iogo.0 initialize app devices
2019-09-02 21:33:43.183 - info: iogo.0 database initialized with 1 hosts
2019-09-02 21:33:43.607 - info: iogo.0 database initialized with 106 instances
2019-09-02 21:33:43.760 - info: iogo.0 database initialized with 23 enums
2019-09-02 21:33:44.848 - info: iogo.0 database initialized with 102 adapters
                                      ? 1 Reply Last reply Reply Quote 0
                                      • ?
                                        A Former User @crunchip last edited by

                                        @crunchip bitte erneut die aktuelle Version von GitHub installieren und nochmal Restart des Adapters

                                        crunchip 1 Reply Last reply Reply Quote 0
                                        • crunchip
                                          crunchip Forum Testing Most Active @Guest last edited by crunchip

                                          @nis adapter gestartet, noch nicht beendet

                                          iogo.0	2019-09-02 22:05:18.796	info	database initialized with 23 enums
iogo.0	2019-09-02 22:05:18.655	info	database initialized with 106 instances
iogo.0	2019-09-02 22:05:18.311	info	database initialized with 1 hosts
iogo.0	2019-09-02 22:05:17.985	info	database initialized with 822 states
iogo.0	2019-09-02 22:05:12.783	info	initialize app devices
iogo.0	2019-09-02 22:05:12.765	info	states from remote database removed
iogo.0	2019-09-02 22:05:12.755	info	logged in as: qwertz <= please keep this uid as your secret
iogo.0	2019-09-02 22:05:12.754	info	licence key found. licence valid until 2020-08-27 20:38:10
iogo.0	2019-09-02 22:05:11.948	info	triggered listener removed
iogo.0	2019-09-02 22:05:11.824	info	starting. Version 0.4.3 in /opt/iobroker/node_modules/iobroker.iogo, node: v10.16.0
host.IoBroker	2019-09-02 22:05:10.322	info	instance system.adapter.iogo.0 started with pid 13700
host.IoBroker	2019-09-02 22:05:10.303	info	object change system.adapter.iogo.0
zwischen drin alle state.system.adapter...has wrong type
iogo.0	2019-09-02 22:05:22.623	info	database initialized with 805 state values
iogo.0	2019-09-02 22:07:20.826	info	database initialized with 102 adapters

                                          adapter gestoppt

                                          host.IoBroker	2019-09-02 22:10:29.063	info	instance system.adapter.iogo.0 terminated with code 156 ()
iogo.0	2019-09-02 22:10:29.018	info	listener removed
iogo.0	2019-09-02 22:10:29.017	info	triggered listener removed
iogo.0	2019-09-02 22:10:29.015	info	signed out
iogo.0	2019-09-02 22:10:29.009	info	listener removed
iogo.0	2019-09-02 22:10:29.001	info	triggered listener removed
iogo.0	2019-09-02 22:10:29.000	info	cleaned everything up...
host.IoBroker	2019-09-02 22:10:28.999	info	stopInstance system.adapter.iogo.0 killing pid 13700
host.IoBroker	2019-09-02 22:10:28.999	info	stopInstance system.adapter.iogo.0
host.IoBroker	2019-09-02 22:10:28.999	info	object change system.adapter.iogo.0
                                          ? 1 Reply Last reply Reply Quote 0
                                          • ?
                                            A Former User @crunchip last edited by

                                            @crunchip sieht recht gut aus, ist auch alles in der App sichtbar?

                                            crunchip 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.2k
                                            Online

                                            30.4k
                                            Users

                                            76.8k
                                            Topics

                                            1.2m
                                            Posts

                                            android app iogo
                                            61
                                            1140
                                            148216
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo