SOLVED: MQTT ESP8266 Gateway issue

[gohan]

Install mysensors library 2.1.0, I had probably the same problem that broke nrf24 after updating to 2.1.1

[Yeitso]

Na thats not it either It seems. Still getting the same errors.

Ran EEPROM clear on both gateway and node.

Change lib from 2.1.1 to 2.1.0 and reluploaded the sketches (with the addition of #define MY_NODE_ID 1 to the node sketch)

0 MCO:BGN:INIT NODE,CP=RRNNA--,VER=2.1.0
4 TSM:INIT
4 TSF:WUR:MS=0
8 TSM:INIT:TSP OK
10 TSM:INIT:STATID=1
12 TSF:SID:OK,ID=1
14 TSM:FPAR
145 TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2152 !TSM:FPAR:NO REPLY
2154 TSM:FPAR
2285 TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4292 !TSM:FPAR:NO REPLY
4294 TSM:FPAR
4425 TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6432 !TSM:FPAR:NO REPLY
6434 TSM:FPAR
6565 TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8574 !TSM:FPAR:FAIL
8577 TSM:FAIL:CNT=1
8579 TSM:FAIL:PDT

0;255;3;0;9;MCO:BGN:INIT GW,CP=RRNGE--,VER=2.1.0
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)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 14
cnt

connected with Johrid, channel 1
dhcp client start...
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
f r0, scandone
....ip:192.168.1.208,mask:255.255.255.0,gw:192.168.1.1
.IP: 192.168.1.208
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
IP: 192.168.1.208
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
0;255;3;0;9;Sending message on topic: mygateway1-out/0/255/3/0/11
0;255;3;0;9;Sending message on topic: mygateway1-out/0/255/3/0/12
0;255;3;0;9;Sending message on topic: mygateway1-out/0/0/0/0/7
0;255;3;0;9;Sending message on topic: mygateway1-out/0/1/0/0/6
Sending initial value
0;255;3;0;9;Sending message on topic: mygateway1-out/0/1/1/0/0
0;255;3;0;9;Sending message on topic: mygateway1-out/0/0/1/0/1
pm open,type:2 0

[Yeitso]

Riiight so when inspecting the radios I have I notice that the H on the back is not ticked. There might be an issue that the seller have sent me the wrong radios.

But removing the define #define MY_IS_RFM69HW did not help.

If one where to run the RFM69W as a HW would that damage the chip?

[Yeitso]

After using lowpowerlabs example sketches "Gateway.ino" and "Node.ino" I now know that the radios work. and at a nice range as well. But they are not HW.

That being said even if I remove #define MY_IS_RFM69HW I'm still getting this issue.

[gohan]

You can't remove that define, otherwise the library doesn't know what radio has to set up. If I remember well the H stands for high power so it should be the same.

[Yeitso]

That define is to turn on high power mode if you have a rfm69hw

I sill have

#define MY_RADIO_RFM69

So radio is define but not in high power mode.

[Johannes Hodne]

I changed back to 2.0.0 lib. Then everything start working again:-)

[Yeitso]

Thank you, so did I and it works.

Will open a ticket on github with this find and hopefully the devs will be able to recreate and fix the issue.

[Johannes Hodne]

anyone got the gatway working with the 2.1.1 lib?

[mpp]

Alas, I'm also struggling with ESP crashes and weird messages:

TSM:INIT
TSF:WUR:MS=0
TSM:INIT:TSP OK
TSM:INIT:STATID=22
TSF:SID:OK,ID=22
TSM:FPAR
TSF:MSG:SEND,22-22-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 5
cnt 
chg_B1:-40

connected with Airport, channel 6
dhcp client start...
chg_B1:-80
!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,22-22-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
chg_B1:-120
!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,22-22-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
!TSM:FPAR:NO REPLY

[gohan]

Is it the same problem as your other post?

[mpp]

@gohan there are different things going wrong, the parent id can't be found (eventhough it is set manually to 0), but there's also a lot of debug specific to the esp module.