Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Skripten / Logik
    4. JavaScript
    5. Datenpunkt von ioBroker nach Variable in CCU schreiben

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Datenpunkt von ioBroker nach Variable in CCU schreiben

    This topic has been deleted. Only users with topic management privileges can see it.
    • paul53
      paul53 @hanan last edited by paul53

      @hanan sagte:

      Der Datenpunkt Zeitpunkt wird immer aktuallisiert und soll der Trigger sein.

      Dann darfst Du nicht den Block binde verwenden, denn der enthält einen Trigger.
      Besser: Lass den Trigger "zeitpunkt" weg !

      1 Reply Last reply Reply Quote 0
      • hanan
        hanan last edited by hanan

        Habe ich jetzt versucht, doch es kommen immer noch Warnmeldungen...

        Hier der Blockly-Code:
        Blockly.jpg

        on({id: 'wiffi-wz.0.root.192_168_1_13.w_ip', change: "ne"}, function (obj) {
         setState('hm-rega.0.4026', obj.state.val);
        });
        on({id: 'wiffi-wz.0.root.192_168_1_13.w_temperatur', change: "ne"}, function (obj) {
         setState('hm-rega.0.3707', obj.state.val);
        });
        on({id: 'wiffi-wz.0.root.192_168_1_13.w_feuchte_rel', change: "ne"}, function (obj) {
         setState('hm-rega.0.3708', obj.state.val);
        });
        on({id: 'wiffi-wz.0.root.192_168_1_13.w_barometer', change: "ne"}, function (obj) {
         setState('hm-rega.0.3709', obj.state.val);
        });
        on({id: 'wiffi-wz.0.root.192_168_1_13.w_wind_mittel', change: "ne"}, function (obj) {
         setState('hm-rega.0.3710', obj.state.val);
        })
        
        paul53 1 Reply Last reply Reply Quote 0
        • paul53
          paul53 @hanan last edited by

          @hanan sagte:

          immer noch Warnmeldungen

          Schau mal nach dem Datenpunkt 'hm-rega.0.3709'. Gibt es ihn ?

          1 Reply Last reply Reply Quote 0
          • hanan
            hanan last edited by

            Jep...

            0511aa36-5f34-436a-a76b-7a4965d8618b-image.png

            Die Warnmeldungen kommen bei allen Datenpunkten.

            paul53 1 Reply Last reply Reply Quote 0
            • paul53
              paul53 @hanan last edited by

              @hanan sagte:

              Die Warnmeldungen kommen bei allen Datenpunkten.

              Die Daten werden aber geschrieben (es sind ja "nur" Warnungen). Welchen Typ haben die Rega-Datenpunkte ? Den gleichen wie die Quell-Datenpunkte ?

              1 Reply Last reply Reply Quote 0
              • hanan
                hanan last edited by hanan

                Jep, die Daten werden geschrieben.

                Hier die Datenpunkte im ioBroker:
                aedffcd2-9a69-4085-85ea-dee5ab86dd16-image.png

                In der CCU sind alle SV als Zahl ausser...
                Zeichenkette = w_barotrend und w_windrichtung
                Logikwert = w_regenmelder und w_sonne_scheint

                paul53 1 Reply Last reply Reply Quote 0
                • paul53
                  paul53 @hanan last edited by

                  @hanan sagte:

                  Hier die Datenpunkte im ioBroker:

                  Daran kann man nicht erkennen, welchen Datentyp die Werte tasächlich haben. Erzeuge mal ein Log:
                  debug output von Typ von Wert von Objekt w_barometer

                  1 Reply Last reply Reply Quote 0
                  • hanan
                    hanan last edited by

                    Hier die Daten vom Datenpunkt w_barometer:

                    {
                    "from": "system.adapter.wiffi-wz.0",
                    "ts": 1557058406498,
                    "common": {
                    "name": 3,
                    "desc": "nn_luftdruck",
                    "unit": "mb",
                    "role": "value.pressure",
                    "id": "w_barometer",
                    "type": "number",
                    "read": true,
                    "write": false
                    },
                    "native": {},
                    "acl": {
                    "object": 1638,
                    "owner": "system.user.admin",
                    "ownerGroup": "system.group.administrator",
                    "state": 1638
                    },
                    "_id": "wiffi-wz.0.root.192_168_1_13.w_barometer",
                    "type": "state"
                    }

                    paul53 1 Reply Last reply Reply Quote 0
                    • paul53
                      paul53 @hanan last edited by

                      @hanan sagte:

                      Hier die Daten vom Datenpunkt w_barometer:

                      common.type: "number" garantiert leider nicht, dass der Wert tatsächlich eine Zahl enthält. Deshalb erzeuge bitte den Log-Eintrag.

                      1 Reply Last reply Reply Quote 0
                      • hanan
                        hanan last edited by

                        javascript.0	2019-05-05 17:55:53.656	warn	at TCP.onread (net.js:601:20)
                        javascript.0	2019-05-05 17:55:53.656	warn	at Socket.Readable.push (_stream_readable.js:208:10)
                        javascript.0	2019-05-05 17:55:53.656	warn	at readableAddChunk (_stream_readable.js:250:11)
                        javascript.0	2019-05-05 17:55:53.656	warn	at addChunk (_stream_readable.js:263:12)
                        javascript.0	2019-05-05 17:55:53.656	warn	at Socket.emit (events.js:211:7)
                        javascript.0	2019-05-05 17:55:53.656	warn	at emitOne (events.js:116:13)
                        javascript.0	2019-05-05 17:55:53.656	warn	at Socket._ultron.on (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:138:22)
                        javascript.0	2019-05-05 17:55:53.656	warn	at Receiver.add (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/Receiver.js:139:10)
                        javascript.0	2019-05-05 17:55:53.656	warn	at Receiver.startLoop (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/Receiver.js:165:16)
                        javascript.0	2019-05-05 17:55:53.656	warn	at Receiver.getData (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/Receiver.js:330:12)
                        javascript.0	2019-05-05 17:55:53.656	warn	at Receiver.dataMessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/Receiver.js:389:14)
                        javascript.0	2019-05-05 17:55:53.656	warn	at Receiver._receiver.onmessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:141:47)
                        javascript.0	2019-05-05 17:55:53.656	warn	at WebSocket.emit (events.js:211:7)
                        javascript.0	2019-05-05 17:55:53.656	warn	at emitOne (events.js:116:13)
                        javascript.0	2019-05-05 17:55:53.656	warn	at WebSocket.onMessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/EventTarget.js:99:16)
                        javascript.0	2019-05-05 17:55:53.656	warn	at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:147:10)
                        javascript.0	2019-05-05 17:55:53.656	warn	at WS.Transport.onData (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:137:8)
                        javascript.0	2019-05-05 17:55:53.656	warn	at WS.Transport.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:145:8)
                        javascript.0	2019-05-05 17:55:53.656	warn	at WS.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)
                        javascript.0	2019-05-05 17:55:53.656	warn	at WS.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:273:10)
                        javascript.0	2019-05-05 17:55:53.656	warn	at Socket.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:456:14)
                        javascript.0	2019-05-05 17:55:53.656	warn	at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Socket.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Manager.ondata (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:335:16)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Decoder.add (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-parser/index.js:251:12)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Decoder.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Decoder.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:345:8)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Manager.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:236:12)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Socket.onevent (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:278:10)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemClient.js:52:30)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Object.change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3425:37)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:364:25)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:963:38)
                        javascript.0	2019-05-05 17:55:53.655	warn	at Object.<anonymous> (script.js.common.Test.nach_CCU:2:3)
                        javascript.0	2019-05-05 17:55:53.655	warn	at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1258:20)
                        javascript.0	2019-05-05 17:55:53.655	warn	Wrong type of hm-rega.0.3709: "string". Please fix, while deprecated and will not work in next versions.
                        
                        paul53 1 Reply Last reply Reply Quote 0
                        • paul53
                          paul53 @hanan last edited by

                          @hanan sagte:

                          Wrong type of hm-rega.0.3709: "string".

                          Das habe ich vermutet. Die Werte müssen erst in eine Zahl gewandelt werden.

                          1 Reply Last reply Reply Quote 0
                          • hanan
                            hanan last edited by

                            Erst mal Danke für den Tipp.
                            Muss mal im Forum schauen wie ich dieses umwandeln kann, hoffe ich finde etwas.

                            paul53 1 Reply Last reply Reply Quote 0
                            • paul53
                              paul53 @hanan last edited by paul53

                              @hanan sagte:

                              wie ich dieses umwandeln kann

                              Blockly_Triggerwert_nach_Zahl.JPG

                              Wert ist eine Eigenschaft des Triggerdatenpunktes (Blöcke Trigger)

                              1 Reply Last reply Reply Quote 0
                              • hanan
                                hanan last edited by

                                Hallo paul53
                                Hat supi geklappt.
                                Besten Dank nochmals für Deine Hilfe..

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

                                Support us

                                ioBroker
                                Community Adapters
                                Donate

                                900
                                Online

                                31.9k
                                Users

                                80.1k
                                Topics

                                1.3m
                                Posts

                                4
                                21
                                1694
                                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