Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Problem:Blockly Sendto lässt sich nicht anwählen

    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

    UNSOLVED Problem:Blockly Sendto lässt sich nicht anwählen

    This topic has been deleted. Only users with topic management privileges can see it.
    • crunchip
      crunchip Forum Testing Most Active @Knallochse last edited by

      @Knallochse nein den hab ich schon länger nicht mehr

      Knallochse 1 Reply Last reply Reply Quote 0
      • crunchip
        crunchip Forum Testing Most Active @liv-in-sky last edited by

        @liv-in-sky aktuell steh ich hier
        Admin 3.6.2
        Js-controller 1.4.2
        Node.js v8.16.0
        NPM 6.4.1

        liv-in-sky 1 Reply Last reply Reply Quote 0
        • liv-in-sky
          liv-in-sky @crunchip last edited by

          @crunchip war wohl gedankenübertragung - hatte post schon geschrieben mit dieser frage? aber dann doch gelöscht, weil ich im moment total verwirt bin

          in dem anderen thread sagt dignix er habe das selbe problem wie du - aber ich sehe keine permitt-prbleme in deinen fehlermeldungen - mach doch nochmal ein npm build mit dieser konstellation damit wir die fehler nochmal aktuell haben

          crunchip 2 Replies Last reply Reply Quote 0
          • crunchip
            crunchip Forum Testing Most Active @liv-in-sky last edited by

            @liv-in-sky mach ich mal, dauert nen moment

            1 Reply Last reply Reply Quote 0
            • Knallochse
              Knallochse @crunchip last edited by

              @crunchip Ich hatte das gleiche Problem, als ich den Cloud Adapter deinstalliert hatte. Dieser musste bei mir installiert sein, aber unter Instanzen nicht laufen (Pause)

              1 Reply Last reply Reply Quote 0
              • liv-in-sky
                liv-in-sky @liv-in-sky last edited by

                @liv-in-sky sagte in Problem:Blockly Sendto lässt sich nicht anwählen:

                ich hatte vor kurzem auch soviele fehler bei jemanden den ich über teamviewer geholfen hatte - die fehler kamen nachdem ich node 10 , den admin und js upgrade machte - danach wieder auf node 8 - aber die fehler blieben
                gelöst habe ich das folgendermaßen - meine annahme war, das ein alter adapter irgendwelche dependencies setzte und deshalb die anderen adapter bei einem rebuild ein problem bekommen.

                @crunchip der letzte post im anderen thread von apollon geht mit meiner these zusammen, dass alte adapter ein problem machen können
                https://forum.iobroker.net/post/267287

                1 Reply Last reply Reply Quote 0
                • crunchip
                  crunchip Forum Testing Most Active @liv-in-sky last edited by crunchip

                  @liv-in-sky @apollon77

                  root@IoBroker:/opt/iobroker# npm rebuild

> bluetooth-hci-socket@0.5.1 install /opt/iobroker/node_modules/bluetooth-hci-socket
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/bluetooth-hci-socket/build“ wird betreten
 CXX(target) Release/obj.target/binding/src/BluetoothHciSocket.o
../src/BluetoothHciSocket.cpp: In member function ‘void BluetoothHciSocket::poll()’:
../src/BluetoothHciSocket.cpp:251:95: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
    Nan::MakeCallback(Nan::New<Object>(this->This), Nan::New("emit").ToLocalChecked(), 2, argv);
                                                                                              ^
In file included from ../src/BluetoothHciSocket.cpp:8:0:
../../nan/nan.h:950:46: note: declared here
  NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                             ^~~~~~~~~~~~
../src/BluetoothHciSocket.cpp: In member function ‘void BluetoothHciSocket::emitErrnoError()’:
../src/BluetoothHciSocket.cpp:275:72: warning: ‘v8::Local<v8::Object> v8::Function::NewInstance(int, v8::Local<v8::Value>*) const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
  Local<Value> error = errorConstructor->NewInstance(1, constructorArgs);
                                                                       ^
In file included from /root/.node-gyp/8.16.0/include/node/v8.h:26:0,
                from /root/.node-gyp/8.16.0/include/node/node.h:63,
                from /root/.node-gyp/8.16.0/include/node/node_buffer.h:25,
                from ../src/BluetoothHciSocket.cpp:7:
/root/.node-gyp/8.16.0/include/node/v8.h:3897:31: note: declared here
                Local<Object> NewInstance(int argc, Local<Value> argv[]) const);
                              ^
/root/.node-gyp/8.16.0/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
  declarator __attribute__((deprecated(message)))
  ^~~~~~~~~~
