My Project

@JahFyahh it was mostly trial and error. I was lucky and my initial setup was good but these sensors have very sensitive adjustment (all cheap sensors do, i think) and sometimes a fraction of a turn is enough to change things. I think I wrote a simple "read in a loop" sketch and shaked it a bit (like a washing machine, small shakes) to see if i have a read. Hope that helps. I think top of the machine vibrates a bit more than back. if you put on the back, maybe try to mount it high as the upper part moves more than the lower part.

the strange think is if i wait a few seconds this goes on with normality.

Hi I would like to test too. On atmega 328p au 8mhz internal board.

@vorowski I'm experimenting with AWS IoT. Will post update if it works.

Finally finished! Here is the post: https://forum.mysensors.org/topic/4691/low-voltage-whole-house-power-supply

@TheoL I don't really use scenes, as most of what I do with Vera is using PLEG. But yes, that is a good idea. Look for updates that will include alarm setting and my garage door states. I just haven't gotten that far yet!

Nice project. Even though some items are in a language I do not understand, the sketch provided me with a better understanding of the MySensors work. Thank you for making the connection of what I know and what I was having trouble understanding.

@BartE (dutch site.. Even better) thanks for the link. I am looking for the safest way, seeing the this will not be in a quick access location. I want to put it away and only return for update/upgrades. But I will also look into an opto-coupler. Thanks for the tip.:+1:

Wooo, cool to see it live!

Welcome to the MySensors commuinty @chuckyancey ! Which part list are you referring to? The recommended size of the capacitor is 4.7 uF to 470 uF. The exact capacity usually doesn't matter. The capacitor needs to handle the same voltage as the radio, so at least 3.3V. 6V is the most common I think (that's what I use)

Hello, Some pictures of my scene controller inspired by this post ! I modified the original sketch to have two functions: keyboard for my alarm (from key 1 to 9) and scene controller (from key 10 to 16). Thanks @awi for the idea and the original sketch ! [image: 1471010532684-scene-controller-1.png] [image: 1471010537792-scene-controller-2.png] [image: 1471010571979-scene-controller-3.png] [image: 1471010569054-scene-controller-4.png] David.

To refine your code: Try to use arduino IDEs "Tab"-Function. Add few tabs to organise your code. e.g. Tab "Network" with functions like init_rf() and just call this function from your setup() or before() method. Same with your actual sensors. Consider making an extra tab to put all the relevant functions there. I try to keep my "Main" tab as clean as possible. As I understand your code right your rf95 receiver acts as a gateway to mysensors MyMessage msg(NODE_ID, V_FLOW); // Set's up mesaaging protocol to reciever, lets it know what variables are used MyMessage vmsg(NODE_ID,V_VOLUME); // V_FLOW means that the data being sent is a flowrate, etc. All your Sensor-Nodes who send to your receiver-serial-gateway should have different IDs and your gateway should use these IDs to send the sensor date to your controller. So NODE_ID should be a variable depending on "from which node" you got your sensor date. Have a look at "MyMessage.h" // Setters for building message "on the fly" MyMessage& setType(uint8_t type); MyMessage& setSensor(uint8_t sensor); MyMessage& setDestination(uint8_t destination); You can change the message Sensor (your actual sensor no the gateway) dynamically on your gateway depending on the payload you get and from which sensor.

@petewill @mfalkvidd After looking I have the 168.. I already have some more ordered that are the 328 though. I should have looked closer when I ordered the first batch. Thanks for the help! I figured it was probably something simple I had overlooked on my end.

Thanks. I did not know for sure if this was still the case in 2.0.0. wait(sleepTimer); added at the bottom of loop() function. now lets rewrite the sketch with your library.

Again right.. but the class definition is in the BL_Control.h file (line 47) The reason not to put the logic is that i yust want some sceleton for this kind of physical controller now i don' t have to include write and reads in the class and i can re-use it maybe for a PB dimmer. That off the declaration with the pinmodes is a habbit from the plain C period and assembler adventures with the AVR. There i set my outputs to a safe state before setting the DDR(x) register. As far as i assume the DDR is only relevant when you read the input (or want to do a logic operation on the input/output state. And it is overkill to write this in C++. But for me i consider it as a good excercise. And no i don't have a question I only wanted it to publish so others can steal maybe a idea Cheers,

You're welcome. It was for me also a struggle to get it working.

@csa02221862 they do but when I see the prices of ink and paper it's cheaper to order pcbs online with 24h option and DHL delivery ;)