@sirzlimz It may be stating the obvious but the photo shown is not a arduino processor but a ESP8266.
Therefore the I/O pins listed in the sketch refer to the GPIO pin number on the ESP8266.
So if PIN 2 is listed in the Sketch it refers to GPIO2 which is the pin marked D4 on the D1 mini module..
The photo shows the Data jumper connected to D2, So trying moving this to D4 with the original sketch.
@sirzlimz I have just tried this circuit out myself on a D1 module and the using the library listed from milesburton it does not work on the ESP8266 in parasitic mode.
If you move the jumper over for powered mode it will work fine.
Trying on an Arduino nano with the same device and breadboard it works fine in both modes.
So testing again and reading the data sheet on the DS18B20 and the section on "Powering the DS18B20" page 7 some insight can be obtained.
Anyway a quick fix is to put another 4.7K resistor in parallel with the first and the system should work with one sensor,
so two possible ways of connection are shown
Powered Mode with the Jumper to 5V, Recommended method, I always power my DS18B20's
This works with multiple devices, (I have just tried with 10 devices on the D1 [with multiple device sketch])
Parasitic Mode with two 4.7K resistors (this trick only works with one device on the bus)
@sirzlimz There are lots of pinout diagrams on the web like below.
For the the arduino use the GPIO number as the pin number
ie
GPIO5 --- marked D1 in Arduino IDE use 5
GPIO13-marked D7
@benhub Short answers, No, Yes, Yes
The regulator will use power if connected.
If your circuit is power hungry then removing the regulator will have limited effect.
The sparkfun schematic on the article that you listed notes to disconnect the regulator for low power, so the advice is consistent.
Unless you are using the genuine sparkfun versions of the pro-mini where the jumper can be cut then physically removing the regulator is recommended.
I made a simple adapter for Pro Minis, Used on it own for new boards with connection holes
If you slide on some dupont cable covers as a guide it makes it easy to program a soldered board
The Led is not actualy runing on AC. Part of the IC generates an low voltage AC signal (Nothing to do Mains Power) then other parts of the IC detect changes to this signal via the pair of diodes at the bottom, and then generate the two signals for the red and green leds.
The bicolor color led has a common terminal in the center and the two outer pins control the two outer pins power the red and green leds.
Utilizing a optocoupler has a safety advantage, as it isolates the power on the sensed unit from the mysensor node. It also allows systems using different control signal voltages to be interconnected.
If you have the arduino analogue pin connected to Pin3, where do you have the arduino GND connected?
As there is a relay that is connected in parallel to the the Upper LED drive transistor,
I recommend using a optocoupler and resistor connected to the relay terminals shown, as these connections are easy to solder wires to.
The resistor will need to be sized to match the voltage on the relay to limit current through the optocoupler led. 
The TLP222A are opto-Mosfet devices so ideal for powering LEDs and small Relays etc as they have a 500mA rating, and the price listed is good value.
However for your application, use the 4N35 that you already have.
Your diagram is reversed as you need to drive the led in the optocoupler from the relay coil connections.
Use the existing 10K as a pullup resistor at the input to the arduino,
On the relay side use a series resistor R1 of about 1Kohm for 12Vdc (expected from a 9Vac supply).
The pins on the sketch and the schematic do not match,
You need to be more careful on matching the items as it will make troubleshooting more difficult.
This sketch is a quick and dirty method, that does basically to work for me using OpenHAB as a controller. (only tested using LED outputs not with an actual computer).
If i was actually going to implement this, I would monitor the POWER LED on the computer for feedback and control of the pulses. ie for shutdown, try short pulse first for controlled shutdown and if not shutdown within expected time span, then preform a hard shutdown.
/*
* PC Power On/Off & Reset Sketch
* Power Pin Pulse = PC Starts if Already Off, *** PC Shutsdown if already on ## this is the operation of my Computer ##
* Power Pin 5 Seconds Low = PC Forced Shutdown
* Reset Pin Pulse Low = PC Reset (if already on)
*
* Using three child IDs
* 1 = Power On/Off
* 2 = Forced OFF
* 3 = Reset
*
* Version 1.0 2018-01-19
*/
/**
* 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
*
* DESCRIPTION
* Example sketch showing how to control physical relays.
* This example will remember relay state after power failure.
* http://www.mysensors.org/build/relay
*/
// Enable debug prints to serial monitor
#define MY_DEBUG
//#define MY_NODE_ID AUTO
#define MY_NODE_ID 155 // my test Node ID, Comment out for Auto ID
// Enable and select radio type attached
#define MY_RADIO_NRF24
//#define MY_RADIO_NRF5_ESB
//#define MY_RADIO_RFM69
//#define MY_RADIO_RFM95
// Enable repeater functionality for this node
#define MY_REPEATER_FEATURE // if you need the repeater function uncomment
#include <MySensors.h>
// Wait times
#define LONG_WAIT 500
#define SHORT_WAIT 50
#define PULSE_TIME 500UL // half a second
#define FORCED_TIME 5000UL // 5 seconds
boolean goPulse;
unsigned long pulseStartTime;
#define POWER_PIN 4 // Arduino Digital I/O pin number for PC Power control
#define RESET_PIN 5 // Arduino Digital I/O pin number for PC Reset control
#define RELAY_ON 1 // GPIO value to write to turn on attached relay
#define RELAY_OFF 0 // GPIO value to write to turn off attached relay
#define CHILD_ID_POWER 143 // these ID used for my test machine. change to suit ie 1
#define CHILD_ID_FORCEDOFF 144 // change to suit ie 2
#define CHILD_ID_RESET 145 // change to suit ie 3
boolean Status_Power = 0;
boolean Status_Forcedoff = 0;
boolean Status_Reset = 0;
boolean is_Power = 0;
boolean is_ForcedOff = 0;
boolean is_Reset = 0;
// Setup Messages
MyMessage msg(CHILD_ID_POWER,V_STATUS);
void before() {
// Set the pins to output mode
pinMode(POWER_PIN, OUTPUT);
pinMode(RESET_PIN, OUTPUT);
// Set the Pin states to known state
digitalWrite(POWER_PIN, RELAY_OFF);
digitalWrite(RESET_PIN, RELAY_OFF);
}
void setup() {
}
void presentation() {
// Send the sketch version information to the gateway and Controller
sendSketchInfo("Relay", "1.0");
wait(LONG_WAIT); // Give gateway time to Process
// Present child ids to conroller
present(CHILD_ID_POWER, S_BINARY, "PC Power on-off");
wait(SHORT_WAIT); // Give gateway time to Process
present(CHILD_ID_FORCEDOFF, S_BINARY, "PC Forced off");
wait(SHORT_WAIT); // Give gateway time to Process
present(CHILD_ID_RESET, S_BINARY, "PC Reset");
wait(SHORT_WAIT); // Give gateway time to Process
}
void loop() {
Serial.println();
Serial.print ("loop start ");
send(msg.setSensor(CHILD_ID_POWER).set( Status_Power));
send(msg.setSensor(CHILD_ID_FORCEDOFF).set( Status_Forcedoff));
send(msg.setSensor(CHILD_ID_RESET).set( Status_Reset));
wait(100000); // wait for testing
}
void receive(const MyMessage &message)
{
// We only expect one type of message from controller. But we better check anyway.
if (message.type==V_STATUS)
switch (message.sensor) {
case CHILD_ID_POWER:
is_Power = message.getBool();
Serial.print("incoming change for Power:");
Serial.print(message.sensor);
Serial.print(", New status: ");
Serial.println((is_Power ? "On":"Off"));
powercmd(); // process pulses etc in subroutine
break;
case CHILD_ID_FORCEDOFF:
is_ForcedOff = message.getBool();
Serial.print("incoming change for FORCED Power OFF:");
Serial.print(message.sensor);
Serial.print(", New status: ");
Serial.println((is_ForcedOff ? "On":"Off"));
forcedcmd();
break;
case CHILD_ID_RESET :
is_Reset = message.getBool();
Serial.print("incoming change for Reset:");
Serial.print(message.sensor);
Serial.print(", New status: ");
Serial.println((is_Reset ? "On":"Off"));
resetcmd();
break;
default:
Serial.print("Unknown/UnImplemented message type: ");
Serial.println(message.type);
}
}
void powercmd() {
// process power pin
if (is_Power != Status_Power) {
digitalWrite(POWER_PIN, RELAY_ON);
delay(PULSE_TIME); // delay used as pulse time is short & multiple processes are not expected
digitalWrite(POWER_PIN, RELAY_OFF);
Status_Power = is_Power;
}
}
void forcedcmd() {
// process forced power off command
if (is_ForcedOff = 1 ) {
digitalWrite(POWER_PIN, RELAY_ON);
delay(FORCED_TIME); // delay used as multiple processes are not expected, quick and dirty
digitalWrite(POWER_PIN, RELAY_OFF);
Status_Forcedoff = 0; // reset status for next time
Status_Power = 0; // power status also reset if power shutoff
}
}
void resetcmd() {
// process reset command
if (is_Reset != 1 ) {
digitalWrite(RESET_PIN, RELAY_ON);
delay(PULSE_TIME); // delay used as multiple processes are not expected, quick and dirty
digitalWrite(RESET_PIN, RELAY_OFF);
Status_Reset = 0;
}
}
@robert the NUMBER_OF_RELAYS is already defined in your sketch, just use as pasted.
I use OpenHAB so i just tried to install Dormotiz and was supreised that it took less than a an hour to install and get working with the relays. (Most of that time was trying to get them to shown up on the dashboard)
Dormotiz is communication fine with my node and i can switch on and off the relays from the Dashboard
In the sort time i have checked i do see that the Last Seen time only changes when i change the state of the relay.
So your program that you posted works for me with both my normal OpenHAB and the new test Domoticz.
I think that i may be miss understanding your actual problem.
@mela You are presenting the devices as Relay Child 1, and Temperature sensors as Child Ids 5 and 6.
But when sending you are sending the temperatures as Child Ids 0 and 1
Change the following send line
// Send in the new temperature
send(msg.setSensor(i).set(temperature,1));
to
// Send in the new temperature
send(msg.setSensor(i+5).set(temperature,1));
so the send function matches the presentation values.
@yemesvee
If using a digital sensor mounted as per Kimot diagram you will receive a pulse stream, check the width of the pulsed to find if mesh or cable.
use the function pulseIn to determine the pulse width.
The simple example of the time duration of a pulse
int SensorPin = 3;
unsigned long duration = 0;
unsigned long CableDuration = 100; // Set to suitable value
unsigned long CableCount = 0;
void setup()
{
pinMode(SensorPin , INPUT);
}
void loop()
{
duration = pulseIn(SensorPin , HIGH);
Serial.print("Duration : ");
Serial.println(duration);
if (duration >= CableDuration) {
++ CableCount;
Serial.print("Cable detection :");
Serial.println(CableCount);
}
}
@dzjr To get the extra resolution sent to the controller try using
send(msg.setSensor(i+21).set(temperature,2));If the mesh moves at constant speed, How about a simple optical IR Sensor (break beam or Reflective), then checking pulse width of signal to detect mesh vs cable. Otherwise synchronize pulse width detection ratio in correlation to mesh speed.
Similar to this
@benhub Short answers, No, Yes, Yes
The regulator will use power if connected.
If your circuit is power hungry then removing the regulator will have limited effect.
The sparkfun schematic on the article that you listed notes to disconnect the regulator for low power, so the advice is consistent.
Unless you are using the genuine sparkfun versions of the pro-mini where the jumper can be cut then physically removing the regulator is recommended.
@dzjr you have the define
#define TEMPERATURE_PRECISION 12
In the github code this is not utilized, so the sensors are operating in 9 bit resolution.
You need to add the following in the before or setup
sensors.setResolution(TEMPERATURE_PRECISION);
@dzjr I also have various old meters, Some have a sealed movement so unable to change the scales.
Below is my meter showing time since last coffee.
@mateos78
Attached is a sketch that i have just tried with domoticz (running on a windows test machine) It works fine when used as a node with a gateway. Encoder/ Switch and webpage slider/switch operating.
However when set up as a single gateway node as your sketch, only the encoder function works, you can vary the lamp level from the slider or the encoder, but the domaticz on/off or the button does not operate correctly. it seems to be the way the messages are acknowledged
I also find that when i change the led dimmer from the encoder the led changes quickly, but it take about ten seconds before the dormoticz web page updates to show each new slider position.
The following Sketch needs the #define OPENHAB2 defined for use with openhab and undefined for Dormoticz
/**
* 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.
*
*******************************
* DESCRIPTION
* This sketch provides an example how to implement a dimmable led light node with a rotary
* encoder connected for adjusting light level.
* The encoder has a click button which turns on/off the light (and remembers last dim-level)
* The sketch fades the light (non-blocking) to the desired level.
*
* Default MOSFET pin is 3
*
* Arduino Encoder module
* ---------------------------
* 5V 5V (+)
* GND GND (-)
* 4 CLK (or putput 1)
* 5 DT (or output 1)
* 6 SW (Switch/Click)
*
* For OpenHAB2 enable @define OPENHAB2
*
* NOTE
* PROBLEM:
* Using as a Gateway Node With Dormoticz the SWITCH ON/OFF DOES not work correcly either from the controller or by the Encoder
* Using as a normal node all functions operate correctly.
*
*/
/
// Enable debug prints
//#define MY_DEBUG
// --- Enable Serial Gateway Transport
#define MY_GATEWAY_SERIAL
//#define MY_INCLUSION_MODE_FEATURE
//#define MY_INCLUSION_BUTTON_FEATURE
//#define MY_INCLUSION_MODE_DURATION 60
//#define MY_INCLUSION_MODE_BUTTON_PIN 8
// --- Enable RS485 transport layer
//#define MY_RS485
// Define this to enables DE-pin management on defined pin
//#define MY_RS485_DE_PIN 12
// Set RS485 baud rate to use
//#define MY_RS485_BAUD_RATE 9600
// Enable and select radio type attached
//#define MY_RADIO_NRF24
//#define MY_RADIO_RFM69
#include <SPI.h>
#include <MySensors.h>
#include <Bounce2.h>
#include <Encoder.h>
#define LED_PIN 3 // Arduino pin attached to MOSFET Gate pin
#define KNOB_ENC_PIN_1 4 // Rotary encoder input pin 1
#define KNOB_ENC_PIN_2 5 // Rotary encoder input pin 2
#define KNOB_BUTTON_PIN 6 // Rotary encoder button pin
#define FADE_DELAY 10 // Delay in ms for each percentage fade up/down (10ms = 1s full-range dim)
#define SEND_THROTTLE_DELAY 400 // Number of milliseconds before sending after user stops turning knob
#define SN "DimmableLED /w button"
#define SV "1.3a"
#define CHILD_ID_LIGHT 1
#define EEPROM_DIM_LEVEL_LAST 1
#define EEPROM_DIM_LEVEL_SAVE 2
// #define OPENHAB2 // Use Define if using OPENHAB2
#define LIGHT_OFF 0
#define LIGHT_ON 1
int dimValue;
int fadeTo;
int fadeDelta;
byte oldButtonVal;
bool changedByKnob=false;
bool sendDimValue=false;
unsigned long lastFadeStep;
unsigned long sendDimTimeout;
char convBuffer[10];
MyMessage dimmerMsg(CHILD_ID_LIGHT, V_DIMMER);
MyMessage statusMsg(CHILD_ID_LIGHT, V_STATUS); // Addition for Status update to OpenHAB Controller
Encoder knob(KNOB_ENC_PIN_1, KNOB_ENC_PIN_2);
Bounce debouncer = Bounce();
void setup()
{
// Set knob button pin as input (with debounce)
pinMode(KNOB_BUTTON_PIN, INPUT);
digitalWrite(KNOB_BUTTON_PIN, HIGH);
debouncer.attach(KNOB_BUTTON_PIN);
debouncer.interval(5);
oldButtonVal = debouncer.read();
// Set analog led pin to off
analogWrite( LED_PIN, 0);
// Retreive our last dim levels from the eprom
fadeTo = dimValue = 0;
byte oldLevel = loadLevelState(EEPROM_DIM_LEVEL_LAST);
Serial.print("Sending in last known light level to controller: ");
Serial.println(oldLevel);
send(dimmerMsg.set(oldLevel), true);
Serial.println("Ready to receive messages...");
}
void presentation() {
// Send the Sketch Version Information to the Gateway
present(CHILD_ID_LIGHT, S_DIMMER);
sendSketchInfo(SN, SV);
}
void loop()
{
// Check if someone turned the rotary encode
checkRotaryEncoder();
// Check if someone has pressed the knob button
checkButtonClick();
// Fade light to new dim value
fadeStep();
}
void receive(const MyMessage &message)
{
#ifdef MY_DEBUG
// This is called when a message is received
Serial.print("Message: "); Serial.print(message.sensor); Serial.print(", type: "); Serial.print(message.type); Serial.print(", Message: ");
#endif
if (message.type == V_STATUS) {
// Incoming on/off command sent from controller ("1" or "0")
int lightState = message.getString()[0] == '1';
int newLevel = 0;
if (lightState==LIGHT_ON) {
// Pick up last saved dimmer level from the eeprom
newLevel = loadLevelState(EEPROM_DIM_LEVEL_SAVE);
} else {
}
// Send dimmer level back to controller with ack enabled
send(dimmerMsg.set(newLevel), true);
// We do not change any levels here until ack comes back from gateway
return;
} else if (message.type == V_PERCENTAGE) {
// Incoming dim-level command sent from controller (or ack message)
fadeTo = atoi(message.getString(convBuffer));
// Save received dim value to eeprom (unless turned off). Will be
// retreived when a on command comes in
if (fadeTo != 0)
saveLevelState(EEPROM_DIM_LEVEL_SAVE, fadeTo);
}
saveLevelState(EEPROM_DIM_LEVEL_LAST, fadeTo);
#ifdef MY_DEBUG
Serial.print("New light level received: ");
Serial.println(fadeTo);
#endif
if (!changedByKnob)
knob.write(fadeTo<<1); //### need to multiply by two (using Shift left)
// Cancel send if user turns knob while message comes in
changedByKnob = false;
sendDimValue = false;
// Stard fading to new light level
startFade();
}
void checkRotaryEncoder() {
long encoderValue = knob.read()>>1 ; //### Divide by 2 (using shift right)
if (encoderValue > 100) {
encoderValue = 100;
knob.write(200); //### max value now 200 due to divide by 2
} else if (encoderValue < 0) {
encoderValue = 0;
knob.write(0);
}
if (encoderValue != fadeTo) {
fadeTo = encoderValue;
changedByKnob = true;
startFade();
}
}
void checkButtonClick() {
debouncer.update();
byte buttonVal = debouncer.read();
byte newLevel = 0;
if (buttonVal != oldButtonVal && buttonVal == LOW) {
if (dimValue==0) {
// Turn on light. Set the level to last saved dim value
int saved = loadLevelState(EEPROM_DIM_LEVEL_SAVE);
newLevel = saved > 1 ? saved : 100; // newLevel = saved > 0 ? saved : 100;
}
send(dimmerMsg.set(newLevel),true);
#ifdef OPENHAB2
send(statusMsg.set(newLevel>0 ? "1" : "0")); // Addition for Status update to OpenHAB Controller, No Echo
#endif
}
oldButtonVal = buttonVal;
}
void startFade() {
fadeDelta = ( fadeTo - dimValue ) < 0 ? -1 : 1;
lastFadeStep = millis();
}
// This method provides a graceful none-blocking fade up/down effect
void fadeStep() {
unsigned long currentTime = millis();
if ( dimValue != fadeTo && currentTime > lastFadeStep + FADE_DELAY) {
dimValue += fadeDelta;
analogWrite( LED_PIN, (int)(dimValue / 100. * 255) );
lastFadeStep = currentTime;
#ifdef MY_DEBUG
Serial.print("Fading level: ");
Serial.println(dimValue);
#endif
if (fadeTo == dimValue && changedByKnob) {
sendDimValue = true;
sendDimTimeout = currentTime;
}
}
// Wait a few millisecs before sending in new value (if user still turns the knob)
if (sendDimValue && currentTime > sendDimTimeout + SEND_THROTTLE_DELAY) {
// We're done fading.. send in new dim-value to controller.
// Send in new dim value with ack (will be picked up in incomingMessage)
send(dimmerMsg.set(dimValue), true); // Send new dimmer value and request ack back
sendDimValue = false;
}
}
// Make sure only to store/fetch values in the range 0-100 from eeprom
int loadLevelState(byte pos) {
return min(max(loadState(pos),0),100);
}
void saveLevelState(byte pos, byte data) {
saveState(pos,min(max(data,0),100));
}
I maybe overlooking something obvious as i only have a couple of hours experience with domoticz.
I made a simple adapter for Pro Minis, Used on it own for new boards with connection holes
If you slide on some dupont cable covers as a guide it makes it easy to program a soldered board