Navigation

    • Register
    • Login
    • Search
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. pw44
    3. Posts
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Posts made by pw44

    • RE: 2021 EU customs regulatory changes — where should I buy now?

      These postal companies, having the monopoly for postal services became pimps, picking pockets for their good.

      posted in General Discussion
      pw44
      pw44
    • RE: Unable to add node - more than 2

      @mfalkvidd said in Unable to add node - more than 2:

      which debugs are necessary?

      MY_DEBUG or MY_DEBUG and MY_DEBUG_VERBOSE_RF24?

      posted in Troubleshooting
      pw44
      pw44
    • RE: Unable to add node - more than 2

      @mfalkvidd i really like the concept, but having troubles by trying more than 2 nodes is simply ridiculous.

      I'm not finding out how to solve it.

      i have 3 nodes. all works, but only 2 at a time. clearing the eeproms and flahsing again, it's like the 2 fastest. in any order. but only 2.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Unable to add node - more than 2

      @mfalkvidd
      thx for answering.

      all use the same radio channel: 72

      the problematic node was working before.

      original: esp8266 gateway + 4 binarys sensor node + weather station node - all ok, no problem
      by trying to add the 6 binary sensor node, this new node was never added.

      clearead all gw + 3 nodes - eeprom.

      now: esp8266 gateway + 4 binarys sensor node + 6 binary sensor node - all ok, no problem
      the weather station node, which was working before, does not get added.

      seams that by node 3, it gets refused.

      {
          "0": {
              "sensor_id": 0,
              "children": {},
              "type": 18,
              "sketch_name": null,
              "sketch_version": null,
              "battery_level": 0,
              "protocol_version": "2.3.2",
              "heartbeat": 0
          },
          "1": {
              "sensor_id": 1,
              "children": {
                  "1": {
                      "id": 1,
                      "type": 0,
                      "description": "",
                      "values": {}
                  },
                  "2": {
                      "id": 2,
                      "type": 0,
                      "description": "",
                      "values": {}
                  },
                  "3": {
                      "id": 3,
                      "type": 0,
                      "description": "",
                      "values": {}
                  },
                  "4": {
                      "id": 4,
                      "type": 0,
                      "description": "",
                      "values": {}
                  }
              },
              "type": 18,
              "sketch_name": "Door Window Sns x4",
              "sketch_version": "1.0",
              "battery_level": 0,
              "protocol_version": "2.3.2",
              "heartbeat": 0
          },
          "2": {
              "sensor_id": 2,
              "children": {
                  "1": {
                      "id": 1,
                      "type": 0,
                      "description": "",
                      "values": {}
                  },
                  "2": {
                      "id": 2,
                      "type": 0,
                      "description": "",
                      "values": {}
                  },
                  "3": {
                      "id": 3,
                      "type": 0,
                      "description": "",
                      "values": {}
                  },
                  "4": {
                      "id": 4,
                      "type": 0,
                      "description": "",
                      "values": {}
                  },
                  "5": {
                      "id": 5,
                      "type": 0,
                      "description": "",
                      "values": {}
                  },
                  "6": {
                      "id": 6,
                      "type": 0,
                      "description": "",
                      "values": {}
                  }
              },
              "type": 18,
              "sketch_name": "Door Window Sns x6",
              "sketch_version": "1.0",
              "battery_level": 0,
              "protocol_version": "2.3.2",
              "heartbeat": 0
          }
      }
      
      posted in Troubleshooting
      pw44
      pw44
    • Unable to add node - more than 2

      Hya,

      i have a esp8266 gateway and had 2 nodes - one with 4 binary sensor (door/window) and one weather station

      Both nodes works very well with the gateway.

      By trying to add a 3rd node, did not work. the 3rd node, a 6 binary sensor (door/window).

      By last resource, i cheared the eeprom of all devices, 3 nodes and the gateway and flashed all again.

      Now, i have 4 binary sensor and 6 binary sensor recognized by the gateway and the weather station not being included.

      Yes, all are using the same radio channel.

      No, no hardware was modified.

      Is there any limitation?

      Any hint of what can be done?

      Thx in advance.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Node inclusion problem.

      @mfalkvidd may this problem be related with eeprom stored vars?

      i will clear the eeproms and flash gatewayand nodes again.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Node inclusion problem.

      This is what i have from GW:

      ⸮⸮⸮⸮⸮hlD⸮x⸮hT⸮76 MCO:BGN:INIT GW,CP=RNNGE---,FQ=80,REL=255,VER=2.3.2
      134 TSF:LRT:OK
      149 TSM:INIT
      163 TSF:WUR:MS=0
      186 TSM:INIT:TSP OK
      207 TSM:INIT:GW MODE
      229 TSM:READY:ID=0,PAR=0,DIS=0
      262 MCO:REG:NOT NEEDED
      scandone
      1367 GWT:TIN:CONNECTING...
      2396 GWT:TIN:CONNECTING...
      scandone
      state: 0 -> 2 (b0)
      4175 GWT:TIN:CONNECTING...
      state: 2 -> 3 (0)
      state: 3 -> 5 (10)
      add 0
      aid 5
      cnt 
      
      connected with Hirschberg, channel 1
      dhcp client start...
      ip:192.168.80.9,mask:255.255.255.0,gw:192.168.80.1
      4393 GWT:TIN:IP: 192.168.80.9
      4424 MCO:BGN:STP
      4442 MCO:BGN:INIT OK,TSP=1
      4471 TSM:READY:NWD REQ
      4498 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
      12252 GWT:TSA:C=0,CONNECTED
      pm open,type:2 0
      22390 GWT:RFC:C=0,MSG=0;255;3;0;2;
      32460 GWT:RFC:C=0,MSG=0;255;3;0;2;
      42660 GWT:RFC:C=0,MSG=0;255;3;0;2;
      52698 GWT:RFC:C=0,MSG=0;255;3;0;2;
      62829 GWT:RFC:C=0,MSG=0;255;3;0;2;
      72967 GWT:RFC:C=0,MSG=0;255;3;0;2;
      83002 GWT:RFC:C=0,MSG=0;255;3;0;2;
      93141 GWT:RFC:C=0,MSG=0;255;3;0;2;
      103175 GWT:RFC:C=0,MSG=0;255;3;0;2;
      

      no node being recognized

      and these are the arduino mini pro gpios being used

      #define BUTTON_PIN1  3                                // Arduino Digital I/O pin for button/reed switch
      #define BUTTON_PIN2  4                                // Arduino Digital I/O pin for button/reed switch
      #define BUTTON_PIN3  5                                // Arduino Digital I/O pin for button/reed switch
      #define BUTTON_PIN4  6                                // Arduino Digital I/O pin for button/reed switch
      #define BUTTON_PIN5  7                                // Arduino Digital I/O pin for button/reed switch
      #define BUTTON_PIN6  8                                 // Arduino Digital I/O pin for button/reed switch
      
      posted in Troubleshooting
      pw44
      pw44
    • RE: Node inclusion problem.

      @mfalkvidd ok, but does it have any influence by node being recognized by gateway?

      posted in Troubleshooting
      pw44
      pw44
    • RE: Node inclusion problem.

      @mfalkvidd well, neither my build gateway or the two working nodes have MY_NODE_ID and MY_PARENT_NODE_ID.

      in one of the posts, one user claimed not being able to include a node, but was able to do it by defining those https://forum.mysensors.org/post/36819.

      so, the question is if those are necessary by having the gateway and nodes, and how to use it?

      shall i define MY_NODE_ID 0 to the gateway and AUTO do the nodes, by MY_PARENT_NODE_ID, or MY_PARENT_NODE_ID 0 to the nodes?

      yes, maybe stupid questions, but i didn't realize, as i have one gateway and two nodes working and a third one not being registered, even with some nrf24l01 replaced.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Node inclusion problem.

      @mfalkvidd ok, i did, and did not understand how it works, that's why i asked.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Node inclusion problem.

      @mfalkvidd

      what are these for?

      #define MY_PARENT_NODE_ID 0

      #define MY_NODE_ID 21

      Thx!

      posted in Troubleshooting
      pw44
      pw44
    • RE: Node inclusion problem.

      @mfalkvidd with linux i'm very confortable... screen /dev/ttyUSB0 9600

      posted in Troubleshooting
      pw44
      pw44
    • RE: Node inclusion problem.

      @pw44 any hint in how to?

      posted in Troubleshooting
      pw44
      pw44
    • RE: nRF24Doctor

      Hya,

      correct me if i'm wrong.

      To make use of this, two units must be built. One for node and other for gateway.

      Is this undestanding correct? If not, how to use nRF24DoctorGateway and nRF24DoctorNode?

      Thx in advance.

      posted in My Project
      pw44
      pw44
    • RE: Node inclusion problem.

      @mfalkvidd the two other nodes are as close as this third, and are being recognized.

      How to get the gateway's log?

      by telnet gateway's ip 5003? or is there any other way without pluging to the arduino ide and opening the serial monitor for debug?

      Regarding "But it could be a problem with the radio or the antenna", it happened with 3 different nrf24l01 (no extendal antenna).

      Thx in advance

      posted in Troubleshooting
      pw44
      pw44
    • Node inclusion problem.

      Hya,

      some time ago i've built a 8266 gateway, a weather station and a binary sensor ( for 4 door/window) and it's working well.

      Today i´ve bult another binary sensor (door/window) with 6 sensors.

      But no way it get's recognized.

      The dbug output shows:

      __  __       ____
      |  \/  |_   _/ ___|  ___ _ __  ___  ___  _ __ ___
      | |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
      | |  | | |_| |___| |  __/ | | \__ \  _  | |  \__ \
      |_|  |_|\__, |____/ \___|_| |_|___/\___/|_|  |___/
              |___/                      2.3.2
      
      209 MCO:BGN:INIT REPEATER,CP=RNNRA---,FQ=16,REL=255,VER=2.3.2
      342 TSM:INIT
      355 TSF:WUR:MS=0
      377 TSM:INIT:TSP OK
      399 TSM:FPAR
      414 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      2492 !TSM:FPAR:NO REPLY
      2516 TSM:FPAR
      2533 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      4612 !TSM:FPAR:NO REPLY
      4636 TSM:FPAR
      4653 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      6731 !TSM:FPAR:NO REPLY
      6756 TSM:FPAR
      6772 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      8851 !TSM:FPAR:FAIL
      8871 TSM:FAIL:CNT=1
      8892 TSM:FAIL:DIS
      8911 TSF:TDI:TSL
      18930 TSM:FAIL:RE-INIT
      18954 TSM:INIT
      18975 TSM:INIT:TSP OK
      18998 TSM:FPAR
      19015 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      21095 !TSM:FPAR:NO REPLY
      21121 TSM:FPAR
      21138 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      23218 !TSM:FPAR:NO REPLY
      23243 TSM:FPAR
      23261 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      25341 !TSM:FPAR:NO REPLY
      25367 TSM:FPAR
      25384 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      27464 !TSM:FPAR:FAIL
      27486 TSM:FAIL:CNT=2
      27508 TSM:FAIL:DIS
      27528 TSF:TDI:TSL
      37548 TSM:FAIL:RE-INIT
      37571 TSM:INIT
      37593 TSM:INIT:TSP OK
      37615 TSM:FPAR
      37633 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      39712 !TSM:FPAR:NO REPLY
      39738 TSM:FPAR
      39755 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      41835 !TSM:FPAR:NO REPLY
      41861 TSM:FPAR
      41878 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      43958 !TSM:FPAR:NO REPLY
      43983 TSM:FPAR
      44001 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      46081 !TSM:FPAR:FAIL
      46102 TSM:FAIL:CNT=3
      46125 TSM:FAIL:DIS
      46144 TSF:TDI:TSL
      56164 TSM:FAIL:RE-INIT
      56187 TSM:INIT
      56209 TSM:INIT:TSP OK
      56231 TSM:FPAR
      56249 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      58329 !TSM:FPAR:NO REPLY
      58354 TSM:FPAR
      58372 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      60451 !TSM:FPAR:NO REPLY
      60477 TSM:FPAR
      60494 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      62574 !TSM:FPAR:NO REPLY
      62600 TSM:FPAR
      62617 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      64697 !TSM:FPAR:FAIL
      64718 TSM:FAIL:CNT=4
      64741 TSM:FAIL:DIS
      64760 TSF:TDI:TSL
      74781 TSM:FAIL:RE-INIT
      74805 TSM:INIT
      74826 TSM:INIT:TSP OK
      74849 TSM:FPAR
      74866 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      76946 !TSM:FPAR:NO REPLY
      76972 TSM:FPAR
      76989 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      79069 !TSM:FPAR:NO REPLY
      79094 TSM:FPAR
      79112 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      81192 !TSM:FPAR:NO REPLY
      81218 TSM:FPAR
      81235 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      83315 !TSM:FPAR:FAIL
      83337 TSM:FAIL:CNT=5
      83359 TSM:FAIL:DIS
      83379 TSF:TDI:TSL
      93399 TSM:FAIL:RE-INIT
      93422 TSM:INIT
      93444 TSM:INIT:TSP OK
      93466 TSM:FPAR
      93484 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      95563 !TSM:FPAR:NO REPLY
      95589 TSM:FPAR
      95606 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      97686 !TSM:FPAR:NO REPLY
      97712 TSM:FPAR
      97729 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      99809 !TSM:FPAR:NO REPLY
      99834 TSM:FPAR
      99852 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      101932 !TSM:FPAR:FAIL
      101954 TSM:FAIL:CNT=6
      101978 TSM:FAIL:DIS
      101998 TSF:TDI:TSL
      112020 TSM:FAIL:RE-INIT
      112045 TSM:INIT
      112067 TSM:INIT:TSP OK
      112091 TSM:FPAR
      112109 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      114191 !TSM:FPAR:NO REPLY
      114217 TSM:FPAR
      114236 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      116317 !TSM:FPAR:NO REPLY
      116343 TSM:FPAR
      116362 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      118443 !TSM:FPAR:NO REPLY
      118469 TSM:FPAR
      118488 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      120568 !TSM:FPAR:FAIL
      120591 TSM:FAIL:CNT=7
      

      as i understand, radio does not connect.

      The radio definitions are the same:

      
      // Enables and select radio type (if attached)
      #define MY_RADIO_RF24
      #define MY_RF24_PA_LEVEL   (RF24_PA_MAX)                                 // RF24_PA_MIN = -18dBm  RF24_PA_LOW = -12dBm RF24_PA_HIGH = -6dBm RF24_PA_MAX = 0dBm
      #define MY_RF24_CHANNEL   (1)  // RF channel for the sensor net, 0-125.  
      

      and gateway and this new device are 1 meter far fom another.

      Any hint of what could avoid the connection?

      The capacitor i've used for the nrf24l01 is a 10uF 25V

      Thx in advance.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Mysensors libray error - esp8266

      @pw44 downgraded ESP from 3.0.1 to 2.7.4 and issue is gone.

      posted in Troubleshooting
      pw44
      pw44
    • Mysensors libray error - esp8266

      Hya,

      i got the following errror while trying to compile the code:

      Sketch wird kompiliert...
      /home/paulo/.arduino15/packages/esp8266/tools/python3/3.7.2-post1/python3 /home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/signing.py --mode header --publickey /home/paulo/Arduino/Projects/PW/MySensors/GatewayESP8266-pw/public.key --out /tmp/arduino_build_767423/core/Updater_Signing.h
      /home/paulo/.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.0.0-newlib4.0.0-gnu23-48f7b08/bin/xtensa-lx106-elf-g++ -D__ets__ -DICACHE_FLASH -U__STRICT_ANSI__ -I/home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/sdk/include -I/home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/sdk/lwip2/include -I/home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/sdk/libc/xtensa-lx106-elf/include -I/tmp/arduino_build_767423/core -c -Os -g -free -fipa-pta -mlongcalls -mtext-section-literals -fno-rtti -falign-functions=4 -std=gnu++17 -MMD -ffunction-sections -fdata-sections -fno-exceptions -DMMU_IRAM_SIZE=0x8000 -DMMU_ICACHE_SIZE=0x8000 -DNONOSDK22x_190703=1 -DF_CPU=80000000L -DLWIP_OPEN_SRC -DTCP_MSS=536 -DLWIP_FEATURES=1 -DLWIP_IPV6=0 -DARDUINO=10813 -DARDUINO_ESP8266_WEMOS_D1MINIPRO -DARDUINO_ARCH_ESP8266 "-DARDUINO_BOARD=\"ESP8266_WEMOS_D1MINIPRO\"" -DFLASHMODE_DIO -DESP8266 -I/home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/cores/esp8266 -I/home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/variants/d1_mini -I/home/paulo/Arduino/Projects/libraries/MySensors -I/home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/libraries/SPI -I/home/paulo/Arduino/Projects/libraries/ESP8266WiFi/src -I/home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/libraries/EEPROM /tmp/arduino_build_767423/sketch/GatewayESP8266-pw.ino.cpp -o /tmp/arduino_build_767423/sketch/GatewayESP8266-pw.ino.cpp.o
      In file included from /home/paulo/.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.0.0-newlib4.0.0-gnu23-48f7b08/xtensa-lx106-elf/include/assert.h:10,
                       from /home/paulo/.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.0.0-newlib4.0.0-gnu23-48f7b08/xtensa-lx106-elf/include/sys/reent.h:503,
                       from /home/paulo/.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.0.0-newlib4.0.0-gnu23-48f7b08/xtensa-lx106-elf/include/stdlib.h:18,
                       from /home/paulo/.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.0.0-newlib4.0.0-gnu23-48f7b08/xtensa-lx106-elf/include/c++/10.2.0/cstdlib:75,
                       from /home/paulo/.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.0.0-newlib4.0.0-gnu23-48f7b08/xtensa-lx106-elf/include/c++/10.2.0/stdlib.h:36,
                       from /home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/cores/esp8266/Arduino.h:27,
                       from /tmp/arduino_build_767423/sketch/GatewayESP8266-pw.ino.cpp:1:
      /home/paulo/Arduino/Projects/libraries/MySensors/core/MyProtocol.cpp: In function 'char* protocolMyMessage2Serial(MyMessage&)':
      /home/paulo/Arduino/Projects/libraries/MySensors/core/MyProtocol.cpp:94:28: error: expected ')' before '__INT8'
         94 |                   PSTR("%" PRIu8 ";%" PRIu8 ";%" PRIu8 ";%" PRIu8 ";%" PRIu8 ";%s\n"), message.getSender(),
            |                            ^~~~~
      /home/paulo/Arduino/Projects/libraries/MySensors/core/MyProtocol.cpp:94:19: note: to match this '('
         94 |                   PSTR("%" PRIu8 ";%" PRIu8 ";%" PRIu8 ";%" PRIu8 ";%" PRIu8 ";%s\n"), message.getSender(),
            |                   ^~~~
      /home/paulo/Arduino/Projects/libraries/MySensors/core/MyProtocol.cpp: In function 'char* protocolMyMessage2MQTT(const char*, MyMessage&)':
      /home/paulo/Arduino/Projects/libraries/MySensors/core/MyProtocol.cpp:103:31: error: expected ')' before '__INT8'
        103 |                   PSTR("%s/%" PRIu8 "/%" PRIu8 "/%" PRIu8 "/%" PRIu8 "/%" PRIu8 ""), prefix,
            |                               ^~~~~
      /home/paulo/Arduino/Projects/libraries/MySensors/core/MyProtocol.cpp:103:19: note: to match this '('
        103 |                   PSTR("%s/%" PRIu8 "/%" PRIu8 "/%" PRIu8 "/%" PRIu8 "/%" PRIu8 ""), prefix,
            |                   ^~~~
      Mehrere Bibliotheken wurden für "ESP8266WiFi.h" gefunden
       Benutzt: /home/paulo/Arduino/Projects/libraries/ESP8266WiFi
       Nicht benutzt: /home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/libraries/ESP8266WiFi
      Mehrere Bibliotheken wurden für "EEPROM.h" gefunden
       Benutzt: /home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/libraries/EEPROM
       Nicht benutzt: /home/paulo/Arduino/Projects/libraries/EEPROM
      Bibliothek MySensors in Version 2.3.2 im Ordner: /home/paulo/Arduino/Projects/libraries/MySensors  wird verwendet
      Bibliothek SPI in Version 1.0 im Ordner: /home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/libraries/SPI  wird verwendet
      Bibliothek ESP8266WiFi in Version 1.0 im Ordner: /home/paulo/Arduino/Projects/libraries/ESP8266WiFi  wird verwendet
      Bibliothek EEPROM in Version 1.0 im Ordner: /home/paulo/.arduino15/packages/esp8266/hardware/esp8266/3.0.0/libraries/EEPROM  wird verwendet
      exit status 1
      Fehler beim Kompilieren für das Board LOLIN(WEMOS) D1 mini Pro.
      

      anyone aware of what it can be?

      thx in advance.

      posted in Troubleshooting
      pw44
      pw44
    • ESP8266 nRF24L01 Gateway - photos of the finished device

      IMG_6623.JPG

      IMG_6624.JPG

      IMG_6633.JPG

      IMG_6633.JPG

      IMG_6632.JPG

      posted in My Project
      pw44
      pw44
    • RE: Which pins should I use for status led on a wemos d1 mini gateway

      @pw44 and so, my first assbled gateway looks like:

      IMG_6624.JPG

      IMG_6623.JPG

      IMG_6634.JPG

      IMG_6633.JPG

      IMG_6632.JPG

      Now i will try a more robust version, with external antenna.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Which pins should I use for status led on a wemos d1 mini gateway

      @BearWithBeard exactly what i was looking for, the pin mapping for D1 MINI.

      Thx!

      posted in Troubleshooting
      pw44
      pw44
    • RE: Which pins should I use for status led on a wemos d1 mini gateway

      @mfalkvidd thx for answering.

      i was looking for the correct mapping for:

      #define MY_DEFAULT_ERR_LED_PIN D0 // Error led pin
      #define MY_DEFAULT_RX_LED_PIN D3 // Receive led pin
      #define MY_DEFAULT_TX_LED_PIN D4 // Transmit led pin

      thx to your hint, D0 =16, D3 = 0, D4 = 2.

      So, i shall change to:

      #define MY_DEFAULT_ERR_LED_PIN 16 // Error led pin
      #define MY_DEFAULT_RX_LED_PIN 0 // Receive led pin
      #define MY_DEFAULT_TX_LED_PIN 2 // Transmit led pin

      posted in Troubleshooting
      pw44
      pw44
    • RE: Which pins should I use for status led on a wemos d1 mini gateway

      @BearWithBeard could you please confirm the correct definitions for the pins?

      #define MY_DEFAULT_ERR_LED_PIN 3 // D0 Error led pin
      #define MY_DEFAULT_RX_LED_PIN 5 // D3 Receive led pin
      #define MY_DEFAULT_TX_LED_PIN 4 // D4 Transmit led pin

      D1 = pin 1
      D3 = pin 5
      D4 = pin 4
      D0 = pin 3

      is this correct?

      thx in advance.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Which pins should I use for status led on a wemos d1 mini gateway

      @BearWithBeard said in Which pins should I use for status led on a wemos d1 mini gateway:

      @pw44 No, this isn't a good idea. You should have all status LEDs in either source or sink configuration, or some LEDs will be inverted (lit by default, off when there is activity).

      D3 and D4 must to be connected like this to not prevent the ESP from booting: GPIO - Resistor - LED cathode - LED anode - VCC. D0 should be connected equally, even if it doesn't matter for the ESP's functionality.

      Besides that, if you don't use I2C, you should also be able to use D1 (GPIO5) and D2 (GPIO4) for status LEDs, inclusion mode button, etc.

      Thank you so much for your answer. Helped me a lot.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Which pins should I use for status led on a wemos d1 mini gateway

      @BearWithBeard

      Just make sure to connect them to VCC, not GND. If either D3 or D4 are pulled low, the ESP won't boot.

      So, D0 to led anode and led cathode to resistor to gnd, correct?

      posted in Troubleshooting
      pw44
      pw44
    • RE: Which pins should I use for status led on a wemos d1 mini gateway

      @Danielo-Rodríguez good question, i'm also looking for it.

      I used D1 for include button.
      #define MY_INCLUSION_MODE_BUTTON_PIN D1

      Tried

      #define MY_DEFAULT_ERR_LED_PIN D0 // 3 // Error led pin
      #define MY_DEFAULT_RX_LED_PIN D3 // 5 // Receive led pin
      #define MY_DEFAULT_TX_LED_PIN D4 // 4 // Transmit led pin

      But did not succeed.

      posted in Troubleshooting
      pw44
      pw44
    • RE: PIR with no interrupt - doubts.

      @Yveaux Thx for the hint! BR

      posted in Troubleshooting
      pw44
      pw44
    • RE: PIR with no interrupt - doubts.

      @Sasquatch

      got it working like, but there is problem: every time it's triggered, motion detected - motion ended and a second time motion detected - motion ended. not finding out why it's triggered a second time.

      // Enable debug prints to serial monitor
      #define MY_DEBUG
      
      // Enable debug prints
      //#define MY_BAUD_RATE 9600
      
      // Enable and select radio type attached
      #define MY_RADIO_RF24
      #define MY_RF24_PA_LEVEL   RF24_PA_HIGH                                 // RF24_PA_MIN = -18dBm  RF24_PA_LOW = -12dBm RF24_PA_HIGH = -6dBm RF24_PA_MAX = 0dBm
      //#define MY_RF24_CHANNEL   (76)  // RF channel for the sensor net, 0-125.  //  0 => 2400 Mhz (RF24 channel 1)
                                                                                  //  1 => 2401 Mhz (RF24 channel 2)
                                                                                  // 76 => 2476 Mhz (RF24 channel 77)
                                                                                  // 83 => 2483 Mhz (RF24 channel 84)
                                                                                  // 124 => 2524 Mhz (RF24 channel 125)
                                                                                  // 125 => 2525 Mhz (RF24 channel 126)
      //#define MY_RF24_BASE_RADIO_ID   0x00,0xFC,0xE1,0xA8,0xA8
      //#define MY_RF24_DATARATE   (RF24_250KBPS)                                 // RF24_250KBPS for 250kbs  RF24_1MBPS for 1Mbps  RF24_2MBPS for 2Mbps.
      //#define MY_RF24_SPI_SPEED   (2*1000000ul)                                 // Define this if you need to run the SPI clock at a different frequency than the default. Default nRF24L01+ SPI speed, 2MHz should be safe for nRF24L01+ clones.
      //#define MY_DEBUG_VERBOSE_RF24
      //#define MY_RADIO_RFM69
      
      #include <MySensors.h>
      
      // Node and sketch information
      #define SKETCH_VER            "1.0"				                  // Sketch version
      #define SKETCH_NAME           "Motion Sensor NoINterrupt"		// Optional child sensor name
      #define CHILD_ID              1				                    	// Id of the sensor child
      #define CHILD_NAME            "Motion Sensor NI"	        	// Optional child sensor name
      #define NODE_REPEATER         false		        	          	// Set true if a repeater node (i.e. always turned on) 
      
      int PIRpin   = 3;      // The digital input you attached your motion sensor.  (Only 2 and 3 generates interrupt!)
      int LEDpin   = 13;
      int PIRstate = LOW;    // we start, assuming no motion detected
      int value    = 0;      // variable for reading the pin status
      int PIRsold  = 0;
      
      // Initialize motion message
      MyMessage msgPIR(CHILD_ID, V_TRIPPED);
      
      
      void setup()
      {
          pinMode(LEDpin, OUTPUT);    // declare LED as output
          pinMode(PIRpin, INPUT);     // declare sensor as input
      }
      
      void presentation()
      {
        sendSketchInfo(SKETCH_NAME, SKETCH_VER);  
        present(CHILD_ID, S_MOTION);
      }
      
      void loop(){
      
        value = digitalRead(PIRpin);   // read input value
        if (value == HIGH) {           // check if the input is HIGH
          digitalWrite(LEDpin, HIGH);  // turn LED ON
          if (PIRstate == LOW) {
            Serial.println("Motion detected!");
            send(msgPIR.set(1));
            PIRstate = HIGH;
          }
        } else {
          digitalWrite(LEDpin, LOW);   // turn LED OFF
          if (PIRstate == HIGH){
            Serial.println("Motion ended!");
            send(msgPIR.set(0));
            PIRstate = LOW;
          }
        }
      }
      

      Thx for the help.

      posted in Troubleshooting
      pw44
      pw44
    • PIR with no interrupt - doubts.

      Hi All,

      i'm trying to make my motion sensor work, without using interrupt.

      / Enable debug prints to serial monitor
      #define MY_DEBUG
      
      // Enable debug prints
      #define MY_BAUD_RATE 9600
      
      // Enable and select radio type attached
      #define MY_RADIO_RF24
      #define MY_RF24_PA_LEVEL   RF24_PA_HIGH                                 // RF24_PA_MIN = -18dBm  RF24_PA_LOW = -12dBm RF24_PA_HIGH = -6dBm RF24_PA_MAX = 0dBm
      //#define MY_RF24_CHANNEL   (76)  // RF channel for the sensor net, 0-125.  //  0 => 2400 Mhz (RF24 channel 1)
                                                                                  //  1 => 2401 Mhz (RF24 channel 2)
                                                                                  // 76 => 2476 Mhz (RF24 channel 77)
                                                                                  // 83 => 2483 Mhz (RF24 channel 84)
                                                                                  // 124 => 2524 Mhz (RF24 channel 125)
                                                                                  // 125 => 2525 Mhz (RF24 channel 126)
      //#define MY_RF24_BASE_RADIO_ID   0x00,0xFC,0xE1,0xA8,0xA8
      //#define MY_RF24_DATARATE   (RF24_250KBPS)                                 // RF24_250KBPS for 250kbs  RF24_1MBPS for 1Mbps  RF24_2MBPS for 2Mbps.
      //#define MY_RF24_SPI_SPEED   (2*1000000ul)                                 // Define this if you need to run the SPI clock at a different frequency than the default. Default nRF24L01+ SPI speed, 2MHz should be safe for nRF24L01+ clones.
      //#define MY_DEBUG_VERBOSE_RF24
      //#define MY_RADIO_RFM69
      
      #include <MySensors.h>
      
      // Node and sketch information
      #define SKETCH_VER            "1.0"				        // Sketch version
      #define SKETCH_NAME           "Motion Sensor NoINterrupt"		// Optional child sensor name
      #define CHILD_ID              1				           	// Id of the sensor child
      #define CHILD_NAME            "Motion Sensor NI"		// Optional child sensor name
      #define NODE_REPEATER         false		        	  	// Set true if a repeater node (i.e. always turned on) 
      
      int PIRpin   = 3;   // The digital input you attached your motion sensor.  (Only 2 and 3 generates interrupt!)
      int LEDpin   = 13;
      int PIRstate = LOW;             // we start, assuming no motion detected
      int value    = 0;                    // variable for reading the pin status
      
      // Initialize motion message
      MyMessage msg(CHILD_ID, V_TRIPPED);
      
      
      void setup()
      {
          pinMode(LEDpin, OUTPUT);      // declare LED as output
          pinMode(PIRpin, INPUT);     // declare sensor as input
      }
      
      void presentation()
      {
        sendSketchInfo(SKETCH_NAME, SKETCH_VER);  
        present(CHILD_ID, S_MOTION);
      }
      
      void loop(){
        value = digitalRead(PIRpin);   // read input value
        if (value == HIGH) {           // check if the input is HIGH
          digitalWrite(LEDpin, HIGH);  // turn LED ON
          if (PIRstate == LOW) {
            // we have just turned on
            Serial.println("Motion detected!");
            send(msg.set(PIRstate==LOW ? 1 : 0));
            // We only want to print on the output change, not state
            PIRstate = HIGH;
          }
        } else {
          digitalWrite(LEDpin, LOW); // turn LED OFF
          if (PIRstate == HIGH){
            // we have just turned of
            Serial.println("Motion ended!");
            send(msg.set(PIRstate==HIGH ? 1 : 0));
            // We only want to print on the output change, not state
            PIRstate = LOW;
          }
        }
      }
      

      but what worked before (without mysensor) is not working anymore. and the Serial.println shows nothing.

      Any hint in how to debug with the Serial.println?

      It compiles with no error, but does not work.

      Thx in advance

      posted in Troubleshooting
      pw44
      pw44
    • RE: gw.sendVariable - library question

      @boum thx, man. i was in doubt, so you confirmed that it's deprecated.

      i was following the code:

      void loop() {     
        // Read digital motion value
        boolean motion = digitalRead( DIGITAL_INPUT_SENSOR ) == LOW; 
      
        // Send debug output to serial monitor
        mprintln(PSTR("Motion sensor %s"), motion ? "ON" : "OFF" );
      
        if (lastMotion != motion) {
          lastMotion = motion;
      
          // Send motion value to sensor
          gw.send( msg.set( motion ? "1" : "0" ) );
        
          if (motion) {
            gw.sleep( SLEEP_TIME );
          }
        }
        
        gw.sleep( INTERRUPT, CHANGE, SLEEP_TIME );
      }
      

      to use the motion sensor without interrupt (pin 2 or 3).

      posted in Development
      pw44
      pw44
    • gw.sendVariable - library question

      Hi,

      getting an example, gw.sendVariable was not recognized and i could not find it.

      Any hint?

      posted in Development
      pw44
      pw44
    • converting a project to mysensors.

      Hi All,

      i have a working project for a curtain controller, which uses a stepper and light sensor, being able to be set to auto, close, open and pause.

      I would like to retrofit it, being able to be used by mysensors.

      Anyone interested to help?

      Thx in advance.

      posted in My Project
      pw44
      pw44
    • RE: Two gateways and nodes

      @mfalkvidd Thx for the reply. It makes sense.

      posted in General Discussion
      pw44
      pw44
    • Two gateways and nodes

      Hi All,

      having two gateways and multiple nodes (with sensors) how to link node A to gateway 1 and node B to gateway 2, i.e.?

      Thx in advance for any help.

      posted in General Discussion
      pw44
      pw44
    • RE: Framework multi sensor/actuator

      any update? did it evolved? Thx in advance.

      posted in My Project
      pw44
      pw44
    • RE: Ethernet Gateway - W5100 - stops responding to sensor and server

      @NeoX i gave up the w5100 gateway (uno r3 + w5100 shiled + NRF24L01+PA-LNA).

      the gateway with NRF24L01+ and Wemos D1 mini is working flawlessly the last two days - so, it will be the way to go.

      posted in Troubleshooting
      pw44
      pw44
    • V_ARMED vs V_TRIPPED questions.

      Re: A few random questions (V_tripped vs V_armed)

      i have a door sensor, and an defined MyMessage msg(CHILD_ID,V_TRIPPED);

      It notifies me wether the door is open or not.

      How can it also be connected to the alarm, in order that:

      1. alarm unarmed and being home, only notify that door is open or not.
      2. alarm armed and being away or not, notifies that door is open or not and in case of open, also activates the alarm.

      how to use V_TRIPPED and V_ARMED?

      Thx in advance

      posted in Development
      pw44
      pw44
    • API questions regarding Home Assistant Core.

      Dear All,

      digging the various fori, i did not find que concrete answers, so i'm posting this to be sure about the understanding.

      The node sketch shall make use of these defs for HA. Is it right?

      // Node and sketch information
      #define SKETCH_VER "0.2" // Sketch version
      #define SKETCH_NAME "SwitchSensor" // Optional node name
      #define CHILD_ID 3 // Id of the sensor child
      #define CHILD_NAME "DoorWindowSensor" // Optional child sensor name
      #define NODE_REPEATE false // Set true if a repeater node (i.e. always turned on)
      #define BUTTON_PIN 3 // Arduino Digital I/O pin for button/reed switch

      As i understood:

      • sketch_name - how it will identify itself for HA
      • child_id - the sensor of this node (i.e. the gpio where the sensor is connected to)
      • child_name - the name for this chid_id

      So, on a node sensor, i can have from 0 to 255 child_id's, each with it's name. But how to give a name for each child, if more than one sensor is connected to the node?

      Is this all right? if not, please educate me in the right way.

      And i'm also getting the following:

      This entity does not have a unique ID, therefore its settings cannot be managed from the UI.

      Any hint?

      posted in Home Assistant
      pw44
      pw44
    • Mysensors Node not being recognized (added)

      Hi All,

      i have HA Core and mysensors gateway + one mysensors door sensor node.

      I simply not finding out how to add the node to be monitored.

      Log debug shows:

      root@wolke:/var/homeassistant/homeassistant# cat home-assistant.log 
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up http
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.2 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up system_log
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.1 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 1: {'cloud', 'alexa', 'auth', 'frontend', 'websocket_api', 'config', 'system_log', 'person', 'lovelace', 'device_automation', 'search', 'webhook', 'onboarding', 'api', 'http'}
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up person
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up lovelace
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up device_automation
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up alexa
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up auth
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up config
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain device_automation took 0.1 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up webhook
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up api
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain alexa took 0.0 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.0 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.0 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.0 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.1 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.0 seconds.
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up search
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain search took 0.0 seconds.
      2020-07-06 08:47:01 INFO (SyncWorker_2) [homeassistant.loader] Loaded camera from homeassistant.components.camera
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setup of domain person took 0.1 seconds.
      2020-07-06 08:47:01 INFO (SyncWorker_4) [homeassistant.loader] Loaded google_assistant from homeassistant.components.google_assistant
      2020-07-06 08:47:01 INFO (SyncWorker_2) [homeassistant.loader] Loaded media_player from homeassistant.components.media_player
      2020-07-06 08:47:01 INFO (MainThread) [homeassistant.setup] Setting up onboarding
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up cloud
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain onboarding took 0.7 seconds.
      2020-07-06 08:47:02 INFO (SyncWorker_8) [homeassistant.loader] Loaded device_tracker from homeassistant.components.device_tracker
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.0 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up frontend
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 0.0 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'default_config', 'input_number', 'input_select', 'zeroconf', 'mysensors', 'updater', 'group', 'scene', 'tts', 'ipp', 'logbook', 'automation', 'zone', 'geo_location', 'sun', 'history', 'system_health', 'nextcloud', 'script', 'mobile_app', 'ssdp', 'input_text', 'mqtt', 'input_datetime', 'map', 'input_boolean', 'upnp', 'met'}
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up input_number
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up input_select
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up updater
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up group
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up scene
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up automation
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up zone
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up sun
      2020-07-06 08:47:02 INFO (SyncWorker_11) [homeassistant.loader] Loaded geo_json_events from homeassistant.components.geo_json_events
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up nextcloud
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up script
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up input_text
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up input_datetime
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up input_boolean
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up met
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up geo_location
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 0.1 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain group took 0.1 seconds.
      2020-07-06 08:47:02 INFO (SyncWorker_7) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up logbook
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 0.1 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.1 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up history
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up system_health
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain script took 0.1 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up map
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain met took 0.1 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.components.geo_location] Setting up geo_location.geo_json_events
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up zeroconf
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain geo_location took 0.1 seconds.
      2020-07-06 08:47:02 INFO (SyncWorker_13) [homeassistant.loader] Loaded google_translate from homeassistant.components.google_translate
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up ipp
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.1 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain system_health took 0.1 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up mobile_app
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up mqtt
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain map took 0.1 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain scene took 0.2 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain input_number took 0.2 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain input_select took 0.2 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain input_text took 0.2 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain input_datetime took 0.2 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain input_boolean took 0.2 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.1 seconds.
      2020-07-06 08:47:02 INFO (SyncWorker_8) [homeassistant.loader] Loaded weather from homeassistant.components.weather
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up tts
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up upnp
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain ipp took 0.1 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.2 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain mqtt took 0.0 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up weather
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 0.2 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.updater
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain weather took 0.0 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain mobile_app took 0.1 seconds.
      2020-07-06 08:47:02 INFO (SyncWorker_3) [homeassistant.loader] Loaded notify from homeassistant.components.notify
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.components.weather] Setting up weather.met
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain upnp took 0.0 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up notify
      2020-07-06 08:47:02 WARNING (zeroconf-ServiceBrowser__elg._tcp.local.-_ipps._tcp.local.-_miio._udp.local.-_googlecast._tcp.local.-_api._udp.local.-_daap._tcp.local.-_esphomelib._tcp.local.-_printer._tcp.local.-_nut._tcp.local.-_spotify-connect._tcp.local.-_dkapi._tcp.local.-_ipp._tcp.local.-_axis-video._tcp.local.-_hap._tcp.local.-_wled._tcp.local.-_viziocast._tcp.local._140061348976384) [zeroconf] Error sending through socket 12
      Traceback (most recent call last):
        File "/var/homeassistant/lib/python3.7/site-packages/zeroconf/__init__.py", line 2792, in send
          bytes_sent = s.sendto(packet, 0, (real_addr, port))
      OSError: [Errno 126] Required key not available
      2020-07-06 08:47:02 INFO (Thread-5) [homeassistant.components.mqtt] Connected to MQTT server wolke.wollny.com.br:1883 (0)
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mobile_app
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain notify took 0.0 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain zeroconf took 0.2 seconds.
      2020-07-06 08:47:02 INFO (SyncWorker_18) [homeassistant.loader] Loaded sensor from homeassistant.components.sensor
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up device_tracker
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 0.1 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up sensor
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.components.notify] Setting up notify.mobile_app
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up ssdp
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 0.0 seconds.
      2020-07-06 08:47:02 INFO (SyncWorker_5) [homeassistant.loader] Loaded brother from homeassistant.components.brother
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setting up mysensors
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain device_tracker took 0.1 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.setup] Setup of domain ssdp took 0.0 seconds.
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mobile_app
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.ipp
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.mobile_app
      2020-07-06 08:47:02 INFO (MainThread) [homeassistant.components.sensor] Not adding entity HP LaserJet 1010 - CUPS+Gutenprint v5.2.13 Uptime because it's disabled
      2020-07-06 08:47:03 WARNING (SyncWorker_9) [mysensors.persistence] File does not exist or is not readable: /var/homeassistant/.homeassistant/mysensors.json
      2020-07-06 08:47:03 INFO (MainThread) [homeassistant.setup] Setting up default_config
      2020-07-06 08:47:03 WARNING (SyncWorker_9) [mysensors.persistence] Trying backup file: /var/homeassistant/.homeassistant/mysensors.json.bak
      2020-07-06 08:47:03 WARNING (SyncWorker_9) [mysensors.persistence] File does not exist or is not readable: /var/homeassistant/.homeassistant/mysensors.json.bak
      2020-07-06 08:47:03 WARNING (SyncWorker_9) [mysensors.persistence] Failed to load sensors from file: /var/homeassistant/.homeassistant/mysensors.json
      2020-07-06 08:47:03 DEBUG (SyncWorker_7) [mysensors.persistence] Saving sensors to persistence file /var/homeassistant/.homeassistant/mysensors.json
      2020-07-06 08:47:03 INFO (MainThread) [homeassistant.setup] Setup of domain default_config took 0.0 seconds.
      2020-07-06 08:47:03 INFO (MainThread) [homeassistant.setup] Setup of domain mysensors took 0.5 seconds.
      2020-07-06 08:47:03 INFO (MainThread) [mysensors.gateway_tcp] Trying to connect to ('192.168.80.9', 5003)
      2020-07-06 08:47:03 INFO (MainThread) [mysensors] Connected to <_SelectorSocketTransport fd=23 read=polling write=<idle, bufsize=0>>
      2020-07-06 08:47:03 DEBUG (MainThread) [mysensors] Receiving 0;255;3;0;14;Gateway startup complete.
      2020-07-06 08:47:03 INFO (MainThread) [mysensors.handler] n:0 c:255 t:3 s:14 p:Gateway startup complete.
      2020-07-06 08:47:03 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] Node update: node 0 child 255
      2020-07-06 08:47:03 DEBUG (MainThread) [mysensors] Receiving 0;255;0;0;18;2.3.2
      2020-07-06 08:47:03 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] Node update: node 0 child 255
      2020-07-06 08:47:03 INFO (MainThread) [homeassistant.components.updater] Submitted analytics to Home Assistant servers. Information submitted includes {}
      2020-07-06 08:47:04 INFO (MainThread) [homeassistant.setup] Setup of domain nextcloud took 1.7 seconds.
      2020-07-06 08:47:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.nextcloud
      2020-07-06 08:47:04 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.nextcloud
      2020-07-06 08:47:12 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.upnp
      2020-07-06 08:47:12 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 11.66s
      2020-07-06 08:47:12 INFO (MainThread) [homeassistant.core] Starting Home Assistant
      2020-07-06 08:47:12 INFO (SyncWorker_6) [homeassistant.components.zeroconf] Starting Zeroconf broadcast
      2020-07-06 08:47:13 DEBUG (SyncWorker_17) [mysensors.persistence] Saving sensors to persistence file /var/homeassistant/.homeassistant/mysensors.json
      2020-07-06 08:47:13 DEBUG (MainThread) [mysensors] Sending 0;255;3;0;2;
      2020-07-06 08:47:13 DEBUG (MainThread) [mysensors] Receiving 0;255;3;0;2;2.3.2
      2020-07-06 08:47:14 INFO (MainThread) [homeassistant.core] Timer:starting
      2020-07-06 08:47:23 DEBUG (MainThread) [mysensors] Sending 0;255;3;0;2;
      2020-07-06 08:47:23 DEBUG (MainThread) [mysensors] Receiving 0;255;3;0;2;2.3.2
      2020-07-06 08:47:33 DEBUG (MainThread) [mysensors] Sending 0;255;3;0;2;
      2020-07-06 08:47:33 DEBUG (MainThread) [mysensors] Receiving 0;255;3;0;2;2.3.2
      2020-07-06 08:47:43 DEBUG (MainThread) [mysensors] Sending 0;255;3;0;2;
      2020-07-06 08:47:43 DEBUG (MainThread) [mysensors] Receiving 0;255;3;0;2;2.3.2
      2020-07-06 08:47:53 DEBUG (MainThread) [mysensors] Sending 0;255;3;0;2;
      2020-07-06 08:47:53 DEBUG (MainThread) [mysensors] Receiving 0;255;3;0;2;2.3.2
      2020-07-06 08:48:03 DEBUG (MainThread) [mysensors] Sending 0;255;3;0;2;
      2020-07-06 08:48:04 DEBUG (MainThread) [mysensors] Receiving 0;255;3;0;2;2.3.2
      
      

      mysensors.json shows:

      root@wolke:/var/homeassistant/homeassistant# cat mysensors.json 
      {
          "0": {
              "sensor_id": 0,
              "children": {},
              "type": 18,
              "sketch_name": null,
              "sketch_version": null,
              "battery_level": 0,
              "protocol_version": "2.3.2",
              "heartbeat": 0
          }
      
      

      What am i missing in order to have UI showing the node?

      Thx in advance

      posted in Home Assistant
      pw44
      pw44
    • RE: NRF24L01+ and NRF24L01+PA-LNA problems - testing in progress

      @monte thx for your answer.

      which kind of gateway do you have? serial, rj45 or wifi?

      the problem i had with all 4 NRF24L01 PA LNA i have.

      posted in Troubleshooting
      pw44
      pw44
    • RE: NRF24L01+ and NRF24L01+PA-LNA problems - testing in progress

      @pw44 - well, today i dismantled both gateways and built the ESP8266 (Wemos D1 mini) with NRF24L01+ (board antenna) and a sensor (door) with a nano v3 with NRF24L01+ (board antenna).

      working with no problem until now.

      seams that NRF24L01+ (board antenna) to NRF24L01+ PA LNA does not work as expected......

      Will continue testing and post the results.

      posted in Troubleshooting
      pw44
      pw44
    • NRF24L01+ and NRF24L01+PA-LNA problems - testing in progress

      Hi all,

      i found this link:

      https://medium.com/@alencarrebeca/working-with-nrf24l01-communicating-with-nrf24l01-pa-na-b1466b4f3223

      It seams to explain some of the problems i'm having.

      Can anyone confirm this?

      Thank you in advance.

      posted in Troubleshooting
      pw44
      pw44
    • Ethernet Gateway - W5100 - stops responding to sensor and server

      Hi All,

      after building the gateway with the w5100 shield + Uno R3 + NRF24L01, it starts, i can telnet to it, it responds.

      Power supply is a 9V 1A feeding the Uno

      After a while, it becomes unresponsive, telnet does not work, but it responds to pings.

      Also extended with the leds for error, tx and rx, but these does not work.

      Any hint what can be happening?

      Thx in advance.

      posted in Troubleshooting
      pw44
      pw44
    • Problems with Nano + W5100 (funduino) + NRF24L01 gateway - no access.

      Hi,

      i built the following:

      IMG_6545.JPG
      IMG_6546.JPG
      IMG_6547.JPG
      IMG_6548.JPG
      IMG_6549.JPG
      IMG_6550.JPG
      IMG_6551.JPG

      With the following code:

      // Enable debug prints to serial monitor
      #define MY_DEBUG
      
      // Enable and select radio type attached
      #define MY_RADIO_RF24
      //#define MY_RADIO_NRF5_ESB
      //#define MY_RADIO_RFM69
      //#define MY_RADIO_RFM95
      
      // Enable gateway ethernet module type
      #define MY_GATEWAY_W5100
      
      // W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
      //#define MY_W5100_SPI_EN 4
      
      // Enable Soft SPI for NRF radio (note different radio wiring is required)
      // The W5100 ethernet module seems to have a hard time co-operate with
      // radio on the same spi bus.
      #if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
      #define MY_SOFTSPI
      #define MY_SOFT_SPI_SCK_PIN 14
      #define MY_SOFT_SPI_MISO_PIN 16
      #define MY_SOFT_SPI_MOSI_PIN 15
      #endif
      
      // When W5100 is connected we have to move CE/CSN pins for NRF radio
      #ifndef MY_RF24_CE_PIN
      #define MY_RF24_CE_PIN 5
      #endif
      #ifndef MY_RF24_CS_PIN
      #define MY_RF24_CS_PIN 6
      #endif
      
      // Enable UDP communication
      //#define MY_USE_UDP  // If using UDP you need to set MY_CONTROLLER_IP_ADDRESS or MY_CONTROLLER_URL_ADDRESS below
      
      // Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
      #define MY_IP_ADDRESS 192,168,80,15
      
      // If using static ip you can define Gateway and Subnet address as well
      //#define MY_IP_GATEWAY_ADDRESS 192,168,80,1
      #define MY_IP_SUBNET_ADDRESS 255,255,255,0
      
      // Renewal period if using DHCP
      //#define MY_IP_RENEWAL_INTERVAL 60000
      
      // The port to keep open on node server mode / or port to contact in client mode
      #define MY_PORT 5003
      
      // Controller ip address. Enables client mode (default is "server" mode).
      // Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
      //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 254
      //#define MY_CONTROLLER_URL_ADDRESS "my.controller.org"
      
      // The MAC address can be anything you want but should be unique on your network.
      // Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use.
      // Note that most of the Arduino examples use  "DEAD BEEF FEED" for the MAC address.
      #define MY_MAC_ADDRESS 0x00, 0x40, 0xFD, 0xEF, 0x35, 0x76
      
      
      // Enable inclusion mode
      #define MY_INCLUSION_MODE_FEATURE
      // Enable Inclusion mode button on gateway
      #define MY_INCLUSION_BUTTON_FEATURE
      // Set inclusion mode duration (in seconds)
      #define MY_INCLUSION_MODE_DURATION 60
      // Digital pin used for inclusion mode button
      #define MY_INCLUSION_MODE_BUTTON_PIN  3
      
      // Set blinking period
      #define MY_DEFAULT_LED_BLINK_PERIOD 300
      
      // Flash leds on rx/tx/err
      // Uncomment to override default HW configurations
      #define MY_DEFAULT_ERR_LED_PIN 7  // Error led pin
      #define MY_DEFAULT_RX_LED_PIN  8  // Receive led pin
      #define MY_DEFAULT_TX_LED_PIN  9  // Transmit led pin
      
      #if defined(MY_USE_UDP)
      #include <EthernetUdp.h>
      #endif
      #include <SPI.h>
      #include <Ethernet.h>
      #include <MySensors.h>
      
      void setup()
      {
        // Setup locally attached sensors
      }
      
      void presentation()
      {
        // Present locally attached sensors here
      }
      
      void loop()
      {
        // Send locally attached sensors data here
      }
      
      

      Serial monitor shows:

      0 MCO:BGN:INIT GW,CP=RNNGA---,FQ=16,REL=255,VER=2.3.2
      4 TSM:INIT
      5 TSF:WUR:MS=0
      12 TSM:INIT:TSP OK
      13 TSM:INIT:GW MODE
      15 TSM:READY:ID=0,PAR=0,DIS=0
      18 MCO:REG:NOT NEEDED
      642 GWT:TIN:IP=255.255.255.255
      1644 MCO:BGN:STP
      1646 MCO:BGN:INIT OK,TSP=1
      1648 TSM:READY:NWD REQ
      1653 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
      

      Log parser shows:

      Node Id	Child Sensor	Command Type	Echo Req/Resp	Type	Payload	Description
      0 MCO:BGN:INIT GW,CP=RNNGA---,FQ=16,REL=255,VER=2.3.2	Core initialization of GW, with capabilities RNNGA---, CPU frequency 16 MHz, library version 2.3.2, release 255
      4 TSM:INIT	Transition to Init state
      5 TSF:WUR:MS=0	Wait until transport ready, timeout 0
      12 TSM:INIT:TSP OK	Transition to Init state:TSP OK
      13 TSM:INIT:GW MODE	Transition to Init state:GW MODE
      15 TSM:READY:ID=0,PAR=0,DIS=0	Transport ready, node id 0, parent node id 0, distance to GW is 0
      18 MCO:REG:NOT NEEDED	No registration needed (i.e. GW)
      Unknown	642 GWT:TIN:IP=255.255.255.255	
      1644 MCO:BGN:STP	Callback setup()
      1646 MCO:BGN:INIT OK,TSP=1	Core initialized, transport status 1, (1=initialized, 0=not initialized, NA=not available)
      1648 TSM:READY:NWD REQ	Send transport network discovery request
      1653 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:	Sent Message without radio ACK
      Sender: 0
      Last Node: 0
      Next Node: 255
      Destination: 255
      Sensor Id: 255
      Command: INTERNAL
      Message Type:I_DISCOVER_REQUEST
      Payload Type: P_STRING
      Payload Length: 0
      Signing: 0
      Failed uplink counter: 0
      Status: OK (OK=success, NACK=no radio ACK received)
      Payload:
      

      but nothing:

      • can't ping to it.
      • arp -a shows the address, but no the mac.

      ANy hint?

      posted in Troubleshooting
      pw44
      pw44
    • RE: wait() with interrupt

      @TRS-80 said in wait() with interrupt:

      @Yveaux & @mfalkvidd,

      I can't help but make it complicated, I'm descended from Germans! 😄 😄 😄

      Aber das Traue ich dir.

      posted in Development
      pw44
      pw44
    • RE: mysensor gateway with ENC28J60 Ethernet doubts!

      @TRS-80 Thank you for your kind answer. WIll wait.

      posted in Hardware
      pw44
      pw44
    • Ethernet Gateway - how reliable is it? which problems and how to avoid?

      HI All!

      i'm struggling to build the ethernet gateway, using the arduino nano v3.0, nrf24l01 and enc28j60.

      what i'm facing:

      • fixed ip works, dhcp (commenting out the fixed ip) causes compilation error (arduino IDE)
      • having usb cable plugged to nano v3.0 to computer and power supply connected ping works.
      • disconnecting the usb cable, ping stops (power supply and ethernet connected)

      Anyone have it working?
      What can you tell me about?
      Which problems are knowns?
      Is it reliable to be in production (work as expected, without extensive maintenence due errors, etc)?

      Those questions refers to my intention to have it working with minimal intervention once installed and configured, and i don't want to start a learning curve to spend lot of time supporting it.

      Thx for all help you may provide.

      posted in Hardware
      pw44
      pw44
    • RE: mysensor gateway with ENC28J60 Ethernet doubts!

      i really can't figure what is going on. with usb connected, i can ping to gateway, with usb disconnected, ping stops. yes, i have a 2 A power supply delivering 3,3 V to nano v3, rf42 and ens28j60 and ethernet cable on rj45.

      does anyone have a reliable gateway working able to share the knowledge with me?

      posted in Hardware
      pw44
      pw44
    • RE: 💬 Building an Ethernet Gateway

      i built the ethernet gateway with the ENC28J60 module, arduino nano v3.0 and RF24 radio, using this guide and there are three problems which i'm not being able to solve (i used the https://github.com/mysensors/MySensorsArduinoExamples/tree/master/libraries/UIPEthernet, as suggested).

      • fixed ip, connected to power supply, ethernet cable and usb - ping works, but HA does not "sees"
      • fixed ip, connected to power supply, ethernet cable but no usb - ping does not works ????
      • commented ip definition, to enable dchp - does not work.
        seams the instructions are outdated -
        i really need help to make it work.
        thx
      posted in Announcements
      pw44
      pw44
    • RE: building the Ethernet gateway

      Hi All,

      for the mysensors the gateway i decided also to give a try with ENC28J60 Ethernet module, RF24 and arduino nano.

      The code i used is:

      // Enable debug prints to serial monitor
      #define MY_DEBUG 
      
      // Enable and select radio type attached
      #define MY_RADIO_RF24
      #define MY_RF24_PA_LEVEL RF24_PA_MAX
      
      // When ENC28J60 is connected we have to move CE/CSN pins for NRF radio
      #define MY_RF24_CE_PIN 5
      #define MY_RF24_CS_PIN 6
      
      // Enable gateway ethernet module type 
      #define MY_GATEWAY_ENC28J60
      
      // Gateway IP address
      #define MY_IP_ADDRESS 192,168,80,9  
      #define MY_IP_GATEWAY_ADDRESS 192,168,80,1
      #define MY_IP_SUBNET_ADDRESS 255,255,255,0
      
      // The MAC address can be anything you want but should be unique on your network.
      // Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use.
      // Note that most of the Ardunio examples use  "DEAD BEEF FEED" for the MAC address.
      #define MY_MAC_ADDRESS 0x00, 0x40, 0xFD, 0xEF, 0x35, 0x70
      
      // The port to keep open on node server mode / or port to contact in client mode
      #define MY_PORT 5003   
      
      // Controller ip address. Enables client mode (default is "server" mode). 
      // Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere. 
      //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 80, 4 
      
      // If MQTT, uncomment the follwoing:
      //#define MY_GATEWAY_MQTT_CLIENT
      //#define MY_MQTT_CLIENT_ID "mysnsg1"
      //#define MY_MQTT_USER "admin"
      //#define MY_MQTT_PASSWORD "bucleta01"
      // MQTT broker ip address or url. Define one or the other.
      //#define MY_CONTROLLER_URL_ADDRESS "mysnsg1.wollny.com.br"
      //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 80, 4
      // The MQTT broker port to to open
      //#define MY_PORT 1883
      // Set this node's subscribe and publish topic prefix
      //#define MY_MQTT_PUBLISH_TOPIC_PREFIX "mysnsg1-out"
      //#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mysnsg1-in"  
      
      // Flash leds on rx/tx/err
      // Set blinking period
      #define MY_DEFAULT_LED_BLINK_PERIOD 300
      
      // Enable inclusion mode
      #define MY_INCLUSION_MODE_FEATURE
      // Enable Inclusion mode button on gateway
      #define MY_INCLUSION_BUTTON_FEATURE
      // Set inclusion mode duration (in seconds)
      #define MY_INCLUSION_MODE_DURATION 60 
      // Digital pin used for inclusion mode button
      #define MY_INCLUSION_MODE_BUTTON_PIN  3 
      
      #define MY_DEFAULT_ERR_LED_PIN 7  // Error led pin
      #define MY_DEFAULT_RX_LED_PIN  8  // Receive led pin
      #define MY_DEFAULT_TX_LED_PIN  9  // the PCB, on board LED
      
      #include <SPI.h>
      #include <UIPEthernet.h>
      #include <MySensors.h>
      
      
      void setup()
      {
      }
      
      void loop() {
      }
      

      on the monitor, i read:

      0 MCO:BGN:INIT GW,CP=RNNGA---,FQ=16,REL=255,VER=2.3.2
      4 TSM:INIT0 MCO:BGN:INIT GW,CP=RNNGA---,FQ=16,REL=255,VER=2.3.2
      4 TSM:INIT
      5 TSF:WUR:MS=0
      12 TSM:INIT:TSP OK
      13 TSM:INIT:GW MODE
      15 TSM:READY:ID=0,PAR=0,DIS=0
      18 MCO:REG:NOT NEEDED
      71 GWT:TIN:IP=192.168.80.9
      1074 MCO:BGN:STP
      1075 MCO:BGN:INIT OK,TSP=1
      1078 TSM:READY:NWD REQ
      1083 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
      0 MCO:BGN:INIT GW,CP=RNNGA---,FQ=16,REL=255,VER=2.3.2
      4 TSM:INIT
      5 TSF:WUR:MS=0
      12 TSM:INIT:TSP OK
      13 TSM:INIT:GW MODE
      15 TSM:READY:ID=0,PAR=0,DIS=0
      18 MCO:REG:NOT NEEDED
      71 GWT:TIN:IP=192.168.80.9
      1074 MCO:BGN:STP
      1075 MCO:BGN:INIT OK,TSP=1
      1078 TSM:READY:NWD REQ
      1083 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
      13182 GWT:TSA:ETH OK
      13190 GWT:RFC:MSG=0;255;3;0;2;
      23293 GWT:RFC:MSG=0;255;3;0;2;
      33400 GWT:RFC:MSG=0;255;3;0;2;
      43508 GWT:RFC:MSG=0;255;3;0;2;
      53615 GWT:RFC:MSG=0;255;3;0;2;
      63723 GWT:RFC:MSG=0;255;3;0;2;
      73830 GWT:RFC:MSG=0;255;3;0;2;
      83937 GWT:RFC:MSG=0;255;3;0;2;
      94044 GWT:RFC:MSG=0;255;3;0;2;
      104153 GWT:RFC:MSG=0;255;3;0;2;
      114259 GWT:RFC:MSG=0;255;3;0;2;
      124366 GWT:RFC:MSG=0;255;3;0;2;
      134474 GWT:RFC:MSG=0;255;3;0;2;
      144581 GWT:RFC:MSG=0;255;3;0;2;
      154689 GWT:RFC:MSG=0;255;3;0;2;
      164798 GWT:RFC:MSG=0;255;3;0;2;
      174905 GWT:RFC:MSG=0;255;3;0;2;
      185013 GWT:RFC:MSG=0;255;3;0;2;
      195324 GWT:RFC:MSG=0;255;3;0;2;
      205228 GWT:RFC:MSG=0;255;3;0;2;
      215334 GWT:RFC:MSG=0;255;3;0;2;
      225441 GWT:RFC:MSG=0;255;3;0;2;
      235549 GWT:RFC:MSG=0;255;3;0;2;
      245657 GWT:RFC:MSG=0;255;3;0;2;
      255970 GWT:RFC:MSG=0;255;3;0;2;
      265872 GWT:RFC:MSG=0;255;3;0;2;
      275980 GWT:RFC:MSG=0;255;3;0;2;
      286088 GWT:RFC:MSG=0;255;3;0;2;
      296196 GWT:RFC:MSG=0;255;3;0;2;
      306302 GWT:RFC:MSG=0;255;3;0;2;
      316411 GWT:RFC:MSG=0;255;3;0;2;
      326518 GWT:RFC:MSG=0;255;3;0;2;
      336625 GWT:RFC:MSG=0;255;3;0;2;
      346733 GWT:RFC:MSG=0;255;3;0;2;
      357048 GWT:RFC:MSG=0;255;3;0;2;
      366948 GWT:RFC:MSG=0;255;3;0;2;
      377056 GWT:RFC:MSG=0;255;3;0;2;
      387163 GWT:RFC:MSG=0;255;3;0;2;
      397270 GWT:RFC:MSG=0;255;3;0;2;
      407377 GWT:RFC:MSG=0;255;3;0;2;
      417485 GWT:RFC:MSG=0;255;3;0;2;
      427592 GWT:RFC:MSG=0;255;3;0;2;
      437701 GWT:RFC:MSG=0;255;3;0;2;
      447807 GWT:RFC:MSG=0;255;3;0;2;
      457916 GWT:RFC:MSG=0;255;3;0;2;
      468024 GWT:RFC:MSG=0;255;3;0;2;
      478131 GWT:RFC:MSG=0;255;3;0;2;
      488238 GWT:RFC:MSG=0;255;3;0;2;
      498345 GWT:RFC:MSG=0;255;3;0;2;
      

      for testing, i installed also mycontroller, but seams there is no interaction.

      also trying to make it dhcp (commenting out the ip line), does not work (complie error).

      beside that, disconnecting the usb cabe makes it becomes unresponsive to ping, even powered and connected to the ethernet cable.

      Home Assistant Core also does not connect to it.

      Thx in advance for any help.

      posted in Troubleshooting
      pw44
      pw44
    • RE: mysensor gateway with ENC28J60 Ethernet doubts!

      @pw44

      Hi All,

      when i disconnect the usb cable (power is on and ethernet cable connected), the gateway stops responding to ping.

      Any hint?

      BR

      posted in Hardware
      pw44
      pw44
    • RE: mysensor gateway with ENC28J60 Ethernet doubts!

      @TRS-80 said in mysensor gateway with ENC28J60 Ethernet doubts!:

      @pw44 said in mysensor gateway with ENC28J60 Ethernet doubts!:

      seams there is no interaction

      This is what it looks like to me, too.

      I base that on:

      • 13182 GWT:TSA:ETH OK which I am guessing means Ethernet is working?
      • Then it just keeps sending GWT:RFC:MSG=0;255;3;0;2; which, according to log parser and serial protocol API documentation command internal (3) value of 2 is "I_VERSION" described as "Used to request gateway version from controller." And because it just keeps sending it over and over, I agree with you, and also think that is where the problem lie.

      Any progress on your end in the meantime?

      No no progress yet. Does not speaks with mycontroller or home assistant.

      posted in Hardware
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @mfalkvidd

      ok, i was curious as i didn't find how to.

      Anyway, is it possible to have the "RF24 IRQ" used as soft?

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @mfalkvidd said in Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.:

      @pw44 unless your nodes send very frequently, you probably don’t need irq.

      If you need irq, you’ll need to use hardware spi.

      Ok, but just in case, how to use the hardware spi in this configurartion (sorry if it seams stupid, but i'm just a very beginner on this).

      Thx for the understanding and also for educating me,.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @mfalkvidd
      thank for the answer.

      i guess the UNO R3 is capable to do it, so, i tried

      #define MY_RX_MESSAGE_BUFFER_FEATURE
      #define MY_RF24_IRQ_PIN 3
      

      and got the following error:

      #error RF24 IRQ usage cannot be used with Soft SPI
      

      Any hint? The idea is having something like 80 nodes when all is done.

      Thx

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @Yveaux and regardin IRQ from RF24, is it necessary to connect to pin2 of UNO R3?

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @Yveaux

      thanks man, you're right. commenting out

      //#define MY_W5100_SPI_EN 4
      

      solved it.

      now, debug shows:

      0 MCO:BGN:INIT GW,CP=RNNGA---,FQ=16,REL=255,VER=2.3.2
      4 MCO:BGN:BFR
      6 TSM:INIT
      7 TSF:WUR:MS=0
      13 TSM:INIT:TSP OK
      15 TSM:INIT:GW MODE
      16 TSM:READY:ID=0,PAR=0,DIS=0
      19 MCO:REG:NOT NEEDED
      696 GWT:TIN:IP=192.168.80.9
      1699 MCO:BGN:STP
      1701 MCO:BGN:INIT OK,TSP=1
      1703 TSM:READY:NWD REQ
      1709 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
      

      just another question: does the 3.3v line from Uno R# enough power to handle the RF24 radio?

      Thx in advance!

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @Yveaux

      @Yveaux said in Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.:

      @pw44 why are spi clk/miso/mosi connected to A0.. 2 ¿

      as described in https://www.mysensors.org/build/ethernet_gateway

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @Yveaux
      Thanks for the reply, removing the sd card or applying your fix did not change the problem.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      these are the real photos of the setup.

      wire codes are the same as the build instructions 😉

      managing the SPI_EN signal? tried with and without, no changes.

      IMG_6519.JPG
      IMG_6520.JPG IMG_6521.JPG IMG_6522.JPG IMG_6523.JPG IMG_6524.JPG IMG_6525.JPG IMG_6526.JPG

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      nothing is working 😞

      // Enable debug prints to serial monitor
      #define MY_DEBUG
      
      // Enable and select radio type attached
      #define MY_RADIO_RF24
      //#define MY_RADIO_NRF5_ESB
      //#define MY_RADIO_RFM69
      //#define MY_RADIO_RFM95
      
      // Enable gateway ethernet module type
      #define MY_GATEWAY_W5100
      
      // W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
      #define MY_W5100_SPI_EN 4
      
      // Enable Soft SPI for NRF radio (note different radio wiring is required)
      // The W5100 ethernet module seems to have a hard time co-operate with
      // radio on the same spi bus.
      #if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
      #define MY_SOFTSPI
      #define MY_SOFT_SPI_SCK_PIN 14
      #define MY_SOFT_SPI_MISO_PIN 16
      #define MY_SOFT_SPI_MOSI_PIN 15
      #endif
      
      // When W5100 is connected we have to move CE/CSN pins for NRF radio
      #ifndef MY_RF24_CE_PIN
      #define MY_RF24_CE_PIN 5
      #endif
      #ifndef MY_RF24_CS_PIN
      #define MY_RF24_CS_PIN 6
      #endif
      
      // Enable UDP communication
      //#define MY_USE_UDP  // If using UDP you need to set MY_CONTROLLER_IP_ADDRESS or MY_CONTROLLER_URL_ADDRESS below
      
      // Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
      //#define MY_IP_ADDRESS 192,168,80,15
      
      // If using static ip you can define Gateway and Subnet address as well
      //#define MY_IP_GATEWAY_ADDRESS 192,168,80,1
      //#define MY_IP_SUBNET_ADDRESS 255,255,255,0
      
      // Renewal period if using DHCP
      #define MY_IP_RENEWAL_INTERVAL 60000
      
      // The port to keep open on node server mode / or port to contact in client mode
      #define MY_PORT 5003
      
      // Controller ip address. Enables client mode (default is "server" mode).
      // Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
      //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 254
      //#define MY_CONTROLLER_URL_ADDRESS "my.controller.org"
      
      // The MAC address can be anything you want but should be unique on your network.
      // Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use.
      // Note that most of the Arduino examples use  "DEAD BEEF FEED" for the MAC address.
      #define MY_MAC_ADDRESS 0x00, 0x40, 0xFD, 0xEF, 0x35, 0x75
      
      
      // Enable inclusion mode
      #define MY_INCLUSION_MODE_FEATURE
      // Enable Inclusion mode button on gateway
      #define MY_INCLUSION_BUTTON_FEATURE
      // Set inclusion mode duration (in seconds)
      #define MY_INCLUSION_MODE_DURATION 60
      // Digital pin used for inclusion mode button
      #define MY_INCLUSION_MODE_BUTTON_PIN  3
      
      // Set blinking period
      #define MY_DEFAULT_LED_BLINK_PERIOD 300
      
      // Flash leds on rx/tx/err
      // Uncomment to override default HW configurations
      #define MY_DEFAULT_ERR_LED_PIN 7  // Error led pin
      #define MY_DEFAULT_RX_LED_PIN  8  // Receive led pin
      #define MY_DEFAULT_TX_LED_PIN  9  // Transmit led pin
      
      #if defined(MY_USE_UDP)
      #include <EthernetUdp.h>
      #endif
      #include <SPI.h>
      #include <Ethernet.h>
      #include <MySensors.h>
      
      void setup()
      {
        // Setup locally attached sensors
      }
      
      void presentation()
      {
        // Present locally attached sensors here
      }
      
      void loop()
      {
        // Send locally attached sensors data here
      }
      

      serial monitor output:

      30055 TSM:FAIL:RE-INIT
      30057 TSM:INIT
      30063 !TSM:INIT:TSP FAIL
      30065 TSM:FAIL:CNT=4
      30067 TSM:FAIL:DIS
      30069 TSF:TDI:TSL
      0 MCO:BGN:INIT GW,CP=RNNGA---,FQ=16,REL=255,VER=2.3.2
      4 TSM:INIT
      5 TSF:WUR:MS=0
      11 !TSM:INIT:TSP FAIL
      13 TSM:FAIL:CNT=1
      15 TSM:FAIL:DIS
      16 TSF:TDI:TSL
      10019 TSM:FAIL:RE-INIT
      10021 TSM:INIT
      10028 !TSM:INIT:TSP FAIL
      10030 TSM:FAIL:CNT=2
      10032 TSM:FAIL:DIS
      10034 TSF:TDI:TSL
      20037 TSM:FAIL:RE-INIT
      20039 TSM:INIT
      20045 !TSM:INIT:TSP FAIL
      20047 TSM:FAIL:CNT=3
      20049 TSM:FAIL:DIS
      20051 TSF:TDI:TSL
      30055 TSM:FAIL:RE-INIT
      30057 TSM:INIT
      30063 !TSM:INIT:TSP FAIL
      30065 TSM:FAIL:CNT=4
      30067 TSM:FAIL:DIS
      30069 TSF:TDI:TSL
      40072 TSM:FAIL:RE-INIT
      40074 TSM:INIT
      40080 !TSM:INIT:TSP FAIL
      40082 TSM:FAIL:CNT=5
      40084 TSM:FAIL:DIS
      40086 TSF:TDI:TSL
      50089 TSM:FAIL:RE-INIT
      50092 TSM:INIT
      50098 !TSM:INIT:TSP FAIL
      50100 TSM:FAIL:CNT=6
      50102 TSM:FAIL:DIS
      50104 TSF:TDI:TSL
      60107 TSM:FAIL:RE-INIT
      60109 TSM:INIT
      60115 !TSM:INIT:TSP FAIL
      60118 TSM:FAIL:CNT=7
      60120 TSM:FAIL:DIS
      60122 TSF:TDI:TSL
      120125 TSM:FAIL:RE-INIT
      120127 TSM:INIT
      120133 !TSM:INIT:TSP FAIL
      120136 TSM:FAIL:CNT=7
      120138 TSM:FAIL:DIS
      120139 TSF:TDI:TSL
      180142 TSM:FAIL:RE-INIT
      180144 TSM:INIT
      180150 !TSM:INIT:TSP FAIL
      180153 TSM:FAIL:CNT=7
      180155 TSM:FAIL:DIS
      180156 TSF:TDI:TSL
      0 MCO:BGN:INIT GW,CP=RNNGA---,FQ=16,REL=255,VER=2.3.2
      4 TSM:INIT
      5 TSF:WUR:MS=0
      11 !TSM:INIT:TSP FAIL
      13 TSM:FAIL:CNT=1
      15 TSM:FAIL:DIS
      16 TSF:TDI:TSL
      10019 TSM:FAIL:RE-INIT
      10021 TSM:INIT
      10028 !TSM:INIT:TSP FAIL
      10030 TSM:FAIL:CNT=2
      10032 TSM:FAIL:DIS
      10034 TSF:TDI:TSL
      20037 TSM:FAIL:RE-INIT
      20039 TSM:INIT
      20045 !TSM:INIT:TSP FAIL
      20047 TSM:FAIL:CNT=3
      20049 TSM:FAIL:DIS
      20051 TSF:TDI:TSL
      30055 TSM:FAIL:RE-INIT
      30057 TSM:INIT
      30063 !TSM:INIT:TSP FAIL
      30065 TSM:FAIL:CNT=4
      30067 TSM:FAIL:DIS
      30069 TSF:TDI:TSL
      
      

      there must be something i'm not being able to figure out....

      dhcp served by dnsmasq. all other devices work without problem.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @mfalkvidd
      no controller yet. i need to make the gateway at least be recognized by the network, either way.

      udp, for dhcp.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @mfalkvidd said in Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.:

      @pw44 the dhcp communication uses udp of course, but after that the MySensors gateway will use tcp unless MY_USE_UDP is defined.

      The gateway doesn't respond to icmp ping?

      Next step would be to check the gateway's debug log.

      if MY_USER_UDP is commented out, i understand that no UPD is enabled from start, correct?

      enabling MY_USER_UDP requires #define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 254
      and #define MY_CONTROLLER_URL_ADDRESS "my.controller.org"

      by enabling fixed ip, none of both is required, which is something not very clear for me.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @mfalkvidd said in Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.:

      @pw44 which machine are you running the arp command on? The router?
      Is 192.168.80.115 the IP the router assigned to the MySensors gateway?

      my server (dnsmasq, dhcp server) - 192.168.80.4
      adsl + router - 192.168.80.1

      mysensor gateway - 192.168.80.115 assigned by 192.168.80.4 (dhcp server)

      with fixed ip address it worked, but i guess maybe udp is not active at mysensors gateway.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @mfalkvidd , thank you.

      no problem, host name can be assined by dhcp.

      problem is that commenting out the ip address, letting dhcp take care produces:

      $ arp
      Address HWtype HWaddress Flags Mask Iface
      192.168.80.115 (incomplete) enp2s0

      @mfalkvidd said in Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.:

      @pw44 what type of hostname are you referring to?
      hostname to identify itself

      @mfalkvidd said in Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.:

      To expand, there are two types of hostnames often used: a mDNS hostname and a hostname option in the DHCP request.

      The reason MY_HOSTNAME doesn't have any effect is that MY_HOSTNAME is only supported by ESP8266 and ESP32. I'll amend the documentation to include that information.

      Some additional info: https://forum.arduino.cc/index.php?topic=622543.0
      got it.

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @mfalkvidd

      Thx, man!

      and to set the hostname? tried MY_HOSTNAME "MySensorsGW" , but no luck 😞

      posted in Troubleshooting
      pw44
      pw44
    • RE: Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      @mfalkvidd

      Thank you for answering, and helping to solve. Having the radio module plugged, it worked.

      How to define it as a dhcp client instead of setting a fixed ip address, having only the mac address defined?

      Thx in advance!

      posted in Troubleshooting
      pw44
      pw44
    • Gateway Uno R3 + W5100 Ethernet Shield for Uno not working.

      Hya,

      My network:

      192.168.80.1 -> 0.0.0.0 (gateway)
      192.168.80.4 (dns, dhcp)

      192.168.80.20 -> mysensors gateway

      not plugged the radio yet.

      after assembling the pack Uno R3 + W5100 Ethernet Shield for Uno, i flashed the following sketch:

      // Enable debug prints to serial monitor
      #define MY_DEBUG
      
      // Enable and select radio type attached
      #define MY_RADIO_RF24
      //#define MY_RADIO_NRF5_ESB
      //#define MY_RADIO_RFM69
      //#define MY_RADIO_RFM95
      
      // Enable gateway ethernet module type
      #define MY_GATEWAY_W5100
      
      // W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
      #define MY_W5100_SPI_EN 4
      
      // Enable Soft SPI for NRF radio (note different radio wiring is required)
      // The W5100 ethernet module seems to have a hard time co-operate with
      // radio on the same spi bus.
      #if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
      #define MY_SOFTSPI
      #define MY_SOFT_SPI_SCK_PIN 14
      #define MY_SOFT_SPI_MISO_PIN 16
      #define MY_SOFT_SPI_MOSI_PIN 15
      #endif
      
      // When W5100 is connected we have to move CE/CSN pins for NRF radio
      #ifndef MY_RF24_CE_PIN
      #define MY_RF24_CE_PIN 5
      #endif
      #ifndef MY_RF24_CS_PIN
      #define MY_RF24_CS_PIN 6
      #endif
      
      // Enable UDP communication
      //#define MY_USE_UDP  // If using UDP you need to set MY_CONTROLLER_IP_ADDRESS or MY_CONTROLLER_URL_ADDRESS below
      
      // Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
      #define MY_IP_ADDRESS 192,168,80,20
      
      // If using static ip you can define Gateway and Subnet address as well
      #define MY_IP_GATEWAY_ADDRESS 192,168,80,4
      #define MY_IP_SUBNET_ADDRESS 255,255,255,0
      
      // Renewal period if using DHCP
      //#define MY_IP_RENEWAL_INTERVAL 60000
      
      // The port to keep open on node server mode / or port to contact in client mode
      #define MY_PORT 5003
      
      // Controller ip address. Enables client mode (default is "server" mode).
      // Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
      //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 254
      //#define MY_CONTROLLER_URL_ADDRESS "my.controller.org"
      
      // The MAC address can be anything you want but should be unique on your network.
      // Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use.
      // Note that most of the Arduino examples use  "DEAD BEEF FEED" for the MAC address.
      #define MY_MAC_ADDRESS 0x00, 0x40, 0xFD, 0xEF, 0x35, 0x75
      
      
      // Enable inclusion mode
      #define MY_INCLUSION_MODE_FEATURE
      // Enable Inclusion mode button on gateway
      #define MY_INCLUSION_BUTTON_FEATURE
      // Set inclusion mode duration (in seconds)
      #define MY_INCLUSION_MODE_DURATION 60
      // Digital pin used for inclusion mode button
      #define MY_INCLUSION_MODE_BUTTON_PIN  3
      
      // Set blinking period
      #define MY_DEFAULT_LED_BLINK_PERIOD 300
      
      // Flash leds on rx/tx/err
      // Uncomment to override default HW configurations
      #define MY_DEFAULT_ERR_LED_PIN 7  // Error led pin
      #define MY_DEFAULT_RX_LED_PIN  8  // Receive led pin
      #define MY_DEFAULT_TX_LED_PIN  9  // Transmit led pin
      
      #if defined(MY_USE_UDP)
      #include <EthernetUdp.h>
      #endif
      #include <SPI.h>
      #include <Ethernet.h>
      #include <MySensors.h>
      
      void setup()
      {
      	// Setup locally attached sensors
      }
      
      void presentation()
      {
      	// Present locally attached sensors here
      }
      
      void loop()
      {
      	// Send locally attached sensors data here
      }
      

      Upload to Uno R3 was successful, and plunging to the ethernet switch, only green led on the RJ45 lights, arp does not shows the mac address defined and ip defined does not pings.

      May i ask for help in order to solve?

      Thx in advance.

      posted in Troubleshooting
      pw44
      pw44