mysgw MQTT Issues

gohan

Why are you using version 2.2.1? What do you see on the node log?

xefil

Why are you using version 2.2.1? What do you see on the node log?

I've noticed this now (remote) connected to the RPi. I can give a check on the logs of the node as soon I'm back.
About the version, which should I use? This is the first I've downloaded (months ago).
I've seen there is a v2.3.0-alpha. I could test it.

Simon

gohan

use the master branch that is 2.2, the 2.2.1 are 2.3 are alpha versions and still under development

xefil

@gohan said in mysgw MQTT Issues:

use the master branch that is 2.2, the 2.2.1 are 2.3 are alpha versions and still under development

Ok, this is something I can test right now!
Same result:

mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0
mysgw: MCO:BGN:INIT GW,CP=RPNGL---,VER=2.2.0
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: MCO:BGN:STP
mysgw: MCO:BGN:INIT OK,TSP=1
mysgw: GWT:RMQ:MQTT RECONNECT
mysgw: connected to 192.168.1.50
mysgw: GWT:RMQ:MQTT CONNECTED
mysgw: GWT:TPS:TOPIC=mygateway1-out/0/255/0/0/18,MSG SENT
mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=27
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OK
mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=27
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OK
mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=27
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OK
mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0

Is the !TFS:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0 actually the answer sent?
Could it be a power issue? The radio is directly connected to 3.3V pin, without capacitor.

Simon

gohan

add capacitor and try again

xefil

@gohan said in mysgw MQTT Issues:

add capacitor and try again

Size? 100uF enough?

gohan

Yes, I use 10uF ceramic because of low ESR

xefil

@gohan

@gohan said in mysgw MQTT Issues:

Yes, I use 10uF ceramic because of low ESR

Actually I've only electrolytic ones, I'll try meanwhile with that, thanks!

Simon

xefil

Hello!

Added capacitor, but it's still not working.
It has worked from some minutes but then no-more.
Here results from Gateway and Node:

Node:

 __  __       ____
|  \/  |_   _/ ___|  ___ _ __  ___  ___  _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| |  | | |_| |___| |  __/ | | \__ \  _  | |  \__ \
|_|  |_|\__, |____/ \___|_| |_|___/\___/|_|  |___/
        |___/                      2.2.0

16 MCO:BGN:INIT NODE,CP=RPNNA---,VER=2.2.0
25 MCO:BGN:BFR
27 TSM:INIT
28 TSF:WUR:MS=0
30 TSM:INIT:TSP OK
31 TSM:INIT:STATID=27
33 TSF:SID:OK,ID=27
35 TSM:FPAR
1036 TSF:MSG:SEND,27-27-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
3043 !TSM:FPAR:NO REPLY
3045 TSM:FPAR
4046 TSF:MSG:SEND,27-27-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6053 !TSM:FPAR:NO REPLY
6055 TSM:FPAR
7056 TSF:MSG:SEND,27-27-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
9063 !TSM:FPAR:NO REPLY
9065 TSM:FPAR
9069 TSF:MSG:SEND,27-27-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
10904 TSF:MSG:READ,0-0-27,s=255,c=3,t=8,pt=1,l=1,sg=0:0
10908 TSF:MSG:FPAR OK,ID=0,D=1
11077 TSM:FPAR:OK
11078 TSM:ID
11080 TSM:ID:OK
11081 TSM:UPL
18379 !TSF:MSG:SEND,27-27-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
20386 TSM:UPL
27659 !TSF:MSG:SEND,27-27-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=1,st=NACK:1
29666 TSM:UPL

..and here the gateway:

