@dzjr this is what I also had in mind but... are you using a commercial sensor or you built one yourself?
When I say "sensor" I mean the device that is currently in the soil.
I checked different commercial sensor and all seem to become unusable in a very short time... this is why I'm really interested in your solution
@dzjr , glad you solved your problem .. but... can you please share which sensor are you using to measure the soil moisture?
I found a lot of sensor suitable for in-house measuring but nothing for outside which is not becoming unusable very quickly.
Whatever information is highly appreciated...
Giacomo
Hi everybody.
I'm trying to add the irrigation system of my terrasse to the existing domotic system.
The idea is to measure the soil moisture of each big flowerpot and send water accordingly.
Since a couple of weeks I'm reading tons of web pages on this subject but everything seems to be related to indoor applications and most of them under evaluate the corrosion aspects of a sensor constantly remaining in a moist soil outdoor.
So, here is the question to the group.
Does anybody have experience in this area and is willing to share it?
Of course, cost wise, I'm not looking for a very expensive sensor, but I'm ready to spend what is needed to have a solid solution, corrosion resistant.
Any idea or suggestion?
Thanks
Giacomo
Sorry... my fault.
Yes, the need to pull the pin low is the only sure info I found around.. 
@gohan , if I understand well, in a relay like the one of the attached picture, you removed the jumper, connected +5V to JD and GND, In1, In2, 3,3V on the other connector?
If this is true I'll be happy because this is how I'd have done.... but I couldn't find anybody confirming it...
Good afternoon everyone. I'm here to get suggestions from those of you who are more experienced than me in electronics.
The problem is simple. I have an ESP8266 (NodeMCU V3 Lolin) and I'd like it to drive a 5Vdc relay.
Searching in internet I can find many samples like this... BUT.... some of them are connecting the positive wire of the relay to Vcc (3,3V), some others to VU (5V) and all say it's perfectly working.
If I find two solution to the same problem I get worried 
Specifically, should I connect Vcc, I'm not sure that the relay would switch in a secure way.
At the same, if I connect it to VU, I'm asking myself if this would not create a problem since the pin triggering the relay is coming from a GPIO pin and should be 3.3V
Please forgive me if this is a stupid question but I have to experience in this area.
Thanks in advance
Giacomo
@pjr, thanks for your update. I went to check the solution proposed in the link you attached... and let me confess... got the concept, but it's complexity is currently not something at my reach.
Meaning.. as my solution is very small and working, for the time been I'll stick to it and spend my time for further function implementation.
My only worry... your example was just a few lines... understandable... how did they end up with 1700 lines of code or this?
Whatever.. I'l go back to it when I have some more time as I prefer an official implementation to a patch like mine...
@pjr , what you are suggesting is exactly what I wanted at the beginning..... but... my understanding from the first answer I got and for this https://www.domoticz.com/forum/viewtopic.php?f=42&t=9775&sid=1fea4af7b12f84f656ca4aa825eb6115
is that the sendHeartbeat() function is basically accepted but disregarded in Domoticz, meaning, would not create problems but not fixing the issues.
Of course this is my understanding and would be glad to have additional opinions/tests
@kimot , right now I'm using the Arduino IDE application which allows me to upload to NodeMCU just using the USB cable.
Reading the ESPeasy documentation I understand that this type of connection is not an option and you must have a USB to TTL interface.
I'd be very happy to hear that I don't need it... otherwise I'm going to get one on monday...
Domoticz log changed from this:
2018-01-05 14:19:04.819 MySensors: Gateway Ready...
2018-01-05 14:19:05.820 MySensors: Gateway Version: 2.1.1
2018-01-05 14:19:05.820 MySensors: Gateway Version: 2.1.1
2018-01-05 14:20:00.270 dzVents: Debug: Dumping domoticz data to /home/pi/domoticz/scripts/dzVents//domoticzData.lua
2018-01-05 14:20:00.293 dzVents: Debug: Event trigger type: time
2018-01-05 14:20:30.855 Error: MySensors1 hardware (7) nothing received for more than 1 Minute!....
2018-01-05 14:20:31.856 Error: Restarting: MySensors1
2018-01-05 14:20:32.829 MySensors: TCP/IP Worker stopped...
2018-01-05 14:20:33.831 MySensors: trying to connect to: 192.168.1.7:5003
2018-01-05 14:20:34.831 MySensors: connected to: 192.168.1.7:5003
2018-01-05 14:20:34.831 MySensors: Gateway Ready...
2018-01-05 14:20:35.832 MySensors: Gateway Version: 2.1.1
2018-01-05 14:20:35.832 MySensors: Gateway Version: 2.1.1
2018-01-05 14:21:00.379 dzVents: Debug: Dumping domoticz data to /home/pi/domoticz/scripts/dzVents//domoticzData.lua
2018-01-05 14:21:00.402 dzVents: Debug: Event trigger type: time
2018-01-05 14:22:00.486 dzVents: Debug: Dumping domoticz data to /home/pi/domoticz/scripts/dzVents//domoticzData.lua
2018-01-05 14:22:00.510 dzVents: Debug: Event trigger type: time
2018-01-05 14:22:00.846 Error: MySensors1 hardware (7) nothing received for more than 1 Minute!....
2018-01-05 14:22:01.847 Error: Restarting: MySensors1
2018-01-05 14:22:02.841 MySensors: TCP/IP Worker stopped...
2018-01-05 14:22:03.842 MySensors: trying to connect to: 192.168.1.7:5003
2018-01-05 14:22:04.843 MySensors: connected to: 192.168.1.7:5003
To this:
2018-01-05 14:55:00.413 dzVents: Debug: Dumping domoticz data to /home/pi/domoticz/scripts/dzVents//domoticzData.lua
2018-01-05 14:55:00.436 dzVents: Debug: Event trigger type: time
2018-01-05 14:55:35.108 (MySensors1) Light/Switch (Security Sensor)
2018-01-05 14:56:00.520 dzVents: Debug: Dumping domoticz data to /home/pi/domoticz/scripts/dzVents//domoticzData.lua
2018-01-05 14:56:00.543 dzVents: Debug: Event trigger type: time
2018-01-05 14:56:20.113 (MySensors1) Light/Switch (Security Sensor)
2018-01-05 14:57:00.127 dzVents: Debug: Dumping domoticz data to /home/pi/domoticz/scripts/dzVents//domoticzData.lua
2018-01-05 14:57:00.151 dzVents: Debug: Event trigger type: time
2018-01-05 14:57:05.120 (MySensors1) Light/Switch (Security Sensor)
2018-01-05 14:57:50.124 (MySensors1) Light/Switch (Security Sensor)
2018-01-05 14:58:00.235 dzVents: Debug: Dumping domoticz data to /home/pi/domoticz/scripts/dzVents//domoticzData.lua
2018-01-05 14:58:00.259 dzVents: Debug: Event trigger type: time
2018-01-05 14:58:35.129 (MySensors1) Light/Switch (Security Sensor)
2018-01-05 14:59:00.344 dzVents: Debug: Dumping domoticz data to /home/pi/domoticz/scripts/dzVents//domoticzData.lua
2018-01-05 14:59:00.367 dzVents: Debug: Event trigger type: time
2018-01-05 14:59:20.134 (MySensors1) Light/Switch (Security Sensor)
My tests with ESPeasy stopped before beginning because I realized that I need a USB to TTL converter that I don't have a t moment... Delayed...
This gave me time to implement the change in NodeMCU sketch which addresses and solves the original problem of this topic.
I'm attaching here the second part of the modified sketch omitting the WiFi part.
In short, I defined a fake "switch" sensor in NodeMCU and I'm sending its modified status to Domoticz every 45 seconds (data timeout in Domoticz is 1 minute).
Important to underline that the new "fake sensor" can remain in the list of "not used" devices in Domoticz.
Here is the code:
// Start of the sensor specific code
#include <SPI.h>
#include <MySensors.h>
#include <pins_arduino.h>
#include <Bounce2.h>
#define CHILD_ID0 0
#define CHILD_ID1 1
#define CHILD_ID2 2
Bounce debouncer1 = Bounce();
Bounce debouncer2 = Bounce();
int oldValue1=-1;
int oldValue2=-1;
int tempo=millis();
int ultimo=0;
MyMessage msg1(CHILD_ID0, V_TRIPPED);
MyMessage msg2(CHILD_ID1, V_TRIPPED);
MyMessage msg3(CHILD_ID2, V_TRIPPED);
void setup()
{
// Setup magnetic contact on D0 with pull-up
pinMode(D0,INPUT_PULLUP);
// After setting up reed switch, setup debouncer
debouncer1.attach(D0);
debouncer1.interval(5);
// Setup magnetic contact on D1 with pull-up
pinMode(D1,INPUT_PULLUP);
// After setting up reed switch, setup debouncer
debouncer2.attach(D1);
debouncer2.interval(5);
}
void presentation()
{
// Present locally attached sensors here
present(CHILD_ID0, S_DOOR);
present(CHILD_ID1, S_DOOR);
present(CHILD_ID2, S_DOOR);
}
// Check if digital input has changed and send in new value
void loop()
{
debouncer1.update();
debouncer2.update();
// Get the update value
int value1 = debouncer1.read();
int value2 = debouncer2.read();
if (millis() > tempo + 45000)
{
Serial.print (millis());
Serial.print (ultimo);
tempo = millis();
send(msg3.set(ultimo));
ultimo = ultimo + 1;
if (ultimo > 1)
{
ultimo = 0;
}
}
if (value1 != oldValue1)
{
// Send in the new value
send(msg1.set(value1==HIGH ? 1 : 0));
oldValue1 = value1;
}
if (value2 != oldValue2)
{
// Send in the new value
send(msg2.set(value2==HIGH ? 1 : 0));
oldValue2 = value2;
}
}```@kimot , I have to confess that I'm still a bit lost when I have to understand which language I'm using in each environment, but this is because I keep jumping from something to something else. Your explanation was very clear and allowed me to solve the "timing problem" if a few minutes.
At the same time... you gave me enough reason to test ESPeasy... and to say it all I have already installed another NodeMCU on the breadboard and starting right now to play
Thanks again
@kimot , sure, I know that tmr.now() is a NodeMCU function and I'm trying to use it in the "void loop()" sketch of my NodeMCU to send a "changed status" at regular interval.
Unfortunately I'm still getting compile errors as if the function has to be declared or requires an "include".
Back to your post above where you mention ESPEasy... I don't know this alternative, but from what I'm reading is just a sketch that you produce with a specific tool instead of using Arduino IDE software, so I cannot see how this can be better or easier compared to Mysensors since the "dumb side" seems to be in Domoticz.
Still since you know both, I'm sure that you have a good reason... so, may I ask you to spend a couple of words more to explain why you think this can make things simpler? Thanks a lot
@mfalkvidd , after a full day of work, trying to implement my configuration on Home Assistant, OpenHAB and Jeedom, I'm back here with a low tail and ready to go back to Domoticz.
Without going in details, each of the above failed implementing either the RFLink or Piface Hardware. None of them seemed to provide a "logical" user interface like Domoticz.
So... here I am... with one day totally lost and trying to recover.
What I want to do now is to define a fake sensor in NodeMCU that will send a change within the data timeout.
May I kindly ask you if you have a working sketch using the tmr function as I can't manage to compile a proper one (tmr not defined)
Thanks in advance
Never heard of cron jobs before... you never stop learning
Still, from what I understand this restart is triggered when Domoticz dies... not when a node has lost contact.
Btw.. The Home Assistant installation is in progress on another SD card.
If you care, the reason why it attracted me is because it seems to have full support for Piface Digital 2, RFLink and MySensors. Second, the documentation seems really well done. A small minus, 32G SD card is recommended... which is big... still I'm currently installing on a 8G card I had available in the house...
Will let you know
@sundberg84 , in the architecture I have in mind for real operations the Raspberry with the main instance of Domoticz will be under UPS, so in my tests I'm assuming that it will be always on.
Probably I may use a small databank between the plug and NodeMCU, so this should protect me against a normal power loss.
Still... the protection with the databank is certainly weaker than a real UPS and this is the reason why I'm doing.
Anyway... wherever you place a monitoring system you have only two solutions:
The second solution, at least, does not interrupts the overall functionality... but let me say it... this is a severe design error in Domoticz if this is the way it is expected to work.
In the meanwhile... I went through all the presentation and the overall documentation of "Home Assistant" and, unless someone will dis encourage me from doing it, tonight I'll give it a try
@mfalkvidd , to tell you the truth I was fearing that the answer would have been this one.
I should bettere say "these ones" because in the post you mentioned I also found confirmation to a doubt I started to have since some time.... should I continue with Domoticz or not
As I said in my introduction I have close to 50 years of IT experience and I loved that project because you get started very quickly... but... if you are someone who likes "architectures"... it's a death.
Plus, you may see yourself, I posted several times in the forum and I almost never received even a comment.
I also saw in the other topic that you were close to the idea to jump to another controller... did you do it??? I gave a quick look to OpenHAB and found it far away from my mentality.. I've not tried anything else and would love to hear other experiences...
Back to the specific issue, I was thinking to force a status update before the data timeout expires.. but I see it's not working if the status is unchanged.
Even if it won't change anything, let me comment that to an "architecture fanatic"as I am, this behavior is just unacceptable. You may decide not to process a device event if there is no change, but you cannot say that you have not received anything from the corresponding hardware because this is just a lie.
Whatever... even if I'm getting tired to survive with patches for the deficiencies of Domoticz, the quick and dirty solution right now seems to implement a fake sensor which changes its status with a proper frequency.
I'm just having troubles to use the tmr.now() in my sketch because the compiler tells me "tmr" is not defined... will see how to solve.
In the meanwhile, advices from you and whomever has experience with other controllers with a better design and a better integration with MySensors it's highly appreciated.
P.S. Another reason why I kept going with Domoticz is that I'm using an RFLink 433 radio interface (nano shop) and I couldn't find another controller supporting this piece of hardware
Hi. Let me first describe the scenario.
Raspberry Pi3 as controller using Domoticz and a NodeMCU v3 Lolin as gateway with sensors on board.
No radio components on NodeMCU... just the built in WiFi, so NodeMCU and Raspberry are connected through "Ethernet".
Since this configuration is part of a security system I'm currently testing what happens in each and every case of failure.
Originally I had no "data timeout" defined for NodeMCU hardware in Domoticz.
In this scenario, simulating a power failure on NodeMCU side, the restart of the gateway was not going after the point in which it asks Domoticz to activate the link... because Domoticz was thinking that the previous session was still active (very bad).
In this situation, a restart of Domoticz was solving the issue... but of course not something you can imagine in an operational project.
Second scenario, same as above, but data timeout set to 1 minute in Domoticz.
With this setting, in the same condition of gateway power failure, Domoticz restarts the connection and everything would be fine... BUT since the Sketch on NodeMCU is set to send data only if one of its sensors changes status.. this will happen seldomly and Domoticz does a restart of the gateway every minute
Still... from the console of the node, I see that a PING is sent with a frequency lower than a minute... but Domoticz seems to ignore it.
Am I missing something? How are managing the "keepalive" between the gateway and the controller???
Here is a copy of what I see on the console:
0;255;3;0;9;Client 0 connected
0;255;3;0;9;Client 0: 0;0;3;0;2;
0;255;3;0;9;Client 0: 0;0;3;0;2;Get Version
0;255;3;0;9;Client 0: 0;0;3;0;18;PING
0;255;3;0;9;Client 0: 0;0;3;0;18;PING
0;255;3;0;9;Client 0: 0;0;3;0;18;PING
0;255;3;0;9;Client 0: 0;0;3;0;18;PING
0;255;3;0;9;Client 0: 0;0;3;0;18;PING
0;255;3;0;9;Client 0: 0;0;3;0;18;PING
0;255;3;0;9;Client 0: 0;0;3;0;18;PING
0;255;3;0;9;Client 0: 0;0;3;0;18;PING
0;255;3;0;9;Client 0 disconnected
0;255;3;0;9;Client 0 connected
0;255;3;0;9;Client 0: 0;0;3;0;2;
0;255;3;0;9;Client 0: 0;0;3;0;2;Get Version
0;255;3;0;9;Client 0: 0;0;3;0;18;PING
and the corresponding log in Domoticz:
2018-01-02 19:15:00.850 Error: MySensors1 hardware (7) nothing received for more than 1 Minute!....
2018-01-02 19:15:01.851 Error: Restarting: MySensors1
2018-01-02 19:15:02.822 MySensors: TCP/IP Worker stopped...
2018-01-02 19:15:03.824 MySensors: trying to connect to: 192.168.1.7:5003
2018-01-02 19:15:04.824 MySensors: connected to: 192.168.1.7:5003
2018-01-02 19:15:04.824 MySensors: Gateway Ready...
2018-01-02 19:15:05.825 MySensors: Gateway Version: 2.1.1
2018-01-02 19:15:05.826 MySensors: Gateway Version: 2.1.1
2018-01-02 19:16:00.064 dzVents: Debug: Dumping domoticz data to /home/pi/domoticz/scripts/dzVents//domoticzData.lua
2018-01-02 19:16:00.081 dzVents: Debug: Event trigger type: time
2018-01-02 19:16:30.838 Error: MySensors1 hardware (7) nothing received for more than 1 Minute!....
2018-01-02 19:16:31.839 Error: Restarting: MySensors1
2018-01-02 19:16:32.834 MySensors: TCP/IP Worker stopped...
2018-01-02 19:16:33.836 MySensors: trying to connect to: 192.168.1.7:5003
2018-01-02 19:16:34.836 MySensors: connected to: 192.168.1.7:5003
2018-01-02 19:16:34.836 MySensors: Gateway Ready...
2018-01-02 19:16:35.837 MySensors: Gateway Version: 2.1.1
2018-01-02 19:16:35.837 MySensors: Gateway Version: 2.1.1
Just a quick additional information.
While deeply testing the full functionality, I realized that if the NodeMCU goes out of main
power AND the magnetic contact connected to D3 (GPIO 0) is closed, the loaded configuration is lost. I found out that usage of GPIO 0, 2, 15 is deprecated because these pin have a meaning during reboot.
For this reason I moved my switch to D0 (GPIO 16) and modified accordingly the sketch of my previous post.
Sorry
Don't be scared , this time I'm not here to ask for help but to contribute.
The good news is that with all the hints received, yesterday I've been able to compile and upload the sketch to NodeMCU.
One year later (today ) I defined the NodeMCU in Domoticz,searched for sensors and everything is now properly working.
My next step now is to add a second sensor to the same NodeMCU but, should I face problems, I think I should start another topic to avoid confusion.
Bottom line... thank you for the help provided and here is the final working sketch that I hope will help someone else
/**
* The MySensors Arduino library handles the wireless radio link and protocol
* between your home built sensors/actuators and HA controller of choice.
* The sensors forms a self healing radio network with optional repeaters. Each
* repeater and gateway builds a routing tables in EEPROM which keeps track of the
* network topology allowing messages to be routed to nodes.
*
* Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
* Copyright (C) 2013-2015 Sensnology AB
* Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
*
* Documentation: http://www.mysensors.org
* Support Forum: http://forum.mysensors.org
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* version 2 as published by the Free Software Foundation.
*
*******************************
*
* REVISION HISTORY
* Version 1.0 - Henrik EKblad
* Contribution by a-lurker and Anticimex,
* Contribution by Norbert Truchsess <norbert.truchsess@t-online.de>
* Contribution by Ivo Pullens (ESP8266 support)
*
* DESCRIPTION
* The EthernetGateway sends data received from sensors to the WiFi link.
* The gateway also accepts input on ethernet interface, which is then sent out to the radio network.
*
* VERA CONFIGURATION:
* Enter "ip-number:port" in the ip-field of the Arduino GW device. This will temporarily override any serial configuration for the Vera plugin.
* E.g. If you want to use the defualt values in this sketch enter: 192.168.178.66:5003
*
* LED purposes:
* - To use the feature, uncomment any of the MY_DEFAULT_xx_LED_PINs in your sketch, only the LEDs that is defined is used.
* - RX (green) - blink fast on radio message recieved. In inclusion mode will blink fast only on presentation recieved
* - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly
* - ERR (red) - fast blink on error during transmission error or recieve crc error
*
* See http://www.mysensors.org/build/esp8266_gateway for wiring instructions.
* nRF24L01+ ESP8266
* VCC VCC
* CE GPIO4
* CSN/CS GPIO15
* SCK GPIO14
* MISO GPIO12
* MOSI GPIO13
* GND GND
*
* Not all ESP8266 modules have all pins available on their external interface.
* This code has been tested on an ESP-12 module.
* The ESP8266 requires a certain pin configuration to download code, and another one to run code:
* - Connect REST (reset) via 10K pullup resistor to VCC, and via switch to GND ('reset switch')
* - Connect GPIO15 via 10K pulldown resistor to GND
* - Connect CH_PD via 10K resistor to VCC
* - Connect GPIO2 via 10K resistor to VCC
* - Connect GPIO0 via 10K resistor to VCC, and via switch to GND ('bootload switch')
*
* Inclusion mode button:
* - Connect GPIO5 via switch to GND ('inclusion switch')
*
* Hardware SHA204 signing is currently not supported!
*
* Make sure to fill in your ssid and WiFi password below for ssid & pass.
*/
// Enable debug prints to serial monitor
#define MY_DEBUG
// Use a bit lower baudrate for serial prints on ESP8266 than default in MyConfig.h
#define MY_BAUD_RATE 9600
// Enables and select radio type (if attached)
//#define MY_RADIO_NRF24
//#define MY_RADIO_RFM69
#define MY_GATEWAY_ESP8266
#define MY_ESP8266_SSID "*********"
#define MY_ESP8266_PASSWORD "**********"
// Enable UDP communication
//#define MY_USE_UDP
// Set the hostname for the WiFi Client. This is the hostname
// it will pass to the DHCP server if not static.
#define MY_ESP8266_HOSTNAME "sensor-gateway1"
// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
// #define MY_IP_ADDRESS 192,168,1,7
// If using static ip you need to define Gateway and Subnet address as well
// #define MY_IP_GATEWAY_ADDRESS 192,168,1,1
// #define MY_IP_SUBNET_ADDRESS 255,255,255,0
// The port to keep open on node server mode
#define MY_PORT 5003
// How many clients should be able to connect to this gateway (default 1)
#define MY_GATEWAY_MAX_CLIENTS 2
// Controller ip address. Enables client mode (default is "server" mode).
// Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
//#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68
// Enable inclusion mode
#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
// #define MY_INCLUSION_BUTTON_FEATURE
// Set inclusion mode duration (in seconds)
#define MY_INCLUSION_MODE_DURATION 60
// Digital pin used for inclusion mode button
#define MY_INCLUSION_MODE_BUTTON_PIN 3
// Set blinking period
// #define MY_DEFAULT_LED_BLINK_PERIOD 300
// Flash leds on rx/tx/err
// Led pins used if blinking feature is enabled above
#define MY_DEFAULT_ERR_LED_PIN 16 // Error led pin
#define MY_DEFAULT_RX_LED_PIN 16 // Receive led pin
#define MY_DEFAULT_TX_LED_PIN 16 // the PCB, on board LED
#if defined(MY_USE_UDP)
#include <WiFiUdp.h>
#endif
#include <ESP8266WiFi.h>
// Start of the sensor specific code
#include <SPI.h>
#include <MySensors.h>
#include <pins_arduino.h>
#include <Bounce2.h>
#define CHILD_ID 0
Bounce debouncer = Bounce();
int oldValue=-1;
MyMessage msg(CHILD_ID, V_TRIPPED);
void setup()
{
// Setup reed switch with pull-up
pinMode(D0,INPUT_PULLUP);
// After setting up reed switch, setup debouncer
debouncer.attach(D0);
debouncer.interval(5);
}
void presentation()
{
// Present locally attached sensors here
present(CHILD_ID, S_DOOR);
}
// Check if digital input has changed and send in new value
void loop()
{
debouncer.update();
// Get the update value
int value = debouncer.read();
if (value != oldValue)
{
// Send in the new value
send(msg.set(value==HIGH ? 1 : 0));
oldValue = value;
}
}```Here I am again.
I worked the whole afternoon on this sketch to include your suggestions and correct the compile errors.
Everything seems to be fine except one residual compile error that I don't seem to be able to solve:
1GatewayESP8266t:171: error: 'msg' was not declared in this scope
send(msg.set(value==HIGH ? 1 : 0));
exit status 1
'msg' was not declared in this scope
The whole current sketch can be found at the end of this post.
Can you kindly help to understand what I'm doing wrong?
As an alternative @Yveaux , since you mentioned that you have several NodeMCU like mine (gateway+onboard contact sensors) would you mind sharing the setch of one of them so that I can learn by sample?
Thanks a lot for your help... here is the sketch
/**
* The MySensors Arduino library handles the wireless radio link and protocol
* between your home built sensors/actuators and HA controller of choice.
* The sensors forms a self healing radio network with optional repeaters. Each
* repeater and gateway builds a routing tables in EEPROM which keeps track of the
* network topology allowing messages to be routed to nodes.
*
* Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
* Copyright (C) 2013-2015 Sensnology AB
* Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
*
* Documentation: http://www.mysensors.org
* Support Forum: http://forum.mysensors.org
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* version 2 as published by the Free Software Foundation.
*
*******************************
*
* REVISION HISTORY
* Version 1.0 - Henrik EKblad
* Contribution by a-lurker and Anticimex,
* Contribution by Norbert Truchsess <norbert.truchsess@t-online.de>
* Contribution by Ivo Pullens (ESP8266 support)
*
* DESCRIPTION
* The EthernetGateway sends data received from sensors to the WiFi link.
* The gateway also accepts input on ethernet interface, which is then sent out to the radio network.
*
* VERA CONFIGURATION:
* Enter "ip-number:port" in the ip-field of the Arduino GW device. This will temporarily override any serial configuration for the Vera plugin.
* E.g. If you want to use the defualt values in this sketch enter: 192.168.178.66:5003
*
* LED purposes:
* - To use the feature, uncomment any of the MY_DEFAULT_xx_LED_PINs in your sketch, only the LEDs that is defined is used.
* - RX (green) - blink fast on radio message recieved. In inclusion mode will blink fast only on presentation recieved
* - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly
* - ERR (red) - fast blink on error during transmission error or recieve crc error
*
* See http://www.mysensors.org/build/esp8266_gateway for wiring instructions.
* nRF24L01+ ESP8266
* VCC VCC
* CE GPIO4
* CSN/CS GPIO15
* SCK GPIO14
* MISO GPIO12
* MOSI GPIO13
* GND GND
*
* Not all ESP8266 modules have all pins available on their external interface.
* This code has been tested on an ESP-12 module.
* The ESP8266 requires a certain pin configuration to download code, and another one to run code:
* - Connect REST (reset) via 10K pullup resistor to VCC, and via switch to GND ('reset switch')
* - Connect GPIO15 via 10K pulldown resistor to GND
* - Connect CH_PD via 10K resistor to VCC
* - Connect GPIO2 via 10K resistor to VCC
* - Connect GPIO0 via 10K resistor to VCC, and via switch to GND ('bootload switch')
*
* Inclusion mode button:
* - Connect GPIO5 via switch to GND ('inclusion switch')
*
* Hardware SHA204 signing is currently not supported!
*
* Make sure to fill in your ssid and WiFi password below for ssid & pass.
*/
// Enable debug prints to serial monitor
#define MY_DEBUG
// Use a bit lower baudrate for serial prints on ESP8266 than default in MyConfig.h
#define MY_BAUD_RATE 9600
// Enables and select radio type (if attached)
//#define MY_RADIO_NRF24
//#define MY_RADIO_RFM69
#define MY_GATEWAY_ESP8266
#define MY_ESP8266_SSID "*********"
#define MY_ESP8266_PASSWORD "**********"
// Enable UDP communication
//#define MY_USE_UDP
// Set the hostname for the WiFi Client. This is the hostname
// it will pass to the DHCP server if not static.
#define MY_ESP8266_HOSTNAME "sensor-gateway1"
// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
// #define MY_IP_ADDRESS 192,168,1,7
// If using static ip you need to define Gateway and Subnet address as well
// #define MY_IP_GATEWAY_ADDRESS 192,168,1,1
// #define MY_IP_SUBNET_ADDRESS 255,255,255,0
// The port to keep open on node server mode
#define MY_PORT 5003
// How many clients should be able to connect to this gateway (default 1)
#define MY_GATEWAY_MAX_CLIENTS 2
// Controller ip address. Enables client mode (default is "server" mode).
// Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
//#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68
// Enable inclusion mode
#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
// #define MY_INCLUSION_BUTTON_FEATURE
// Set inclusion mode duration (in seconds)
#define MY_INCLUSION_MODE_DURATION 60
// Digital pin used for inclusion mode button
#define MY_INCLUSION_MODE_BUTTON_PIN 3
// Set blinking period
// #define MY_DEFAULT_LED_BLINK_PERIOD 300
// Flash leds on rx/tx/err
// Led pins used if blinking feature is enabled above
#define MY_DEFAULT_ERR_LED_PIN 16 // Error led pin
#define MY_DEFAULT_RX_LED_PIN 16 // Receive led pin
#define MY_DEFAULT_TX_LED_PIN 16 // the PCB, on board LED
#if defined(MY_USE_UDP)
#include <WiFiUdp.h>
#endif
#include <ESP8266WiFi.h>
// Start of the sensor specific code
#include <SPI.h>
#include <MySensors.h>
#include <pins_arduino.h>
#include <Bounce2.h>
#define CHILD_ID 0
Bounce debouncer = Bounce();
int oldValue=-1;
void setup()
{
// Setup reed switch with pull-up
pinMode(D3,INPUT_PULLUP);
// After setting up reed switch, setup debouncer
debouncer.attach(D3);
debouncer.interval(5);
}
void presentation()
{
// Present locally attached sensors here
present(CHILD_ID, S_DOOR);
}
// Check if digital input has changed and send in new value
void loop()
{
debouncer.update();
// Get the update value
int value = debouncer.read();
if (value != oldValue)
{
// Send in the new value
send(msg.set(value==HIGH ? 1 : 0));
oldValue = value;
}
}```@gbuico Sorry, but I'm getting crazy trying to put together the right code for the local sensor directly connected to NodeMCU GPIO (pin 0, id D3)
I did my best to merge the NodeMCU specific commands with the Door/Window/Switch sample in MySensors documentation
So far I came out with the attached sensor definition.
Could you please let me know if this is the right way to define my contact?
Also... could you please confirm that the "debouncer" code applies to NodeMCU as well... and this allows me to connact the magnetic contact wires directly to D3 and ground without a capacitor in parallel?
Thanks in advance
#include <Bounce2.h>
#define CHILD_ID 0
#define D3 0 // NodeMCU I/O pin for reed switch
Bounce debouncer = Bounce();
int oldValue=-1;
void setup()
{
// Setup reed switch with pull-up
pinMode(D3,INPUT_PULLUP);
// After setting up reed switch, setup debouncer
debouncer.attach(BUTTON_PIN);
debouncer.interval(5);
}
void presentation() {
present(CHILD_ID, S_DOOR);
}
// Check if digital input has changed and send in new value
void loop()
{
debouncer.update();
int value = debouncer.read();
if (value != oldValue) {
// Send in the new value
send(msg.set(value==HIGH ? 1 : 0));
oldValue = value;
}
}```@yveaux said in Wifi Gateway on Arduino:
@gbuico said in Wifi Gateway on Arduino:
Having no practical experience with NodeMcu I just think of it as something not powerfull enough to do its job, then I realize that in some areas of the house I'll just need to monitor 2-3 magnetic switches... and you seem to say that this works fine for you
The NodeMCU board contains a regular esp8266, which has more than enough oomph to handle the wifi connection, some sensors and the mySensors stack! Don't worry!
I had a quick look and the link you've posted seems to sell the regular NodeMCU boards.
@Yveaux , I received my modules today at lunch time and a couple of hours later the NodeMCU is up and connected to WiFi, so I think it's proper to acknowledge that your step-by-step guide is extremely precise.
If I can contribute, the main issue I had to face has been a TSP initialization failure caused by the attempt to open the radio module which is not there in my setup.
Surely my fault but I went straight to define SSID and password ad indicated... but I didn't read carefully the other setup parameters...
Bottom line... thank you... now going to add the sensor logic and integrate everything in Domoticz
Thanks to both.
@Yveaux, if I understand well your suggestion is to use ONLY the NodeMcu board and using Arduino just for the programming.
Having no practical experience with NodeMcu I just think of it as something not powerfull enough to do its job, then I realize that in some areas of the house I'll just need to monitor 2-3 magnetic switches... and you seem to say that this works fine for you.
Should you confirm, may I ask you to confirm that these units are exactly what I need?
https://www.amazon.fr/AZ-Delivery-NodeMCU-ESP8266-développement-development/dp/B074Q2WM1Y/ref=sr_1_5?ie=UTF8&qid=1514286274&sr=8-5&keywords=ESP8266%2BCH340&th=1
Unfortunately I can't buy in the suggested shops, even if they are cheaper, because they have a delivery time which is not compatible with my crazy movements between locations.
If not, whatever alternative with a quick delivery time in France would be appreciated... as I have no relation with the shop pf the link
@mfalkvidd, going back on a shield that can fit directly on Arduino, what I found is this article:
https://www.amazon.co.uk/ROKOO-ESP8266-ESP-12E-Wireless-Converter/dp/B0768GRGV2
I understand that this shield is mounted directly on Arduino adding WiFi but leaving to Arduino the task of managing sensors... Am I wrong?
To both, in my project I'm not planning to use the radio connection, so all the sensors will be connected directly to gateways.
Thanks for being so kind
@mfalkvidd , thanks for your answer which is really good news. If your mention on using esp8266 as a shield means that someone is buying a shield with esp8266 to plug directly on Arduino, this is exactly what I had in mind since I'm terrible with soldering.
Having said so, I found that shield and I'd love to share it here just to get advices but I don't know which is the right way to show it without breaking the rules of the forum (advertising).
Could you please advise me on how I can share what I found?
Thanks for your time
Hi, all. Since it's my first topic in this forum, let me say a couple of general word on myself and my project.
I started to work in Information Technology in 1969 and I designed and build my first domotic project back in 1993, based on a PS/ mod.30 without HDD as a controller, plus handmade nodes based n 8052. Dinosaurs were still around.
A month ago I started my current project using Domoticz on Raspberry Pi3, RFlink for 433 devices.
Up to now there were two additional RPi still running Domoticz as slave and collecting inputs and actuators.
A few days ago I saw accidentally Mysensors, went through all the documentation and decided for a new design of the project using Arduino and Mysensors as Gateway/Sensor
Now, straight to the problem, I'm almost sure that while reading the documentation in these days I saw a clear example where the Arduino gateway had a WiFi connection to communicate with the controller.
Today, while preparing my shopping list, I tried to find again that info... and it seems disappeared.
All I find about Wifi points to ESP8266 acting also as sensor collector.. no Arduino.
Am I missing something? Can't believe that I'm the only one willing to build a WiFi Gateway... must be the blindness of the novice.
Thanks for reading till here... hope to get some answers..
Giacomo