Handling NACKs

[mfalkvidd]

@sundberg84 sorry for going off topic, but what limitations have you experienced?

I've been thinking about using something better than Domoticz for a long time. Maybe Grafana is the way to go.

[BearWithBeard]

@mfalkvidd Domoticz is a full-blown home automation system, isn't it? Grafana is just a monitoring dashboard that pulls data from a time-series database (like InfluxDB) and generates fancy graphs. It can't automate and control things or send commands other than alarms (eg. if a value exceeds a threshold, or no new data came in since x minutes, send an email).

One of InfluxDBs limitations is that you can't use (or only some basic) math operations on db queries, which may limit what you can graph in Grafana. Also, changing data types of existing fields in measurements is also not possible, which is annoying, because Grafana treats values differently based on their data type. @sundberg84 can probably name more limitations. I'd love to switch to Carbon / Graphite for data collection and storage... if only it wouldn't take time to read up, setup and migrate all the data. :tired_face:

By the way - great idea to use the indication handler to log radio reliability! :+1: Definitely going to implement this on my gateways repeaters when I find the time.

[sundberg84]

@mfalkvidd - @BearWithBeard said it. The limitations are mostly math related. For example, you cant show a graph with current and last years values (timeshift) on the same graph due to that limitation in InfluxDB. I want to compare power usage this day to same day last year - not possible. Im looking to change to Graphite as well instead of Influx.

Moving from Domoticz to HA was a great move for me, but not as i thought. Im using HA more or less just as an umbrella. I would say im using only the OS Hass.IO and not using Home Assistant that much. Whats good in Home Assistant is that its quite easy to integrate different protocolls like MySensors or whatever you use. But after that I dont use Home Assistant but the great possibilities to have add-ons on Hass.IO. I use Node Red for all my automations (Extremly easy compared to code!), Influx + Grafana for visual, motionEyeOs for camera secutiry and more... all you have to do is install the addon from the "store" and you are more or less ready to go. These addons im sure you can install with domoticz as well if you like the integrations with the different protocolls there.

i think we have handeled the NACK questions so no worries for me if we go off topic, but if you rather like send me a dm.

[sundberg84]

I just love this idea. Implemented the code on my second now, one to go.

[mfalkvidd]

@sundberg84 very nice. I'm happy we were able to implement it with so little effort. What does your graph look like now?

Mine is very boring, as I suspected. Don't have any outgoing traffic from my GW. Will have to add it to my nodes to get any useful data.

[sundberg84]

@mfalkvidd i didnt fins time yet to implement more. But very good for two repeaters.

[alowhum]

Very cool stuff.

@mfalkvidd Would it be possible to create the functionality, but to measure the successrate of outgoing messages from the gateway node?

For example, I'l love to be able to see how often the controller/gateway tries to toggle a distant node, but fails.

[mfalkvidd]

@alowhum unless I misunderstand your suggestion, that's exactly what I have already done.

[alowhum]

Ah, now I see. Thanks!

[evb]

@sundberg84 If I get it correct you implemented in your repeater sketch the use of the MySensors indication handler?

void indication(indication_t ind)
{
  switch (ind)
  {
    case INDICATION_TX:
      txOK++;
      break;
    case INDICATION_ERR_TX:
      txERR++;
      break;
  }
}

txOk and txErr are always incremented in the sketch and send to the gateway.
Yet I see in your graphs a hourly count? Graphs from Grafana?
Can you explain how you did this?

[sundberg84]

@evb - yes, that is correct, here is a complete sketch with a GW (Nrf24 - ethernet)

// Enable debug prints to serial monitor
#define MY_DEBUG

// Enable and select radio type attached
#define MY_RADIO_NRF24
#define MY_RF24_PA_LEVEL RF24_PA_MAX

// Enable gateway ethernet module type
#define MY_GATEWAY_W5100

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

#define MY_IP_ADDRESS 192,168,1,8   // If this is disabled, DHCP is used to retrieve address
// 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, 0x01, 0x08 //AF-A0-F2-15-3B-1C

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

// Uncomment to override default HW configurations
#define MY_DEFAULT_ERR_LED_PIN 7  // Error led pin
#define MY_DEFAULT_RX_LED_PIN  9  // Receive led pin
#define MY_DEFAULT_TX_LED_PIN  8  // the PCB, on board LED


#define MY_INDICATION_HANDLER
static uint32_t txOK = 0;
static uint32_t txERR = 0;
#define REPORT_INTERVAL 300000 // Report every 5 minutes
#define CHILD_ID_TX_OK 0
#define CHILD_ID_TX_ERR 1

#include <SPI.h>

#if defined(MY_USE_UDP)
#include <EthernetUdp.h>
#endif
#include <Ethernet.h>
#include <MySensors.h>

MyMessage txOKmsg(CHILD_ID_TX_OK, V_CUSTOM);
MyMessage txERRmsg(CHILD_ID_TX_ERR, V_CUSTOM);

void indication(indication_t ind)
{
  switch (ind)
  {
    case INDICATION_TX:
      txOK++;
      break;
    case INDICATION_ERR_TX:
      txERR++;
      break;
  }
}

void presentation()
{
  //Send the sensor node sketch version information to the gateway
  sendSketchInfo("Gateway #1", "1.0");
  present(CHILD_ID_TX_OK, S_CUSTOM);
  present(CHILD_ID_TX_ERR, S_CUSTOM);
}

void setup()
{
}

void loop() {

  static unsigned long last_send = 0;
  if (millis() - last_send > REPORT_INTERVAL) {
    send(txOKmsg.set(txOK));
    send(txERRmsg.set(txERR));
    last_send = millis();
  }

}

In Home Assistant you need to create a sensor that breaks down the incrementing number to each intervall you want.
I use a utility_meter.

utility_meter:
hourly_ok_gw:
    source: sensor.gateway_1_0_0
    cycle: hourly
  hourly_err_gw:
    source: sensor.gateway_1_0_1
    cycle: hourly

This sensors will be sent to Grafana each hour just like any other sensor and you can create a graph there: