3. No new node possible

No new node possible

  • gloob

    Hello,

    I have a problem with my network. I can not connect any new nodes to the network.

    The gateway shows the following error:

    0;255;3;0;9;Client 0: 0;0;3;0;5;1
0;255;3;0;9;TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;TSF:PNG:SEND,TO=0
0;255;3;0;9;TSF:CKU:OK
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0

    And on the node i see:

    0 MCO:BGN:INIT NODE,CP=RNNNA--,VER=2.1.1
4 TSM:INIT
4 TSF:WUR:MS=0
12 TSM:INIT:TSP OK
14 TSM:FPAR
16 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2025 !TSM:FPAR:NO REPLY
2027 TSM:FPAR
2029 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4038 !TSM:FPAR:NO REPLY
4040 TSM:FPAR
4042 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6051 !TSM:FPAR:NO REPLY
6053 TSM:FPAR
6055 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8065 !TSM:FPAR:FAIL
8067 TSM:FAIL:CNT=1
8069 TSM:FAIL:PDT
18073 TSM:FAIL:RE-INIT
18075 TSM:INIT
18083 TSM:INIT:TSP OK
18085 TSM:FPAR
18087 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20097 !TSM:FPAR:NO REPLY
20099 TSM:FPAR
20101 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
22110 !TSM:FPAR:NO REPLY
22112 TSM:FPAR
22114 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
24123 !TSM:FPAR:NO REPLY
24125 TSM:FPAR
24127 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
26136 !TSM:FPAR:FAIL
26138 TSM:FAIL:CNT=2
26140 TSM:FAIL:PDT
36143 TSM:FAIL:RE-INIT
36145 TSM:INIT
36153 TSM:INIT:TSP OK
36155 TSM:FPAR
36157 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
37013 TSF:MSG:READ,200-200-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
38166 !TSM:FPAR:NO REPLY
38168 TSM:FPAR
38170 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:

    Any ideas if this problem is related to the controller (FHEM) or to MySensors?

    0
  • gloob

    Existing nodes work without any problem:

    0;255;3;0;9;!TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;TSF:MSG:READ,100-100-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=100
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;!TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;TSF:MSG:READ,100-100-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=100
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;!TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;TSF:MSG:READ,100-100-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=100
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;!TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;TSF:MSG:READ,196-196-0,s=1,c=1,t=0,pt=7,l=5,sg=0:22.4
0;255;3;0;9;TSF:MSG:READ,196-196-0,s=2,c=1,t=1,pt=2,l=2,sg=0:45
0;255;3;0;9;TSF:MSG:READ,196-196-0,s=199,c=1,t=38,pt=7,l=5,sg=0:2.922
0;255;3;0;9;TSF:MSG:READ,196-196-0,s=255,c=3,t=0,pt=1,l=1,sg=0:73

    Even when I set a fixed None ID in the sketch it will not join the network.

    When the node is sending a request, I see an update in the debug log of the gateway. So the message gets send correctly.

    0 tekka 1 Reply
  • tekka
    Admin

    @gloob Looks like you have a power issue on your GW hardware:

    0;255;3;0;9;!TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0

    Try adding a larger cap on the radio or replace the power supply.

    0
  • gloob

    Hello,

    actually I already have a cap next to the radio and the power is supplied by a ams1117 but I will try to change the power supply of the WeMos.

    The strange thing is, that all other nodes (6 with temp, hum and battery) are working without any problems. I only get this issue with new nodes.
    Will it help to set the node ID manually in the node sketch?

    0 tekka 1 Reply
  • tekka
    Admin

    @gloob cap size gw and nodes? Antenna type?

    0 gloob 1 Reply
  • gloob

    @tekka

    The gateway has a 47µF cap and the nodes use 10uF.

    For the gateway I use a NRF24L01-SMD PA+LNA radio module and the nodes use "normal" NRF24L01 modules without PA+LNA.

    0
  • flopp

    On a NOT working node try with a nRF from a WORKING node.
    Place the NOT working node on the same location as a WORKING

    0
  • gloob

    I did this test also. When I flash a node that was working before with a new ID, it will not join the network.
    When I flash it back, to use the old static ID, it is working again without any problems.

    Currently I think it is a problem with the WeMos pro mini. I will try it with an other WeMos when it arrives from china.

    0 flopp 1 Reply
  • flopp

    @gloob
    Do you have to allow new Nodes in your controller?

    0
  • gloob

    Inclusion mode is set on the controller. But I think I don't have to activate this in the controller if the node has a static ID.

    0 rejoe2 1 Reply
  • rejoe2

    @gloob: FHEM also requires to have inclusion mode active when NODE_ID is assigned in the sketch.

    0
  • gloob

    But even when I set FHEM to inclusion_mode = 1, I get this error.
    I would assume that the node finds the parent without a running controller if the node ID and parent ID are static.

    0 rejoe2 1 Reply
  • rejoe2

    You already tried to restart the node after turning inclusion mode on?
    As long as the parent node is present, the node will send it's messages towards this one, but I'm not sure if this (esp. the presentation()) really needs the controller to answer accordingly.
    Other: are you using MQTT?

    0
  • gloob

    Yes I also tried to restart the node when inclusing mode is on and I don't use MQTT.

    0
  • rejoe2

    Don't have no further idea, but maybe it is really HW-related wrt to this post: https://forum.mysensors.org/topic/6063/solved-mqtt-esp8266-gateway-issue.
    Indicates some kind of incompability between the MySensors-libs 2.1.1 and the Wemos D1 mini defs, other variants of the ESP8266 may be affected, too. MySensors versions between 2.0.0-beta and 2.1.1 have issues with the nrf-part, so downgrading is not the best idea either.
    Do you have the possibility to make tests with a serial GW or at least use the WIFI-GW in a "fake serial mode" (don't really know whether this is possible or not)?

    0
  • gloob

    So the other thread mentions to go back to 2.0.0
    I will try this today and give feedback.

    0
  • rejoe2

    When downgrading I would expect trouble wrt. to the nrf part (other thread is about other RF-chip). Did you try to use the GW as fake serial GW or at least tried to analyse serial output more in depth?
    Btw.: Another user reported having trouble including new nodes with a network-GW, see here: https://forum.mysensors.org/topic/6149/ethernet-gateway-shows-up-on-vera-but-doens-t-want-to-include-devices. As this is the 3rd in very short time, most likely problems will be solved pretty soon.

    EDIT: found even a 4th, pretty similar one: https://forum.mysensors.org/topic/6118/problem-connecting-to-gateway

    Pretty astonishing, because the recent days I built a RS485-GW using the 2.1.1-libs without trouble wrt. including some testnodes in FHEM.
    the only problems I ran into where the neccessity to assingne node ID's manually and I had to restart the other serial GW; this one stopped receiving regular updates from my nrf-nodes.
    Very strange...

    0
  • รอเรือ

    And here is a 5th similar issue I believe: https://forum.mysensors.org/topic/6147/tsm-fpar-no-reply

    0
  • gloob

    Thanks for your support. For me it seems that we have some general problems at the moment.

    I will try the following things later:

    #define MY_NODE_ID 10
#define MY_PARENT_NODE_ID 0
#define MY_PARENT_NODE_IS_STATIC

    1. use dev version of 2.1.1

    2. downgrade to 2.0.0 or less to check if the hardware is working without any problems

    3. use a serial gateway or try to use my WeMos in serial mode

    These are the topics with a similar error (just as a summary for myself):
    https://forum.mysensors.org/topic/6147/tsm-fpar-no-reply
    https://forum.mysensors.org/topic/6118/problem-connecting-to-gateway
    https://forum.mysensors.org/topic/6063/solved-mqtt-esp8266-gateway-issue

    Edit: does anybody have an idea how to use a ESP as serial gateway?

    0
  • rejoe2

    Wrt to using the ESP as serial GW: I only did some short test some time ago, but the serial output seemed to be pretty similar to what I would expect from a regular serial GW. So I would at first just rty to use the USB port and change the definition in FHEM.

    You could also try to use the dev version before downgrading. At first look, there seems not to be a specific fix wrt. this problem, but you never know...

    0
  • gloob

    I did not flash all my nodes with a static node ID and now all new nodes can join the network and are visible in FHEM.

    #define MY_NODE_ID 10
#define MY_PARENT_NODE_ID 0

    I think there is any problem with my WeMos gateway. I will analyze this more in detail, when I have some more time.

    0
  • alowhum
    Plugin Developer

    For anyone finding this: I solved it by clearing the eeprom of the Arduino. There's a special sketch for that under examples.

    0
Log in to reply
 

Suggested Topics

  • hek


    Announcements •  

    3
  • Gibber


    Troubleshooting •  

    8
  • TheoL


    Troubleshooting •  

    6
  • kamilb85


    Troubleshooting •  

    2

0
Online

11.4k
Users

11.1k
Topics

112.7k
Posts



Copyright 2019 Sensnology   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service