@gohan Ah really? I've loosely been following last i saw there was a proof of concept mentioned.

I use MQTT and Openhab2 - I find it more flexible then the Ethernet GW but yes you need to have a good understanding on all systems I suppose.

Somethings to note

• MySensors binding doesn't support MQTT gateway as far as I know, you need to use the MQTT binding and configure your OH items accordingly.
• MySensors binding is in the IOT market place and not openhab-addons
• You'll need to assign node ID to your nodes manually.

Not entirely sure what your problem is here but don't think you've got all the right pieces for the puzzle yet.

You need to change the MQTT topics in the OpenHab MQTT config.

MYS 2.0 is publishing data to this topic.

MyMQTT/27/5/1/0/4

However openhab is subscribing to this topic.

MyMQTT/27/5/V_PRESSURE

Hope this helps.

@SuperKris said:

The keypad will not be used to enter numbers. I will place a sticker over it converting the text on the switches to functions as "turn party lights on", "switch heater on", and "turn on garden lights for 5 min". These buttons will be coupled to certain actions by the controller. I'm using Domoticz on a Rpi.

Nice idea. When you do it could you provide a photo? Like to know how clean it looks.

I was wondering about this but currently don't have any nodes that need to report errors. I thought though I would wrap the error in a string including a prefix as well as importance of the error and send it back to the controller via S_VAR

I use MQTT gateway and I would have NodeRed listen out for any string with the prefix and send me an alert or log the event depending on the importance.

Just an idea at the moment but might help you.

@sundberg84

In power input I would suggest moving GND to the middle of VCC/RAW so you could using a 2 pin block for GND/RAW like what is shown in post 205. Might cause tracing issues though for you.

@TheoL said:

Why? Because it was fun and it can be done

Ha, I agree with this! Just curious about the fun after connecting it up.

There was a Node Red update the other week BTW, version 0.15

I'd be interested to know what you have planned with Azure IoT once you've got the data in to it? Not had time to investigate myself.

I'd go with NodeRed in between a local MQTT server and Azure IoT as going direct to Azure puts a dependency on the internet connection.

@Meshx86 the openhab binding doesnt support MQTT as far as I know.

If you are using the MQTT binding then you need another controller/method to provide the internal functions for my sensors. I use NodeRed workflow to listen for ID requests and it provides them.

Or static assign them in the node stretch.

@NiklasO

Here is it.

// Enable debug prints to serial monitor
//#define MY_DEBUG

//#define MY_NODE_ID 200
#define MY_SENSOR_ID 1

// Enable and select radio type attached
#define MY_RADIO_NRF24
//#define MY_RADIO_RFM69

// Enable repeater functionality for this node
#define MY_REPEATER_FEATURE

// LCD includes
#include <Wire.h> 
#include <LiquidCrystal_I2C.h>

// MYS includes
#include <SPI.h>
#include <MySensors.h>

#define LCD_ON 1  // GPIO value to write to turn on attached relay
#define LCD_OFF 0 // GPIO value to write to turn off attached relay

LiquidCrystal_I2C lcd(0x3f, 20, 4); //0x3f is the LCD address.
String LINE_BLANK = "                    ";

void before() {
}

void setup() {
  // Set off  LCD module
  lcd.begin (); 
  lcd.backlight();

  lcd.setCursor(0, 0); //
  lcd.print("Ready!"); // We expect the controller to remove this from display.
}

void presentation()
{
  // Send the sketch version information to the gateway and Controller
  sendSketchInfo("LCD Display", "1.0");

  present(MY_SENSOR_ID, S_INFO);
}


void loop()
{
  // extra processing if required.
}

void receive(const MyMessage &message) {
  // We only expect one type of message from controller. But we better check anyway.
  if (message.type == V_STATUS) {
    // Use V_STATUS to turn on/off the LCD display
    // if supported by LCD.
  }

  // temp string, probably don't need this.
  if (message.type == V_VAR1) {
    writeScreen(0, message.data);
  }

  if (message.type == V_VAR2) {
    writeScreen(1, message.data);
  }

  if (message.type == V_VAR3) {
    writeScreen(2, message.data);
  }

  if (message.type == V_VAR4) {
    writeScreen(3, message.data);
  }
}

void writeScreen(int line, String text)
{
  // Trim whitespace from incoming text.
  text.trim();

  // Remove anything over 20 char in text.
  if(text.length() > 19)
  {
      text.remove(20);
  }
  
  // Clear the line
  lcd.setCursor(0, line);
  lcd.print(LINE_BLANK);

  // Set Line
  lcd.setCursor(0, line);
  lcd.print(text);
}

@NiklasO I have something similar running on MYS 2.0 and can paste the code. I'm using a 4x1 display and using V_VAR-1-4 to send each line over.
If that's useful to you I can post it.

In that case what makes you think its not recognized?

Have you installed the Arduino software?
I had one of these until I lost it. I'm sure it was just plug and play and I'm sure the driver is included in the Arduino software installer.

https://www.arduino.cc/en/Main/Software

@Reza Oh I understand that but with stop command you could quite quickly have the shutter fully open but the motors still running. Right?

Nice, I was wondering about something like this but couldn't think how you'd handle limits? Unless the motor handles them..

Thats impressive, out of interest are you doing anything with this data in domotiocz?

This is because the sensor is still initialising and unable to complete as it is unable to find the gateway. It'll loop until it does find a gateway/parent, once it has it'll then go on to process your code.

Have you set up a gateway already?

I had this problem recently. Turned out to be a bad radio.

Ive started out with openHAB2. I was using a Ethernet gateway and tested the mysensors binding but found the combo was too limited. I much prefer having the MQTT gateway and the data be accessible to anything that subscribes, although I also now use openHAB to republish its item changes to MQTT as well which is probably a better approach.

I don't think the main new features in version 2 are very mature at the moment as well, discovered things for example get put in to a non human readable database and the web ui's are not fully functional.

With that being said I'm using node red to provide node ID's and configuring items manually and since beta3 it's been solid as a rock.

Don't know if it has a project website but it can be found here https://forum.mysensors.org/topic/838/windows-gui-controller-for-mysensors

On the Demonstration video what is each device? There are three devices but only two code examples.

Am I right in saying the left device is the motion sensor, the middle device is getting the sensor data over RS-485 from the left device and sending it over the air to the right device which is an Ethernet gateway by the looks of it? Or has the video got nothing to do with the code examples?