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. Error/Bug
  4. [Gelöst] Absoluter Beginner benötigt Hilfe: error No Value found for net_send

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.9k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.3k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.5k

[Gelöst] Absoluter Beginner benötigt Hilfe: error No Value found for net_send

Scheduled Pinned Locked Moved Error/Bug
14 Posts 2 Posters 1.3k 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.
  • StabilostickS Offline
    StabilostickS Offline
    Stabilostick
    wrote on last edited by
    #4

    Kommunizierst du mit dem Raspberry über WLAN oder per Ethernet-Kabel?

    Mach malls /sys/class/net/und````
    sudo ip addr show

    1 Reply Last reply
    0
    • U Offline
      U Offline
      unda
      wrote on last edited by
      #5

      Über Kabel.

      pi@raspberrypi:~ $ ls /sys/class/net/

      enxb827eb34d24e lo wlan0

      pi@raspberrypi:~ $ sudo ip addr show

      1: lo: <loopback,up,lower_up>mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

      inet 127.0.0.1/8 scope host lo

      valid_lft forever preferred_lft forever

      inet6 ::1/128 scope host

      valid_lft forever preferred_lft forever

      2: enxb827eb34d24e: <broadcast,multicast,up,lower_up>mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

      link/ether b8:27:eb:34:d2:4e brd ff:ff:ff:ff:ff:ff

      inet 192.168.13.40/24 brd 192.168.13.255 scope global enxb827eb34d24e

      valid_lft forever preferred_lft forever

      inet6 2a00:ab60:2b3:bb01:3405:db9:59f:bfab/64 scope global mngtmpaddr noprefixroute dynamic

      valid_lft 7078sec preferred_lft 3478sec

      inet6 fe80::5c76:1283:39fb:4621/64 scope link

      valid_lft forever preferred_lft forever

      3: wlan0: <broadcast,multicast,up,lower_up>mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

      link/ether b8:27:eb:61:87:1b brd ff:ff:ff:ff:ff:ff

      inet 192.168.13.39/24 brd 192.168.13.255 scope global wlan0

      valid_lft forever preferred_lft forever

      inet6 2a00:ab60:2b3:bb01:90f1:82e:6b2b:3c9b/64 scope global mngtmpaddr noprefixroute dynamic

      valid_lft 7078sec preferred_lft 3478sec

      inet6 fe80::52fd:b958:acab:fa22/64 scope link

      valid_lft forever preferred_lft forever</broadcast,multicast,up,lower_up></broadcast,multicast,up,lower_up></loopback,up,lower_up>

      1 Reply Last reply
      0
      • StabilostickS Offline
        StabilostickS Offline
        Stabilostick
        wrote on last edited by
        #6

        Naja, nachdem bei Dir das Netzwerkinterface enxb827eb34d24e heißt und nicht eth0 wie oben bei der Fehlermeldung erklärt sich das, oder?

        1 Reply Last reply
        0
        • StabilostickS Offline
          StabilostickS Offline
          Stabilostick
          wrote on last edited by
          #7

          Network interface naming rules changed with Debian 9. There are a few reasons behind this, you can read the details here:

          https://lists.debian.org/debian-user/20 … 01453.html

          If you just upgraded your system from Debian-8 to Debian-9, old ethXX schema will continue to work. But, if you install a fresh Debian-9 system, new schema will be used.

          So, old schema is deprecated in Debian 9, and will not be supported any more in Debian 10 (similarly Ubuntu 18.04 LTS).

          1 Reply Last reply
          0
          • U Offline
            U Offline
            unda
            wrote on last edited by
            #8

            Okay, das heißt das Interface hat nen komischen Namen (warum auch immer) und ich muss es umbenennen, damit der Fehler weg ist.

            Das werde ich bestimmt irgendwie hinbekommen.

            Danke erst mal für die Hilfe :-)

            1 Reply Last reply
            0
            • StabilostickS Offline
              StabilostickS Offline
              Stabilostick
              wrote on last edited by
              #9

              Kannst den Namen des Interfaces im Admin in der Adapterkonfiguration ändern?

              1 Reply Last reply
              0
              • StabilostickS Offline
                StabilostickS Offline
                Stabilostick
                wrote on last edited by
                #10

                Ansonsten:

                Switch to the old schema with adding new kernel parameters:

                Edit /etc/default/grub file and add

                net.ifnames=0 biosdevname=0

                parameters to GRUB_CMDLINE_LINUX variable like that:

                GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
                

                Update the grub config and reboot the system:

                $ sudo update-grub

                $ sudo reboot

                1 Reply Last reply
                0
                • U Offline
                  U Offline
                  unda
                  wrote on last edited by
                  #11

                  So weit die Theorie. "cannot open `/etc/default/grub' (No such file or directory)"

                  Ich werd mir das morgen noch mal näher angucken. Bislang wollen alle Wege, die mir Google genannt hat nicht funktionieren.

                  1 Reply Last reply
                  0
                  • StabilostickS Offline
                    StabilostickS Offline
                    Stabilostick
                    wrote on last edited by
                    #12

                    Ok, je nach OS…. schau mal hier:

                    https://raspberrypi.stackexchange.com/q ... -named-enx

                    1 Reply Last reply
                    0
                    • StabilostickS Offline
                      StabilostickS Offline
                      Stabilostick
                      wrote on last edited by
                      #13

                      Und:

                      If you on Raspbian raspi-config is easiest.

                      sudo raspi-config

                      Select "2. Network options"

                      Select "N3 Network interface names"

                      Select "No". It's now disabled predictable network interface names.

                      Click "OK" and "Finish". Then it will reboot your raspberry pi.

                      1 Reply Last reply
                      0
                      • U Offline
                        U Offline
                        unda
                        wrote on last edited by
                        #14

                        Es hat funktioniert. Vielen Dank! :)

                        1 Reply Last reply
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        Support us

                        ioBroker
                        Community Adapters
                        Donate

                        777

                        Online

                        32.5k

                        Users

                        81.6k

                        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