Apr 10 21:49:36 mysensors-gateway mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
Apr 10 21:49:36 mysensors-gateway mysgw: TSF:MSG:FPAR REQ,ID=27
Apr 10 21:49:38 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
Apr 10 21:49:38 mysensors-gateway mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
Apr 10 21:49:38 mysensors-gateway mysgw: TSF:MSG:FPAR REQ,ID=27
Apr 10 21:49:40 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
Apr 10 21:49:41 mysensors-gateway mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
Apr 10 21:49:41 mysensors-gateway mysgw: TSF:MSG:FPAR REQ,ID=27
Apr 10 21:49:43 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
Apr 10 21:49:44 mysensors-gateway mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
Apr 10 21:49:44 mysensors-gateway mysgw: TSF:MSG:FPAR REQ,ID=27
Apr 10 21:49:46 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
Apr 10 21:49:47 mysensors-gateway mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
Apr 10 21:49:47 mysensors-gateway mysgw: TSF:MSG:FPAR REQ,ID=27
Apr 10 21:49:48 mysensors-gateway mysgw: TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
Apr 10 21:49:49 mysensors-gateway mysgw: TSF:MSG:READ,27-27-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
Apr 10 21:49:49 mysensors-gateway mysgw: TSF:MSG:PINGED,ID=27,HP=1
Apr 10 21:49:50 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
Apr 10 21:49:50 mysensors-gateway mysgw: TSF:MSG:READ,27-27-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
Apr 10 21:49:50 mysensors-gateway mysgw: TSF:MSG:PINGED,ID=27,HP=1
Apr 10 21:49:52 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
Apr 10 21:49:53 mysensors-gateway mysgw: TSF:MSG:READ,27-27-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
Apr 10 21:49:53 mysensors-gateway mysgw: TSF:MSG:PINGED,ID=27,HP=1
Apr 10 21:49:54 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
Apr 10 21:49:54 mysensors-gateway mysgw: TSF:MSG:READ,27-27-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
Apr 10 21:49:54 mysensors-gateway mysgw: TSF:MSG:PINGED,ID=27,HP=1
Apr 10 21:49:55 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
Apr 10 21:49:58 mysensors-gateway mysgw: TSF:MSG:READ,27-27-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
Apr 10 21:49:58 mysensors-gateway mysgw: TSF:MSG:PINGED,ID=27,HP=1
Apr 10 21:50:00 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
Apr 10 21:50:00 mysensors-gateway mysgw: TSF:MSG:READ,27-27-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
Apr 10 21:50:00 mysensors-gateway mysgw: TSF:MSG:PINGED,ID=27,HP=1
Apr 10 21:50:01 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
Apr 10 21:50:02 mysensors-gateway mysgw: TSF:MSG:READ,27-27-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
Apr 10 21:50:02 mysensors-gateway mysgw: TSF:MSG:PINGED,ID=27,HP=1
Apr 10 21:50:03 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
Apr 10 21:50:03 mysensors-gateway mysgw: TSF:MSG:READ,27-27-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
Apr 10 21:50:03 mysensors-gateway mysgw: TSF:MSG:PINGED,ID=27,HP=1
Apr 10 21:50:05 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1

Seems the GW is not able to send out the answer.
BTW It gets every message from the node...

Ideas?

Thanks!

Simon

gohan

move node closer. You could also try swapping the 2 radio modules to see if the problem changes.

xefil

@gohan said in mysgw MQTT Issues:

move node closer. You could also try swapping the 2 radio modules to see if the problem changes.

Strange is, the same radios had worked well until I've switched to RPi GW.
From the logs, correct me if I'm wrong, the issue seems to be on the gateway, not able to send the return/ack message:

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

The node is sending well!

TSF:MSG:SEND,27-27-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:

Or not??

I've added capacitors 100uf to both and, as well, added a copper coli antenna 868Mhz.
Now the GW is 10meters far away from the node. There is only one wall between.
I was testing to switch to RF69 radios which should be better if compared to nRF24L01+ in terms of range and walls.
This is not what expected...

I'll try to replace the radio on the GW side.

Any other suggestion is well appreciated!

Thanks, Simon

gohan

