General Discussion

Thanks for that advice. I reckon ill get started with some hacking and see how far I get! Thanks!

I like the logical grouping of sensors in nodes. It also saves me a lot of 'hardware'. And there is the challenge of combining code, (conflicting) libraries and amount of memory. Which I actualy like. You need to use some best practices (like non blocking code) and be aware of timing issues though.

I rebooted the sensor and now it does store the sensorID. (Could this have been as I was on 1.6.5-R5 and now on 1.7.7 or the IDE?)

Thanks for the input all I might put two sensors together and see what transpires to see if I can narrow things down a bit and see if it is specifically a sensor issue or the controller.

Thanks for the feedback. I only just found this post and it looks like this is what I am looking for:- link text

How did you get it to work?? Could you write a noob tutorial on how it works with bootloaders and how to upload them? I've downloaded the mysensors1.5 zip file, but what are the next steps, how do i get it to show up in arduino sketch and after that what must i change and how do i upload it in my arduino??

Hi! If you connect the ethernet gateway to your routner/switch then domotiocz/raspberry will find and read from that IP given to the ethernet gw. If you want you can connect the radio directly onto the raspberry (http://forum.mysensors.org/topic/1151/tutorial-raspberry-pi-nrf24l01-direct-connection) but I dont know much about that. Yes, atleast i have 4 sensors in the same node. I dont know max and has never combined sensors and actuators. Dont know :) Welcome!

Hi, thats a LOT of text - wow. but very interesting (didnt read everything until now). Is there a topic or discussion ongoing on this? Maybe it can be redone with "mysensors 2.0" (in parallel to 1.5).. I will make a deep-dive into the source code now. Its too interesting and i like this kind of coding ;) At last: Sry that i opened another topic for this question. looks like i didnt use the right words in the search :/ Greetings

@Starjade Here's a good write-up as to what MySensors is about: http://www.mysensors.org/about/components. The intent of MySensors is for a Home Automation system (the controller) to talk to remote sensors through a gateway using NRF24L01+ radio modules, although other radio types are now supported as well. Cheers Al

hi guys thanks all for the responses. Tis all clear now and makes sense

@TD22057 said: @John-Connolly You may want to the try the client gateway from this thread: http://forum.mysensors.org/topic/524/mqtt-client-gateway It's a real MQTT client (point it at your Mosquitto broker) which I find easier to understand than the pseudo-broker that the MQTT gateway uses. That's EXACTLY what I need/want! Thanks! I'll give it a shot the second the new kit arrives from AliExpress...which is taking its time.

Great,Thnx, Exactly what I was looking for! Mark

I've been planning on using JST PH (2.0 mm pitch) connectors on my custom PCB's to connect the external connectors (GX12, 3.5 mm headphone jacks, 5.5 mm power sockets) from the sensor case to the board. They're nice in that they're fairly small, polarized, and cheap. But - you need to buy a good crimper - the pins are incredibly tiny. I almost decided to by the plugs with wires attached because they're so hard to crimp. None the crimpers I own was small enough so I ordered the (Engineer PA 09)]http://www.ebay.com/itm/Engineer-PA-09-Mini-Molex-Amp-JST-Crimp-Tool-Wire-Terminal-Crimping-Pliers-/252030460510?hash=item3aae2fa25e] which seems to be the cheapest "good" option. Another option on the board (I wouldn't use these on the sensor case) are Dupont 2-pin connector. These "Dupont" connectors require a female pin (which is also really cheap) and push on to standard 0.1" pitch pins on a PCB (like the 4x2 NRF radios). They have the advantage that they use less space than the JST connectors but are not polarized. Search for "Dupont connector" on ebay to find tons of options. I can't decide if the easier crimping and less board space are worth the risk of mounting connectors backwards and potentially wrecking components.

@fets No - the NRF radio has 5V tolerant inputs (you still need to supply it 3.3V on VCC, but it can handle 5V on the signal lines). The RFM radio does not - it needs 3.3V on the signal lines. So the NRF works fine w/ 3.3V and 5V arduino's. The RFM radio needs this modification when used with 5V arduino's. FYI - I found someone who build a small break out board for the radio and had an optional level shifter using a simple resistor network and said it worked great. I liked the idea, but not his board layout so I modified it and ordered some from OSHPark a few days ago. The original board is here. My modified board (no 3.3V regulator or flash support) is here. I wanted minimum width in order to mount the board on the side of a box (thickness dimension). Warning: I haven't tested this yet (order arrives in 2 weeks) so I haven't published schematics or anything else for it yet so I wouldn't order it if anyone is interested. There are tons of RFM69 breakout boards with various features (including one that plugs into an NRF 2x4 socket) if you search for them on OSHPark.

I m on win10, no pb tu use IDE 1.6.5 ftdi and ch340 drivers are default include

Ok got the scroll to work, it is in from the edge of black area, I need to touch and bee still for a second ... Then drag. Thanks for your help.

You can actually combine both I think. Search for sleep. There is a sleep function bool sleep(int interrupt, int mode, unsigned long ms=0); that both listenes to an interrupt and wakes up after a certain time. The return boolean value indicates which one.

Although i like the idea, it will force you to send a value even if it has not changed. Defeats a bit a battery optimized sensor node.

https://www.youtube.com/watch?v=60P1xG32Feo