Yes, this works using the radiohead library and those sketches. I didn't need to connect any extra wires. I'm not looking at connecting to LoRaWAN at the moment, just mysensors.
I read the board is similar to Arduino Zero also, so i will try using that as a base and try fixing forward so the feather M0 with lora can work with mysensors, if nobody has had this working yet? (mysensors with adafruit feather m0 LoRa RFM9*).
Thanks 
@pierrot10 I've got my two new M0 ATSAMD21 boards talking, so the hardware is good :), i used the radioheads library. These definately sound a better chip than the 32u4, although I'll have to see how they go on battery comsumption.
This might sound dumb but I can't compile mysensors scripts (serial gateway) with my boards, I'm using adafruits board defination. Looking at mysensors i can't see this board, except the Sensebender (ATSAMD21), but it has a completely different pin layout. Does that mean I need to map each ping to the correct reference in the code to get this to work with mysensors ?
Thanks @pierrot10, that is fantastic!
I actually have a dead feather 32u4 now, so will order more, but after reading what you say it sounds like the M0 model with the newer updated chipset is a better option.
Just a question on running the base lora radio (feather M0) to a raspberry pi, i presume it will work okay using the standard serial/USB connection. I haven't tried it, as my radio is dead.
Anyway I better order these new ones and getting making, thanks
Thanks very much @pierrot10, that is exactly what i was looking for :). I've got 2x Adafruit Feather 32u4 LoRa Radio, which has the the ATmega32u4 chipset. I believe the M0 model has the newer ATSAMD21G18 chipset. I think apart from the libraries, it should work the same.
I'm trying to connect a Feather bord using the Lora radio to mysensors and i can't get any reception. I've looked through the forums and documentation but I can't see if it is actually supported by mysensors, any help appreciated in pointing me in the correct direction? or if anyone knows if it is compatiable ? thanks
@jkandasa Thanks for the follow up. I can see MyController is modifying the serial message into a customized MQTT msg (as you have said).
MyController works great with the serial so it would be good to keep that as is, and if we had an independent service to publish to a separate MQTT broker would be very helpful?
@FotoFieber MyController is getting the MQTT msg, but doesn't like it's format, i've had continuous error msg like below:
2017-02-16 18:17:34,657 ERROR [Thread-4] [org.mycontroller.standalone.provider.mysensors.MySensorsProviderBridge:60] Unable to process this rawMessage:RawMessage(gatewayId=2, data=2;0;1;0;23;36, subData=mysensors/1/out/, isTxMessage=false, networkType=MY_SENSORS)
org.mycontroller.standalone.message.RawMessageException: Unknown message format, Topic:mysensors/1/out/, PayLoad:2;0;1;0;23;36
at org.mycontroller.standalone.provider.mysensors.MySensorsRawMessage.updateMQTTMessage(MySensorsRawMessage.java:114) ~[mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
MyController is set up with the correct topic, as seen in above Topic:/mysensors/1/out/ (i've also tried without the ending /).
@FotoFieber Thanks for the suggestion, I got that working. I have had to change MyController to read an MQTT gateway. Problem now is MyController can't read the MQTT format of this script. Any suggestions or tips ?
MyController does such a great job with handling MySensors' data, it would be a pity to loose that functionality.
@jkandasa As a seperate service is okay, it would be very helpful. Thank you
