Posts made by el tigro

SOLVED..... Such a mug, such a small error. One character missing in wireless key.

NODE CODE
#define MY_DEBUG
#define MY_RADIO_NRF24
#define MY_NODE_ID 66
#include <SPI.h>
#include <MySensors.h>
#include <Bounce2.h>
#define RELAY_PIN 7
#define BUTTON_PIN 6
#define CHILD_ID 2
#define RELAY_ON 1
#define RELAY_OFF 0
#include <SPI.h>
#include <avr/wdt.h>
#include <Wire.h>
#define RESETWATCHDOG
Bounce debouncer = Bounce();
bool state = false;
bool initialValueSent = false;

MyMessage msg(CHILD_ID, V_STATUS);

void setup()
{
Serial.begin(115200);
pinMode(BUTTON_PIN, INPUT_PULLUP);
debouncer.attach(BUTTON_PIN);
debouncer.interval(10);
digitalWrite(RELAY_PIN, RELAY_ON);
pinMode(RELAY_PIN, OUTPUT);
}

void presentation() {
sendSketchInfo("Grey Lamp", "1.0");
present(CHILD_ID, S_BINARY);
}

void loop()
{
wdt_reset();
if (!initialValueSent) {
Serial.println("Sending initial value");
send(msg.set(state ? RELAY_ON : RELAY_OFF));
Serial.println("Requesting initial value from controller");
request(CHILD_ID, V_STATUS);
wait(2000, C_SET, V_STATUS);
}

if (debouncer.update()) {
if (debouncer.read() == LOW) {
state = !state;
send(msg.set(state ? RELAY_ON : RELAY_OFF), true);
}
}

}

void receive(const MyMessage &message) {
if (message.isAck()) {
Serial.println("This is an ack from gateway");
}

if (message.type == V_STATUS) {
if (!initialValueSent) {
Serial.println("Receiving initial value from controller");
initialValueSent = true;
}
state = (bool)message.getInt();
digitalWrite(RELAY_PIN, !state ? RELAY_ON : RELAY_OFF);
send(msg.set(state ? RELAY_ON : RELAY_OFF));
}
}

@el-tigro
I have other nodes / devices and they all do the same.
HA config

mysensors:
gateways:
- device: '/dev/ttyUSB0'
persistence_file: '/config/myhouse/mysensors.json'
- device: mqtt
persistence_file: '/config/myhouse/mysensors4.json'
topic_in_prefix: 'mygateway1-out'
topic_out_prefix: 'mygateway1-in'
optimistic: false
persistence: true
retain: true
version: '2.0'

mqtt:
broker: 192.168.1.***
port: 1883
client_id: home-assistant-1
keepalive: 60

Gateway code

#define MY_DEBUG
#define MY_BAUD_RATE 115200
#define MY_RADIO_NRF24
#define MY_GATEWAY_MQTT_CLIENT
#define MY_GATEWAY_ESP8266
#define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway1-out"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway1-in"
#define MY_MQTT_CLIENT_ID "Gateway"
#define MY_ESP8266_SSID "BTHub6-36PM"
#define MY_ESP8266_PASSWORD "88888888"
#define MY_ESP8266_HOSTNAME "Gateway node"
#define MY_CONTROLLER_IP_ADDRESS 192, 168, 1,***
#define MY_IP_GATEWAY_ADDRESS 192,168,1,***
#define MY_IP_SUBNET_ADDRESS 255,255,255,0
#define MY_PORT 1883
#include <ESP8266WiFi.h>
#include <MySensors.h>

void setup() {
}

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

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

