Ping Pong with ESP8266 results in !TSM:FPAR:NO REPLY [solved]

[gohan]

Besides the ping pong sketch, did you have trouble running normal gateway sketch and adding the other esp8266 as node?

[mpp]

@gohan not sure if I understand your question since I don't know what can be expected from the Gateway?

Here's the gateway log:

0;255;3;0;9;MCO:BGN:INIT GW,CP=RRNGE--,VER=2.1.1
0;255;3;0;9;TSF:LRT:OK
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
scandone
state: 0 -> 2 (b0)
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 6
cnt 
chg_B1:-40
f r-40, 
connected with Airport, channel 6
dhcp client start...
scandone
.chg_B1:-80
............ip:192.168.0.164,mask:255.255.255.0,gw:192.168.0.1
.IP: 192.168.0.164
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mygateway1-out/0/255/0/0/18
pm open,type:2 0

I see the following in the mqtt log:

mygateway1-out/0/255/0/0/18 2.1.1

[gohan]

I forgot to ask: are you using any nrf24 or rfm69 radio or are you trying to make the esp8266 talk to each other over wifi?

[mpp]

@gohan i'm using rfm69. Somehow I got it to work with one ESP gateway and 2 ESP nodes. All three have an rfm69 chip. I don't understand why you need a gateway to do ping pong?

[gohan]

The mysensors protocol relies on the gateway, you can't do without it unless you are using other ping pong code that are not relying on mysensors.

[mpp]

@gohan then shouldn't there be a note in the documentation of the ping pong sketch about this?

[gohan]

I'll take a look

[mpp]

@gohan thanks!

[gohan]

Actually it is explained in this page how the mysensors network works, but I'll see how to add a line in the example sketch

[mpp]

@gohan thanks for the feedback. According to that page it seems you not only need a gateway but also a controller. This explains why my nodes don't get a node id automatically.

[gohan]

The controller is needed for auto ID, but it can also be used myscontroller. It is also written in different places that manual id should be set also in case of problems.

[mpp]

@gohan indeed you're right. What did you mean with "myscontroller"?

Setting the node id manually for the ping pong sketch makes them communicate to the Gateway:

#define MY_NODE_ID 201

Would auto ID work with the ESP MQTT Gateway and OpenHab controller?

I have an MQTT server up and running and OpenHab is installed with the following configuration in /etc/openhab2/services/mqtt.cfg:

broker.url=tcp://127.0.0.1:1883
broker.clientId=OpenHab
broker.retain=true
broker.async=false

Yet I still get !TSM:FPAR:NO REPLY

[gohan]

https://forum.mysensors.org/topic/838/windows-gui-controller-for-mysensors

I'd start from the ethernet gateway and work it out from there, myscontroller works with ethernet gateway. In openhab I don't know how to enable auto id, but there must be something in documentation. To be honest assigning manually ID has to be done only once because it is saved in eeprom and read at every boot, so I don't see it so mandatory to have the controller handling it.

[mpp]

@gohan, do you mean http://www.mycontroller.org? I can't find any project page with downloads on the link you provided. There is a download link to a zip file somewhere in the comments but impossible to say if that is still up to date as it dates from 2015.

[gohan]

yes, it's the zip file. It is a windows app. Mycontroller it is actually a controller like Domoticz or Openhab. I know it is a little old, but it works.

[mpp]

@gohan, I switched over to mycontroller (from OpenHab) and I'm using Arduino's nodes and I'm still getting errors not finding the parent.

I'm using the Mock sketch and tested with setting the ID manually but no luck.

0 MCO:BGN:INIT NODE,CP=RRNNA--,VER=2.1.1
4 TSM:INIT
4 TSF:WUR:MS=0
108 TSM:INIT:TSP OK
110 TSM:INIT:STATID=99
112 TSF:SID:OK,ID=99
114 TSM:FPAR
3241 TSF:MSG:SEND,99-99-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
5249 !TSM:FPAR:NO REPLY
5251 TSM:FPAR
8378 TSF:MSG:SEND,99-99-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
10385 !TSM:FPAR:NO REPLY
10387 TSM:FPAR
13514 TSF:MSG:SEND,99-99-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
15521 !TSM:FPAR:NO REPLY
15523 TSM:FPAR

Edit: adding a 4.7 capacitor didn't change this. Neither did downgrading to 2.0.

Starting sensor (RRNNA-, 2.0.0)
TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=254)
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:FAIL
!TSM:FAILURE
TSM:PDT
TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=254)
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:FAIL
!TSM:FAILURE
TSM:PDT
TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=254)
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:

Any idea?

[gohan]

On the gateway do you see any message received? Can you post the gateway log when nodes are registering?

[mpp]

@gohan, when using the WemosD1 (without capacitor!) and a static ID, I get the following:

0;255;3;0;9;TSF:MSG:READ,253-253-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=253
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-253-253,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,253-253-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=253,HP=1
0;255;3;0;9;TSF:MSG:SEND,0-0-253-253,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
0;255;3;0;9;TSF:MSG:READ,253-253-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
0;255;3;0;9;TSF:MSG:SEND,0-0-253-253,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
0;255;3;0;9;TSF:MSG:READ,253-253-0,s=255,c=0,t=17,pt=0,l=5,sg=0:2.1.1
0;255;3;0;9;Sending message on topic: mpp-mygateway1-out/253/255/0/0/17

When I do the same for the Pro Mini, there is nothing to see. When I flash a Moteino test sketch it works properly.

[gohan]

@mpp the gateway is getting the message and it replies so you could either have a power issue on gateway or range problem. How far are the gw and node?

[mpp]

@gohan tested with less than a meter up to 10 meters. In fact the Wemos Node now is working as it shows up in mycontroller but the Pro Mini doesn't receive a response from the GW.