I forgot you had rfm69, so capacitor is not that important. Try to look at my rfm69 signal scanner and look for the code to print on debug the rssi of signal and output power and try to move around to see if you get any value change. I had problems with rpi3 gw using the alpha version, but on stable it works. You could also try to compile it as an ethernet gateway just to see if you get any changes. Can you also post the configure parameters you user?

xefil

@gohan said in mysgw MQTT Issues:

I forgot you had rfm69, so capacitor is not that important. Try to look at my rfm69 signal scanner and look for the code to print on debug the rssi of signal and output power and try to move around to see if you get any value change. I had problems with rpi3 gw using the alpha version, but on stable it works. You could also try to compile it as an ethernet gateway just to see if you get any changes. Can you also post the configure parameters you user?

Hello!
Which parameters?
compiling parameters of the GW?
I've configured it with:

./configure --my-transport=rfm69 --my-rfm69-frequency=868 --my-gateway=mqtt --my-controller-ip-address=192.168.1.50 --my-mqtt-publish-topic-prefix=mygateway1-out --my-mqtt-subscribe-topic-prefix=mygateway1-in --my-mqtt-client-id=raspberryRFM69

About the rfm69 signal scanner, should it run on the node or on the RPi?
(where to find it?)

Thanks @gohan :-)

gohan

https://forum.mysensors.org/topic/7822/portable-rfm69-signal-scanner/6

xefil

@gohan said in mysgw MQTT Issues:

https://forum.mysensors.org/topic/7822/portable-rfm69-signal-scanner/6

Ok, then I need to upload it on the node (which is on a little wooden bird house) and go around with my laptop connected on it :-) Not a problem.
But would that report issues on the GW RPi as well? How?

Meanwhile I can try to compile the ethernet version to give it a try.

Thanks, Simon

xefil

Hello @gohan
Installed ethernet version:

./configure --my-gateway=ethernet --my-port=5003

And it's even worst:

# ./mysgw -d
mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0
mysgw: MCO:BGN:INIT GW,CP=RNNGL---,VER=2.2.0
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: !TSM:INIT:TSP FAIL
mysgw: TSM:FAIL:CNT=1
mysgw: TSM:FAIL:DIS
mysgw: TSF:TDI:TSL
mysgw: TSM:FAIL:RE-INIT
mysgw: TSM:INIT
mysgw: !TSM:INIT:TSP FAIL
mysgw: TSM:FAIL:CNT=2
mysgw: TSM:FAIL:DIS
mysgw: TSF:TDI:TSL
mysgw: TSM:FAIL:RE-INIT
mysgw: TSM:INIT
mysgw: !TSM:INIT:TSP FAIL
mysgw: TSM:FAIL:CNT=3
mysgw: TSM:FAIL:DIS
mysgw: TSF:TDI:TSL
mysgw: TSM:FAIL:RE-INIT
mysgw: TSM:INIT
mysgw: !TSM:INIT:TSP FAIL

Using the mqtt version at least the init gets completed.
Ideas?

Simon

MasMat

Just a quick idea: are you powering the RFM69 from the Rpi?
I use a Rpi Zero W and when I powered my radio NRF24 from that it doesnt get enough juice even with caps.
I now use a bigger USB-wall wart and use AMS1117-3.3 to power the radio (PA-version) and added caps.

My two cents

xefil

@masmat said in mysgw MQTT Issues:

Just a quick idea: are you powering the RFM69 from the Rpi?
I use a Rpi Zero W and when I powered my radio NRF24 from that it doesnt get enough juice even with caps.
I now use a bigger USB-wall wart and use AMS1117-3.3 to power the radio (PA-version) and added caps.

My two cents

Hello,

I've tried to get 3.3V from external source, but same situation:

