General Discussion

Hi @neelam, welcome to the forum! The dimmer example should work. If you want to use only the esp8266 with wifi (no nrf/rfm or other radio), you'll also need to add gateway settings from https://www.mysensors.org/build/esp8266_gateway

Ok,thanks for responds guys

I'm using miceuz's Chirp I2C sensors here. Found it to be much more reliable and consistent than the cheap analogue sensors, particularly dealing with large outdoor temperature variations. The "rugged" model works a charm. I'm getting about 12 months off 2x AAA batteries, using some aggressive sleeping. As you've surmised, hook up the power in line to a Digital Out so you're not constantly powering the sensor when your board is asleep. You'll need to wait() about 200ms for the board to wake up after supplying power, and take a few dummy readings each time you wake it for it to stabilise.

There is no need to change sketch version. That field is for information only. I don't think controllers support removing anything automatically. Maybe if they have an external api. I'm unable to find anything like that in the Domoticz api: http://www.domoticz.com/wiki/Domoticz_API/JSON_URL's But since it is possible to delete stuff from the Domoticz web UI, maybe you can just check what a delete request looks like?

@monte said in easy FPGA'S: I have same questions as some guys in the comment section of that video. I know what FPGA is, but I can't understand what is the use scenario for those who are using MCU's for their projects. And as we are on mysensors forum, maybe you have in mind some application for FPGA to our common needs? I can't imagine myself starting to learn verilog right now, but I hear about it from all around so I might consider learning it in near future, but I can't make myself learn stuff unless I see some interesting application of new knowledge. Thanks for bringing this up. I'll concede the point, because after looking into it a bit more, I think you're probably right. I mean, the newer ARM chips consume less than 100na in sleep mode and seem generally quite power efficient: https://www.microchip.com/design-centers/32-bit/sam-32-bit-mcus/sam-l-mcus

@CrankyCoder I heard that in the Netherlands at least there are technically no laws agains placing sensors in trees :-)

Atc will try to keep TX rssi above - 70db by adjusting the TX power. If you move the node away from gateway you should see TX rssi decrease until - 70 then the power should start rising as you get farther away

As promised this is my wiring and code, hope this help people out First the wiring. Radio - Mega Pin +3V - NA -3V - NA CSN/CS(Yellow) - 6 CE(Orange) - 5 SCK(Green) - 14 MISO(White) - 15 MOSI(Blue) - 16 IRQ(Gray) - 2 Switch - Mega Left - RESET Right - 3 (inclusion Button) LEDs - Mega Red(Err) - 40 Orange(Rx) - 42 Green(Tx) - 44 All are grounded with 330 Ohm resistors. And here is my Sketch. One thing I had done when I was just getting lots of shutdowns and errors was to wipe the board - I uploaded blink and left it alone for a minute and then reloaded the gateway with the updated libraries and (knocking on wood) it seems to be stable. /** * 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 Tomas Hozza <thozza@gmail.com> * * * DESCRIPTION * The EthernetGateway sends data received from sensors to the ethernet link. * The gateway also accepts input on ethernet interface, which is then sent out to the radio network. * * The GW code is designed for Arduino 328p / 16MHz. ATmega168 does not have enough memory to run this program. * * LED purposes: * - To use the feature, uncomment MY_DEFAULT_xxx_LED_PIN in the sketch below * - 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/ethernet_gateway for wiring instructions. * */ // Enable debug prints to serial monitor #define MY_DEBUG // Enable and select radio type attached #define MY_RADIO_RF24 // Enable gateway ethernet module type #define MY_GATEWAY_W5100 // W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal) //#define MY_W5100_SPI_EN 4 // Enable Soft SPI for NRF radio (note different radio wiring is required) // The W5100 ethernet module seems to have a hard time co-operate with // radio on the same spi bus. #if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD) #define MY_SOFTSPI #define MY_SOFT_SPI_SCK_PIN 14 #define MY_SOFT_SPI_MISO_PIN 16 #define MY_SOFT_SPI_MOSI_PIN 15 #endif // When W5100 is connected we have to move CE/CSN pins for NRF radio #ifndef MY_RF24_CE_PIN #define MY_RF24_CE_PIN 5 #endif #ifndef MY_RF24_CS_PIN #define MY_RF24_CS_PIN 6 #endif // Enable UDP communication //#define MY_USE_UDP // If using UDP you need to set MY_CONTROLLER_IP_ADDRESS below // Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP) #define MY_IP_ADDRESS 192,168,1,XXX // If using static ip you can define Gateway and Subnet address as well #define MY_IP_GATEWAY_ADDRESS 192,168,1,XXX #define MY_IP_SUBNET_ADDRESS 255,255,255,XXX // Renewal period if using DHCP //#define MY_IP_RENEWAL_INTERVAL 60000 // The port to keep open on node server mode / or port to contact in client mode #define MY_PORT 5003// // 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, 254 // The MAC address can be anything you want but should be unique on your network. // Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use. // Note that most of the Ardunio examples use "DEAD BEEF FEED" for the MAC address. #define MY_MAC_ADDRESS 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED // Set LOW transmit power level as default, if you have an amplified NRF-module and // power your radio separately with a good regulator you can turn up PA level. #define MY_RF24_PA_LEVEL RF24_PA_MAX // 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 90 // Digital pin used for inclusion mode button #define MY_INCLUSION_MODE_BUTTON_PIN 3 // Set blinking period #define MY_DEFAULT_LED_BLINK_PERIOD 300 // Inverses the behavior of leds #define MY_WITH_LEDS_BLINKING_INVERSE // Flash leds on rx/tx/err // Uncomment to override default HW configurations #define MY_DEFAULT_ERR_LED_PIN 40 // Error led pin #define MY_DEFAULT_RX_LED_PIN 42 // Receive led pin #define MY_DEFAULT_TX_LED_PIN 44 // Transmit led pin #if defined(MY_USE_UDP) #include <EthernetUdp.h> #endif #define MY_SIGNING_SOFT #define MY_SIGNING_SOFT_RANDOMSEED_PIN 23 #define MY_SIGNING_WEAK_SECURITY #include <Ethernet.h> #include <MyConfig.h> #include <MySensors.h> void setup() { // Setup locally attached sensors } void presentation() { // Present locally attached sensors here } void loop() { // Send locally attached sensors data here }```