../src/BluetoothHciSocket.cpp:282:93: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
  Nan::MakeCallback(Nan::New<Object>(this->This), Nan::New("emit").ToLocalChecked(), 2, argv);
                                                                                            ^
In file included from ../src/BluetoothHciSocket.cpp:8:0:
../../nan/nan.h:950:46: note: declared here
  NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                             ^~~~~~~~~~~~
 SOLINK_MODULE(target) Release/obj.target/binding.node
 COPY Release/binding.node
make: Verzeichnis „/opt/iobroker/node_modules/bluetooth-hci-socket/build“ wird verlassen

> iobroker@1.1.2 install /opt/iobroker/node_modules/iobroker
> node lib/prepareSetup.js && node lib/setup.js

NPM version: 6.4.1
npm version >= 5: disabling package-lock
npm install iobroker.discovery@stable --production --save

> serialport@6.2.2 install /opt/iobroker/node_modules/iobroker.discovery/node_modules/serialport
> prebuild-install || node-gyp rebuild

npm WARN react-beautiful-dnd@9.0.2 requires a peer of react@^16.3.1 but none is installed. You must install peer dependencies yourself.
npm WARN react-motion@0.5.2 requires a peer of react@^0.14.9 || ^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-redux@5.0.7 requires a peer of react@^0.14.0 || ^15.0.0-0 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN svg-inline-react@1.0.3 requires a peer of react@^0.14.0 || ^15.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.3 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@0.1.4 (node_modules/xpc-connection):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+ iobroker.discovery@1.3.0
added 2 packages from 4 contributors, removed 82 packages, updated 11 packages and audited 48050 packages in 81.804s
found 142 vulnerabilities (64 low, 17 moderate, 61 high)
 run `npm audit fix` to fix them, or `npm audit` for details
packet folder is: /opt/iobroker/node_modules/iobroker.discovery | exists: true
npm install iobroker.admin@stable --production --save
npm WARN react-beautiful-dnd@9.0.2 requires a peer of react@^16.3.1 but none is installed. You must install peer dependencies yourself.
npm WARN react-motion@0.5.2 requires a peer of react@^0.14.9 || ^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-redux@5.0.7 requires a peer of react@^0.14.0 || ^15.0.0-0 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN svg-inline-react@1.0.3 requires a peer of react@^0.14.0 || ^15.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.3 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@0.1.4 (node_modules/xpc-connection):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+ iobroker.admin@3.6.2
updated 1 package and audited 48050 packages in 84.565s
found 142 vulnerabilities (64 low, 17 moderate, 61 high)
 run `npm audit fix` to fix them, or `npm audit` for details
packet folder is: /opt/iobroker/node_modules/iobroker.admin | exists: true
npm install iobroker.js-controller@stable --production --save

> iobroker.js-controller@1.5.11 preinstall /opt/iobroker/node_modules/iobroker.js-controller
> node lib/preinstallCheck.js

NPM version: 6.4.1
npm version >= 5: disabling package-lock

> ursa-optional@0.9.10 install /opt/iobroker/node_modules/ursa-optional
> node rebuild.js


> diskusage@0.2.6 install /opt/iobroker/node_modules/diskusage
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/diskusage/build“ wird betreten
 CXX(target) Release/obj.target/diskusage/src/main.o
 CXX(target) Release/obj.target/diskusage/src/diskusage_posix.o
 SOLINK_MODULE(target) Release/obj.target/diskusage.node
 COPY Release/diskusage.node
make: Verzeichnis „/opt/iobroker/node_modules/diskusage/build“ wird verlassen

> iobroker.js-controller@1.5.11 install /opt/iobroker/node_modules/iobroker.js-controller
> node iobroker.js setup first

npm WARN react-beautiful-dnd@9.0.2 requires a peer of react@^16.3.1 but none is installed. You must install peer dependencies yourself.
npm WARN react-motion@0.5.2 requires a peer of react@^0.14.9 || ^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-redux@5.0.7 requires a peer of react@^0.14.0 || ^15.0.0-0 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN svg-inline-react@1.0.3 requires a peer of react@^0.14.0 || ^15.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.3 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@0.1.4 (node_modules/xpc-connection):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+ iobroker.js-controller@1.5.11
added 17 packages from 30 contributors, removed 2 packages, updated 3 packages and audited 48132 packages in 92.007s
found 160 vulnerabilities (75 low, 18 moderate, 67 high)
 run `npm audit fix` to fix them, or `npm audit` for details
packet folder is: /opt/iobroker/node_modules/iobroker.js-controller | exists: true
Write "./iobroker start" to start the ioBroker
Auto-start was enabled. Write "update-rc.d -f iobroker.sh remove" to disable auto-start
iobroker is started. Go to "http://ip-addr:8081" to open the admin UI.