@monte
Node debug. Appears to register but then no response to initial value request.
0 MCO:BGN:INIT NODE,CP=RNNNA--,VER=2.1.1
3 TSM:INIT
4 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
12 TSM:INIT:STATID=66
15 TSF:SID:OK,ID=66
16 TSM:FPAR
53 TSF:MSG:SEND,66-66-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
192 TSF:MSG:READ,0-0-66,s=255,c=3,t=8,pt=1,l=1,sg=0:0
197 TSF:MSG:FPAR OK,ID=0,D=1
2060 TSM:FPAR:OK
2061 TSM:ID
2062 TSM:ID:OK
2064 TSM:UPL
2069 TSF:MSG:SEND,66-66-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
2082 TSF:MSG:READ,0-0-66,s=255,c=3,t=25,pt=1,l=1,sg=0:1
2086 TSF:MSG:PONG RECV,HP=1
2089 TSM:UPL:OK
2092 TSM:READY:ID=66,PAR=0,DIS=1
2096 TSF:MSG:SEND,66-66-0-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
2103 TSF:MSG:READ,0-0-66,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
2110 TSF:MSG:SEND,66-66-0-0,s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=OK:2.1.1
2118 TSF:MSG:SEND,66-66-0-0,s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=OK:0
4127 TSF:MSG:SEND,66-66-0-0,s=255,c=3,t=11,pt=0,l=9,sg=0,ft=0,st=OK:Grey Lamp
4135 TSF:MSG:SEND,66-66-0-0,s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=OK:1.0
4144 TSF:MSG:SEND,66-66-0-0,s=2,c=0,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
4150 MCO:REG:REQ
4153 TSF:MSG:SEND,66-66-0-0,s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=OK:2
4176 TSF:MSG:READ,0-0-66,s=255,c=3,t=27,pt=1,l=1,sg=0:1
4182 MCO:PIM:NODE REG=1
4184 MCO:BGN:STP
4185 MCO:BGN:INIT OK,TSP=1
Sending initial value
4190 TSF:MSG:SEND,66-66-0-0,s=2,c=1,t=2,pt=2,l=2,sg=0,ft=0,st=OK:0
Requesting initial value from controller
4198 TSF:MSG:SEND,66-66-0-0,s=2,c=2,t=2,pt=0,l=0,sg=0,ft=0,st=OK:
Sending initial value
6207 TSF:MSG:SEND,66-66-0-0,s=2,c=1,t=2,pt=2,l=2,sg=0,ft=0,st=OK:0
Requesting initial value from controller

I'm going crazy, any help appreciated.

My setup.
Pi 3 controller on ethernet.
HASSOS recently installed.
MQTT.
NodeMCU 09 wifi gateway.
My sensors switch / lamp.

Nodes and gateway talking fine. Controller and gateway register with MQTT server on HA (mosquitto).

Nodes are registering with gateway but not getting 'initial value' back from HA and repeats request.

This happened after I updated HA. Any help appreciated.

sorted works a treat now. My bad, used a sketch I had tinkered with in the past. sketches melded now. Finished sketch below for them that might need. The sketch is for domestic light swith.

#define MY_NODE_ID 5
#define MY_DEBUG
#define MY_RADIO_NRF24
#include <SPI.h>
#include <MySensors.h>
#include <Bounce2.h>
#include <DHT.h>
#define DHT_DATA_PIN 7
#define CHILD_ID 3
#define BUTTON_PIN  3
#define SENSOR_TEMP_OFFSET 0
#define CHILD_ID_TEMP 1
Bounce debouncer = Bounce();
static const uint64_t UPDATE_INTERVAL = 5000;
static const uint8_t FORCE_UPDATE_N_READS = 2;
float lastTemp;
unsigned long interval = 5000;
unsigned long previousMillis = 0;
uint8_t nNoUpdatesTemp;
int oldValue = -1;
bool metric = true;
MyMessage msg(CHILD_ID, V_LIGHT);
MyMessage msgTemp(CHILD_ID_TEMP, V_TEMP);
DHT dht;


void presentation()
{
  sendSketchInfo("kitchen Lights", "1.1");
  present(CHILD_ID, S_LIGHT);
  present(CHILD_ID_TEMP, S_TEMP);
  metric = getConfig().isMetric;
}

void setup()
{
  pinMode(BUTTON_PIN, INPUT);
  digitalWrite(BUTTON_PIN, HIGH);
  debouncer.attach(BUTTON_PIN);
  debouncer.interval(5);
  dht.setup(DHT_DATA_PIN);
  if (UPDATE_INTERVAL <= dht.getMinimumSamplingPeriod()) {
    Serial.println("Warning: UPDATE_INTERVAL is smaller than supported by the sensor!");
  }
}

