Posts made by diggs

@awi @Sparkman

Thanks guys, will implement these and see how it goes

@5546dug @hek

Thanks guys. Will jump in and see what happens.

Hi all,

Just wondering if it is OK to have two gateways running within range of each other. I have a home system running, but want to build a system for a friend and do the testing at home. That means I will have two gateways (and their nodes) within range of each other when doing the test and build.

I would imagine both gateways will pickup all nodes. Would this cause confusion in the systems?

Thanks for the advice

@jkandasa as discussed on chat, but thought I would put the info her as well.

Using one of the 4 USB ports on the PI.

Versions

Linux raspberrypi 4.1.6-v7+ #810 SMP PREEMPT Tue Aug 18 15:32:12 BST 2015 armv7l GNU/Linux

@jkandasa I do have an AMA0, but it does not work on that one either. The gateway is definitely connected to ACM0. Which is the one it works on when I have Domoticz connected up.

Something odd is happening with the PI USB side of things. Tried switching to another port but no luck there either.

As a side, I installed on windows and it works fine, so I know the gateway is OK, but I really want it running on the PI at some point

@jkandasa Checked my settings and they were already set as per that article, so I don't believe that is the trouble I am facing. From the logs I sent you, anything else you think could be causing the issue. Was the port being opened OK in the system?

@jkandasa OK thanks

At least I am not going crazy

@davidbd Thanks for the reply.

Yep, can connect to the port and see the node / gateway data in the line.

Still nothing though in the Mycontroller

All my settings seem pretty standard, so not sure what the issue would be or what to check next.

#========================================================================
# MySensors Gateway settings
# Select Type of gateway will be used, Only one gateway will be used
# Types -> serial, ethernet, mqtt
#========================================================================
mcc.ethernet.gateway.type=serial

#========================================================================
# MySensors Serial port settings
# In this section select: Driver, port name and baud rate
# Available drivers -> [pi4j, jssc, jserialcomm, auto]
#========================================================================
mcc.serialport.driver.type=auto
mcc.serialport.name=/dev/ttyACM0
mcc.serialport.baud.rate=115200

#========================================================================
# MySensors Ethernet Gateway settings
# Update host name/ip and port number, Default: 192.168.178.6:5003
# Keep alive check frequency in seconds
#========================================================================
mcc.ethernet.gateway.host=192.168.178.6
mcc.ethernet.gateway.port=5003
mcc.ethernet.gateway.keep.alive.frequency=60

#========================================================================
# MySensors MQTT Gateway settings
# Update broker host name/ip and port number, Default: 192.168.178.6:1883
# Root topic name of broker
# Note: MQTT_TRANSLATE_TYPES will be not supported
# Disable MQTT_TRANSLATE_TYPES in your MQTT gateway
#========================================================================
mcc.mqtt.gateway.broker.host=192.168.178.6
mcc.mqtt.gateway.broker.port=1883
mcc.mqtt.gateway.broker.root.topic=MyMQTT

#========================================================================
# Database
# Where do you want to keep your database.
# It is highly recommended  to take a backup of this db on upgrade. 
# Database: H2DB, location and name, example:/tmp/mycontroller
#========================================================================
mcc.h2db.location=../conf/mycontroller

#========================================================================
# Web files, will be located under ../www by default
# For web used angularjs
#========================================================================
www.file.location=../www/

#========================================================================
# Web Application server configuration
# bind.address - interface to bind. 0.0.0.0 - all available interfaces
# You can use either http or https, enable.https - https is enabled
# if https is enabled specify keystore file details
# It is highly recommended to use https also change default keystore file
#========================================================================
bind.address=0.0.0.0
enable.https=true
http.port=8443
ssl.keystore.file=../conf/keystore.jks
ssl.keystore.password=password
ssl.keystore.type=JKS

#logger configuration - logback.xml

@jkandasa Thanks

Have now done all that. Stopped the Domoticz server, started Mycontroller. I get the webpage up now, but still no nodes showing up and for some reason nothing is being written to my logs the past few hours at all.

What can I look at?

@jkandasa Thanks for that.

The latest Java version has go me going as far as server access goes, but I am having issues opening the serial port it seems.

I am trying to run in parallel with Domoticz, but I maybe having an issue trying to access the same port I am guess.

Suggestions on how to get around that?