> iobroker.amazon-dash@0.3.1 preinstall /opt/iobroker/node_modules/iobroker.amazon-dash
> apt install libpcap-dev -y || true

Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
libpcap-dev ist schon die neueste Version (1.8.1-3).
Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
 linux-image-4.9.0-7-amd64
Verwenden Sie »apt autoremove«, um es zu entfernen.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 3 nicht aktualisiert.

> socketwatcher@0.3.0 install /opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/socketwatcher
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/socketwatcher/build“ wird betreten
 CXX(target) Release/obj.target/socketwatcher/socket_watcher.o
../socket_watcher.cpp: In static member function ‘static void SocketWatcher::Callback(uv_poll_t*, int, int)’:
../socket_watcher.cpp:77:60: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
  Nan::MakeCallback(watcher->handle(), callback, argc, argv);
                                                           ^
In file included from ../socket_watcher.hpp:8:0,
                from ../socket_watcher.cpp:5:
../../nan/nan.h:959:46: note: declared here
  NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                             ^~~~~~~~~~~~
 SOLINK_MODULE(target) Release/obj.target/socketwatcher.node
 COPY Release/socketwatcher.node
make: Verzeichnis „/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/socketwatcher/build“ wird verlassen

> pcap@2.1.0 install /opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap/build“ wird betreten
 CXX(target) Release/obj.target/pcap_binding/pcap_binding.o
 CXX(target) Release/obj.target/pcap_binding/pcap_session.o
../pcap_session.cc: In static member function ‘static void PcapSession::PacketReady(u_char*, const pcap_pkthdr*, const u_char*)’:
../pcap_session.cc:85:102: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
    Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(session->packet_ready_cb), 0, NULL);
                                                                                                     ^
In file included from ../pcap_session.h:4:0,
                from ../pcap_session.cc:7:
../../nan/nan.h:959:46: note: declared here
  NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                             ^~~~~~~~~~~~
 SOLINK_MODULE(target) Release/obj.target/pcap_binding.node
 COPY Release/pcap_binding.node
make: Verzeichnis „/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap/build“ wird verlassen

> socketwatcher@0.3.0 install /opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/socketwatcher
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/socketwatcher/build“ wird betreten
 CXX(target) Release/obj.target/socketwatcher/socket_watcher.o
../socket_watcher.cpp: In static member function ‘static void SocketWatcher::Callback(uv_poll_t*, int, int)’:
../socket_watcher.cpp:77:60: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
  Nan::MakeCallback(watcher->handle(), callback, argc, argv);
                                                           ^
In file included from ../socket_watcher.hpp:8:0,
                from ../socket_watcher.cpp:5:
../../nan/nan.h:959:46: note: declared here
  NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                             ^~~~~~~~~~~~
 SOLINK_MODULE(target) Release/obj.target/socketwatcher.node
 COPY Release/socketwatcher.node
make: Verzeichnis „/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/socketwatcher/build“ wird verlassen

> usb@1.5.0 install /opt/iobroker/node_modules/iobroker.ble/node_modules/usb
> node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using request for node-pre-gyp https download
[usb] Success: "/opt/iobroker/node_modules/iobroker.ble/node_modules/usb/src/binding/usb_bindings.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile

> @abandonware/noble@1.9.2-2 install /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build“ wird betreten
 SOLINK_MODULE(target) Release/obj.target/noble.node
 COPY Release/noble.node
make: Verzeichnis „/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build“ wird verlassen

> usb@1.5.0 install /opt/iobroker/node_modules/iobroker.ble/node_modules/usb
> node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using request for node-pre-gyp https download
[usb] Success: "/opt/iobroker/node_modules/iobroker.ble/node_modules/usb/src/binding/usb_bindings.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile

> @abandonware/bluetooth-hci-socket@0.5.3-1 preinstall /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket
> npm install node-pre-gyp

+ node-pre-gyp@0.12.0
updated 6 packages and audited 95 packages in 4.815s
found 0 vulnerabilities

(node:31989) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit

