RFM69HCW Feather M0 MQTT

[Andrew Maynard]

I'm thinking of switching to esp8266 gateway. maybe get that working then try again with raspberry pi? I'm not ready to give up. I dont see as much documentation though.

[mfalkvidd]

@andrew-maynard what type of documentation are you looking for?

• Debugging FAQ, shows the most common problems and how to troubleshoot them
• The Getting started guide describes how MySensors is designed to work
• We have build pages that describe how to build a lot of different sensors and gateways
• The Download/API page has links to documentation for the serial API, the Sensor API and the technical documentation.
• The forum (search) has over 90,000 posts covering experience from thousands of MySensors users.

[Andrew Maynard]

oh I didnt mean it as not enough documentation in total. you guys put some serious hard work in this project and I really do appreciate it. I would think you guys are paid! I just meant in terms of raspberry pi as a gateway with rfm69hcw. Am I wrong? btw this is one of the liveliest communities I've experienced! once again thank you and I do appreciate it!

[Andrew Maynard]

I'm on the beginner side so it seems a little easier to change a few things in the esp8266gateway sketch and go.

[mfalkvidd]

@andrew-maynard I'd say that if you have Linux experience, the Raspberry Pi gateway is probably easier to configure and troubleshoot (since it will be a familiar environment). But if you're not already familiar with Linux, learning Linix+MySensors at the same time will be harder than using the esp8266 gateway.

[Andrew Maynard]

This is the debug from the gateway.
If for some reason the transceiver isn't working it should say in debug, correct?

Aug 02 01:17:32 INFO  Starting gateway...
Aug 02 01:17:32 INFO  Protocol version - 2.3.1-alpha
Aug 02 01:17:32 DEBUG MCO:BGN:INIT GW,CP=RPNGL---,VER=2.3.1-alpha
Aug 02 01:17:32 DEBUG TSF:LRT:OK
Aug 02 01:17:32 DEBUG TSM:INIT
Aug 02 01:17:32 DEBUG TSF:WUR:MS=0
Aug 02 01:17:32 DEBUG TSM:INIT:TSP OK
Aug 02 01:17:32 DEBUG TSM:INIT:GW MODE
Aug 02 01:17:32 DEBUG TSM:READY:ID=0,PAR=0,DIS=0
Aug 02 01:17:32 DEBUG MCO:REG:NOT NEEDED
Aug 02 01:17:32 DEBUG MCO:BGN:STP
Aug 02 01:17:32 DEBUG MCO:BGN:INIT OK,TSP=1
Aug 02 01:17:32 DEBUG GWT:RMQ:MQTT RECONNECT
Aug 02 01:17:32 DEBUG connected to 192.168.1.110
Aug 02 01:17:32 DEBUG GWT:RMQ:MQTT CONNECTED
Aug 02 01:17:32 DEBUG GWT:TPS:TOPIC=domoticz/out/MyMQTT/0/255/0/0/18,MSG SENT

[scalz]

the debug can tell you if spi is working ok.
when you get FPAR NO REPLY it could be because of bad rfm69 interrupt. but your define looks ok..
could you try to add in your sketch define this one:

#define MY_RFM69_RST_PIN 4

As your rfm69 reset signal is routed to D4..

[mfalkvidd]

Could the problems be related to https://github.com/mysensors/MySensors/issues/1155 ?

[Andrew Maynard]

@scalz YES!!! I think that was the problem on the Feather m0 side. still not receiving messages though. i did test it out with

pi@raspberrypi3:~ $ mosquitto_pub -t 'domoticz/in/MyMQTT' -m '0,29'

I see it in the domoticz log.

2018-08-05 02:17:49.130 Status: MySensorsMQTT: connected to: 192.168.1.110:1883
2018-08-05 02:17:49.230 Status: MQTT: Subscribed
2018-08-05 02:17:55.937 Status: MQTT: Worker stopped...
2018-08-05 02:17:56.939 Status: MQTT: Connecting to 192.168.1.110:1883
2018-08-05 02:17:57.040 Status: MQTT: connected to: 192.168.1.110:1883
2018-08-05 02:17:57.040 Status: MySensorsMQTT: connected to: 192.168.1.110:1883
2018-08-05 02:17:57.141 Status: MQTT: Subscribed
2018-08-05 02:45:42.707 MySensorsMQTT: Topic: domoticz/in/MyMQTT, Message: 0,29

I figure it cant hurt to show my ./configure.

pi@raspberrypi3:~ $ ./configure --my-gateway=mqtt --my-controller-ip-address=192.168.1.110 --my-mqtt-publish-topic-prefix=domoticz/out/MyMQTT --my-mqtt-subscribe-topic-prefix=domoticz/in/MyMQTT --my-mqtt-client-id=pi  --my-transport=rfm69 --my-rfm69-frequency=433 --my-is-rfm69hw^C

Am I missing something? Is there a something specific I should enter below for my client id?

--my-mqtt-client-id=pi 

Thanks again for responding. I appreciate it!

[Andrew Maynard]

@mfalkvidd I will try it on an esp8266 tomorrow and see if anything changes. When going back versions is there anything else i need to do besides deleting directory and going through ./configure again? I will try the 2.2 version first. I already went from 2.3.1 to 2.3.0.

[mfalkvidd]

@andrew-maynard deleting and starting over is fine. If you're comfortable with git you can switch branch/tag instead of deleting.

[Andrew Maynard]

@mfalkvidd I switched gateway to esp8266

451843 GWT:TPS:TOPIC=domoticz/out/MyMQTT/100/1/1/0/0,MSG SENT
452390 TSF:MSG:READ,100-100-0,s=0,c=1,t=1,pt=7,l=5,sg=0:45.7
452454 GWT:TPS:TOPIC=domoticz/out/MyMQTT/100/0/1/0/1,MSG SENT
453679 TSF:MSG:READ,100-100-0,s=1,c=1,t=0,pt=7,l=5,sg=0:77.5
453743 GWT:TPS:TOPIC=domoticz/out/MyMQTT/100/1/1/0/0,MSG SENT

Im still not seeing it on the domoticz log

2018-08-05 18:37:30.458 Error: Esp8266 MQTT Gateway hardware (5) nothing received for more than 5 Minutes!....
2018-08-05 18:37:31.459 Error: Restarting: Esp8266 MQTT Gateway
2018-08-05 18:37:32.293 Status: MQTT: Worker stopped...
2018-08-05 18:37:33.295 Status: MQTT: Connecting to 192.168.1.110:1883
2018-08-05 18:37:33.396 Status: MQTT: connected to: 192.168.1.110:1883
2018-08-05 18:37:33.396 Status: MySensorsMQTT: connected to: 192.168.1.110:1883
2018-08-05 18:37:33.497 Status: MQTT: Subscribed

When i try to test it using

pi@raspberrypi3:~ $ mosquitto_sub -v -t 'domoticz/out/MyMQTT'

nothing happens and freezes cmd prompt. it does publish though

pi@raspberrypi3:~ $ mosquitto_pub -t 'domoticz/in/MyMQTT' -m '0,29'

I have to be missing something stupid!

[Andrew Maynard]

Would it be wise to close this and move it to Domoticz MySensors forum? It looks like its an issue with mqtt or domoticz.