2015-09-27 15:45:16,568 ERROR [main] [org.mycontroller.standalone.gateway.serialport.SerialPortPi4jImpl:68] Failed to load serial port,
java.io.IOException: Unable to open the serial port/device. (Error #2)
        at com.pi4j.jni.Serial.open(Native Method) ~[mycontroller-standalone-0.0.2-alpha4-single.jar:na]
        at com.pi4j.io.serial.impl.SerialImpl.open(SerialImpl.java:151) ~[mycontroller-standalone-0.0.2-alpha4-single.jar:na]
        at com.pi4j.io.serial.impl.SerialImpl.open(SerialImpl.java:242) ~[mycontroller-standalone-0.0.2-alpha4-single.jar:na]
        at org.mycontroller.standalone.gateway.serialport.SerialPortPi4jImpl.initialize(SerialPortPi4jImpl.java:61) [mycontroller-standalone-0.0.2-alpha4-single.jar:na]
        at org.mycontroller.standalone.gateway.serialport.SerialPortPi4jImpl.<init>(SerialPortPi4jImpl.java:40) [mycontroller-standalone-0.0.2-alpha4-single.jar:na]
        at org.mycontroller.standalone.StartApp.startServices(StartApp.java:217) [mycontroller-standalone-0.0.2-alpha4-single.jar:na]
        at org.mycontroller.standalone.StartApp.main(StartApp.java:78) [mycontroller-standalone-0.0.2-alpha4-single.jar:na]
2015-09-27 15:45:16,646 INFO [main] [org.mycontroller.standalone.db.TimerUtils:144] Updated Time:[SunRise:Sun Sep 27 10:36:00 AEST 2015, SunSet:Sun Sep 27 22:41:00 AEST 2015], City:[latitude:11.2333, longit$
[Sun Sep 27 15:45:21 AEST 2015] TJWS httpd 0.0.0.0 - [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,localport=8443]] is listening.

For some reason cannot seem to get it running.

Have installed the software and the server appears to start, but there is no web access and this is what I get when I check the log.

Have I setup something incorrect

Running on a PI

Exception in thread "main" java.lang.UnsupportedClassVersionError: org/mycontroller/standalone/StartApp : Unsupported major.minor version 52.0
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:792)
        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
        at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
        at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)

java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) Client VM (build 24.0-b56, mixed mode)

Just wondering if it is possible to run two controllers side by side both looking at the same serial port?

i.e. can I run Domoticz and MyController at the same time in serial mode with the one gateway or would it cause issues?

I have a requirement where I will be running a sensor in a remote location that I will not have physical access to for several weeks. I will have remote access via either port forwarding on the remote network or using weaved on the PI.

http://www.weaved.com/in-action/weaved-iot-kit

The issue I have is that from time to time, a node may lock-up and stop communicating (often due to a noisy electrical environment). While it is not a common thing, I cannot afford to lose comms with the node, so I am after a way to either

1. have the node reboot at some specific time or some type of watchdog system on board to do this

2. a way to reboot the node remotely when I see it not responding anymore

Any suggestions, tips and pointers appreciated. If I had to change controller for this specific project I could consider that, but must have the remote access.

Setup

Raspberry PI
Serial Gateway
Moisture Detection Sensor
NRF24 Radio
Domoticz Controller
Weaved (http ssh access)

Thanks for the input all

I might put two sensors together and see what transpires to see if I can narrow things down a bit and see if it is specifically a sensor issue or the controller.

@BartE Thanks for that. My issue ended up being with the signal lead from the sensor to the arduino. A bad connector. Your advice on the pull-up resistor was very useful.

Thanks

Hi all,

Just looking for some help here. I have uploaded the soil moisture sensor sketch, but when I look on the serial port, it is just a constant stream of messages alternating as below. Eventually the system fails.

Even if if I disconnect the moisture sensor from the system it does the same thing, so not the sensor. If I upload a different sketch to the node (Dallas temp sensor for example) it does not have the issue, so I am thinking it is something in the moisture sensor sketch.

Any suggestions on what is happening?

Below are the messages that stream past in the serial monitor at high speed