Does adding ack to messages help trigger any failures if something can't deliver? ... well that didn't make much sense. So lets say i have 2 repeaters on my network. i have a sensor that wakes up to report info. it normally goes to repeater1 -> gateway but repeater1 is acting up. Could you tell it to wait for an ack? after X amount of time with no ack would it trigger to find a new parent?

Hi, wow, quick answer. I'm on the way right now, I'm testing it Friday. (It would be a real shame to take softspi by this controller. ;-) ) Thank you, hyx

@sigolhi Yes, communication between two nodes is possible without a controller and gateway. I do this. And I tie them to each other in the air, it is not necessary to prescribe in the sketches. See my videos in this topic. Carefully look :) Master - Slave Сommunication | Micro Network

You should do the same for requestTime();

@chisight Thanks for the idea, I'll keep it in mind but for this project some of the relays will be controlling lights etc, so minimum delay is desireable. Thanks.

@hard-shovel Thanks for the response. The volume control is motorised so no need to 'remember' where it is as it is possible to manually change it and there is no feedback that could be used to determine changes. The remote control requires you to hold the volume buttons (+&-) down until desired volume level is achieved so I suppose I could start repeating the IRSend code from the node if one valid volune command is received. The first time the node gets a valid volume command it just repeates the send over and over until it gets another identical command which stops the loop. I'll think more about it and also see if the controller has something that might be suitable. Edit - Why not just start the volume repeating the code to go in whatever direction you want at a suitable speed and add a volume 'Stop' button - that would be easier! - I think I'll try that at the weekend...... ;) Thanks again, I can finally start hiding all the remotes cluttering up the place! :)

Duh .. . yeah . ... like @skywatch said.

@Johhnywalter I don't have equipment to test this, sorry. I only wanted an indication of the level of dust in a bedroom. But for now I have shelved this as I have more ijmportant things to take care of.

Thanks for some interesting info! The reason is 1. To save memory for adding more sensors, signing etc and 2. To save battery energy on battery nodes. So there is likely more than one solution to this problem. Also, I have used 'for' loops as well and wonder how this affects memory and battery drain? Thanks

I made heating as simply as possible - with good house insulation ( 20cm foam PVC for walls and 40 cm for roof ). I am using el. floor heating ( cables ) on both floors + fireplace like backup for unpredicable situations and for fun. I know, that heating cost me 2 or 3 times more than with heatpump, but consuption is low and investition was really very low too. ( cca 600 euros all heating cables and I made all work myself ) Regulation in this time ( and last winter ) by cheap Wemos with relay board and ESPeasy firmware on it in each room. It can regulate room or floor temperature ( I am using floor temperature regulation ) . Mode of operation and temperature setting are made from Domoticz, but regulation is made by Wemos itself - not running Domoticz needed. Temperatures and energy consumption are reported back to Domoticz. It was very funny two weekends project. One weekend familiarization with ESPeasy and next weekend regulator and Domoticz integration making. But it is not final stage, because ESP is very energy "hungry" and 4 lines of my UTP cable is not enough for cca 7 Wemos with relays on each part of bus. And I do not want wi-fi using for my sensors. But I need quick solution and it was.

@alowhum Zigbee being "a standard" is not an advantage at all. As you put it, it is indeed not true at all. Using "a standard" in the meaning of "a formal definition of one of the piece of your puzzle" is only an advantage when you want to potentially replace that piece by a piece produced by another manufacturer and still get that talking to the rest of the puzzle. You should also consider that there are two kind of standards : "committee" standards, where experts provide a formal document and people pay to adopt that way of doing things, and "de facto" standard, where there are enough users that do things the same way (or buy the same thing) that it guarantees sufficient resiliency. For example, USB is a committee standard (but if you use A, micro, mini etc. you have to adapt), Arduino Uno is a de facto standard (and there as well, you can choose between Uno or micro, etc.), and its success made possible the clones costing a few bucks.