@alowhum Thank you for sharing this! - This looks like exactly the kind of thing I was trying to achieve.
Hopefully I get some time at the weekend to test it out.
Cheers! :)
@terence-faul this is not a fail prove design. Nodes are not typically moved even within one GW. Each GW must have each one channel and the same goes for nodes. Otherwise, in theory you may have a situation that the same node is reporting to one GW and then to the other GW. For controller this is going to be a chaos. A lot of data will be shared between two similar child IDs, i.e. for example two similar temperature child IDs for one node will have one measurement assigned through the first GW to the first temperature child ID and another measurement assigned to another child ID through another GW.
Hmmm. Looking up scintillometers, I see they are advertised as "large aperture", so you may need an array of photo[diodes,cells], which adds a lot of complexity, matching, summing etc,but maybe you could get away with a condenser lens.
@grubstake yes it is still current info and works both for the new driver and for the old driver, which is used by default (and what OP asked about)
If you are using the new driver you can set the frequency in hertz if you want to.
@apl2017 on the öast message, the node is not getting ack from the next node. The mose common cause is i sufficiently clean power supply. What size of capacitor are you using? How is the radio getting its power?
Adding wait(200) before the send call can help the power to stabilize.
Since all communication before works, wiring and everything else should be ok.
@rjgmba hi and welcome to the forum!
https://www.mysensors.org/build/connect_radio decribes how to connect the radio for any node or gateway - it is not limited to serial.
A gateway has 1 transport and 1 controller interface.
The transport can be rfm69, nrf24, rs485, etc
The controller interface can be serial, ethernet(tcp), mqtt
So what you want is probably a gateway with rfm69 transport and mqtt controller interface.
Program the gateway based on the instructions on the first link you posted. Change the code from
// Enables and select radio type (if attached)
#define MY_RADIO_RF24
//#define MY_RADIO_RFM69
//#define MY_RADIO_RFM95
to
// Enables and select radio type (if attached)
//#define MY_RADIO_RF24
#define MY_RADIO_RFM69
//#define MY_RADIO_RFM95
connect the radio based on the instructions on the second link.
@jerby thanks for reporting. Could you share the CSMA levels for your area? (#define MY_DEBUG_VERBOSE_RFM69 and check the debug log to see what it prints)
@gohan Exactly, and the project I'm working on is "no soldering and no programming required (unless you want to)".
I guess I'll try ordering one of these modules and see if it can handle full power.
Guys you are right is too early to quit , i have to try the RFM69 433Mhz as well before quitting , i was planning to wire my house with a 5v power supply to power all the sensors but i guess using a lower freq can help me to avoid that , will give it a try , lest just hope the rfm69 arrive, cuz i always have problems with evay ,
thanks guys you open mi mind one more time
@kimot The main thing is that I got them flashed. I still have yet to figure out the new firmware and test them, but I am confident I can get them to work.
Thanks again.