Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. WICHTIGE Info für Nutzer des RWE-SmartHome Adapters (Innogy-SmartHome)!

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    794

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    18
    1
    6.2k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.6k

WICHTIGE Info für Nutzer des RWE-SmartHome Adapters (Innogy-SmartHome)!

Scheduled Pinned Locked Moved ioBroker Allgemein
149 Posts 24 Posters 35.6k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    PArt
    wrote on last edited by
    #6

    Die erste sehr rudimentäre Version ist ab sofort unter https://github.com/PArns/ioBroker.innogy-smarthome zu finden!

    Beachtet bitte, das es noch keinerlei Errorhandling gibt und die Version noch nicht im Langzeittest getestet ist

    Wer sich dennoch traut, immer ran damit

    1 Reply Last reply
    0
    • P Offline
      P Offline
      PArt
      wrote on last edited by
      #7

      Das erste NPM-Package ist nun online und es wurden eine reihe weiterer Geräte hinzugefügt.

      Wenn jemand als role "unknown" erhält, so möge er mir bitte die RAW-Daten des Gerätes bzw. der Property schicken, ich kann diese dann relativ einfach hinzufügen!

      1 Reply Last reply
      0
      • P Offline
        P Offline
        PArt
        wrote on last edited by
        #8

        Der Adapter ist nun auch im Repo! Danke bluefox

        1 Reply Last reply
        0
        • T Offline
          T Offline
          torstenh
          wrote on last edited by
          #9

          Hallo zusammen,

          Adapter ist installiert und funktioniert prima!

          Danke…

          Grüße,

          Torsten

          1 Reply Last reply
          0
          • P Offline
            P Offline
            PArt
            wrote on last edited by
            #10

            Schau bitte einmal nach, ob du Objekte mit dem Typ/Rolle "unknown" hast, da ich noch nicht alle Geräte eingebunden/getestet habe …

            Falls ja, poste bitte einmal die RAW Daten, damit ich diese ebenfalls einbinden kann

            1 Reply Last reply
            0
            • T Offline
              T Offline
              torstenh
              wrote on last edited by
              #11

              …...ich habe momentan nur Heizungstermostate und die funktionieren. :roll:

              Grüße,

              Torsten

              1 Reply Last reply
              0
              • T Offline
                T Offline
                torstenh
                wrote on last edited by
                #12

                …..ich hatte heute das Problem das der Adapter grün war aber die Werte nicht gestimmt haben. Nach einem Neustart des Adapters lief alles wieder.

                Grüße,

                Torsten

                1 Reply Last reply
                0
                • P Offline
                  P Offline
                  PArt
                  wrote on last edited by
                  #13

                  Ja, das Problem ist mir auch schon aufgefallen und ich habe eben einen ersten Workaround getestet bzw. die Lib entsprechend angepasst. Ich will das ganze noch bei mir testen, bevor ich alles online stelle.

                  Derzeit scheinen die Sessions nach knapp 24h abzulaufen, auch wenn ich diese über einen Timer refreshe. Das sind eben derzeit leider noch die Kinderkrankheiten

                  1 Reply Last reply
                  0
                  • S Offline
                    S Offline
                    stephan61
                    wrote on last edited by
                    #14

                    Hallo Part bekomen nach update auf Version 0.0.6

                    beim Anmeldung kommt folgender Fehler im Log

                    innogy-smarthome.0 2017-01-11 14:01:33.672 error GOT AN ERROR:{}

                    Gruss Stephan

                    Ps unter ObjeKte erscheint das Thermostat im Raum jeweils 2 mal

                    siehe Bild

                    516_inno.png

                    1 Reply Last reply
                    0
                    • P Offline
                      P Offline
                      PArt
                      wrote on last edited by
                      #15

                      Das die Heizung 2x erscheint ist so beabsichtigt, da man hierüber die Räume steuert, falls z.B. 2 Heizungen im Raum sind. Erspart das Umstellen mehrerer Ventile. Die 2. Ansicht bzw. das 2. Gerät ist auch dann vorhanden, wenn man die Netatmo Wetterstation an die Zentrale gebunden hat. Das ganze ist so von Innogy vorgegeben und diese virtuellen Geräte werden von der API genutzt um den Zustand/Temperatur eines Raumes in der offiziellen GUI anzuzeigen.

                      Die Meldungen sind derzeit "nur" Debugmeldungen, werde diese ein wenig erweitern, da ich mir im Moment nicht erklären kann, warum die Meldung bei dir leer ist. Ich denke, das ich heute Abend ein weiteres Update veröffentlichen werde, welches uns dann hoffentlich ein wenig mehr Infos gibt

                      1 Reply Last reply
                      0
                      • S Offline
                        S Offline
                        stephan61
                        wrote on last edited by
                        #16

                        Hallo Part

                        Habe auf version 0.0.8 upgedatet bei update kommt folgenden Warnung

                        iobroker	2017-01-12 17:11:10.461	info	exit 0
                        iobroker	2017-01-12 17:11:10.314	info	upload [0] innogy-smarthome.admin /opt/iobroker/node_modules/iobroker.innogy-smarthome/admin/index.html index.html text/html
                        iobroker	2017-01-12 17:11:10.127	info	upload [1] innogy-smarthome.admin /opt/iobroker/node_modules/iobroker.innogy-smarthome/admin/innogy-smarthome.png innogy-smarthome.png image/png
                        iobroker	2017-01-12 17:11:10.092	info	got /opt/iobroker/node_modules/iobroker.innogy-smarthome/admin
                        
                        iobroker	2017-01-12 17:11:08.618	info	npm WARN unmet dependency which is version 2.6.0
                        iobroker	2017-01-12 17:11:08.618	info	WARN unmet dependency /opt/iobroker/node_modules/iobroker.rflink/node_modules/serialport/node_modules/node-pre-gyp/node_modules/tar-pack requires debug@'~2.2.0' but will loadnpm WARN unmet dependenc
                        iobroker	2017-01-12 17:11:08.604	info	npm
                        
                        iobroker	2017-01-12 17:08:37.612	info	WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
                        iobroker	2017-01-12 17:08:37.607	info	npm
                        iobroker	2017-01-12 17:08:37.607	info	WARN peerDependencies The peer dependency request@^2.34 included from request-promise-core will nonpm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
                        iobroker	2017-01-12 17:08:37.605	info	npm
                        iobroker	2017-01-12 17:08:32.130	info	npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
                        iobroker	2017-01-12 17:08:32.123	info	The peer dependency request@^2.34 included from request-promise will nonpm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
                        iobroker	2017-01-12 17:08:32.118	info	WARN peerDependencies
                        iobroker	2017-01-12 17:08:32.116	info	npm
                        iobroker	2017-01-12 17:08:07.048	info	npm install https://github.com/PArns/ioBroker.innogy-smarthome/tarball/master --production --prefix "/opt/iobroker" (System call)
                        iobroker	2017-01-12 17:08:05.957	info	install https://github.com/PArns/ioBroker.innogy-smarthome/tarball/master
                        iobroker	2017-01-12 17:08:03.426	info	url "https://github.com/PArns/ioBroker.innogy-smarthome/tarball/master" innogy-smarthome
                        

                        und bei Start kommt folgender Fehler im Log Zeit Nachricht

                        x

                        javascript.0 2017-01-12 17:13:59.620 info javascript.0 script.js.common.Strom.Buegeleisen._Stromverbrauch_auswerten: Bügeleisen: 210.34 / aus

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/lib/Receiver.js:508:14

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Receiver.applyExtensions (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/lib/Receiver.js:371:5)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/lib/Receiver.js:536:18

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Receiver.ontext (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:841:10)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at WebSocket.emit (events.js:172:7)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at emitTwo (events.js:87:13)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at WebSocket.onMessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:442:14)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/lib/transports/websocket.js:146:10)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at WS.Transport.onData (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/lib/transport.js:137:8)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at WS.Transport.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/lib/transport.js:145:8)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at WS.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at WS. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/lib/socket.js:268:10)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Socket.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/lib/socket.js:451:14)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Manager.ondata (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:322:16)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Decoder.add (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/socket.io-parser/index.js:246:12)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Decoder.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/socket.io-parser/node_modules/component-emitter/index.js:134:20)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Decoder. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:332:8)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:236:12)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:312:9)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:644:25)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3834:18)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Adapter.emit (events.js:166:7)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at emitNone (events.js:67:13)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Adapter.initSmartHome (/opt/iobroker/node_modules/iobroker.innogy-smarthome/main.js:123:15)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at SmartHome.init (/opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/lib/smarthome/index.js:85:17)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at SmartHome._initialize (/opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/lib/smarthome/index.js:234:8)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error From previous event:

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at processImmediate [as _immediateCallback] (timers.js:383:17)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at /opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/lib/smarthome/index.js:238:23

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at ShTypeParser.parseConfig (/opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/lib/smarthome/typeparser.js:37:26)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at Object.getDescriptorFile (/opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/lib/utils/index.js:21:12)

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error at /opt/iobroker/node_modules/iobroker.innogy-smarthome/node_modules/innogy-smarthome-lib/lib/utils/index.js:27:22

                        innogy-smarthome.0 2017-01-12 17:13:27.602 error STACK:TypeError: Cannot read property 'call' of undefined

                        innogy-smarthome.0 2017-01-12 17:13:27.598 error GOT AN ERROR:{}

                        Gruß Stephan

                        1 Reply Last reply
                        0
                        • P Offline
                          P Offline
                          PArt
                          wrote on last edited by
                          #17

                          Mach mal bitte eine neuinstallation des Adapters, es scheint, als würde bei dir eine Abhängigkeit nicht richtig installiert werden! Beachte bitte auch, das du mind. Node 4 brauchst

                          Gib mal node -v auf der Konsole ein

                          Der Fehler scheint auch durch ein Script getriggert zu werden!? Schaltest du da bereits etwas drüber? Wenn ja, was?

                          1 Reply Last reply
                          0
                          • S Offline
                            S Offline
                            stephan61
                            wrote on last edited by
                            #18

                            Hallo Part habe den Adapter kompl gelöscht

                            und neu installiert es kommt wieder der gleiche Fehler

                            habe node v4.7.2

                            Pi 2 B + mit Jessie

                            Gruss Stephan

                            1 Reply Last reply
                            0
                            • T Offline
                              T Offline
                              torstenh
                              wrote on last edited by
                              #19

                              Hallo,

                              bei mir läuft IO Broker auf Windows Home Server und ich habe das gleiche Problem. Auch mit Neuinstallation des Adapters kommen diese Fehlermeldungen. Mir ist aufgefallen das ich mich nicht autorisieren kann, da kommt eine "Zeitüberschreitung"

                              Grüße,

                              Torsten

                              Node Version: 4.3.1

                              Wie gesagt bei mir sind nur die Heizungventile dran und diese werden nicht angezeigt!

                              Die Fehlermeldungen im Log kommen nach dem Login vom Adapter

                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at processImmediate [as _immediateCallback] (timers.js:383:17)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Immediate.Async.drainQueues [as _onImmediate] (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\simple-oauth2\node_modules\bluebird\js\main\asyn
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Async._drainQueues (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\simple-oauth2\node_modules\bluebird\js\main\async.js:133:10)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Async._drainQueue (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\simple-oauth2\node_modules\bluebird\js\main\async.js:123:16)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Promise._settlePromises (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\simple-oauth2\node_modules\bluebird\js\main\promise.js:700:14)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Promise._settlePromiseAt (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\simple-oauth2\node_modules\bluebird\js\main\promise.js:582:21)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Promise.successAdapter (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\simple-oauth2\node_modules\bluebird\js\main\nodeify.js:23:30)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at tryCatcher (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\simple-oauth2\node_modules\bluebird\js\main\util.js:26:23)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\oauth2\index.js:43:17
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\main.js:39:31
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at SmartHome.init (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\smarthome\index.js:85:17)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at SmartHome._initialize (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\smarthome\index.js:228:52)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error From previous event:
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\smarthome\index.js:230:25
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at SmartHome.finalize (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\smarthome\index.js:109:17)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at SmartHome._uninitialize (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\smarthome\index.js:245:28)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Requestor.call (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\requestor\index.js:42:17)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Requestor.doRequest (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\lib\requestor\index.js:48:12)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error From previous event:
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at process._tickCallback (node.js:351:17)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at nextTickCallbackWith2Args (node.js:437:9)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at endReadableNT (_stream_readable.js:905:12)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at IncomingMessage.emit (events.js:166:7)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at emitNone (events.js:72:20)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at IncomingMessage.g (events.js:260:16)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at IncomingMessage. (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\request-promise\node_modules\request\request.js:1001:12)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Request.emit (events.js:169:7)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at emitOne (events.js:77:13)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Request. (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\request-promise\node_modules\request\request.js:1081:10)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Request.emit (events.js:172:7)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at emitTwo (events.js:87:13)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Request.self.callback (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\request-promise\node_modules\request\request.js:186:22)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Request.RP$callback [as _callback] (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\request-promise\node_modules\request-promise-core\lib\plumb
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at Request.plumbing.callback (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\request-promise\node_modules\request-promise-core\lib\plumbing.js:10
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error at new StatusCodeError (C:\ioBroker\node_modules\iobroker.innogy-smarthome\node_modules\innogy-smarthome-lib\node_modules\request-promise\node_modules\request-promise-core\lib\errors.js:32:15)
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error STACK:StatusCodeError: 404 - {"errorcode":2012,"description":"Session not found","messages":["Session not found: d283aa51a7d749afb32b4adb6616fbc7"]}
                              ! innogy-smarthome.0 2017-01-13 17:37:40.696 error GOT AN ERROR:{"name":"StatusCodeError","statusCode":404,"message":"404 - {"errorcode":2012,"description":"Session not found","messages":["Session not found: d283aa51a7d749afb32b4adb6616fbc7[/spoiler]

                              1 Reply Last reply
                              0
                              • P Offline
                                P Offline
                                PArt
                                wrote on last edited by
                                #20

                                Bei dir ist das ein anderer Fehler … Anscheinend habe ich mit dem letzten Update etwas beim Sessionhandling kaputt gemacht! Schaue ich mir morgen an! Danke fürs testen

                                1 Reply Last reply
                                0
                                • T Offline
                                  T Offline
                                  torstenh
                                  wrote on last edited by
                                  #21

                                  …..kein Problem!

                                  immer wieder gern...

                                  Grüße,

                                  Torsten

                                  1 Reply Last reply
                                  0
                                  • P Offline
                                    P Offline
                                    PArt
                                    wrote on last edited by
                                    #22

                                    Ok, ich habe den Fehler von euch beiden gefunden! Ich habe anscheinend mehr kaputt gemacht, als ich gedacht habe …

                                    Neue Version ist auf dem Weg

                                    1 Reply Last reply
                                    0
                                    • S Offline
                                      S Offline
                                      stephan61
                                      wrote on last edited by
                                      #23

                                      Hallo Part nach update

                                      kommt keine Fehlermeldung mehr

                                      alle Thermostate und Rauchmelder werden angezeigt.

                                      Vielen Dank für deine Arbeit

                                      Gruß Stephan

                                      1 Reply Last reply
                                      0
                                      • P Offline
                                        P Offline
                                        PArt
                                        wrote on last edited by
                                        #24

                                        Hallo Stephan,

                                        danke fürs Feedback!

                                        Derzeit sind noch ein paar Debugmeldungen aktiviert, da ich noch den Keyrenew testen will. Funktioniert dieser (alle 2 Tage ab der 1. Anmeldung), dann werde ich auch diese entfernen

                                        Patrick

                                        1 Reply Last reply
                                        0
                                        • T Offline
                                          T Offline
                                          torstenh
                                          wrote on last edited by
                                          #25

                                          ….alle Termostate sind da und es funktioniert wieder!

                                          Danke für die Mühe und die klasse Arbeit!

                                          Grüße,

                                          Torsten

                                          1 Reply Last reply
                                          0

                                          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                          With your input, this post could be even better 💗

                                          Register Login
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          527

                                          Online

                                          32.8k

                                          Users

                                          82.7k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe