Topics created by moskovskiy82

@hard-shovel said in Water Sensor: typical types are H11AA1 or LTV814 etc Thank you! Seems like the best way to for me than. Will order and wait for them to arrive

@moskovskiy82 Add a wait call after sending the initial value. I don't understand why you want to invert the saved state before sending it to the controller.

I can't test this but something like: #define SN "Four Fader Test" #define SV "0.1a" #define NUMBER_OF_DIMMERS 4 //System settings #define MY_RADIO_NRF24 #define MY_RF24_CE_PIN 8 //ADDED #define MY_NODE_ID 71 #include <MySensors.h> #include <SPI.h> #include "Fade.h" MyMessage dimmer[NUMBER_OF_DIMMERS]; MyMessage light[NUMBER_OF_DIMMERS]; Fade fader[NUMBER_OF_DIMMERS]; byte leds[NUMBER_OF_DIMMERS] = {3, 5, 6, 9}; void before() { int i = 0; for (auto fdr : fader) { fdr = Fade(leds[i++], 10, 0, 255, MILLIS_TIMER); // led speed 5 milliseconds/step; pwm at 0 min and 255 max (MILLIS_TIMER) fdr.begin(); } i = 0; for (auto msg : dimmer) msg = MyMessage(i++, S_DIMMER); i = 0; for (auto msg : light) msg = MyMessage(i++, S_BINARY); } void presentation() { sendSketchInfo(SN, SV); int i = 0; for (auto d : dimmer) present(i++, S_DIMMER); } void setup() { Serial.begin(9600); Serial.println(F("Setup Complete...")); } void loop() { uint32_t currentMillis = millis(); for (auto fdr : fader) fdr.update(currentMillis); } void receive(const MyMessage &message) { if (message.type == V_STATUS || message.type == V_PERCENTAGE) { int requestedLevel = atoi(message.data); if (message.type == V_STATUS) requestedLevel = requestedLevel ? 100 : 0; else requestedLevel = constrain(requestedLevel, 0, 100); fader[message.sensor].setTarget(map(requestedLevel, 0, 100, 0, 255)); send(light[message.sensor].set(requestedLevel > 0 ? 1 : 0)); send(dimmer[message.sensor].set(requestedLevel)); } } I used my non-blocking Fade.h: #ifndef Fade_h #define Fade_h #include <Arduino.h> enum timer{ MILLIS_TIMER, MICROS_TIMER }; class Fade { public: Fade() {}; Fade(int pin, uint32_t timeStep = 15, uint8_t minVal = 0, uint8_t maxVal = 255, timer timerSelect = MILLIS_TIMER); void begin(); void setTarget(int to); void update(); void update(uint32_t time); uint8_t getMin(); uint8_t getMax(); uint8_t getCurrent(); uint32_t readSpeed(); uint32_t writeSpeed(uint32_t time); uint8_t getSetpoint(); private: uint8_t _min; uint8_t _max; uint8_t _targetFade; uint8_t _pwmRate; uint32_t _time; uint32_t _last; uint8_t _pin; bool _microsTimer; }; #endif and my Fade.cpp: #include "Fade.h" #include <Arduino.h> Fade::Fade(int pin, uint32_t timeStep, uint8_t minVal, uint8_t maxVal, timer timerSelect) { _pin = pin; _time = timeStep; _min = minVal; _max = maxVal; analogWrite(_pin, _min); _pwmRate = _min; _microsTimer = timerSelect; } void Fade::begin() { analogWrite(_pin, _min); } void Fade::setTarget(int to) { _targetFade = (uint8_t) constrain(to, _min, _max); this->update(); } void Fade::update() { this->update(_microsTimer? micros() : millis()); } void Fade::update(uint32_t time) { if (time - _time > _last) { _last = time; if (_pwmRate > _targetFade) analogWrite(_pin, --_pwmRate); if (_pwmRate < _targetFade) analogWrite(_pin, ++_pwmRate); } } uint8_t Fade::getSetpoint() { return _targetFade; } uint8_t Fade::getCurrent() { return _pwmRate; } uint32_t Fade::readSpeed() { return _time; } uint32_t Fade::writeSpeed(uint32_t time) { _time = time; } uint8_t Fade::getMin() { return _min; } uint8_t Fade::getMax() { return _max; }