void loop()
{
  debouncer.update();
  int value = debouncer.read();
  if (value != oldValue) {
    send(msg.set(value == HIGH ? 1 : 0));
    oldValue = value;
  }
  unsigned long currentMillis = millis();
  if ((unsigned long)(currentMillis - previousMillis) >= interval) {
    dht.readSensor(true);
    float temperature = dht.getTemperature();
    if (isnan(temperature)) {
      Serial.println("Failed reading temperature from DHT!");
    } else if (temperature != lastTemp || nNoUpdatesTemp == FORCE_UPDATE_N_READS) {
      lastTemp = temperature;
      if (!metric) {
        temperature = dht.toFahrenheit(temperature);
      }
      nNoUpdatesTemp = 0;
      temperature += SENSOR_TEMP_OFFSET;
      send(msgTemp.set(temperature, 1));
#ifdef MY_DEBUG
      Serial.print("T: ");
      Serial.println(temperature);
#endif
    } else {
      nNoUpdatesTemp++;
    }
    previousMillis = millis();
  }
}

Hi.
I have put a dht11 sensor on my arduino nano light switch. The hardware switch is incase no UI or ALEXA down. I don't need the humidity component so I removed it.

#define MY_DEBUG
#define MY_RADIO_NRF24
#define MY_REPEATER_FEATURE
#define MY_NODE_ID 5
#include <SPI.h>
#include <MySensors.h> 
#include <elapsedMillis.h> 
#include <Bounce2.h>
#include <DHT.h>
#define DHT_DATA_PIN 7
#define RELAY_PIN  5
#define BUTTON_PIN  3
#define CHILD_ID 1
#define RELAY_ON 1
#define RELAY_OFF 0
#define SENSOR_TEMP_OFFSET 0
static const uint64_t UPDATE_INTERVAL = 5000;
static const uint8_t FORCE_UPDATE_N_READS = 1;
Bounce debouncer = Bounce();
bool state = false;
bool initialValueSent = false;
#define CHILD_ID_TEMP 3
unsigned long interval=10000; // the time we need to wait
unsigned long previousMillis=0; // millis() returns an unsigned long.
float lastTemp;

uint8_t nNoUpdatesTemp;
bool metric = true;
MyMessage msg(CHILD_ID, V_STATUS);
MyMessage msgTemp(CHILD_ID_TEMP, V_TEMP);
DHT dht;


void presentation()  
{ 
  sendSketchInfo("kitchen switch", "1.1");
  
  present(CHILD_ID, S_BINARY);
 present(CHILD_ID_TEMP, S_TEMP);
  metric = getConfig().isMetric;
}

void setup()
{
  pinMode(BUTTON_PIN, INPUT_PULLUP);
  debouncer.attach(BUTTON_PIN);
  debouncer.interval(10);
  digitalWrite(RELAY_PIN, RELAY_OFF);
  pinMode(RELAY_PIN, OUTPUT);
  
  dht.setup(DHT_DATA_PIN); // set data pin of DHT sensor
  if (UPDATE_INTERVAL <= dht.getMinimumSamplingPeriod()) {
    Serial.println("Warning: UPDATE_INTERVAL is smaller than supported by the sensor!");
  }
}

void loop()      
{  
 
if (!initialValueSent) {
    Serial.println("Sending initial value");
    send(msg.set(state?RELAY_ON:RELAY_OFF));
    Serial.println("Requesting initial value from controller");
    request(CHILD_ID, V_STATUS);
    wait(5000, C_SET, V_STATUS);
    presentation();
  }
  if (debouncer.update()) {
    if (debouncer.read()==LOW) {
      state = !state;
    send(msg.set(state?RELAY_ON:RELAY_OFF), true);   
    }
  }

 unsigned long currentMillis = millis();
 if ((unsigned long)(currentMillis - previousMillis) >= interval) {
  
  dht.readSensor(true);
  float temperature = dht.getTemperature();
  if (isnan(temperature)) {
    Serial.println("Failed reading temperature from DHT!");
  } else if (temperature != lastTemp || nNoUpdatesTemp == FORCE_UPDATE_N_READS) {

    lastTemp = temperature;
    if (!metric) {
      temperature = dht.toFahrenheit(temperature);
    }
    nNoUpdatesTemp = 0;
    temperature += SENSOR_TEMP_OFFSET;
    send(msgTemp.set(temperature, 1));

    #ifdef MY_DEBUG
    Serial.print("T: ");
    Serial.println(temperature);
    #endif
  } else {
    nNoUpdatesTemp++;
  }
 previousMillis = millis();
 }}
