Posts made by mpp

It will depend on the interval but I'd also be interested in this.

Thanks for the extensive reply, I'll come back with feedback once I got to test everything.

Quick response wrt the battery:

• I already tested the better 3,7V Lithium battery on the new MySensors setup as well and it runs for a bit more than a week. The one in the picture (old setup) has been running for about half a year (since January).
• When using the 3x LR44 on the old setup it runs for months, with MySensors it runs a bit over a day.

Hi @scalz, thank you for all the tips. I'll checkout the dev branch. Some questions though:

• As you can see on the WeMos picture I'm already using a 10uF capacitor. Since I use the RFM69 HW version I should use a 100uF capacitor?
• It is mounted over the Ground and 3V pins, is this correct?
• Should I only use it on the gateway or also on the node?
• Where can I find documentation on the decoupling capacitor for esp8266 or can you tell me what pins I should mount it over?
• Could you also point me to some documentation (a schematic perhaps) about how to build a filter?

Kind Regards

Here are some pictures: http://imgur.com/a/xZNoA

@scalz well, I'm only using the moteino as gateway with the script from moteino itself. I read a lot about antenna's (and know that it's advised to use the same antenna on receiver and transmitter) but to my surprise I got really good results by using a wire on the gateway and coils on the nodes.

I had also noted improved performance when using ATC in my old setup.

Now for my MySensors setup I am using coiled antenna's on both gateway (esp8266) and node (pro mini).

I could run some tests with wire antenna's on the gateway and node aswell. I'll try to post some pictures as well.

All my gateways are usb powered (through an adapter in an electrical outlet). My old setup (moteino gateway) had a serial connection to a Raspberry Pi. It seems unlikely but could the Esp8266 wifi transmissions (2.4ghz) cause interference with the rfm radio (433mhz)?

Hi,

Thanks for the extensive reply, I'll try to respond as good as possible;

I'm not sure what you mean by driver version, I'm using MySensors 2.1.1

I'm using the same nodes in both setup: an 8MHz Arduino Pro Mini with an RFM69HW with coiled antenna's connected as described here and a HTU21D. Everything is powered by 3x LR44 batteries or a single AA 3.6V Lithium battery.

In my old setup I'm indeed using a true Moteino board as gateway with half wire antenna. In my MySensors setup I'm using an ESP8266 with RFM69HW and coiled antenna.

The only difference here is that my Moteino gateway uses the standard Moteine half length wire antenna.

Code can be found here:
https://gist.github.com/MPParsley/d4339c2abb332640218c277e11d9f69c

And here:
https://gist.github.com/MPParsley/a3d36fe774b96c87ef33c5f887a8771f

Hey, sorry I somehow created a new topic instead of a response to an existing one. Thank you for your response.

I'm trying to understand how the rfm69 library is being used in MySensors.

I like the fact that it supports encryption (which MySensors doesn't support?).
Also the fact that it buffers radio transmissions is nice and especially useful wrt the failing ACK (NACK's) I keep getting. With MySensors I need to add wait() calls after each transmission just to get the ACK. This doesn't make much sense to me and it's causing high drain on the battery.
Something else which is making MySensors more expensive wrt to energy is the fact that each sensor reading sends another transmission (something that is more compressed in the rfm69 example sketches e.g. "node:temp:hum:pressure" is sent in one message). But I understand this is the cost of all the nice features MySensors and the MQTT gateway have to offer.

In the end I don't understand why my nodes run for months with a moteino sketch (sending temperature+humidity every minute) and the same functionality on the same node only runs for a day with mysensors code. I read a lot about using caps to solve power issues but there must be a software issue (since I get that hardware running for months with a moteino sketch)? Is it the buffering that is different, is the sleep less efficient (LowPower.h), ... the only thing that I see which can explain this is that there is a sleep of 500ms between sending temperature & humidity which means the device needs to be awake about 100x longer.

Indeed the rfm69 library works together with the pro mini but I can't get it to work on the ESP8266.

How do you get it to run for so long? What is the interval you're using?

Are you still using delays between transmissions?

I never had these transmission errors when using the rfm69 library from lowpowerlab. With that lib my nodes would run for months on 3x LR44 batteries. With these delays the same node runs for 1 day...

I wish there was a hybrid solution between lowpowerlab (awesome low level transmission) and mysensors (awesome features/framework).

The advice in this (old) thread is to downgrade to 2.0.0, is that still valid?

How did you solve this finally?

I'm also experiencing a huge amount of NACK's. Adding large delays solves the NACK's but isn't an option as I want to use batteries.

Thanks for the tips.

No, you need to feed a regulated voltage to VCC. The "easy" explanation is that the voltage regulator is only engaged when providing a powersource to RAW.

I don't get this, I never use RAW so there's no advantage in removing the regulator.. ?

Isn't it the other way round, that the regulator is only engaged when using VCC?

thanks @sundberg84, seems like I broke mine as well. Some questions remain:

• How can the board keep working when it is completely removed, don't you need to bridge some pads?
• What pins should I use to program it (There's only one VCC pint but some arduino clones seem indicate several GND pins where some other indicate blk or dtr)
• What voltage do I supply without the regulator (I assume 3.3)?

It's not clear to me how to properly cut the regulator. According to this documentation it should suffice to cut one leg but then I don't see how this could work?

This is the board I'm using:

Should I completely remove the regulator? Or how will it work if I only cut the lower right leg?

I tried cutting the wire just before the circle as marked on the image but then I couldn't program the board anymore. Perhaps I cut it in the wrong place or I'm feeding it gnd/vcc wrongly?

@gohan I have a bunch of HW

@gohan so I'd need a 3.6v battery, I'm considering the BME280 or the HTU21d sensor.

@Nca78 would this setup work with the rfm69 radio?

Thx for the tip. Only vcc or vcc and ground? Wouldn't want to damage my laptop...

that's the idea yes. But the thing is, I'm seeing these messages through the serial interface when USB powered. Not sure what to expect when I power the node from the battery.

Unfortunately adding delays will cost battery. I'll do some testing with different power supplies.

The following code results in a st=NACK for send msg2 and msg3:

send(msg1);
send(msg2);
send(msg3);

This results in a st=OK for all

send(msg1);
wait(LONG_WAIT);
send(msg2);
wait(LONG_WAIT);
send(msg3);

A power issue perhaps?

"Disconnect or desolder the 3.3 VDC regulator because it is not needed." => Why it isn't needed? I assume it is needed when connecting a sensor that requires 3.3V (e.g. HTU21d or even the RFM69)? I assume the assumption made here is that you're using 2 AA 1.5V batteries? I'm using 3 LR44 (3x1.55V) so I suppose I still need the regulator.

upgrading to the latest build fixed my issues.

Thanks guys for the support!

@jkandasa here's 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
 *
 * DESCRIPTION
 * The ESP8266 MQTT gateway sends radio network (or locally attached sensors) data to your MQTT broker.
 * The node also listens to MY_MQTT_TOPIC_PREFIX and sends out those messages to the radio network
 *
 * LED purposes:
 * - To use the feature, uncomment any of the MY_DEFAULT_xx_LED_PINs in your sketch
 * - 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
 *
 * 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_RFM69
#define MY_RFM69_FREQUENCY RF69_433MHZ
#define MY_IS_RFM69HW
#define MY_RF69_IRQ_PIN D1
#define MY_RF69_IRQ_NUM MY_RF69_IRQ_PIN
#define MY_RF69_SPI_CS D8
#define MY_RFM69_NETWORKID 99

#define MY_GATEWAY_MQTT_CLIENT
#define MY_GATEWAY_ESP8266

// Set this node's subscribe and publish topic prefix
#define MY_MQTT_PUBLISH_TOPIC_PREFIX "mpp1-out"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mpp1-in"

// Set MQTT client id
#define MY_MQTT_CLIENT_ID "mpp-1"

// Enable these if your MQTT broker requires usenrame/password
//#define MY_MQTT_USER "username"
//#define MY_MQTT_PASSWORD "password"

// Set WIFI SSID and password
#define MY_ESP8266_SSID "Airport"
#define MY_ESP8266_PASSWORD "********"

// 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 "mqtt-sensor-gateway"

// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
//#define MY_IP_ADDRESS 192,168,178,87

// If using static ip you need to define Gateway and Subnet address as well
//#define MY_IP_GATEWAY_ADDRESS 192,168,178,1
//#define MY_IP_SUBNET_ADDRESS 255,255,255,0


// MQTT broker ip address.
#define MY_CONTROLLER_IP_ADDRESS 192, 168, 0, 177

// The MQTT broker port to to open
#define MY_PORT 1883

/*
// 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
#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
*/

#include <ESP8266WiFi.h>
#include <MySensors.h>

void setup()
{
}

void presentation()
{
	// Present locally attached sensors here
}


void loop()
{
	// Send locally attech sensors data here
}

This is the UI

I added abc to the id (mpp-1abc) and it behaves the same as if no gateway has been configured.

What I don't understand now is how the nodes could be detected by mycontrolled (now the client id is different)?

Hi @jkandasa, I'm using the latest 0.0.3.Alpha2 release. I tested both with mosquitto and the built in broker.
As soon as I enable the Gateway in the UI I keep getting connections very fast (10 per second).

0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQT0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164

This happens both with mosquitto as with moquette.

These are the topics I'm using: mpp1-in and mpp1-out

I also noticed a java.lang.NullPointerException in the log, see https://github.com/mycontroller-org/mycontroller/issues/245

2017-05-15 15:28:22,570 INFO [MQTT Rec: mpp-1] [org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener:115] MQTT Gateway[tcp://192.168.0.177:1883] Reconnected successfully...
2017-05-15 15:28:22,653 ERROR [nioEventLoopGroup-5-1] [io.moquette.server.netty.NettyMQTTHandler:84] Bad error in processing the message
java.lang.NullPointerException: null
	at io.moquette.spi.impl.ProtocolProcessor.route2Subscribers(ProtocolProcessor.java:460) ~[mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.moquette.spi.impl.ProtocolProcessor.processPublish(ProtocolProcessor.java:310) ~[mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.moquette.server.netty.NettyMQTTHandler.channelRead(NettyMQTTHandler.java:61) ~[mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.moquette.server.netty.metrics.MessageMetricsHandler.channelRead(MessageMetricsHandler.java:46) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:276) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:263) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.moquette.server.netty.metrics.BytesMetricsHandler.channelRead(BytesMetricsHandler.java:47) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:266) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) [mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
2017-05-15 15:28:22,788 ERROR [MQTT Rec: mpp-1] [org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener:55] MQTT Gateway[id:6, Name:MPP, serverURI:tcp://192.168.0.177:1883] connection lost! Error:Connection lost
2017-05-15 15:28:22,927 INFO [MQTT Rec: mpp-1] [org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener:115] MQTT Gateway[tcp://192.168.0.177:1883] Reconnected successfully...

@mfalkvidd, I only have one Gateway with the ID "mpp-1".

"mpp-1" is both the client id in the gateway sketch:

// Set MQTT client id
#define MY_MQTT_CLIENT_ID "mpp-1"

and the "Client id" in the gateway setting on mycontroller, but I assume this is correct?

As soon as I change the latter the loop drops and the Gateway is connected to MQTT but then I no longer have that Gateway configured in mycontroller?

My GatewayESP8266MQTTClient keeps connecting to the MQTT connection, these messages appear really fast (several per second):

0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp1-out/0/255/0/0/18
IP: 192.168.0.164

The MQTT log show the following:

1494858022: New client connected from 192.168.0.164 as mpp-1 (c1, k15).
1494858022: New connection from 192.168.0.177 on port 1883.
1494858022: Client mpp-1 already connected, closing old connection.
1494858022: New client connected from 192.168.0.177 as mpp-1 (c1, k5000).
1494858022: New connection from 192.168.0.164 on port 1883.
1494858022: Client mpp-1 already connected, closing old connection.
1494858022: New client connected from 192.168.0.164 as mpp-1 (c1, k15).
1494858022: New connection from 192.168.0.177 on port 1883.
1494858022: Client mpp-1 already connected, closing old connection.

So it appears that the Gateway tries to connect but is then immediately being kicked out.

Could it be that it is being kicked out by its own (previous) attempt to connect OR is there a problem with the controller?

Is there a setting to configure the connection timeout?

How long can you get these running on a single battery?

Thanks @mfalkvidd, the table on the controller page says yes for “node ID generation" which seems to contradict this?

Setting the ID manually still results in no parent being found though.

I'd love to help provide a step by step guide but I can't get it to work properly with the ESP MQTT gateway and Pro Mini RFM69 nodes. Does this controller support MY_NODE_ID AUTO?

Thanks for the design. According to https://www.mysensors.org/build/connect_radio there should be a Decoupling-Capacitor or is that only needed for the NRF module?

@gohan they're all HW, yes. I tested with single wire and coil antenna's. Atm I'm testing with authentic Moteino's with single wire. They all result in !TSM:FPAR:FAIL.

Removing some of the config lines seems to have an effect:

0 MCO:BGN:INIT NODE,CP=RRNNA--,VER=2.1.1
4 TSM:INIT
4 TSF:WUR:MS=0
8 TSM:INIT:TSP OK
10 TSF:SID:OK,ID=254
12 TSM:FPAR
143 TSF:MSG:SEND,254-254-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
1232 TSF:MSG:READ,0-0-254,s=255,c=3,t=8,pt=1,l=1,sg=0:0
1239 TSF:MSG:FPAR OK,ID=0,D=1
2150 TSM:FPAR:OK
2150 TSM:ID
2152 TSM:ID:OK
2154 TSM:UPL
2285 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
2314 TSF:MSG:READ,0-0-254,s=255,c=3,t=8,pt=1,l=1,sg=0:0
2320 !TSF:MSG:LEN,0!=8
2435 TSF:MSG:READ,0-0-254,s=255,c=3,t=25,pt=1,l=1,sg=0:1
2441 TSF:MSG:PONG RECV,HP=1
2443 TSM:UPL:OK
2445 TSM:READY:ID=254,PAR=0,DIS=1
2580 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=NACK:0100
2717 TSF:MSG:READ,0-0-254,s=255,c=3,t=0,pt=1,l=1,sg=0:1
2723 !TSF:MSG:LEN,0!=8
2795 TSF:MSG:READ,0-0-254,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
2936 !TSF:MSG:SEND,254-254-0-0,s=255,c=0,t=17,pt=0,l=5,sg=0,ft=1,st=NACK:2.1.1
3076 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=6,pt=1,l=1,sg=0,ft=2,st=NACK:0
3110 TSF:MSG:READ,0-0-254,s=255,c=3,t=0,pt=6,l=2,sg=0:0100
3117 !TSF:MSG:LEN,0!=9
Send Sketch Info: 5197 TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=11,pt=0,l=14,sg=0,ft=3,st=OK:MockMySensors 
5341 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=12,pt=0,l=4,sg=0,ft=0,st=NACK:v0.5
MockMySensors v0.5
5480 TSF:MSG:READ,0-0-254,s=255,c=3,t=0,pt=6,l=2,sg=0:0100
5486 !TSF:MSG:LEN,0!=9
Get Config: Metric
Presenting Nodes
________________
  S_DOOR
6375 TSF:MSG:SEND,254-254-0-0,s=1,c=0,t=0,pt=0,l=12,sg=0,ft=1,st=OK:Outside Door
________________
6434 MCO:REG:REQ
6567 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=NACK:2
6664 TSF:MSG:READ,0-0-254,s=255,c=3,t=0,pt=6,l=2,sg=0:0100
6670 !TSF:MSG:LEN,0!=9
6744 TSF:MSG:READ,0-0-254,s=255,c=3,t=27,pt=1,l=1,sg=0:1
6750 MCO:PIM:NODE REG=1
6752 MCO:BGN:STP
GW Started
7254 MCO:BGN:INIT OK,TSP=1



#########################
RandomNumber:36
Send Battery Level
7290 TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=0,pt=1,l=1,sg=0,ft=1,st=OK:36
Request Time
7929 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=1,pt=0,l=0,sg=0,ft=0,st=NACK:
Door is: Open
8509 TSF:MSG:SEND,254-254-0-0,s=1,c=1,t=16,pt=2,l=2,sg=0,ft=1,st=OK:1
System is: Armed
8646 !TSF:MSG:SEND,254-254-0-0,s=1,c=1,t=15,pt=1,l=1,sg=0,ft=0,st=NACK:1
8783 !TSF:MSG:SEND,254-254-0-0,s=255,c=3,t=0,pt=1,l=1,sg=0,ft=1,st=NACK:36
8792 TSF:MSG:READ,0-0-254,s=255,c=3,t=27,pt=1,l=1,sg=0:1
8798 !TSF:MSG:LEN,0!=8
#########################

So now the node is sending data but there's no ack/Invalid message length.

@gohan I have several RFM69 radio's and they're all working (with the Moteino sketch) on a Pro Mini.

Here's my config:

#define MY_RADIO_RFM69
#define MY_RFM69_FREQUENCY RF69_433MHZ
#define MY_IS_RFM69HW
#define MY_RF69_IRQ_PIN 4
#define MY_RF69_IRQ_NUM MY_RF69_IRQ_PIN
#define MY_RF69_SPI_CS 15
#define MY_RFM69_NETWORKID 99
#define MY_NODE_ID 123

@gohan tested with less than a meter up to 10 meters. In fact the Wemos Node now is working as it shows up in mycontroller but the Pro Mini doesn't receive a response from the GW.

@gohan, when using the WemosD1 (without capacitor!) and a static ID, I get the following:

0;255;3;0;9;TSF:MSG:READ,253-253-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=253
0;255;3;0;9;TSF:PNG:SEND,TO=0
0;255;3;0;9;TSF:CKU:OK
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;TSF:MSG:SEND,0-0-253-253,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;TSF:MSG:READ,253-253-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=253,HP=1
0;255;3;0;9;TSF:MSG:SEND,0-0-253-253,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
0;255;3;0;9;TSF:MSG:READ,253-253-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
0;255;3;0;9;TSF:MSG:SEND,0-0-253-253,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
0;255;3;0;9;TSF:MSG:READ,253-253-0,s=255,c=0,t=17,pt=0,l=5,sg=0:2.1.1
0;255;3;0;9;Sending message on topic: mpp-mygateway1-out/253/255/0/0/17

When I do the same for the Pro Mini, there is nothing to see. When I flash a Moteino test sketch it works properly.

@christophe-cluzel have you had a chance to get the rfm69 modules to work?

@Yveaux thanks for you response. I don't this this is the cause though, I have tested these transceivers and they're running perfectly with the Moteino code.
@ledfreak3d, did you manage to get it fixed?

@gohan, I switched over to mycontroller (from OpenHab) and I'm using Arduino's nodes and I'm still getting errors not finding the parent.

I'm using the Mock sketch and tested with setting the ID manually but no luck.

0 MCO:BGN:INIT NODE,CP=RRNNA--,VER=2.1.1
4 TSM:INIT
4 TSF:WUR:MS=0
108 TSM:INIT:TSP OK
110 TSM:INIT:STATID=99
112 TSF:SID:OK,ID=99
114 TSM:FPAR
3241 TSF:MSG:SEND,99-99-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
5249 !TSM:FPAR:NO REPLY
5251 TSM:FPAR
8378 TSF:MSG:SEND,99-99-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
10385 !TSM:FPAR:NO REPLY
10387 TSM:FPAR
13514 TSF:MSG:SEND,99-99-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
15521 !TSM:FPAR:NO REPLY
15523 TSM:FPAR

Edit: adding a 4.7 capacitor didn't change this. Neither did downgrading to 2.0.

Starting sensor (RRNNA-, 2.0.0)
TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=254)
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:FAIL
!TSM:FAILURE
TSM:PDT
TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=254)
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:FAIL
!TSM:FAILURE
TSM:PDT
TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=254)
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 254-254-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:

Any idea?

@Yveaux what is a blob?

Wow, very simple indeed! You're just using the ESP12E chip, have you tried using a microcontroller like the NodeMCU or WeMos D1?

@melwinek thank you. What controller and sketch are you using?

@melwinek why are you using #define MY_RFM69_NEW_DRIVER? The documentation about this doesn't explain why you should or should not use it.

@gohan there are different things going wrong, the parent id can't be found (eventhough it is set manually to 0), but there's also a lot of debug specific to the esp module.

Alas, I'm also struggling with ESP crashes and weird messages:

TSM:INIT
TSF:WUR:MS=0
TSM:INIT:TSP OK
TSM:INIT:STATID=22
TSF:SID:OK,ID=22
TSM:FPAR
TSF:MSG:SEND,22-22-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 5
cnt 
chg_B1:-40

connected with Airport, channel 6
dhcp client start...
chg_B1:-80
!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,22-22-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
chg_B1:-120
!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,22-22-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
!TSM:FPAR:NO REPLY

Would be nice to have a link to the example sketches (the ones using external libraries) here: https://github.com/mysensors/MySensorsArduinoExamples

@gohan, do you mean http://www.mycontroller.org? I can't find any project page with downloads on the link you provided. There is a download link to a zip file somewhere in the comments but impossible to say if that is still up to date as it dates from 2015.

@gohan indeed you're right. What did you mean with "myscontroller"?

Setting the node id manually for the ping pong sketch makes them communicate to the Gateway:

#define MY_NODE_ID 201

Would auto ID work with the ESP MQTT Gateway and OpenHab controller?

I have an MQTT server up and running and OpenHab is installed with the following configuration in /etc/openhab2/services/mqtt.cfg:

broker.url=tcp://127.0.0.1:1883
broker.clientId=OpenHab
broker.retain=true
broker.async=false

Yet I still get !TSM:FPAR:NO REPLY

@gohan thanks for the feedback. According to that page it seems you not only need a gateway but also a controller. This explains why my nodes don't get a node id automatically.

@gohan thanks!

@gohan then shouldn't there be a note in the documentation of the ping pong sketch about this?

@sundberg84 i'm not using nrf at the moment but rfm69. Does the rfm radio also require a cap? And could you point me to a schematic for a cap on the voltage regulator? Doesn't the esp have an internal voltage regulator?

@gohan i'm using rfm69. Somehow I got it to work with one ESP gateway and 2 ESP nodes. All three have an rfm69 chip. I don't understand why you need a gateway to do ping pong?

@sundberg84 are you using the Decoupling-Capacitor as described here?

@gohan not sure if I understand your question since I don't know what can be expected from the Gateway?

Here's the gateway log:

0;255;3;0;9;MCO:BGN:INIT GW,CP=RRNGE--,VER=2.1.1
0;255;3;0;9;TSF:LRT:OK
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
scandone
state: 0 -> 2 (b0)
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 6
cnt 
chg_B1:-40
f r-40, 
connected with Airport, channel 6
dhcp client start...
scandone
.chg_B1:-80
............ip:192.168.0.164,mask:255.255.255.0,gw:192.168.0.1
.IP: 192.168.0.164
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
IP: 192.168.0.164
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mygateway1-out/0/255/0/0/18
pm open,type:2 0

I see the following in the mqtt log:

mygateway1-out/0/255/0/0/18 2.1.1

Yes, I checked the debug page.

I followed all the documented steps:

 *  To use this sketch, assemble MySensors nodes - they need nothing more than a radio
 *  1.  Flash each node with the same sketch, open the console and type either 0 or 1 to the respective nodes to set thei ID
 *  2.  You only need to set the node id once, and restart the nodes
 *  3.  To being a ping-pong test, simply type T in the console for one of the nodes.

Some documentation is missing:

• You need to set the MY_NODE_ID to 201 or 200 when using it with ESP8266
• You also need a Gateway, even when testing Node to Node ping pong

It's not clear what the expected result is, I'd expect something like Ping from node 200, then Pong! from node 201. But it would seem that it gives "Ying node", then "Yang node".

Hello,

I have 2 identical ESP8266 Node MCU's. Each has the Ping Pong example sketch installed to it.

Now I'm getting a lot of Find Parent errors:

TSM:INIT
TSM:INIT:TSP OK
TSM:INIT:STATID=201
TSF:SID:OK,ID=201
TSM:FPAR
TSF:MSG:SEND,201-201-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,201-201-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,201-201-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,201-201-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
!TSM:FPAR:FAIL
TSM:FAIL:CNT=7

Why does a ping pong sketch between 2 nodes ask for a parent?

What is needed to find the parent?

Thanks!

edit: updating the controller to the latest version has fixed the issue.

Just wanted to share this information.

I encountered quite a lot of wdt reset errors on my ESP nodes until I found this thread here.

So reconnecting USB should fix it.

@ErrK, see this topic http://www.esp8266.com/viewtopic.php?f=6&t=10901

I had the same issue, pressing reset didn't work but reconnecting the USB cable did the trick.

What would be needed to make this work with the MQTT gateway?

See this remark:

@tekka said in MySensors 2.0.0 Released:

@mpp said in MySensors 2.0.0 Released:

pm open,type:2 0

This is a message emitted by the ESP8266 core, not MySensors related.

I suggest you add the following to enable debugging on the serial interface:

#define MY_DEBUG

Also tripple check your wiring, it seems to make the ESP very unstable if there's a loose/bad connection. TSM:FAIL:CNT could indicate a problem with the radio/transmission.

The problems seem to have been caused by a bad connection on D1.

Still I find it strange that a Wifi login appears on the serial interface after programming the pingpong sketch.

@mfalkvidd said in Troubleshoot Nano temp/humidity to ESP8266-MQTT gateway issue:

I don't think handing out dynamic IDs works with mqtt.

It took me some time to find out that dynamic IDs don't work (yet?) with MQTT. Is there some documentation about this? Perhaps a note about this could be added here or a feature request could be opened here?

@gohan thanks for the reply but that was just a typo. The sketch compiles and uploads properly. Yet I keep seeing connections to my Wifi when I upload the ping pong script for example, this doesn't seem to be normal.

So I connected the radio to the ESP and the Pro Mini as described.

Installed the DHT sketch on the Pro Mini and added:

#define MY_RADIO_RFM69
#define MY_RFM69_FREQUENCY RF69_433MHZ
#define MY_IS_RFM69HW
#define MY_RFM69_NETWORKID 99

The Serial output:

TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,Starting sensor (RRNNA-, 2.0.0)
TSM:INIT
TSM:RADIO:OK
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:FAIL
!TSM:FAILURE
TSM:PDT
TSM:INIT
TSM:RADIO:OK
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:FAIL
!TSM:FAILURE
TSM:PDT
TSM:INIT
TSM:RADIO:OK
TSM:FPAR
TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:

Installed the default ESP MQTT gateway sketch on the ESP and added:

#define MY_RADIO_RFM69
#define MY_RFM69_FREQUENCY RF69_433MHZ
#define MY_IS_RFM69HW
#define MY_RF69_IRQ_PIN D1
#define MY_RF69_IRQ_NUM MY_RF69_IRQ_PIN
#define MY_RF69_SPI_CS D8
#define MY_RFM69_NETWORKID 99

The serial output:

K⸮⸮q⸮⸮0;255;3;0;9;Starting gateway (RRNGE-, 2.0.0)
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSM:RADIO:OK
0;255;3;0;9;TSM:GW MODE
0;255;3;0;9;TSM:READY
scandone
state: 0 -> 2 (b0)
f 0, state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 3
cnt 
scandone

connected with MPPort, channel 6
dhcp client start...
.............ip:192.168.0.219,mask:255.255.255.0,gw:192.168.0.1
.IP: 192.168.0.219
0;255;3;0;9;No registration required
0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1
IP: 192.168.0.219
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
pm open,type:2 0
0;255;3;0;9;TSP:SANCHK:OK
0;255;3;0;9;TSP:SANCHK:OK
0;255;3;0;9;TSP:SANCHK:OK
0;255;3;0;9;TSP:SANCHK:OK
0;255;3;0;9;TSP:SANCHK:OK
0;255;3;0;9;TSP:SANCHK:OK

I'm seeing the initial message in mqtt but not the messages from the node: mygateway1-out/0/255/0/0/18 2.1.1

Any idea what could be going wrong?

Hi @tekka Some documentation on "pm open,type:2 0" and what it means would be useful.

@lafleur I also see "pm open,type:2 0". Did you happen to install the ping pong sketch?

probably not related but I'm using an RFM69 with the ESP8266.

..ip:192.168.0.219,mask:255.255.255.0,gw:192.168.0.1
.IP: 192.168.0.219
0;255;3;0;9;No registration required
0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1
IP: 192.168.0.219
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
pm open,type:2 0

How did you get it to work finally?

I keep getting these "Soft WDT reset" crashes:

0;255;3;0;9;MCO:BGN:INIT GW,CP=RRNGE--,VER=2.1.1
0;255;3;0;9;TSF:LRT:OK
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 3
cnt
0;255;3;0;9;!TSM:INIT:TSP FAIL

connected with Airport, channel 6
dhcp client start...
0;255;3;0;9;TSM:FAIL:CNT=1
0;255;3;0;9;TSM:FAIL:PDT
ip:192.168.0.149,mask:255.255.255.0,gw:192.168.0.1
pm open,type:2 0
0;255;3;0;9;TSM:FAIL:RE-INIT
0;255;3;0;9;TSM:INIT

Soft WDT reset

ctx: cont
sp: 3ffef260 end: 3ffef550 offset: 01b0

stack>>>
3ffef410: 00000004 3ffef940 3ffef5ec 402030bd
3ffef420: 00000027 3ffef940 3ffef5ec 40203071
3ffef430: 3ffef604 00000001 3ffef5ec 402031b5
3ffef440: 00000000 00000016 3ffef5ec 402033f0
3ffef450: 0000002f 3ffef940 3ffef5ec 000000ff
3ffef460: 00000000 00000016 3ffef5ec 402044bd
3ffef470: 00020401 40040203 33060305 40086c07
3ffef480: 42190009 07264025 dc291028 2d2f882e
3ffef490: 90376330 8f3c4238 306f123d 000000ff
3ffef4a0: 00000063 00000000 3ffefa30 40203834
3ffef4b0: 3ffef758 00000000 00000000 0000466d
3ffef4c0: 3ffef758 00000000 00000000 40204574
3ffef4d0: 3ffef758 0000466d 40204290 40204599
3ffef4e0: 00000000 00000000 00000000 40202e15
3ffef4f0: 000007ce 00000000 00000000 40204ca9
3ffef500: 3fffdad0 3ffef5a7 00000000 402050e7
3ffef510: 600002ff 00020000 3ffef758 3ffee528
3ffef520: 3fffdad0 3ffef5a7 3ffefa10 40205355
3ffef530: feefeffe 00000000 3ffee520 402053c0
3ffef540: feefeffe feefeffe 3ffee530 40100114
<<<stack<<<

Hi,

When I press the reset button after reprogramming my Node MCU, it seems to be running the old script again. I'm seeing this behavior on 2 different NodeMCU's. What am I doing wrong here?

My ESP Node MCU seem to behave weird:

• install the Gateway script
• reprogram with the Blink script => it's blinking
• press reset
  And it seems to be running the gateway script again?

⸮% ⸮=c⸮⸮MCO:BGN:INIT NODE,CP=RRNNE--,VER=2.1.1
TSM:INIT
TSF:WUR:MS=0
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 3
cnt
!TSM:INIT:TSP FAIL
TSM:FAIL:CNT=1

connected with Airport, channel 6
dhcp client start...
TSM:FAIL:PDT

After installing the ping pong script and then the mqtt gateway, I noticed the node started with a dhcp but then asked the node id (0 2) which is part of the ping pong script?

connected with Airport, channel 6
dhcp client start...
0;255;3;0;9;MCO:REG:NOT NEEDED
f r-1, scandone
.............ip:192.168.0.219,mask:255.255.255.0,gw:192.168.0.1
.IP: 192.168.0.219
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
IP: 192.168.0.219
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mpp-mygateway1-out/0/255/0/0/18
pm open,type:2 0

=> This last line seems to come from the previous ping/pong script?

Why do I keep getting traces of previous scripts? Do I need to run the clear eeprom script every time before I program the node?

@Omemanti you'll need to uncomment this line for the RFM69H:

#define MY_IS_RFM69HW // Mandatory if you radio module is the high power version (RFM69HW and RFM69HCW), Comment it if it's not the case

I'm using Moteino's with and without H in the same network without issues.

Now I'm trying to get into mysensors but I'm running into a lot of issues:

• Node MCU with RFM69 keeps crashing after flasing it with the Gateway sketch
• Flashing the same node with a blink script works but when I reset it or flash any larger sketch to it, it is running the old gateway sketch!
• Can't seem to get a simple arduino pro mini to run with the RFM69

I'd like to create a network of ESP8266 (Node MCU) + RFM69 MQTT gateway and Arduino Pro Mini + RMF69 nodes (and repeaters)

Any tips how you got the ESP8266 or the Pro Mini working are welcome?

@hek just tested the gateway sketch on an esp with an rfm69 and it looks really promising. Would it be possible to communicate with moteino's or do I have to create arduino+rfm69 nodes running the mysensor sketch?

This wasn't clear to me either, I was expecting to see setup() & loop(). Perhaps a note or some documentation why this is empty would be useful.

Can this be used with RabbitMQ as broker?

Would it be possible to build an MQTT gateway using the ESP8266 WiFi Gateway?

Thank you for this nice write up.

I have some "low power" questions:

• Will the RTC continue to work when the Arduino is set to Sleep?
• Is there a way to save battery and wake up the Arduino using the RTC?
• What is the power consumption of a get time request?
• What is the autonomy of the RTC?