Thank you. Will do so and report back

Well guess it was a bug. Removed some of the include libs. Deleted serial output and ... it worked. Now one more thing to solve but i guess that's another story

If you are having trouble reading the serial prints you could send a msg to controller stating the value as 100 degrees/100% - this would then give peakson the graph to indicate errors instead of trying to get the serial. I am not sure (and as I have only been attempting to program arduinos for a month or so, could be very wrong ) but I don't think your if/else statement is structured correctly and the else part is only linked to the if(isnan(temparature)). If You could try separate if/else for temp and humidity, i.e. if(isnan(temparature) { ...error msg } else { ...send temp message } If(isnan(humidity) { ...error msg } else { ...send humidity msg } I'm also not sure if you need this line: delay(dht.getMinimumSamplingPeriod()); As you are only sampling every 60 seconds anyway...

@mfalkvidd Thank you! That solved everything. Well almost. At the end of the heatpump sensor there was a call to two functions sendHeatpumpCommand(); sendNewStateToGateway(); After moving the RGB code to the case switch - everytime i change the RGB light the AC beeps as it receives the command. Is there an easy solution for this?

Yes it was. Was powering the radio off an Arduino Nano's 3,3V and found that it didn't provide enough power to the radio. Switched to another nano and everything was fine. Thank you. P.S. A capacitor on the nrf power line didn't help