void receive(const MyMessage &message) {
  if (message.isAck()) {
     Serial.println("This is an ack from gateway");
  }
  if (message.type == V_STATUS) {
    if (!initialValueSent) {
      Serial.println("Receiving initial value from controller");
      initialValueSent = true;
    }
    state = (bool)message.getInt();
    digitalWrite(RELAY_PIN, state?RELAY_ON:RELAY_OFF);
    send(msg.set(state?RELAY_ON:RELAY_OFF));
  }
}

my problem is that the temp shows ok, the switch sends commands when tripped but is not on the Home Assistant UI or in entities. I need this switch to show up to set triggers.

Any help appreciated

Pi3 Home assistant + mosquitto
esp8266 wireless gateway
nano nodes Nrf2401 radios

1485777547: Sending PINGRESP to mysensors-1
1485777562: Received PINGREQ from mysensors-1
1485777562: Sending PINGRESP to mysensors-1
1485777563: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/5/25/1/0/16', ... (1 bytes))
1485777563: Sending PUBLISH to home-assistant-1 (d0, q0, r0, m0, 'mygateway1-out/5/25/1/0/16', ... (1 bytes))
1485777565: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/5/25/1/0/16', ... (1 bytes))
1485777565: Sending PUBLISH to home-assistant-1 (d0, q0, r0, m0, 'mygateway1-out/5/25/1/0/16', ... (1 bytes))

This is the mqtt log for one on / off cycle.

Here is the most basic sketch I could find and tweaked the code to run as a toggle on a domestic light switch.

#define MY_RADIO_NRF24
#include <MySensors.h>
#include <SPI.h>
#define MY_NODE_ID 25
#define OPEN 1
#define CLOSE 0
#define switchpin 3
int oldvalue = OPEN;
MyMessage msg(MY_NODE_ID, V_TRIPPED);
uint8_t value = OPEN;

void setup()
{
  pinMode (switchpin, INPUT_PULLUP);
}

void presentation()
{
  sendSketchInfo("TESTER", "");
  present(MY_NODE_ID, S_DOOR);
}

void loop()
{
  if (digitalRead(switchpin) == !oldvalue)
  {
    value = value == OPEN ? CLOSE : OPEN;
    send(msg.set(value));
    oldvalue = value;
  }
}

With this code alone,no yaml entry, the node is found by HA and shows accordingly as triggered if the switch is flicked. mqtt all good, gateway happy.

How the fook do I attach switch result to the intended node?
Do I need a yaml entry for the physical switch? I tried but failed.
Do I then need to set up a trigger?

switch:
  - platform: mqtt
    name: "TESTER"
    command_topic: "mygateway1-in/2/2/1/0/2"
    payload_on: "1"
    payload_off: "0"
    optimistic: false
    qos: 0
    retain: true

This just gives me a new (software) switch in my dash and controls the light but physical switch (node 2 child 2) doesn't work.

Hello mate and thanks for chirping in. I realised a while ago that this project was well above my current knowledge base but thats like a red rag to bull, stubborn old git that I am.

After I got my HA, mqtt, MySensors and the gateway talking, my first few nodes found and set themselves up pretty much. I didn't have to jump into message construction, pub/sub, complex yaml code and that's the bit I'm stuck on. Once I get it, I'm away, the penny just hasn't dropped yet.

I think I need a night in, just me and mqtt, a nice meal, a bottle of soco, a few cuddles and really get to know each other. I guess thats true cyber sex, i do have a wife and kids.... honest.

Any reccommended sites, tutorials will be appreciated.

Cheers

This is the yaml entry for mqtt switch from HA website

switch:
  - platform: mqtt
    name: "Bedroom Switch"
    state_topic: "home/bedroom/switch1"
    command_topic: "home/bedroom/switch1/set"
    payload_on: "ON"
    payload_off: "OFF"
    optimistic: false
    qos: 0
    retain: true

There is no similar refence for mysensors switch section.

It's hard to ask when your not sure what your asking for.

I did have a look at that I assume I would need to insert a trigger also. It all seemed a bit over the top for the simplest of operation. All I want is if pin 3 goes high, publish light on.

The bit I can't get my head around is that there is no details of topics etc to establish what goes where. Because I don't know, it is all a bit 'magic' how the communications work.

Once again I must be missing something. Nowhere can I find and example of a simple domestic 240v light switch and light fitting.

I have lights on my HA, can control them with PC, phone, ALEXA, no problem, but I want manual switches (wifi) on the walls also.

I use the relay sketch for the light fitting side, all working fine.

Can I find anything relating to the switch side..... naffink.

