jonas
New Member
Posts: 1
|
Post by jonas on Dec 11, 2014 15:36:14 GMT
This is the follow up thread for my question in the comment section on the original instructables project (http://www.instructables.com/id/Uber-Home-Automation/?ALLSTEPS). Thanks for the great tutorial and for setting up the forum, Eric!
The goal is to replace the gateway of two Arduinos in the original project with a direct connection between the Raspberry Pi and a RFM69 chip. I will try doing that by using an RPi port of HopeRF's Arduino library by Eric Trombly (https://github.com/etrombly/RFM69).
In the first step I will try to get this up and running on a RPi with a RFM69CW board connected. I will use a stripped down version of Raspbian (https://github.com/debian-pi/raspbian-ua-netinst) as OS which served me well in other projects. Once I have this running reliably I will continue by installing Mosquitto and OpenHab.
The current status is that I received all necessary items which I need to get started (1x Arduino Nano, 2x RFM69CW). I will probably start during the Christmas holidays and will post my progress here.
|
|
|
Post by timotapu on Dec 12, 2014 7:49:56 GMT
Hi jonas Good to know you're working on this. I wanted to ask, how are you connecting the two? Since I'm a beginner in home automation, maybe the questions are silly, but please bear with me What I mean is that the Pi is basically a board, but where did you find a compatible RFM69CW board? I found chips, not not something you can directly link to the Pi. Thanks in advance
|
|
|
Post by Admin on Dec 13, 2014 23:58:19 GMT
This is the follow up thread for my question in the comment section on the original instructables project (http://www.instructables.com/id/Uber-Home-Automation/?ALLSTEPS). Thanks for the great tutorial and for setting up the forum, Eric! The goal is to replace the gateway of two Arduinos in the original project with a direct connection between the Raspberry Pi and a RFM69 chip. I will try doing that by using an RPi port of HopeRF's Arduino library by Eric Trombly (https://github.com/etrombly/RFM69). Thanks for trying this out. I haven't had time lately to keep working on it, but I'm very interested in what you find out. Once you get this working, bi-directional comms should be easy to implement, so it takes care of quite a few items. Let us know! Edit: made this a sticky thread. Alexandre Bouillot has also done some work on this. I think he's actually created a port of the Arduino gateway in Raspberry Pi and included etrombly's python library? This might get you started quicker. github.com/abouillot/HomeAutomation/tree/master/piGateway
|
|
|
Post by istvan on Dec 28, 2014 10:28:15 GMT
|
|
|
Post by computourist on Jan 5, 2015 15:14:28 GMT
Hi, The instructable article inspired me to build a simular setup. I have now an Arduino based gateway working in duplex mode. This means messages get passed from end node to MQTT broker and vice versa. End nodes send sensor data, but also receive instructions for end node control and actuator control. Code is on: github.com/computourist/RFM69-MQTT-client
|
|
|
Post by HippoTraxius on Jan 5, 2015 20:50:07 GMT
|
|
|
Post by camblonie on Jan 10, 2015 18:44:37 GMT
Anyone have issue with computourist's setup? I think I'm going to make the switch today.
|
|
|
Post by demondreamer on Jan 11, 2015 5:44:38 GMT
Hi, The instructable article inspired me to build a simular setup. I have now an Arduino based gateway working in duplex mode. This means messages get passed from end node to MQTT broker and vice versa. End nodes send sensor data, but also receive instructions for end node control and actuator control. Code is on: github.com/computourist/RFM69-MQTT-client I'm very much looking forward to trying out your sketches. I had cobbled together a somewhat working version of the bidirectional unified gateway a few months ago with help from others on the Instructables site. It proved to be unreliable and I haven't got around to fixing the bugs on it. Have you had any trouble maintaining the MQTT connection? There seemed to always be a problem keeping the gateway connected to MQTT, requiring all sorts of watchdog code in the sketch to reconnect when it dropped. I would also move this post to a new forum topic as one doesn't already exist on about the unified bidirectional arduino gateway. Lots of people ask about it and it should have a thread of it's own. -Demondreamer
|
|
|
Post by computourist on Jan 12, 2015 9:26:34 GMT
@ demondreamer: I have found no problems with the stability of MQTT connection. In a duplex design the gateway subscribes to an MQTT topic, so the connection is used by a heartbeat to check for new messages. This will keep the link active. In a read-only design no subscription is used and I can imagine the link going down because of a time-out. But again: I have had no such experiences. - Computourist
|
|
|
Post by demondreamer on Jan 14, 2015 5:31:41 GMT
@ demondreamer: I have found no problems with the stability of MQTT connection. In a duplex design the gateway subscribes to an MQTT topic, so the connection is used by a heartbeat to check for new messages. This will keep the link active. In a read-only design no subscription is used and I can imagine the link going down because of a time-out. But again: I have had no such experiences. - Computourist Computourist, could you post up some examples or more detailed instructions on how your gateway and node works? Your design is pretty different from Eric's and I'm having trouble wrapping my mind around it. I've got the gateway wired up as per your schematic on Github, though I'm using a Buono Arduino clone and Wiznet Ethernet shield. I noticed that you're not using the RFM69's DIO0 pin on the gateway or node. I'm curious about that as that pin is used in Eric's design, for an interrupt I think. At this point, I have the gateway responding (in the serial monitor) to MQTT messages I generate using "MyMQTT" android app, but I keep getting "wrong message format in MQTT subscription" Could you give a few examples of actual commands you use? -Demondreamer
|
|
|
Post by computourist on Jan 14, 2015 10:13:57 GMT
@ Demondreamer: The DIO0 pin should be connected to D2. I will adapt the schematics. Do not forget to disable interrupts during handling of ethernet traffic by changing file W5100.h in the library, as described in harizanov.com/2012/04/rfm12b-and-arduino-ethernet-with-wiznet5100-chip/I will try to make some time to write up a more detailed description in the next few days. As for MQTT: You should subscribe to subject: home/rfm_gw/nb/node02/# . This will give you all messages from node 02. You should publish to a specific device, fe: topic: home/rfm_gw/sb/node02/dev10 payload: ON to switch on the LED on node 2 topic: home/rfm_gw/sb/node02/dev01 payload: 20 to set the transmission interval to 20 seconds topic: home/rfm_gw/sb/node02/dev08 payload: ON to generate a message each time the button is pressed topic: home/rfm_gw/sb/node02/dev31 payload: READ to read temperature topic: home/rfm_gw/sb/node02/dev02 payload: READ to read radio signal strength If you have no end node active (yet) the gateway will try to connect and fail after a few retries. It will respond with a message in topic: /home/rfm_gw/nb/node02/dev00 and the text "connection lost node 2" in the payload. Hope this helps....
|
|
|
Post by Admin on Jan 15, 2015 0:46:52 GMT
That's awesome! I've never gone back to debug why I needed two Arduinos for the gateway. I see you got the radio.setCS(RFM_SS) to work. Did you have to do anything special to the RFM69 library? Or did you just use the library as is from lowpowerlab and only needed that line to make the interrupt work? You did a lot of work around disabling interrupts and stuff to make it reliable. That's pretty huge. Thanks so much for sharing this. Eric Hi, The instructable article inspired me to build a simular setup. I have now an Arduino based gateway working in duplex mode. This means messages get passed from end node to MQTT broker and vice versa. End nodes send sensor data, but also receive instructions for end node control and actuator control. Code is on: github.com/computourist/RFM69-MQTT-client
|
|
|
Post by computourist on Jan 15, 2015 9:59:31 GMT
Hi Eric, Changes needed were Slave Select pin on RFM69 and Interrupt-disable in the WZ library. No changes needed in the RFM library... It seems the W5100 doesn't handle multiple devices on the SPI bus very well. Some suggest using an inverter to control the SEN-pin on the WZ5100 to enable the SPI-bus to float. See: wiznethk.blogspot.nl/2009/09/spi-guide.htmlI tried that but for me it doesn't seem to make much difference. I am using the WZ5100 with SEN tied high thru a pull-up (as in the orginal module) and have a stable system. - Computourist That's awesome! I've never gone back to debug why I needed two Arduinos for the gateway. I see you got the radio.setCS(RFM_SS) to work. Did you have to do anything special to the RFM69 library? Or did you just use the library as is from lowpowerlab and only needed that line to make the interrupt work? You did a lot of work around disabling interrupts and stuff to make it reliable. That's pretty huge. Thanks so much for sharing this. Eric
|
|
|
Post by demondreamer on Jan 15, 2015 15:52:58 GMT
It helps immensely! I'm able to send and receive MQTT messages the gateway understands now. The next leap is to get the messages through to the node I have some uncertainty whether or not my Ethernet shield will be usable or if I need to buy something more agreeable. I think you are using something like the W5100 Ethernet Network Module. Given the problems with the whole Ethernet part of this project, can you post a link to the specific module you're using? Is there any reason the Ethernet Shield specifically shouldn't work? I know there is/was some sort of bug in how the w5100 chip handled sharing the SPI bus, but in the comments of the RFM12B and Arduino Ethernet with WizNet5100 chip page people are reporting the later models of the Ethernet Shield have the inverter fix implemented already. The Slave Select issue seems to be resolved as well. The Ethernet Shield has to be pin 10 because it's not physically reconfigure able (very easily), but no matter as the RFM69 can be reconfigured in the sketch to use another pin. Regarding, "disable interrupts during handling of ethernet traffic by changing file W5100.h in the library, as described in harizanov.com/2012/04/rfm12b-and-arduino-ethernet-with-wiznet5100-chip/" after reading the link you referenced, I believe it's saying to replace: #else inline static void initSS() { DDRB |= _BV(2); }; inline static void setSS() { PORTB &= ~_BV(2); }; inline static void resetSS() { PORTB |= _BV(2); }; #endif
with: #else inline static void initSS() { DDRB |= _BV(2); }; inline static void setSS() { cli(); PORTB &= ~_BV(2); }; inline static void resetSS() { PORTB |= _BV(2); sei(); }; #endif That should be all, right? To me the instructions on that page were a bit unclear, so I'm posting this here for verification and reference to others. Thank you for taking the time to answer all these questions. -Demondreamer @ Demondreamer: The DIO0 pin should be connected to D2. I will adapt the schematics. Do not forget to disable interrupts during handling of ethernet traffic by changing file W5100.h in the library, as described in harizanov.com/2012/04/rfm12b-and-arduino-ethernet-with-wiznet5100-chip/I will try to make some time to write up a more detailed description in the next few days. As for MQTT: You should subscribe to subject: home/rfm_gw/nb/node02/# . This will give you all messages from node 02. You should publish to a specific device, fe: topic: home/rfm_gw/sb/node02/dev10 payload: ON to switch on the LED on node 2 topic: home/rfm_gw/sb/node02/dev01 payload: 20 to set the transmission interval to 20 seconds topic: home/rfm_gw/sb/node02/dev08 payload: ON to generate a message each time the button is pressed topic: home/rfm_gw/sb/node02/dev31 payload: READ to read temperature topic: home/rfm_gw/sb/node02/dev02 payload: READ to read radio signal strength If you have no end node active (yet) the gateway will try to connect and fail after a few retries. It will respond with a message in topic: /home/rfm_gw/nb/node02/dev00 and the text "connection lost node 2" in the payload. Hope this helps....
|
|
|
Post by computourist on Jan 16, 2015 8:58:14 GMT
I am using the exact same Network Module you point to in your post. This board does not contain the inverter for the SEN-signal, but somehow it works OK without. Any W5100 shield should work; In some cases the ICSP connector needs to be connected in order to provide all signals. I built my system using perf-board and a Pro Mini 328 Mini ATMEGA328 3.3V 8MHz... With respect to the changes in W5100.h you're correct again: Whenever the ethernet module seizes the bus (on setSS) you have to disable interrupts generated by the RFM board. When the W5100 releases the bus (on resetSS) you have to re-enable interrupts... - Computourist It helps immensely! I'm able to send and receive MQTT messages the gateway understands now. The next leap is to get the messages through to the node I have some uncertainty whether or not my Ethernet shield will be usable or if I need to buy something more agreeable. I think you are using something like the W5100 Ethernet Network Module. Given the problems with the whole Ethernet part of this project, can you post a link to the specific module you're using? Is there any reason the Ethernet Shield specifically shouldn't work? I know there is/was some sort of bug in how the w5100 chip handled sharing the SPI bus, but in the comments of the RFM12B and Arduino Ethernet with WizNet5100 chip page people are reporting the later models of the Ethernet Shield have the inverter fix implemented already. The Slave Select issue seems to be resolved as well. The Ethernet Shield has to be pin 10 because it's not physically reconfigure able (very easily), but no matter as the RFM69 can be reconfigured in the sketch to use another pin. Regarding, "disable interrupts during handling of ethernet traffic by changing file W5100.h in the library, as described in harizanov.com/2012/04/rfm12b-and-arduino-ethernet-with-wiznet5100-chip/" after reading the link you referenced, I believe it's saying to replace: #else inline static void initSS() { DDRB |= _BV(2); }; inline static void setSS() { PORTB &= ~_BV(2); }; inline static void resetSS() { PORTB |= _BV(2); }; #endif
with: #else inline static void initSS() { DDRB |= _BV(2); }; inline static void setSS() { cli(); PORTB &= ~_BV(2); }; inline static void resetSS() { PORTB |= _BV(2); sei(); }; #endif That should be all, right? To me the instructions on that page were a bit unclear, so I'm posting this here for verification and reference to others. Thank you for taking the time to answer all these questions. -Demondreamer
|
|
|
Post by demondreamer on Jan 16, 2015 23:36:15 GMT
Well, I've managed to get everything working, though the gateway locks up after 1-10 transmissions. I can send MQTT messages to and get replies from the node but after a random amount of transmissions, the gateway stops responding and the node starts reporting "no connection" on the serial monitor. I also get random "invalid message structure.. " on the node's serial output. I'm assuming at this point that the Arduino Ethernet shield is not playing nice with the RFM69, and at some point everything locks up. I've ordered a couple of those W5100 Ethernet modules that you're using to try out. I may also try to get my hands on some 74HCO4 inverter ICs and see if I can muddle my way through that hack. It would be nice to get these three Ethernet Shields I have working. According to "An Atlas of Arduino Ethernet Shields" the cheap knockoff Wiznet Ethernet Shields I have are the "Ethernet Shield 05" or "version 2.0", from 2010. Most of the talk about the inverter hack dates around 2011 so my Ethernet boards probably have that flaw. My setup so far: Gateway:
Buono UNO R3, Arduino Uno clone, switch at 3.3v Wiznet 5100 Ethernet Shield (probably the "05" or "ver. 2.0") (no-brand clone) RFM69HW Node: Buono UNO R3, Arduino Uno clone, switch at 3.3v RFM69HW Using the MyMQTT android app to test publishing messages and receive subscription messages . I am using the exact same Network Module you point to in your post. This board does not contain the inverter for the SEN-signal, but somehow it works OK without. Any W5100 shield should work; In some cases the ICSP connector needs to be connected in order to provide all signals. I built my system using perf-board and a Pro Mini 328 Mini ATMEGA328 3.3V 8MHz... With respect to the changes in W5100.h you're correct again: Whenever the ethernet module seizes the bus (on setSS) you have to disable interrupts generated by the RFM board. When the W5100 releases the bus (on resetSS) you have to re-enable interrupts... - Computourist
|
|
|
Post by computourist on Jan 17, 2015 12:55:27 GMT
According to the schematics of your shield an inverter is in place: You'll have to look elsewhere for the cause.. Is your MQTT link stable ? What is the signal strenght of the radio link ? Are you using a reliable power source ? I have had problems in the past with cheap USB power supplies. Another cause might be the 3.3 Volt Arduino. Atmel does not guarantee proper working at 16 Mhz at this voltage. That's why I'm using an ATMEGA328 at 8Mhz. BTW: I use MQTT.fx as a MQTT client and found it handy for testing. You can also subscribe to Mosquitto-server and monitor # of messages, clients etc. - Computourist Well, I've managed to get everything working, though the gateway locks up after 1-10 transmissions. I can send MQTT messages to and get replies from the node but after a random amount of transmissions, the gateway stops responding and the node starts reporting "no connection" on the serial monitor. I also get random "invalid message structure.. " on the node's serial output. I'm assuming at this point that the Arduino Ethernet shield is not playing nice with the RFM69, and at some point everything locks up. I've ordered a couple of those W5100 Ethernet modules that you're using to try out. I may also try to get my hands on some 74HCO4 inverter ICs and see if I can muddle my way through that hack. It would be nice to get these three Ethernet Shields I have working. According to "An Atlas of Arduino Ethernet Shields" the cheap knockoff Wiznet Ethernet Shields I have are the "Ethernet Shield 05" or "version 2.0", from 2010. Most of the talk about the inverter hack dates around 2011 so my Ethernet boards probably have that flaw. My setup so far: Gateway:
Buono UNO R3, Arduino Uno clone, switch at 3.3v Wiznet 5100 Ethernet Shield (probably the "05" or "ver. 2.0") (no-brand clone) RFM69HW Node: Buono UNO R3, Arduino Uno clone, switch at 3.3v RFM69HW Using the MyMQTT android app to test publishing messages and receive subscription messages .
|
|
|
Post by demondreamer on Jan 18, 2015 4:35:43 GMT
Well, at least I can cross off the inverter possibility for now. The MQTT link stability between the Arduinos and the broker has always been an issue. With Eric's dual gateway design there were always disconnections, but he wrote code that would re-establish the connection whenever it would go down. It works pretty well, though I think the gateway can miss transmissions if they occur while it's re-establishing the link. Same issue with Abouillot's unified gateway. It would drop the MQTT connection periodically and his solution was to check for and reconnect to the broker periodically. In my experience, the brokers worked perfectly; I could communicate with them always through other means, like MyMQTT. I always suspected there was a bug in the pubsubclient library, or that we just weren't using it properly. Your gateway though, as far as I can tell, is not dropping the MQTT connection. It looks to me like it's just locking up while sending or receiving using the RFM69. Sometimes on the first transmission, sometimes after eight or nine. Sometimes the radio led remains on as if it crashed before it got to the part of the sketch that tells it to turn back off. I don't think it's a MQTT issue as the gateway serial monitor stops showing any activity. Typing the commands you implemented in your gateway sketch produces no response, and resetting the node so it sends it's "I'm alive" signal produces no response on the gateway serial monitor either. The signal strength is about -27, the gateway and node are sitting right next to each other. I've had them about 2000 feet apart and got a stable signal in the past, so that should be good. The power supply from the USB hub the Arduinos are plugged into I think is sufficient. Just in case though I tried several others, including a 5v 1 amp smartphone charger and a 12v 1 amp power supply adapter. (The Buonos can handle power input up to 19v) The clock speed/power issue sounds plausible. I don't think there's an easy way to convert Uno clones to 8mhz though. I've ordered some bi-directional logic level converters with the thought that I can turn the Arduino and Ethernet Shield back to run on 5v and just the RFM69 on 3.3v. I also ordered an 8mhz, 3.3v Arduino Pro Mini. Enough is enough! lol MQTT.fx looks like a nice tool! Thanks for the recommendation. I'll update when my new toys come in or if I make any progress. -Demondreamer According to the schematics of your shield an inverter is in place: You'll have to look elsewhere for the cause.. Is your MQTT link stable ? What is the signal strenght of the radio link ? Are you using a reliable power source ? I have had problems in the past with cheap USB power supplies. Another cause might be the 3.3 Volt Arduino. Atmel does not guarantee proper working at 16 Mhz at this voltage. That's why I'm using an ATMEGA328 at 8Mhz. BTW: I use MQTT.fx as a MQTT client and found it handy for testing. You can also subscribe to Mosquitto-server and monitor # of messages, clients etc. - Computourist
|
|
|
Post by Admin on Jan 21, 2015 2:49:38 GMT
Well, at least I can cross off the inverter possibility for now. The MQTT link stability between the Arduinos and the broker has always been an issue. With Eric's dual gateway design there were always disconnections, but he wrote code that would re-establish the connection whenever it would go down. It works pretty well, though I think the gateway can miss transmissions if they occur while it's re-establishing the link. Same issue with Abouillot's unified gateway. It would drop the MQTT connection periodically and his solution was to check for and reconnect to the broker periodically. In my experience, the brokers worked perfectly; I could communicate with them always through other means, like MyMQTT. I always suspected there was a bug in the pubsubclient library, or that we just weren't using it properly. Your gateway though, as far as I can tell, is not dropping the MQTT connection. It looks to me like it's just locking up while sending or receiving using the RFM69. Sometimes on the first transmission, sometimes after eight or nine. Sometimes the radio led remains on as if it crashed before it got to the part of the sketch that tells it to turn back off. I don't think it's a MQTT issue as the gateway serial monitor stops showing any activity. Typing the commands you implemented in your gateway sketch produces no response, and resetting the node so it sends it's "I'm alive" signal produces no response on the gateway serial monitor either. -Demondreamer That's totally true. I don't know the MQTT library for Arduino well, and just pieced together the reconnect portions based on what I was seeing. When I tried the sample code that came with the knolleary MQTT library, I think I was seeing the same type of sporadic disconnect issue. I thought the "loop" call in the code was suppose to fix any disconnects, but it didn't seem like it was. There was even a time when one Wiznet module seem to have more disconnect issues and another Wiznet module was almost getting none...so I don't know what the root cause is. I wish there was a bullet-proof example of using the MQTT library out there, and I do have a suspicion I'm using it wrong. Or there's a bug...but it's the only Arduino MQTT library so I hope not. This thread is really interesting, thanks for all the info. Eric
|
|
|
Post by camblonie on Jan 22, 2015 0:58:49 GMT
I can report that after trying to tie the ethernet shield to a Pro-mini and failing somehow, I fell back to the Bouno 3.3v Uno's with the ethernet shield for the gateway. The base sketches from Computourist have been communicating for 24 hours now. I'm looking forward to customizing as soon as I can find some time this week. -Scott
|
|
|
Post by computourist on Jan 22, 2015 16:09:36 GMT
Nice to hear somebody got it working I just released a new version. I found out the MQTT link would return after I unplugged and replugged the network connection, but the southbound datastream would not work. This is fixed now so full recovery of the MQTT link after a network outage is OK now. - Computourist I can report that after trying to tie the ethernet shield to a Pro-mini and failing somehow, I fell back to the Bouno 3.3v Uno's with the ethernet shield for the gateway. The base sketches from Computourist have been communicating for 24 hours now. I'm looking forward to customizing as soon as I can find some time this week. -Scott
|
|
|
Post by demondreamer on Jan 22, 2015 20:08:58 GMT
Well, I think I've solved my problem. With camblonie's confirmation that Computourist's sketches work on the Buono+Ethernet Shield+RFM69, I went back and started going over things again. I built a second gateway using a different Buono+Ethernet Sheild+RFM69 and powered it using a high quality 2.5 amp, 5v power supply. Same lockup problem as before, so.. not an issue with the hardware. I then stared going over the libraries that are included in the sketch. PubSubClient is latest version. Ethernet is latest version, changes called for in the sketch are implemented. SPI is.. where is the SPI library? It's not in the Arduino 1.5.7 libray or the library in My Documents. I have no idea where it is. I switch to Arduino IDE 1.0.5-r2 and there's a SPI library folder there, so I load the gateway sketch in there. Then I check the RFM69 library. It's about 6 months old. I downloaded the latest from the Github repository, re-upload the gateway sketch and everything is working great. so, here's what's working for me now: RFM_MQTT_GW_19.ino sketch RFM_DHT_NODE_17.ino sketch Arduino IDE 1.0.5-r2 modify the libraries\Ethernet\utility\w5100.h file as discussed earlier install the latest version of the RFM69 library on hardware: - Buono Uno R3, switch set at 3.3v, powered by a USB hub, 5v 1-2.5 amp phone chargers, a 12v car battery, 4AA LiPo batteries, never had a problem with any of these actually..
- Arduino Ethernet Shield v5 (clone) (NOTE: it's my belief that most Ethernet Shields have the original Arduino Ethernet Shield's flaw already fixed in the boards design)
- RFM69HW (SS to Arduino digital pin 8)
Thank you Computourist, Eric and camblonie, for helping me figure this out! Now that I have a working gateway I'll be moving on to understanding how to interact with the sketch, adding sensors and so on.
|
|
|
Post by Admin on Jan 23, 2015 2:54:12 GMT
This is really exciting. I want to try this out too. BTW, if someone wants to draft up a post that summarizes how to do this, I'll unsticky this thread and sticky the new post. I would help to link to this thread so people can see the process.
Awesome!
|
|
|
Post by computourist on Jan 23, 2015 15:54:56 GMT
I finally sat down and wrote a short description. Hope this gives you a better idea of how things work.... It's on Github. - Computourist This is really exciting. I want to try this out too. BTW, if someone wants to draft up a post that summarizes how to do this, I'll unsticky this thread and sticky the new post. I would help to link to this thread so people can see the process. Awesome!
|
|
|
Post by camblonie on Jan 24, 2015 16:02:48 GMT
Great job Computourist. The guide is awesome.
|
|
|
Post by jaydub on Jan 25, 2015 17:16:30 GMT
Hey all. I'm new to Arduino and RaspPi. Not a programmer, but definitely a tinkerer and Home Automation enthusiast. I got a RaspPi for Christmas, found the instructables, and I was hooked. I'm trying to start with a series of door and window sensors, linked to my RaspPi via the RFM69HW. I found this guy's work here, rdepablos.merlitec.com/mixed/rfm69-library-for-raspberry-pi and thought maybe I could get away with not using arduino on the RaspPi side, and just tie the RFM69HW right into the RaspPi. Will this work?
|
|
|
Post by lynn on Jan 26, 2015 4:04:34 GMT
Hey all. I'm new to Arduino and RaspPi. Not a programmer, but definitely a tinkerer and Home Automation enthusiast. I got a RaspPi for Christmas, found the instructables, and I was hooked. I'm trying to start with a series of door and window sensors, linked to my RaspPi via the RFM69HW. I found this guy's work here, rdepablos.merlitec.com/mixed/rfm69-library-for-raspberry-pi and thought maybe I could get away with not using arduino on the RaspPi side, and just tie the RFM69HW right into the RaspPi. Will this work? Try github.com/abouillot/HomeAutomation/tree/master/piGateway. I've had good luck getting my Pi <-> RFM69HW gateway working with his code. I'm using Eric's excellent Instructable for the nodes.
|
|
|
Post by backonline on Feb 17, 2015 20:25:36 GMT
Try github.com/abouillot/HomeAutomation/tree/master/piGateway. I've had good luck getting my Pi <-> RFM69HW gateway working with his code. I'm using Eric's excellent Instructable for the nodes. Does this work on duplex mode? Did you had any problem until now?
|
|
|
Post by thinkpeace on Feb 18, 2015 4:00:31 GMT
I created an RFM69/RTC PCB for the Raspberry Pi B+. The Eagle files are here: oshpark.com/shared_projects/u7wV37hW . 3 of these PCBs can be ordered from OshPark for $18.65. I've tested it with the RFM69 installed using the github.com/abouillot/HomeAutomation/tree/master/piGateway library. I haven't tested the RTC DS1307 yet. The only components needed to use the RFM69 portion are a 2x20 socket header, an RFM69 module, and optionally a u.FL SMT connector (http://www.adafruit.com/products/1661) or solder a piece of wire as an antenna. It has a cutout so that it fits in the Flirc case. flirc.tv/product/flirc-raspberry-pi-case/I included the RTC clock so that the Raspberry Pi can keep time even if power and internet connection are lost. Eric
|
|
|
Post by camblonie on Feb 18, 2015 12:26:38 GMT
Thanks for sharing Eric. OSH park is a great deal and I'm planning to do some sensor nodes. Do you have any sensor nodes designed yet?
|
|