@moskovskiy82 Have a look at my Fire pit RGB striplight controller, The Mosfets in that project run very cool (can't detect any heat rise at all) with 10m of rgb strip lighting connected.

So nobody has done it yet? What about mosfets? Can the same schematics be used as with led strips? But how to limit the power fed to crees?

Well took the plunge. VCC 12V GND - GND as shared on 7805 with arduino IN - Digital pin of arduino to control. Works for now...

@moskovskiy82 the automatic builds are tested with 1.8.2 currently.

@moskovskiy82 said in Orange PI zero. Problem running the gateway: Yes i also believe ./configure shoul be one line - it's just that documentation is not that clear for not tech guys like me. So if maintainer of the page is reading this - it should be better done like for the Raspberry gateway page. It's more clear. I've updated the Orange Pi page. Thanks for catching this.

At least it was getting id 75

Hi, it is some time since I made this (and used it to be honest) but you can check this post where I integrated what you are asking about. https://forum.mysensors.org/topic/4552/sleeping-while-waiting-for-double-click-delayed-sleep/3 Node and the code is unfortunately not in use currently so I do not recall all the details, but maybe you can get something out of it

Sorry tp bump an old one but still haven't found a solution. MQTT passes it as mys-in/36/0/1/0/40 255,85,73 So the message payload can be passed directly to arduino as PWM values

How did this go from a relay/power issue to changing RGB color values?

@moskovskiy82 could you describe why you want the average? Are you sure the median wouldn't be a better choice? Or letting the controller handle averaging, since it will have access to past events even if the sensor is restarted.

@moskovskiy82 can you subscribe and publish something on the pc? Then do the same on the rpi. At least that should work...

Yes. The two power supplies need a common reference, so the grounds need to be connected. BR Jonas

@moskovskiy82 said: GP2Y1010 There are many sketches available for Arduino: http://arduinodev.woofex.net/2012/12/01/standalone-sharp-dust-sensor/ You have to (1) adopt it for MySensors (2) change it according to your needs Good luck

You only need to enable if if you actually use the resulting ack message for something. If you look at the RelayWithButton example you can see an example of how the local relay only get updated when the ack is received (after pressing the local button).

Ok got it working. But now i see the main problem. When you change the colour - there is a lag so othe colours are seen. Same goes to switching off. For example we were at white light fullbrightness than switched off. You can first see the light becoming yelow, than blue than off. How can this be fixed? If i understand correctly - you have to pass all these HSB value processing to arduino and have the controller send 3 values at once. Are there any examples?

Well, uncomment the #define MY_LEDS_BLINKING_FEATURE and to be sure define all 3 LEDS to one (unused) pin. So you will make sure that is/is not the reason for the wrong behaviour.

@moskovskiy82 if it's allways reporting x.0 than you store the result of the reading in a double of long. If you want to get rid of the decimals. You only have to cast the value to an int. This will truncate the value. long x = 2.3; Serial.println( (int)x ); will result in 2

Well everything almost fixed. The code if somebody will be building something similar... 4 push buttons attached and 3 dimmers + MQ and DHT22 All the logic is supposed to be handled by the controller. Problems remaining... If you set the button state in the controller - it doesn't get updated on the node... Any hints appreciated on this And the major problem - if the node resets the LIGHTS are ON! As has been hinted in another topic the code has to be rewritten so in the beginning it sets the values to zero and informs the controller isntead of pulling values. But my lack of knowledge stops me on this one. So help will be much appreciated #define SN "Kitchen Hood" #define SV "1.0" #include <MySensor.h> #include <SPI.h> #include <DHT.h> #include <math.h> #include <Wire.h> #include <Bounce2.h> //DEFINE CHILD_IDS #define DIMMER_NODE_1 0 #define DIMMER_NODE_2 1 #define DIMMER_NODE_3 2 #define CHILD_ID_HUM 4 #define CHILD_ID_TEMP 5 #define CHILD_ID_MQ 6 #define CHILD_BUT1 7 #define CHILD_BUT2 8 #define CHILD_BUT3 9 #define CHILD_BUT4 10 //BUTTONS #define BUTTON_PIN1 A0 #define BUTTON_PIN2 A1 #define BUTTON_PIN3 A2 #define BUTTON_PIN4 A3 //MQ+DHT #define MY_LEDS_BLINKING_FEATURE #define HUMIDITY_SENSOR_DIGITAL_PIN 8 const int MQ_Pin = A4; //DIMMER #define LED_PIN_1 3 #define LED_PIN_2 5 #define LED_PIN_3 6 #define FADE_DELAY 10 MySensor gw; DHT dht; //BUTTONS Bounce debouncer_1 = Bounce(); Bounce debouncer_2 = Bounce(); Bounce debouncer_3 = Bounce(); Bounce debouncer_4 = Bounce(); int oldValue_1=-1; int oldValue_2=-1; int oldValue_3=-1; int oldValue_4=-1; bool state1; bool state2; bool state3; bool state4; MyMessage msgbut1(CHILD_BUT1,V_TRIPPED); MyMessage msgbut2(CHILD_BUT2,V_TRIPPED); MyMessage msgbut3(CHILD_BUT3,V_TRIPPED); MyMessage msgbut4(CHILD_BUT4,V_TRIPPED); //MQ+DHT float lastTemp; float lastHum; float hum_floa; float last_mq_reading; MyMessage msgHum(CHILD_ID_HUM, V_HUM); MyMessage msgTemp(CHILD_ID_TEMP, V_TEMP); MyMessage msgMQ(CHILD_ID_MQ, V_LEVEL); //DIMMER byte currentLevel[3] = {0,0,0}; MyMessage dimmerMsg0(0, V_DIMMER); MyMessage lightMsg0(0, V_LIGHT); MyMessage dimmerMsg1(1, V_DIMMER); MyMessage lightMsg1(1, V_LIGHT); MyMessage dimmerMsg2(2, V_DIMMER); MyMessage lightMsg2(2, V_LIGHT); unsigned long SLEEP_TIME = 30000; // Sleep time between reads (in milliseconds) void setup() { Serial.begin(9600); Serial.println( SN ); gw.begin( incomingMessage ); gw.sendSketchInfo(SN, SV); //MQ+DHT dht.setup(HUMIDITY_SENSOR_DIGITAL_PIN); gw.present(CHILD_ID_HUM, S_HUM); gw.present(CHILD_ID_TEMP, S_TEMP); gw.present(CHILD_ID_MQ, S_AIR_QUALITY); gw.wait( 50 ); //DIMMER gw.present( DIMMER_NODE_1, S_DIMMER ); gw.wait( 50 ); gw.present( DIMMER_NODE_2, S_DIMMER ); gw.wait( 50 ); gw.present( DIMMER_NODE_3, S_DIMMER ); gw.wait( 50 ); gw.request( DIMMER_NODE_1, V_DIMMER ); gw.wait( 50 ); gw.request( DIMMER_NODE_2, V_DIMMER ); gw.wait( 50 ); gw.request( DIMMER_NODE_3, V_DIMMER ); //BUTTONS pinMode(BUTTON_PIN1,INPUT); digitalWrite(BUTTON_PIN1, HIGH); pinMode(BUTTON_PIN2,INPUT); digitalWrite(BUTTON_PIN2, HIGH); pinMode(BUTTON_PIN3,INPUT); digitalWrite(BUTTON_PIN3, HIGH); pinMode(BUTTON_PIN4,INPUT); digitalWrite(BUTTON_PIN4, HIGH); debouncer_1.attach(BUTTON_PIN1); debouncer_1.interval(5); debouncer_2.attach(BUTTON_PIN2); debouncer_2.interval(5); debouncer_3.attach(BUTTON_PIN3); debouncer_3.interval(5); debouncer_4.attach(BUTTON_PIN4); debouncer_4.interval(5); gw.present(CHILD_BUT1, S_DOOR); gw.wait( 50 ); gw.present(CHILD_BUT2, S_DOOR); gw.wait( 50 ); gw.present(CHILD_BUT3, S_DOOR); gw.wait( 50 ); gw.present(CHILD_BUT4, S_DOOR); gw.wait( 50 ); } void loop() { gw.process(); int value_but_1 = debouncer_1.read(); int value_but_2 = debouncer_2.read(); int value_but_3 = debouncer_3.read(); int value_but_4 = debouncer_4.read(); //BUTTONS debouncer_1.update(); if (value_but_1 != oldValue_1) { if ( value_but_1==0) { state1 = !state1; gw.send(msgbut1.set(state1)); } oldValue_1 = value_but_1; } debouncer_2.update(); if (value_but_2 != oldValue_2) { if ( value_but_2==0) { state2 = !state2; gw.send(msgbut2.set(state2)); } oldValue_2 = value_but_2; } debouncer_3.update(); if (value_but_3 != oldValue_3) { if ( value_but_3==0) { state3 = !state3; gw.send(msgbut3.set(state3)); } oldValue_3 = value_but_3; } debouncer_4.update(); if (value_but_4 != oldValue_4) { if ( value_but_4==0) { state4 = !state4; gw.send(msgbut4.set(state4)); } oldValue_4 = value_but_4; } } //DHT+MQ delay(dht.getMinimumSamplingPeriod()); float temperature = dht.getTemperature(); if (isnan(temperature)) { Serial.println("Failed reading temperature from DHT"); } else if (temperature != lastTemp) { lastTemp = temperature; gw.send(msgTemp.set(temperature, 1)); } float humidity = dht.getHumidity(); if (isnan(humidity)) { Serial.println("Failed reading humidity from DHT"); } else if (humidity != lastHum) { lastHum = humidity; gw.send(msgHum.set(humidity, 1)); } float mq_reading = analogRead(MQ_Pin); if (isnan(mq_reading)) { Serial.println("Failed mq_reading"); } else if (mq_reading != last_mq_reading) { last_mq_reading = mq_reading; gw.send(msgMQ.set(mq_reading, 1)); } //DIMMER void incomingMessage(const MyMessage &message) { if (message.type == V_LIGHT || message.type == V_DIMMER) { int requestedLevel = atoi( message.data ); requestedLevel *= ( message.type == V_LIGHT ? 100 : 1 ); requestedLevel = requestedLevel > 100 ? 100 : requestedLevel; requestedLevel = requestedLevel < 0 ? 0 : requestedLevel; Serial.print( "Changing level to " ); Serial.print( requestedLevel ); Serial.print( ", from " ); Serial.println( currentLevel[message.sensor] ); fadeToLevel( requestedLevel, message.sensor); switch(message.sensor) { case 0: gw.send(lightMsg0.set(currentLevel[0] > 0 ? 1 : 0)); gw.send( dimmerMsg0.set(currentLevel[0]) ); break; case 1: gw.send(lightMsg1.set(currentLevel[1] > 0 ? 1 : 0)); gw.send( dimmerMsg1.set(currentLevel[1]) ); break; case 2: gw.send(lightMsg2.set(currentLevel[2] > 0 ? 1 : 0)); gw.send( dimmerMsg2.set(currentLevel[2]) ); break; } } } void fadeToLevel( int toLevel, byte sensorId ) { int delta = ( toLevel - currentLevel[sensorId] ) < 0 ? -1 : 1; while ( currentLevel[sensorId] != toLevel ) { currentLevel[sensorId] += delta; switch(sensorId) { case 0: analogWrite( LED_PIN_1, (int)(currentLevel[sensorId] / 100. * 255) ); break; case 1: analogWrite( LED_PIN_2, (int)(currentLevel[sensorId] / 100. * 255) ); break; case 2: analogWrite( LED_PIN_3, (int)(currentLevel[sensorId] / 100. * 255) ); break; } delay( FADE_DELAY ); } }```

Check out the other topic http://forum.mysensors.org/topic/3664/mqtt-dimmer-message/7

gw.process is called in the loop, so messages should be processed even with repeater mode turned off. I suggest upgrading the library to 1.5.4 for the nodes, as the bug regarding payloads was solved with that version.

The answer was simple Change digitalWrite( LED_PIN_1, 0); to analogWrite( LED_PIN_1, 0);

@gohan these values are just the ones i used and should filter lowpass at about 5.9 kHz. The ripple on the LM2596s is usually arround 25-50kHz. (Depends on which clone you get. ;)) I'm no electrical engineer. Maybe @AWI can comment if there may be a more suitable component selection.