> @abandonware/bluetooth-hci-socket@0.5.3-1 install /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket
> node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using request for node-pre-gyp https download
[@abandonware/bluetooth-hci-socket] Success: "/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/binding.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile
npm ERR! path /opt/iobroker/node_modules/iobroker.discovery/node_modules/@types/iobroker/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.discovery/node_modules/@types/iobroker/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-06-03T07_11_55_104Z-debug.log
root@IoBroker:/opt/iobroker#
                  liv-in-sky Stabilostick 3 Replies Last reply Reply Quote 0
                  • liv-in-sky
                    liv-in-sky @crunchip last edited by

                    @crunchip schau ich mir gleich mal an

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

                      Also das meiste sind warnungen und können ignoriert werden. Ich würde bei so eonem Fehler der scheinbar von "iobroker.discovery" getriggert wird einfach die gleiche discovery Version drüber installieren.

                      Also ggf in "node_modules/iobroker.discovery/package.json" rausfinden welche Version es ist und dann per

                      npm install iobroker.discovery@version --production

                      diese neu installieren. Danach nochmals npm rebuild

                      1 Reply Last reply Reply Quote 0
                      • liv-in-sky
                        liv-in-sky @crunchip last edited by liv-in-sky

                        @crunchip also kein einziges permit problem - ich glaube der fixer hilft da nicht weiter

                        aber es ist genau der fall wie bei dem anderen user.

                        da haben auch die ganzen depreciated sachen drin getanden

                        ich denke es ist so:
                        irgend ein alter adapter hat eine abhängigkeit zu einer alten version eines node programms - dieses programm gehört nicht direkt zu iobroker, sondern sind standard module, die von manchen adaptern genutzt werden. z.b. nan.h - eventuell werden diese module nicht upgedated von node version wegen der abhängigkeit

                        deshalb muss man alte adapter erst deinstallieren ( welchen weiß ich nicht genau) danach npm rebuild bis keine fehler mehr kommen - evtl node nochmal installieren - dann alten adapter wieder installieren

                        sicher bin ich mir da nicht - deshalb wäre es cool, wenn apollon noch drauf sieht

                        während ich verfasse:
                        hat er gerade gemacht !

                        denn discovery hab ich bei dem aqnderen user auch deinstalliert

                        1 Reply Last reply Reply Quote 0
                        • Stabilostick
                          Stabilostick @crunchip last edited by Stabilostick

                          @crunchip

                          Bitte installiere den cloud-Adapter nach und teste dann das Sendto noch einmal.

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

                            @Stabilostick du bist der Beste😅

                            Knallochse 1 Reply Last reply Reply Quote 0
                            • Knallochse
                              Knallochse @crunchip last edited by Knallochse

                              @crunchip Danke fürs lesen 😡
                              https://forum.iobroker.net/post/267285

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

                                das hier hilft auch oft

                                https://forum.iobroker.net/topic/15253/sendto-in-blockly

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

                                  @Knallochse habe das später erst gelesen, da das Problem dann mehr oder weniger übergegangen ist, den js.controller auf v10 zu bringen, ist das dann erstmal untergegangen.
                                  SORRY, nicht böse sein, bin ja steht für jeden Hinweis dankbar.
                                  Der cloud war schon längere Zeit deinstalliert, Skripte und Blocky haben aber trotzdem noch funktioniert.
                                  Und heute Nacht, dann mehr oder weniger eine Reinstallation vollbracht, in der Hoffnung das sich dieses Problem von selbst löst.
                                  Gruss und danke dir trotzdem nochmal.

                                  Knallochse 1 Reply Last reply Reply Quote 0
                                  • Knallochse
                                    Knallochse @crunchip last edited by

                                    @crunchip kein Problem. Hättest dein Problem halt eher gelöst 😀

                                    @apollon77 liegt die Abhängigkeit der Sendto Funktion im Blockly mit dem alten Cloud-Adapter an unseren Installationen oder müsste da mal was gefixt werden?
                                    (es funktioniert ja erst mal, wenn die Cloud-Adapter Instanz vorhanden ist)

                                    dslraser 1 Reply Last reply Reply Quote 0
                                    • dslraser
                                      dslraser Forum Testing Most Active @Knallochse last edited by dslraser

                                      @Knallochse
                                      @crunchip

                                      habt Ihr das gelesen ?

                                      https://forum.iobroker.net/topic/15253/sendto-in-blockly/2

                                      und die Lösung etwas weiter unten

                                      https://forum.iobroker.net/topic/15253/sendto-in-blockly/5

                                      crunchip Knallochse 2 Replies Last reply Reply Quote 0
                                      • crunchip
                                        crunchip Forum Testing Most Active @dslraser last edited by

                                        @dslraser gelesen ja, bei mir war das Problem aber nicht das selbe

                                        1 Reply Last reply Reply Quote 0
                                        • Knallochse
                                          Knallochse @dslraser last edited by

                                          @dslraser bei mir besteht ebenfalls ein anderes Problem

                                          dslraser 1 Reply Last reply Reply Quote 0
                                          • dslraser
                                            dslraser Forum Testing Most Active @Knallochse last edited by

                                            @Knallochse
                                            @crunchip

                                            dann sorry, ich dachte es wäre was ähnliches...

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            783
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            blockly bug darstellungsfehler fehler skript
                                            7
                                            44
                                            2359
                                            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