send: 1-1-0-0 s=0,c=1,t=16,pt=2,l=2,sg=0,st=ok:1
1
send: 1-1-0-0 s=0,c=1,t=16,pt=2,l=2,sg=0,st=ok:0
0
send: 1-1-0-0 s=0,c=1,t=16,pt=2,l=2,sg=0,st=ok:1
1
send: 1-1-0-0 s=0,c=1,t=16,pt=2,l=2,sg=0,st=ok:0
0
send: 1-1-0-0 s=0,c=1,t=16,pt=2,l=2,sg=0,st=ok:1
1

This is the standard sketch i am using

/**

• 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
• Example sketch sending soil moisture alarm to controller
• http://www.mysensors.org/build/moisture
  */

#include <SPI.h>
#include <MySensor.h>

#define DIGITAL_INPUT_SOIL_SENSOR 3 // Digital input did you attach your soil sensor.
#define INTERRUPT DIGITAL_INPUT_SOIL_SENSOR-2 // Usually the interrupt = pin -2 (on uno/nano anyway)
#define CHILD_ID 0 // Id of the sensor child

MySensor gw;
MyMessage msg(CHILD_ID, V_TRIPPED);
int lastSoilValue = -1;

void setup()
{
gw.begin();

// Send the sketch version information to the gateway and Controller
gw.sendSketchInfo("Soil Moisture Sensor", "1.0");
// sets the soil sensor digital pin as input
pinMode(DIGITAL_INPUT_SOIL_SENSOR, INPUT);
// Register all sensors to gw (they will be created as child devices)
gw.present(CHILD_ID, S_MOTION);
}

void loop()
{
// Read digital soil value
int soilValue = digitalRead(DIGITAL_INPUT_SOIL_SENSOR); // 1 = Not triggered, 0 = In soil with water
if (soilValue != lastSoilValue) {
Serial.println(soilValue);
gw.send(msg.set(soilValue==0?1:0)); // Send the inverse to gw as tripped should be when no water in soil
lastSoilValue = soilValue;
}
// Power down the radio and arduino until digital input changes.
gw.sleep(INTERRUPT,CHANGE);
}

Hi all,

Not sure if this a domoticz or mysensor issue. Every once in a while I will get a random temp reading on my graph and I am not sure exactly how to go about tracking down the issue, so any advice appreciated. The sensor being used is a DS18B20 on a serial gateway to a PI. Normally if I lose radio connection the sensor data will flatline so the issue must be somewhere else. In this case it has dropped to zero degrees.

@kolaf I was wondering what you needed to do to get MQTT working with the MySensors and Domoticz. Can you point me in the right direction for that?

Thanks, I will watch out for conflicting node id's

I have two gateways (home & work) and I am wanting to swap some sensors back and forth between gateways.

Is there any issue in moving sensors between gateways?

Once the sensor ID is assigned by the first gateway, does it then keep that ID when moved to the second gateway or will the second gateway try and assign a new ID?

l was just wondering if anyone had a sketch for connecting a K type thermocouple to the mysensors network or could point me in the right direction?

I received a coupe today and want get them hooked up

http://www.ebay.com.au/itm/400798924042?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT

@m26872 . Yes, I have a couple of K Type thermocouples on the way to do a bit of testing with as well as I will have a requirement for some reasonably extreme temps in some applications, -196 to +150

Ok, Thanks. Will give that a try

@AWI Thanks for the reply. When I first setup the sensors I am sure i deleted those extra ones, but they seem to have come back again for some reason. Is there a way to permanently delete them?

Will Domoticz always combine the temp and humidity if they are from the one DT22 sensor? Would be good to report and graph them separately

Not sure if this is a Domoticz or MySensors question, but I seem to get a lot of duplicate sensors in Domoticz. Anyone seen this before and have an idea what it is about or how to stop it. ID's are the same

Hi all,

Just wondering what is the best option for a low power temperature sensor. I had read a few things where the DS18B20 was not the most power efficient way of doing things (could be wrong). Would be measuring around the 4 deg mark.

As it will be purely battery powered project, looking for the best low power option with reasonable accuracy/stability

Any info or just point me in the right direction

hi guys

thanks all for the responses. Tis all clear now and makes sense

@ch3b7 Thanks for that.

When reading through the API info, the 0,0,3,0,9 message relates to an internal type message, which I get. However I don't understanding why I seem to get it continually occurring on my serial port when I monitor it (every few minutes). However when I am running MYSController, the only internal message that comes up is when the gate way reboots?

Wondering why I would see the difference.

Serial Output

MYSController Output with only two internal messages