@Mark-Swift let us know how they perform. The supplier looks very professional. Would be interesting if they really reach the promised 2.1km (I wonder with which antenna) even better to use 3.3v (hence on my next one to play it safe I'll use a spare 5v -> 3.3v level shift converter too). Or use a 3.3V pro mini.

@moskovskiy82 , it makes sense. Glad you ruled it out!

long previousMillis = 0; // will store last time something happened long interval = 5000; // interval at which to blink (milliseconds) void loop() { unsigned long currentMillis = millis(); if(currentMillis - previousMillis > interval) { // save the last time something happened previousMillis = currentMillis; Insert your code here... } } Note millis() does not work if you are using gw.sleep()

No answer for this one?

@moskovskiy82 NO there should be no problem when swapping L and N.

for me it has impact on the accuracy of readings... if we can speak of accuracy on MQ series sensors...

DHT - Yes, Using 2xAA to VCC will also work untill it reaches somewhere around 2.6-2.8V where the arduino will stop working. I use booster and have nodes almost hitting a year now, still running and reporting good health.

@moskovskiy82 said: Invalid protocol "MQTT" Please search the forum first before you post an issue.

If you use Set to send your temp/hum you can define how many decimals you want: MyMessage& set(float value, uint8_t decimals); For example: gw.send(msgTemp.set(temperature, 1)); will send you the value with 1 decimal. Reference: here

i Know it's in repeater mode. I couldn't find any downsides in turning it on except that the sleep function had to be disabled. It still acts as a sensor node

If you still want the delay you can use gw.wait instead. That will process incoming radio messages.

im pretty sure I turned it off in mosquito - namely for opentracks.

@Tmaster I am not doubting the principle of increasing effective radiated power by way of relocating the antenna, or improving the radiation lobe in a set direction. The additional gain is important with weak signals at both send and receive ends, but at 50m it should not be an issue at these frequencies unless there are major attenuations to the signal. I have to guess you already have a dipole at the receiver ?

I don't think Arduino has a standard sleep function. Which function do you mean? The MySensors sleep function does several things, including powering down the radio (if a radion is used). It is quite power efficient.

Try adding a cap on between GND/VCC to stabilise the power supply.

Hi. I know this topic is a few months old now, but I'm wondering if you were able to accomplish what you wanted to do. I have a wifi gateway set up and would like to do something similar but with Home Genie as the broker running on a Raspberry PI. Did you have to modify the MQTT Client code much to fit your needs? I'm new to MySensors, but I've been researching topics as much as possible before I dive into the code. Can you point me to the version of the client code that worked for you? I would appreciate any help or tips as I am eager to set up several sensors around the house and perhaps a relay to control a garage door. Thanks.

I think the instructions in the gateway sketch are quite clear: CSN/CS GPIO15 ... and ... Connect GPIO15 via 10K pulldown resistor to GND This will pull the GPIO to GND during flashing and allows control of CSN when the gateway code is running.