Apr 16 23:27:02 mysensors-gateway mysgw: MCO:BGN:INIT GW,CP=RPNGL---,VER=2.2.0
Apr 16 23:27:02 mysensors-gateway mysgw: TSF:LRT:OK
Apr 16 23:27:02 mysensors-gateway mysgw: TSM:INIT
Apr 16 23:27:02 mysensors-gateway mysgw: TSF:WUR:MS=0
Apr 16 23:27:02 mysensors-gateway mysgw: TSM:INIT:TSP OK
Apr 16 23:27:02 mysensors-gateway mysgw: TSM:INIT:GW MODE
Apr 16 23:27:02 mysensors-gateway mysgw: TSM:READY:ID=0,PAR=0,DIS=0
Apr 16 23:27:02 mysensors-gateway mysgw: MCO:REG:NOT NEEDED
Apr 16 23:27:02 mysensors-gateway mysgw: MCO:BGN:STP
Apr 16 23:27:02 mysensors-gateway mysgw: MCO:BGN:INIT OK,TSP=1
Apr 16 23:27:02 mysensors-gateway mysgw: GWT:RMQ:MQTT RECONNECT
Apr 16 23:27:02 mysensors-gateway mysgw: connected to 192.168.1.50
Apr 16 23:27:02 mysensors-gateway mysgw: GWT:RMQ:MQTT CONNECTED
Apr 16 23:27:02 mysensors-gateway mysgw: GWT:TPS:TOPIC=mygateway1-out/0/255/0/0/18,MSG SENT
Apr 16 23:27:42 mysensors-gateway mysgw: TSF:MSG:READ,1-27-177,s=48,c=0,t=32,pt=7,l=23,sg=1: 0
Apr 16 23:27:42 mysensors-gateway mysgw: !TSF:MSG:LEN,7!=32
Apr 16 23:27:45 mysensors-gateway mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
Apr 16 23:27:45 mysensors-gateway mysgw: TSF:MSG:BC
Apr 16 23:27:45 mysensors-gateway mysgw: TSF:MSG:FPAR REQ,ID=27
Apr 16 23:27:45 mysensors-gateway mysgw: TSF:PNG:SEND,TO=0
Apr 16 23:27:45 mysensors-gateway mysgw: TSF:CKU:OK
Apr 16 23:27:45 mysensors-gateway mysgw: TSF:MSG:GWL OK
Apr 16 23:27:47 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
Apr 16 23:27:51 mysensors-gateway mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
Apr 16 23:27:51 mysensors-gateway mysgw: TSF:MSG:BC
Apr 16 23:27:51 mysensors-gateway mysgw: TSF:MSG:FPAR REQ,ID=27
Apr 16 23:27:51 mysensors-gateway mysgw: TSF:CKU:OK,FCTRL
Apr 16 23:27:51 mysensors-gateway mysgw: TSF:MSG:GWL OK
Apr 16 23:27:53 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0

Possible the problem is only sending and not receiving?
I've not tested the signal scanner right now.
I was hoping it's a power issue :'(

Simon

xefil

Hello @gohan ,

I was able to compile correctly the network IP mode. I had compiled it with the wrong transport.
BTW, now it initialized correctly, BUT same problems.
I've replaced the radio as well (only on the gateway).
Here the logs:

mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0
mysgw: MCO:BGN:INIT GW,CP=RPNGL---,VER=2.2.0
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: Listening for connections on 0.0.0.0:5003
mysgw: MCO:BGN:STP
mysgw: MCO:BGN:INIT OK,TSP=1
mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=27
mysgw: TSF:PNG:SEND,TO=0
mysgw: TSF:CKU:OK
mysgw: TSF:MSG:GWL OK
mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysgw: TSF:MSG:BC
mysgw: TSF:MSG:FPAR REQ,ID=27
mysgw: TSF:CKU:OK,FCTRL
mysgw: TSF:MSG:GWL OK

As you can see the SEND message fails.
I'll try now to move the node closer and then try the scanner.

Hope it helps :-(

Simon

gohan

You have to check both gw and node at same time in order to understand if message is delivered but ack fails or else.

mysgw MQTT Issues

20

11.7k

11.2k

113.1k