This is also something I have started playing with. Having node-red in the system seems like a powerful way to move and connect information around the place between the mysensor system and all sorts of interfaces.

It would be good to have an area where we could share the nodes and codes etc.

What code do you use for parsing the serial data into its different parts?

At the moment I have the mysensors serial gateway talking to domoticz directly (as standard) with the node-red serial node picking up serial data in parallel to then send off other places (influxdb, mqtt etc). At the moment I can grab the serial data, but no idea how to parse it out for useful sending on.

I have had a read through the general API info and I think I generally understand the message formats, but not sure why my system would always be sending the following string/payload and what it exactly means (think it is from the temp/humidity sensor reading.

0;0;3;0;9;read: 20-20-0;0;3;0;9;read: 20-20-0
s=1,c=1,t=0,pt=7,l=5,sg=0:5.0

The other message is OK which is from the straight temp sensor. That is easy to understand.

2;0;1;0;0;15.7

Hi all,

Just wondering if there are any options for connections of MySensors MQTT through to Domoticz.

Had a bit of a hunt around but could not see anything obvious or if something is being worked on at all

@jkandasa thanks for the reply. Will add in the issues section

Cheers

Looks very cool and straight forward. Nice work!

Wondering if there is a way to extract the logged sensor data for import into other packages/spreadsheets etc for further analysis?

@John

Happy to try the snapshots to get a feel for how things are developing and the direction headed

@Oitzu

Cool. Have had a little play with the demo system. I like the slider option on the Graph to allow a zoom in. Very functional and simple. What system/database is used to store the data an does it have limits?

@john @Oitzu Thanks for the suggestions. Will look over those controllers in a little more depth.

One of the other things I am keen to be able to do with the controller is drill down into the data in a fairly easy and straight forward manner to look at temperature variations, alarms etc so I shall see how those systems go.

Not sure if this is a straight forward question or not. I have played around a bit with Domoticz and OpenHAB which are great as controllers, but I also have an application where I have a couple of sites where I just want to have a simple network of sensors (mysensors) but with a basic/simple (idiot proof) interface for users to view, log and recall the data as required, maybe a few realtime alerts based on values. Happy to use a PI to serve out the info if required and most machines on the network are windows based.

With all the controller options available (or others not listed), is there one strategy that is particularly suited for this type of simple data presentation and logging?

I would like the core of the system to be local and not have to depend on an external connection to the www

Something robust that just works.

Any input appreciated

Thanks for all help everyone. Finally getting everything up and running generally. I got the system running and talking to OpenHAB initially with the MQTTGateway (1.5) and the instructions here for setting up items etc in openhab. So I can now see Temp and Humidity readings.

http://forum.mysensors.org/topic/303/mqtt-broker-gateway

It ended up pretty straight forward. With that MQTTGateway broker running, I could actually subscribe to it with MQTTSpy and see the data. Only issue was that the MQTTGateway only seems to allow one client connection at a time, so once I had OpenHAB connected I could no longer connect with MQTTSpy, but at least it all worked and I can get reading in OpenHAB.

What I then tried was to bridge my Mosquitto Broker to the MQTTGateway broker to make broker access a little more flexible.

OpenHAB <> Mosquitto <> MQTTGateway

I got them talking/bridged and the data feed made it through to OpenHAB, so all good.

Only question I now have is about subscribing with the Mosquitto Broker in bridge mode.

If I connect MQTTSpy to the Mosquitto Broker and create a catch-all subscribed topic as "#" I see all the readings coming from the MQTTGateway to Mosquitto/OpenHAB, all good. However if I use MQTTSpy and subscribe to a specific topic such as "MyMQTT/20/0/V_HUM" nothing shows in the feed, though that topic is shown under the "#" topic and OpenHAB is picking up the feed data just fine.

This subscription matches how the item is setup and also what I see in the "#" feed.

{mqtt="<[mysensor:MyMQTT/20/0/V_HUM:state:default]"}

Anyone have any suggestions why the direct subscription does not pickup the feed?

Cheers

This is my bridge setting in Mosquitto config

connection MMQTTtoSensor
address 192.168.0.175:1883
clientid MyMQTT
cleansession true
notifications true
topic #

@TD22057 Thanks for the reply. That would mean then the IRQ is not used with this setup then,

Hi all, I am about to try this as well as I have the same setup with the etehrnet shiled, but I don't really understand the wiring instructions. As the Ethernet shield is fixed on the board what does it mean by connecting MISO/SO to pin 12 and MOSI/SI to pin 11 etc?

Apologies if this is a silly question

Thanks guys.

It is all a little bit clearer now. Will do some playing around.

The problem I currently have is I don't seem to be able to get OpenHAB to publish to my Mosquito broker, but I think it is an OpenHAB issue.

Broker is running and I have the MQTT-spy subscribed to all topics "#"

My broker shows messages sent from the arduino (running MQTT_Basic sketch) as well as messages sent from the command line, but nothing from OpenHab. I have the installed the MQTT binding in OpenHab and enabled in the configuration file. Also setup the switch the way I believe to be correct, but noting sent.

Will quiz them on the openhab forum

@tomkxy thanks for the detailed reply. Will give it a go when I am back home. When testing the MQTTClientGateway, which you say is a Broker Client, then programs like MQTT-Spy would not be able to connect to it. You would really just be looking for the pub's on the Mosquitto to check functionality?? Is that the correct understanding?

With the original MQTTGateway, would be good at some point to find some way of connecting to and testing (mqtt-spy or mqtt.fx etc)

I will eventually work this stuff out!

Cheers

thanks @TD22057 & @tomkxy

So @tomkxy when you say I need to configure the ip and port from the broker, that would be the mosquito broker you are referring to not the arduino MQTT client gateway?

Is that correct?

Is there still a requirement to set the IP & port on the arduino gateway running the MQTT "client"

Fairly new to all of this and still trying to get my head around it.

Setting up for MQTT as my gateway and trying to understand it.

With MQTT running as the gateway, is it acting as a client or a broker? I have read a few conflicting posts.

I have mosquito also running on my system, so when I setup the MQTT sketch for the gateway, do I put in the mosquitto IP and port (the broker) or am I assigning the IP and port to the actual arduino gateway to set it up as a broker ?

I have tried setting up the sketch with an IP and port number as a broker, but cannot seem to connect to it using the testing clients like MQTT Spy and MQTT FX. Should I be able to use these software packages to connect?

Any guidance appreciated.

@hek

No worries, thanks for clarifying

looking forward to trying the new release.

One question, it mentions the new sensors, where would I find the "multimeter" sensor? Had a look but could not see anything

New sensors: RGB, RGBW, Color, Multimeter, HVAC, Sprinkler, Water leak, Sound, Vibration, Moisture

@jribera Been try to get this happening myself. Can you provide the sketch you ended up using to get this happening so I can try it. I know what all my codes are, just need to get a sketch happening to interface back to my controller (Domoticz Serial)

Cheers

I would also like to know if this is doable on the the Domoticz platform as well

I was also thinking an RTC would be needed and perhaps an little sd card for extra data storage at the sensor node. The issue still would seem to be getting the domoticz controller to properly manage the missed data when it does eventually come through. In the case of domoticz, it seems to just use the last read data and plot that. Might also start a thread on the domoticz site and see what thoughts they have on that side as well.

Thanks for all the input

So a case in point, the sensor connection and or gateway dropped out for a period and my graph flat-lined. Would be nice to get around this somehow with basic local sensor data storage, but seems not a simple as it sounds

hi fot

thanks for the reply. Would be a very handy feature to have.

Any posts or other forums that have a bit of info on how to start going about this type of thing? though I am guessing from what you are saying that a lot of the work would also have to be handled by the controller as well, which in my case is Domoticz.

Can a local sensor node log data if it is not able to communicate back to the gateway to send current reading?

I have a simple dallas temp sensor node and I am wondering if the sensor can log data in the event it cannot contact the gateway. Once the connection is back-up and running it then sends the backlog of data.

Tried a few experiments myself and it does appear to behave in this way, but wondering if this is an option?

Cheers

Bit of a newbie question.

I have my mysensors gateway talking to Domoticzc. I also have a lot of old 433 mhz switches and sockets around the place I want to use. Now I have been doing a lot of reading in the forums working out how to get my 433 mhz gear talking to domoticz via the gateway and a lot of the posts discuss learning the codes sent bu the 433 gear.

My question is, in domoticz, with the switches, they have a learning mode for the switch that listens to incomming signals. If everything is setup OK, can this function be used once basic connectivity is made with the 433 gear and the gateway? If you could point me to the best posts on the subject I will dig further.