Topics created by ferpando

Thank you. I'll make some tests if I can find one

Hello, Here's a simple schematic of the project

You can also use json to control your nodes... have a look the wiki there as well.

Oregon is 433mhz right? You need a 433mhz reciever and either decode it into MySensors language or connect a reciever like RFXCom or RFLink (work with Domoticz) to your controller (=Not MySensor). Both above support Oregon. Here is a good project by petewill that includes decoding 433mhz to MySensors: http://forum.mysensors.org/topic/7/controlling-blinds-com-rf-dooya-motors-with-arduino-and-vera

When radio drivers setup was created in 1.5 the channel radio constructor argument was simply forgotten. I think there was a pull request fixing this but I will probably not do any more patches of 1.5.

@tbowmo said: http://forum.mysensors.org/topic/1965/nodered-injected-between-domoticz-and-mysensors Thank you for the answer. I'll take a look at that.

@Drcashman by outputs you mean to control 2-3 light fades? I guess it wouldn't be too difficult. Just add counters for current and requested values for each fade to keep them independent

It needs a minimum load onthe output, in order to function correctly. If this minimum requirement is not met, the output couod become unstable, and self oscillate. I've Seen this with an electronic transformer for halogen lights, where i use led lamps instead. Needed 1-2 halogen spots on it (it supplies 5 spots in total) in order for the electronic transformator to work correctly

@Nuubi No more node lock-ups since I installed that power supply, so it works as expected.

Hello sir, have any update? we are waiting for your new updates. Thank you

@ferpando Hi, I am installing your HomeRelay_1 program (16 relay with Arduino) and would like the MyBuffer.h and MyBuffer.cpp. The only ones I have found have (sensor, type) for buffer.push where you actually have (sensor, type,string data). The program will not compile on v1.6.5. Thank you for all that you do for the community!

@hek version 1.0.6 ok, I added the include and compiled correctly. Thank you

With the help from @korttoma & @AWI , I put together this sketch. I've tested it and it works. Have fun! #include <MySensor.h> #include <SPI.h> unsigned long SLEEP_TIME = 120000; // Sleep time between reports (in milliseconds) #define DIGITAL_INPUT_SENSOR 3 // The digital input you attached your motion sensor. (Only 2 and 3 generates interrupt!) #define INTERRUPT DIGITAL_INPUT_SENSOR-2 // Usually the interrupt = pin -2 (on uno/nano anyway) #define CHILD_ID 1 // Id of the sensor child #define LED_PIN 5 MySensor gw; // Initialize motion message MyMessage msg(CHILD_ID, V_TRIPPED); void setup() { gw.begin(); // Send the sketch version information to the gateway and Controller gw.sendSketchInfo("Motion Sensor", "1.0"); pinMode(DIGITAL_INPUT_SENSOR, INPUT); // sets the motion sensor digital pin as input pinMode(LED_PIN, OUTPUT); // Register all sensors to gw (they will be created as child devices) gw.present(CHILD_ID, S_MOTION); } void loop() { // Read digital motion value boolean tripped = digitalRead(DIGITAL_INPUT_SENSOR) == HIGH; Serial.println(tripped); gw.send(msg.set(tripped?"1":"0")); // Send tripped value to gw { if (tripped){ // from the "Blink" example sketch :-) digitalWrite(LED_PIN, HIGH); // turn the LED on (HIGH is the voltage level) delay(1000); // wait for a second digitalWrite(LED_PIN, LOW); // turn the LED off by making the voltage LOW delay(1000); } // Sleep until interrupt comes in on motion sensor. Send update every two minute. gw.sleep(INTERRUPT,CHANGE, SLEEP_TIME); } }

I want a rigol too. But better not buy one, I have my trusty 60mhz Tektronix scope which is enough at the moment

I think you are on the right track. There' s no need for the interrupt in your case. So you don't have to worry about what process is being interrupted. @ferpando said: It was just a quick proof of concept.. I guess I should set tripped to false once the message is sent John had the right logic. You don't want to set tripped false until the input (ie: motion dectector output) goes false, not when a message is sent. His suggested logic sends one message whenever the motion detector goes active, and not again until it goes inactive and active again. (Which happens after no motion for some time period adjustable via a pot on the motion detector).

