@drock1985 said:
Hey @Pierre-P
Yeah, you would need a new gateway for each radio type.
I found a new mysensors page ! here:
https://www.mysensors.org/download/sensor_api_15#create-repeating-nodes
Advanced initialization
It's also possible to construct an instance with RFM69 radio driver and/or enable signing support. You can choose one of the following radio drivers:
MyTransportNRF24 transport(RF24_CE_PIN, RF24_CS_PIN, RF24_PA_LEVEL_GW);
or
MyTransportRFM69 transport(RFM69_FREQUENCY, RFM69_NETWORKID, RF69_SPI_CS, RF69_IRQ_PIN, isRFM69HW, RF69_IRQ_NUM);
@andriej
Hi, I had problem using the main branch mysensors/Raspberry, that because of the bit-field struct (header_s) in Sensor.h They will get packed in different order on the arduino compared to the RPi (at least with my compiler, gcc). In order to fix this I created the 1.4dev branch. It uses full bytes instead of the bit-fields, but you need (of cause) to compile both the sensors (arduino) and the gateway (RPi) using the 1.4dev branch.
We need to fix this in the main branch later on (and use the same files as in mysensors/Arduino/libraries/MySensors)
It depends a lot on what you can do. As @OldSurferDude wrote, if you want a cheap solution, this is the way to go. Also when you need something that is not available on the market. Here below the list of my camper nodes.
IMO mySensors is the best possible alternative, if not the only one, to the systems that rely on standards, which require way too many resources for the job they are asked.
In my case, several nodes have edge capabilities, because they have to keep working even if the controller is not responsive.