I have built the hardware, arduino nano,NRF2401+ all sat on the back of a single UK light switch. Thats all good and tested also. It's the code I dont have or guidance to set it up.

Lights, temp, alexa were all basically plug and play with minor tweaks, this, a most simple use, baffled again.

Please help.

Well, the sun shines on a dogs arse some days.

We've only gone and done it, HA dash with relay sw. can controll led from dash. I honestly have sticky stuff running down my leg. You have no idea how happy I am.

For future reference.
I was flicking the power to reset pi in between config changes. My mosquitto was not starting from boot, so nothing to connect to, hence the errors when the code was right.
Also reset your nodes after a change.

This my yaml for the following setup

nodes are arduino nanos with nrf2401+ radio. (mysensors 2.0)

gateway is esp8266 NodeMCU 1.09. Wifi with NRF2401+

Pi 3 hosts Home Assistant and Mosquitto broker. Installed with All in one image.

mysensors:
  gateways:
    - device: mqtt
      persistence_file: '/home/homeassistant/mysensors4.json'
      topic_in_prefix: 'mygateway1-out'
      topic_out_prefix: 'mygateway1-in'
  debug: true
  optimistic: false
  persistence: true
  retain: true
  version: 2.0

mqtt:
  broker: localhost
  port: 1883
  client_id: home-assistant-1
  keepalive: 60

Righty. I'm off to play. Be back very soon when i get stuck.

Cheers for now fella, thank you for all your help.

OK. we are in, no errors in HA but have this in HA log.

17-01-23 22:19:55 mysensors.mysensors: File does not exist or is not readable: /home/homeassistant/mysensors4.json
17-01-23 22:19:55 mysensors.mysensors: Trying backup file: /home/homeassistant/mysensors4.json.bak
17-01-23 22:19:55 mysensors.mysensors: File does not exist or is not readable: /home/homeassistant/mysensors4.json.bak
17-01-23 22:19:55 mysensors.mysensors: Failed to load sensors from file: /home/homeassistant/mysensors4.json

I have tried a few file path but always the same.

Hi again.

here is my home-assistant.log

fingers double crossed

pi@raspberrypi:/home/homeassistant/.homeassistant $ less home-assistant.log
17-01-23 19:36:57 homeassistant.components.mqtt: Can't connect to the broker. Please check your settings and the broker itself
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/mqtt/__init__.py", line 262, in setup
    birth_message)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/mqtt/__init__.py", line 351, in __init__
    self._mqttc.connect(broker, port, keepalive)
  File "/home/homeassistant/.homeassistant/deps/paho/mqtt/client.py", line 686, in connect
    return self.reconnect()
  File "/home/homeassistant/.homeassistant/deps/paho/mqtt/client.py", line 808, in reconnect
    sock = socket.create_connection((self._host, self._port), source_address=(self._bind_address, 0))
  File "/usr/lib/python3.4/socket.py", line 509, in create_connection
    raise err
  File "/usr/lib/python3.4/socket.py", line 500, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
17-01-23 19:36:57 homeassistant.bootstrap: component mqtt failed to initialize
17-01-23 19:36:57 homeassistant.bootstrap: Component mqtt failed to setup
17-01-23 19:36:57 homeassistant.components.mysensors: No devices could be setup as gateways, check your configuration
17-01-23 19:36:57 homeassistant.bootstrap: component mysensors failed to initialize
17-01-23 19:36:57 homeassistant.components.mqtt: Can't connect to the broker. Please check your settings and the broker itself
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/mqtt/__init__.py", line 262, in setup
    birth_message)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/mqtt/__init__.py", line 351, in __init__
    self._mqttc.connect(broker, port, keepalive)
  File "/home/homeassistant/.homeassistant/deps/paho/mqtt/client.py", line 686, in connect
    return self.reconnect()
  File "/home/homeassistant/.homeassistant/deps/paho/mqtt/client.py", line 808, in reconnect
    sock = socket.create_connection((self._host, self._port), source_address=(self._bind_address, 0))
  File "/usr/lib/python3.4/socket.py", line 509, in create_connection
    raise err
  File "/usr/lib/python3.4/socket.py", line 500, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
17-01-23 19:36:57 homeassistant.bootstrap: component mqtt failed to initialize

Same same, no different i'm affraid. It's pissing me off now, more because I don't understand enough to do more for myself. I think this is going to be shelved for a while.
I am talking about the wifi gateway,