@hek said: http://www.mysensors.org/build/debug#enabling-debug-logging I had to clear the eprom and reprogram. Now it's working again. One of the times I was trying to add the sensor without the radio plugged in. My bad :-S

I have the "System Monitor" plugin installed so I get it as a Variable in the advanced tab.

@mainali This circuit might help with what you are doing. See attached. Try building this circuit and connect "signal & ground" to dimmer LED actuator PWM. Again I can't stress enough be careful with AC power!!!

You may want to disconnect everything and just leave the power supply and arduino, then measure the RAW pin and VCC pin, RAW should be anything above 5V, VCC should read 5V for the 5V version and 3.3V for the 3.3V version. Any other readings on VCC suggest that your regulator on the arduino is faulty.

@Yveaux You might be right, but then again how would I learn about shift registers if I don't use them?

@hek I managed to get it working. Thanks again for the pointers.

@hek I've been trying to get some buttons in the vera plugin but I've had not much luck. I addded some code to arduino.xml and arduino.json but nothing appears. I uploaded the files to the repo. Could you take a look when you have the time? S_Arduino.xml D_Arduino1.json L_Arduino.lua Yesterday I also made a new system for the nodes to have also a queue. Looks something like this: #include <MySensor.h> #include <SPI.h> #include <MyBuffer.h> ....... long previousMillis = 0; // will store last time buffer was processed long interval = 1000; // interval at which to check buffer MyBuffer buffer; // define a new buffer MySensor gw; .......... void setup() { .... sensor setup code.... } void loop() { gw.process(); unsigned long currentMillis = millis(); if(currentMillis - previousMillis > interval) { previousMillis = currentMillis; processBuffer(); } } void incomingMessage(const MyMessage &message) { buffer.push(message.sensor,message.type); } //gets message from buffer if exists void processBuffer(){ if(!buffer.isEmpty()){ String msg=buffer.pop(); int mIndex = msg.indexOf(';'); int secondmIndex = msg.indexOf(';,', mIndex+1); String firstValue = msg.substring(0, mIndex); String secondValue = msg.substring(mIndex+1, secondmIndex); int sensor = firstValue.toInt(); int type = secondValue.toInt(); processMsg(sensor, type); } } //process message from queue void processMsg(int sensor, int type){ //do some stuff } It's pretty basic but it works. The library files are here: MyBuffer.h MyBuffer.cpp

@Zeph said: Or better still, optocouplers or an analog switch as described above... Yes, that's a better option as relays are quite power hungry and bulky.

It's not recommended. Let the gateway handle radio<->serial communication to minimize missed messages.

Is any of this code archived someplace? Any direction to get started? I want to shut off my tv via Vera Edge.

Hello again, My sensor node had the radio module too close to the arduino so I thought it might cause interference. I modified it a bit putting the radio 3-4cm away and with the antenna up and it started working like a charm. The problem I have now is that I don't have a node module on vera's interface. I have only the lightswitch. Tx: fr=3,to=0,la=3,ne=0,ci=3,mt=2,ty=2,cr=13: Ack: received OK Message available on pipe 1 Sent ack msg to 0 Rx: fr=0,to=3,la=0,ci=3,mt=3,t=2,cr=134(ok): 0 Message addressed for this node. Message available on pipe 1 Sent ack msg to 0 Rx: fr=0,to=3,la=0,ci=3,mt=1,t=2,cr=55(ok): 1 Message addressed for this node. Relaying message back to gateway. Tx: fr=3,to=0,la=3,ne=0,ci=3,mt=1,ty=2,cr=28: 1 Ack: received OK Incoming change for relay on pin:3, New status: 1 Message available on pipe 1 Sent ack msg to 0 Rx: fr=0,to=3,la=0,ci=3,mt=1,t=2,cr=80(ok): 0 Message addressed for this node. Relaying message back to gateway. Tx: fr=3,to=0,la=3,ne=0,ci=3,mt=1,ty=2,cr=123: 0 Ack: received OK Incoming change for relay on pin:3, New status: 0

Yes, but you need to reconfigure io-pins correctly. Join the discussion here: http://forum.mysensors.org/topic/115/implementing-multiple-sensors#780