Hello have with the gateway constantly disconnects after a few days and I can only reactivate it by resetting on the gateway.
Have now inserted a separate power supply with a large electrolytic capacitor 5000 µF-let's see....
Hello have with the gateway constantly disconnects after a few days and I can only reactivate it by resetting on the gateway.
Have now inserted a separate power supply with a large electrolytic capacitor 5000 µF-let's see....
@hard-shovel said in ESP8266Wifi Gateway won't connect:
MySensors version 2.3.2 and ESP8266 core 2.7.4 works
hello, he runs, after much effort and nerves
The values are a little bit very fluctuating? Probably you can only get away with a very accurate stable voltage of 5.0V.
Unfortunately, it's not that simple. Then it would have worked. What else could have caused this strange behavior?
The MOSFET_outputs are two blank pins. I haven't found anything official about this, except in a post here and a circuit. I supply the voltage converter with VCC and at the bottom of these pins towards the RESET button.
Oh, thank you so much. I had to make some small changes though. Maybe it's the newer Ceech Board version.
// IO PINS
pinMode( 13 , OUTPUT ); //unclear why this is so
...
present(0, S_MULTIMETER);
present(0, S_CUSTOM);
...
digitalWrite( POWER , HIGH );
...
digitalWrite( POWER , LOW );
Hi, I'm working with Ceech-Board for a pool sensor. I'm rewriting the code from V1.5 to 2.x. I encountered a problem with DIGITALWRITE which I can't explain.
Only if I set PINMODE unequal to the PIN for DIGITALWRITE, this output works.
void setup() {
pinMode(5, OUTPUT); // Setzt den Digitalpin 13 als Outputpin
}
void loop() {
digitalWrite(4, HIGH); // Setzt den Digitalpin 13 auf HIGH = "Ein"
delay(1000); // Wartet eine Sekunde
digitalWrite(4, LOW); // Setzt den Digitalpin 13 auf LOW = "Aus"
delay(1000); // Wartet eine Sekunde
}
It worked with pin 3, 5 and 13 e.g.
On the board the PIN D4 is followed by a MOSFET for switching. This worked once, once again not. No I seem to have found the problem, but what is the cause?
I'm getting low readings. The voltage at the sensor was OK. So it had to be the calculation. In my opinion the conversion of the 1023 values into a voltage is missing which can then be calculated further.
uint16_t uv = analogRead(UV_SENSOR_ANALOG_PIN);// Get UV value
uv = (uv* (5 / 1023.0))*1000;
if (uv>1170) {
uv=1170;
}
API 2.0
Sensors:
HC-SR501 (Motion)
DHT-22 (Temperature/Humidity)
MQ135 (Airquality)
MH-Z19/14 (CO2) --> Coming soon
@paqor
Probably one should not speak of a sensor CO2 value as well as responding to many other particles at the MQ135. The most accurate CO2 measurement we certainly be possible only with a MH-Z14. I now have to buy me a part and will then calibrate the MQ135 so. With the MQ135 can z. B. only say something about the air quality in relation to the outside air. It is rather a relative value.
Here the comparison of MH-14T (yellow) and MQ135 (red). One sees the calibration and as yet are both curves to each other.
[https://smarthome.gleisnetze.de/38-mhz-14-erste-erfahrungen-mit-dem-co2-sensor-fuer-mysensors-arduino-fhem]
Wahrscheinlich sollte man beim MQ135 nicht von einem CO2 Wert sprechen da der Sensor auch auf viele andere Partikel reagiert. Die genaueste CO2 Messung wir sicher nur mit einem MH-Z14 möglich sein. Ich habe mir jetzt so ein Teil bestellt und werde dann den MQ135 damit kalibrieren. Mit dem MQ135 lässt sich z. B. nur etwas zur Luftgüte im Verhältnis zur Außenluft sagen. Es ist also eher ein relativer Wert.
@TheoL said:
@paqor That's great. I looked at the Sketch you posted on your site and noticed you're still using a delay. Which as short as it may be can cause messages to be missed.
void loop(){ //----------------------------------------------------------------------------- //TEMP_FEUCHTE delay(dht.getMinimumSamplingPeriod());
My advice is to do this with a wait as well.
void loop(){ //----------------------------------------------------------------------------- //TEMP_FEUCHTE wait(dht.getMinimumSamplingPeriod()); // Changed ByTheo
That way you don't block incoming messages. Generally, if you want your sketch to wait use a wait.
genial, works perfectly....
Okay, super, Thank you very much for your effort. I will correct it immediately
VIELEN VIELEN DANK!!!!
Thanks alot
Hello, unfortunately is triggered no message here. The "textField" I applied and it is also available with a value. It is not even the "println" will be displayed. What am I doing wrong?
sleep(SLEEP_TIME); //sleep for: sleepTime
}
//incomingMessage_____________________________________________________
void receive(const MyMessage& message)
{
gasSensor.setR0(R0C);
Serial.println(F("Incoming Message:"));
}
@gieljnssns said in Air Quality Sensor:
@paqor
I'm interested, but i'm using mysensors 2.0. Can you update your sketch?
@paqor
https://gleisnetze.de/2016/08/07/sensoren4sketch/
@gieljnssns said:
@paqor
I'm interested, but i'm using mysensors 2.0. Can you update your sketch?
Yes, sure but I need time. I'm not a good programmer and need a lot of testing. My Englich is not particularly good. As some patience please, because I have to house, garden, woman and taking care of animals.
Has the type of installation (horizontal or vertical) have an impact on the values of MQ135? I have found no photos of built-in sensors already exist in the data sheet a statement.
Hello, there are statements if the values increase the MQ135 when a room ventilated, without people and is furnished? I I have several rooms here an increase over time. Perhaps this is also by the increase in temperature, sunlight or gases from the furniture. I have not found any literature on this. Is this behavior with other users as well?
I have compiled from various sources themselves something. The result is https://gleisnetze.de/2015/12/25/das-erste-kleine-programm/ described herein. The most plausible values I received with the MQ135.h library. For that I have then added the transfer after MySensors / FHEM.
I've read about. It sounds interesting.
I stand a little hard with the development. Is there a skit for MQ135.h and MYSENSORS?
I will test this afternoon.
I have used the code from epiere. Baking I have not done. I use different power supplies (USB, Samsung and a large controllable power supply). I sometimes feel that contacts do not function properly. But the sensor draws but only about 100 mA = 0.1 A? Then it seems to be on branding. I have three new sensors. Mostly we read that it is only an attempt here is to measure the CO2 content. When I check the values with a measuring instrument with which agree the details here https://olimex.wordpress.com/2015/05/26/experimenting-with-gas-sensors-and-arduino/ Branding should work outdoors? Can you show me a chart or values?
I have a question for the MQ135. Do not always be above 500 ppm, the measured values? I also get values of 0. I suspect that it is due to the conversion. The values vary greatly. Is that normal? I get the values with an ordinary power supply.