I am gonna stick with HA and mysensors but rehash my hardware. I have PI's , Nano's, Yun, Mini's and ESP8266's. What combination / configuration would you recommend for ease of setup.

Gonna try running mosquiito on a seperate Pi to HA first off.

Should my gate gateway sketch have presentation details in it, coz it doesn't. I removed comments to reduce size.

/**

 * The ESP8266 MQTT 

#include <EEPROM.h>
#include <SPI.h>

// Enable debug prints to serial monitor
#define MY_DEBUG 
#define MY_BAUD_RATE 9600
#define MY_RADIO_NRF24
#define MY_GATEWAY_MQTT_CLIENT
#define MY_GATEWAY_ESP8266
#define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway1-out"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway1-in"
#define MY_MQTT_CLIENT_ID "mysensors-1"
#define MY_ESP8266_SSID "BTHub5-C2FC"
#define MY_ESP8266_PASSWORD "xxxxxxxxx"
 #define MY_ESP8266_HOSTNAME "mqtt-sensor-gateway" ///
#define MY_CONTROLLER_IP_ADDRESS 192,168,1,115
#define MY_PORT 1883      
 /*
// Flash leds on rx/tx/err
#define MY_LEDS_BLINKING_FEATURE
// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300

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

#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
}

mysensors:
  gateways:
    - device: mqtt
      persistence_file: '/home/homeassistant/.homeassistant/mysensors4.json'
      topic_in_prefix: 'mygateway1-out'
      topic_out_prefix: 'mygateway1-in'
  debug: true
  optimistic: false
  persistence: true
  retain: true
  version: 2.0

mqtt:
  broker: 192.168.1.115
  client_id: home-assistant-1

is giving the same

Invalid config
The following components and platforms could not be set up:

    mysensors
    mqtt

Please check your config 

To clarify in my head, everything that is connected to HA needs a block in config with minimum set of data but can be finely tuned with further commands if need be.
If this is the case, how is the gateway identified in the first block of code.

To make sure I am not mis-reading debug, this is my arduino nano node

Starting repeater (RNNRA-, 2.0.0)
TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=1)
TSM:FPAR
TSP:MSG:SEND 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSP:MSG:READ 0-0-1 s=255,c=3,t=8,pt=1,l=1,sg=0:0
TSP:MSG:FPAR RES (ID=0, dist=0)
TSP:MSG:PAR OK (ID=0, dist=1)
TSM:FPAR:OK
TSM:ID
TSM:CHKID:OK (ID=1)
TSM:UPL
TSP:PING:SEND (dest=0)
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=ok:1
TSP:MSG:READ 0-0-1 s=255,c=3,t=25,pt=1,l=1,sg=0:1
TSP:MSG:PONG RECV (hops=1)
TSP:CHKUPL:OK
TSM:UPL:OK
TSM:READY
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=ok:0100
TSP:MSG:SEND 1-1-0-0 s=255,c=0,t=18,pt=0,l=5,sg=0,ft=0,st=ok:2.0.0
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=ok:0
TSP:MSG:READ 0-0-1 s=255,c=3,t=15,pt=6,l=2,sg=0:0100
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=11,pt=0,l=12,sg=0,ft=0,st=ok:Relay+button
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=ok:1.0
TSP:MSG:SEND 1-1-0-0 s=1,c=0,t=3,pt=0,l=0,sg=0,ft=0,st=ok:
Request registration...
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=ok:2
TSP:MSG:READ 0-0-1 s=255,c=3,t=27,pt=1,l=1,sg=0:1
Node registration=1
Init complete, id=1, parent=0, distance=1, registration=1
Sending initial value
TSP:MSG:SEND 1-1-0-0 s=1,c=1,t=2,pt=2,l=2,sg=0,ft=0,st=ok:0
Requesting initial value from controller

This is My gateway

0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGE--,VER=2.1.0
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
no BTHub5-C2FC found, reconnect after 1s
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
reconnect
f 0, 0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
scandone
f -180, ....scandone
no BTHub5-C2FC found, reconnect after 1s
reconnect
f r0, ....scandone
no BTHub5-C2FC found, reconnect after 1s
reconnect
f 0, .....scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1
cnt 
.0;255;3;0;9;TSF:MSG:READ,1-1-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=1
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

connected with BTHub5-C2FC, channel 6
dhcp client start...
0;255;3;0;9;TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
..ip:192.168.1.117,mask:255.255.255.0,gw:192.168.1.254
.IP: 192.168.1.117
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
IP: 192.168.1.117
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
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;TSF:MSG:SEND,0-0-1-1,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,1-1-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
0;255;3;0;9;TSF:MSG:SEND,0-0-1-1,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,1-1-0,s=255,c=0,t=18,pt=0,l=5,sg=0:2.0.0
0;255;3;0;9;Sending message on topic: mygateway1-out/1/255/0/0/18
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
0;255;3;0;9;Sending message on topic: mygateway1-out/1/255/3/0/6

And here is broker

login as: pi
pi@192.168.1.115's password:

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Jan 19 22:04:56 2017
pi@raspberrypi:~ $ mosquitto -v
1484863517: mosquitto version 1.3.4 (build date 2014-08-22 06:10:51+0000) starting
1484863517: Using default config.
1484863517: Opening ipv4 listen socket on port 1883.
1484863517: Opening ipv6 listen socket on port 1883.
1484863518: New connection from 192.168.1.117 on port 1883.
1484863518: New client connected from 192.168.1.117 as mysensors-1 (c1, k15).
1484863518: Sending CONNACK to mysensors-1 (0)
1484863518: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/0/255/0/0/18', ... (5 bytes))
1484863518: Received SUBSCRIBE from mysensors-1
1484863518:     mygateway1-in/+/+/+/+/+ (QoS 0)
1484863518: mysensors-1 0 mygateway1-in/+/+/+/+/+
1484863518: Sending SUBACK to mysensors-1
1484863518: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/2/0/2', ... (0 bytes))
1484863519: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/1/0/2', ... (1 bytes))
1484863520: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/1/0/2', ... (1 bytes))
1484863520: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/2/0/2', ... (0 bytes))
1484863522: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/1/0/2', ... (1 bytes))
1484863522: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/2/0/2', ... (0 bytes))
1484863524: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/1/0/2', ... (1 bytes))
1484863524: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/2/0/2', ... (0 bytes))
1484863526: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/1/0/2', ... (1 bytes))
1484863526: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/2/0/2', ... (0 bytes))
1484863528: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/1/0/2', ... (1 bytes))
1484863528: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/2/0/2', ... (0 bytes))
1484863530: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/1/0/2', ... (1 bytes))
1484863530: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/2/0/2', ... (0 bytes))
1484863532: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/1/0/2', ... (1 bytes))
1484863532: Received PUBLISH from mysensors-1 (d0, q0, r0, m0, 'mygateway1-out/1/1/2/0/2', ... (0 bytes))
1484863534: Received PINGREQ from mysensors-1
1484863534: Sending PINGRESP to mysensors-1

It won't matter that my broker and HA are on the smae pi will it.

Your a rare breed fella, don't let the wifey know ya refusing $$ lol. Will make a donation.... if ya sort me out.

@el-tigro said:

 mysensors:
   gateways:
     - device: mqtt
       persistence_file: 'home/homeassistant/.homeassistant/mysensors4.json'
       topic_in_prefix: 'mygateway1-out'
       topic_out_prefix: 'mygateway1-in'
   debug: true
   optimistic: false
   persistence: true
   retain: true
   version: 2.0

Good morning from blighty. I retained your format and indentations, I think. Sorry for typo's, it was 1am and a few southern comforts. The hidden .homeassistant folder, was part of install and is where my config file lives, is that not good.

You are exposing my dumb ass here lol, i thought we just configured the '-device :mqtt'.
This is from HA website for mysensors but all I can see to configure is the boker IP. I tried it along with the previous code.... same error.

Where I come from, it's rude not to accept a drink between men and I don't mean a virtual drink. Your service and assistance is invaluable to me and the least I could do is slide you a bottle of Southern Comfort. So stop being humble, stop being rude and email me an paypal addy.

 mqtt:
   broker: IP_ADDRESS_BROKER
   port: 1883
   client_id: home-assistant-1
   keepalive: 60
   username: USERNAME
   password: PASSWORD
   certificate: /home/paulus/dev/addtrustexternalcaroot.crt
   protocol: 3.1
   birth_message:
     topic: 'hass/status'
     payload: 'online'
     qos: 1
     retain: true
   will_message:
     topic: 'hass/status'
     payload: 'offline'
     qos: 1
     retain: true

looked for a path to certificate...... no idea there. Tried leaving in and without

my mosquitto mqtt has no username or pw at the moment. Tried leaving in and without.

Once again I am at your mercy lol

Some progress, probably me not understanding.

firstly, my humble apologes if I come across as thick. 2 weeks ago I was playing with arduino IDE and NRF24 libraries. To me Linux was a nerd code, way above me and cmd prompt was chinese.

is my persistence part right? It is the same path I take to configure.yaml

mysensors:
  gateways:
    - device: mqtt
      persistence_file: 'home/homeassistance/.homeassistance/mysensors4.json'
      topic_in_prefix: 'mygateway1-out'
      topic_out_prefix: 'mygateway1-in'
  debug: true
  optimistic: false
  persistence: true
  retain: true
  version: 2.0

I left the pub/sub part as is, content can come later.... I assume.

Good and bad results.
Home assistant socket :8123 stays up (crashed every time for me) but shows errors.

Invalid config
The following components and platforms could not be set up:

    mysensors
    mqtt

Please check your config 

Is my syntax correct?

I have been looking at the work you put in and your result, some folk deserve a drink. Do you have paypal details?

wow, your message grew as I was writing, I will try what you suggested now, thanks

Firstly, thanks for replying, you are at present, my only contact with hope. Hey..come back don't run away. lol.

Once I get one working node, I can start to disect how it's done and apply (hopefully) to the next node, that's my funked up way of doing things. I am getting confused now, my gateway is an ESP8266 (NodeMCU) and my nodes are arduino.

My brain fart is understanding the device identification system, terms and syntax so to speak.

• device: '/dev/ttyUSB0'

it means nothing to me other than a pointer, to something. That something, makes somebody's config work based on their setup. In the terms/syntax used above, I have no idea what I have, where to point to and what i need to tell it to do or tell it to do.

No info, i can find, point's towards (or am I blinded) my wireless gateway and connecting to HA.

I feel like I am trying to make a cake, I know I have all the ingredients right, everything is weighed out correct, I followed all the recipe-ish, but still it remains gooey. I do it over and over and still the same result, gunky mess, no cake. Then I realise I farted at the little 1 liner about turning the oven on and missed it.

any help or pointers appreciated.

@el-tigro

I assume the above example is instructions for 4 devices, 1 being mqtt broker.

what is - device: '/dev/ttyUSB0' and how does it identify the device? It looks like a path to a destination file, where? what is it?

how many of the 4 sets of instructions are relavent to my setup and which if any can i drop? Mqtt to stay

how do I identify, what do i need to identify / present for my wireless gateway and node?

thanks again.

@el-tigro

Ok. How would I configure the example from HA to my setup?? many thanks.

mysensors:
gateways:
- device: '/dev/ttyUSB0'
persistence_file: 'path/mysensors.json'
baud_rate: 38400
- device: '/dev/ttyACM0'
persistence_file: 'path/mysensors2.json'
baud_rate: 115200
- device: '192.168.1.18'
persistence_file: 'path/mysensors3.json'
tcp_port: 5003
- device: mqtt
persistence_file: 'path/mysensors4.json'
topic_in_prefix: 'mygateway1-out'
topic_out_prefix: 'mygateway1-in'
debug: true
optimistic: false
persistence: true
retain: true
version: 2.0

Hi all. Bordering on suicidal, please help.

Pi 3 with all in one (raspian lite - mosquitto - home assistant) installed
NodeMCU 1.09 wireless GW with nrf2401+ radio.
arduino nano clone mysensors relay. v2 node

Node talks to GW ok
GW talks to node ok
GW talks to mosquitto ok
mosquitto talk to GW ok
Home assistant boots up with :8123 ok
getting HA to find sensors, configure configure.yaml...... NOT OK
because of this, no GW to HA communication.

How I managed the above, I really have no idea. I am one of the mugs that believed the arduino hype. "No coding experience required, cut and paste, simple"..... What a load of tripe. lol. I now know a little bit about alot of areas but now and again I just hit a wall. I cannot get my head around how to configure the configure.jaml file. Every time I try it crashes the browser socket.

A simple working example and I will be away and learn from there. I feel like a dumb blonde on this but I swear, if you guys don't help me out, I am putting the wife in the garden shed for the rest of the winter.

Thanks in advance.