Posts made by AffordableTech

Hi @pierrot10 and others,
Sorry, I was called away unexpectedly...

I've had no experience using nails other than testing the gyprock ones in the link I sent.

I think your idea of 9 pairs spread across the wall is excellent as the key data you seek is the moisture source and how it progress across the wall.

You can just connect the 9 sensors to one of those analog switch modules and the Feather and start logging data. You biggest problem will probably working out the distance between the 2 nails. Once it setup (in summer), you can make sure they all read the same value by a software 'calibration value' for each pair.

I'd also suggest putting a newer BMP680 device in the room, perhaps 3" to 6 " away from the wall, just to have a temp, humidity and barometric pressure. I don't know exactly what it my tell you, but one thing I have learned is 'data is like money', there is no such thing as too much! (especially when you only get one shot at it a year).

I think your chances of success look good as long as the distance between the two nails give you a sufficient data range.

Good luck, and I look forward to reading how it turns out.

Paul

@zboblamont maybe it was Trump asking the question (in disguise)?

Paul

@8667 while you are probably correct, the lack of info makes that an assumption. I chose to answer in detail, just in case it was a serious question and there may well be reasons why fixing is not an option at this stage.

Regardless, I hope the answer / method may be of later use to someone else with a 'similar' need to measure the moisture content of something other than soil.

But yes, I too will be keen to see if or when the OP comes back.

Paul

Hello @pierrot10,
Firstly, let's talk about normal ambient (outdoor) humidity for a moment, 100% means the air is saturated with the maximum moisture as it can hold.

In a normal hose, the humidity will typically be the same in every room, unless there is some special factor, e.g. the bathroom humidity will increase dramatically when someone takes a hot shower.

Next, let's think about a humidity sensor, it can only read the humidity in it's immediate (close) proximity.

Now, let's look at the wall in question, is it a normal wall in a normal house? This would be helpful to know, i.e. if it is a wall in an underground cellar (basement) it helps to explain why this particular wall is getting wet.

The fact that the wall is getting wet tells me the humidity in the immediate (close) proximity will almost certainly be 100% when wet and probably ambient 'room' humidity when not. This is where I believe your solution may be, and here is what I would suggest, assuming you want an alarm when the wall is in danger.

My Suggested Solution
I'd suggest you get two small humidity sensors and connect them both to an Arduino and make adjustments as needed in software so they read the same value (at your desk (workbench).

Note: One sensor is to be mounted in the wall and the other to be located in the room, 500mm to 1 meter distance away from the wall, so make your wires the necessary length before you calibrate the sensor readings.

Drill the smallest diameter hole in the wall to fit one sensor in. If the hole needs to be say 20mm diameter, make the hole 40mm deep (100% deeper). I would suggest you angle the hole 3 to 5 degrees so any excess moisture can drain out (and not damage sensor).

Insert one sensor all the way inside the hole, then cover the hole, but NOT airtight. Some examples: Find a plastic bottle cap the same (similar) diameter as the hole in the wall and drill lots of small holes in it. Another option would be to go to your hardware store and buy a small amount of "fiberglass fly screen' (mesh). Use two layers to make the mesh finer (smaller).

The Arduino Code

There are many ways to do this, but based on previous work with humidity sensors, here is what I would do.

a Lora radio will not give you the distance you need, so I would use an ESP8266 or ESP32 chip (with WiFi). The ESP8266 Node 1 would be ideal for this project and is very well priced. This will allow the device to upload the data to a cloud server, of which there are many free ones to select from (check out AdaFruit's I/O Cloud Service, from memory it offers nice graphic display of data etc. I support / recommend AdaFruit because the provide lots of free code and drivers to the hobby community. It's a nice way of saying thanks!

The WiFi device will also allow you to remotely connect, read the data, modify sensor calibration values etc and most importantly, you will be able to perform OTA (over the air) software updates.

*Create a 3 by 24 array of bytes for data storage.
*Every 60 minutes, take 5 readings from in-wall sensor, discard any obviously bad readings, and average the good values. Repeat the same for the in-room sensor.
*Record the hourly average for each sensor as well as the difference between to two (just for convenience), into the array of bytes, using one set of 3 bytes for each hour of the day.
*Upload the three hourly values to a cloud server, along with the date/time as required.
*At midnight (hour zero), just overwrite previous array data values.

Reasoning Behind Design
By placing the sensor deep in the wall and covering the hole a bit, this sensor will read the humidity in its immediate environment, but the holes are important to make sure water does not accumulate in the hole and damage the sensor or cause faulty readings.

By having a second sensor away from the wall, it will read the general room temperature. Be comparing the two values, you can raise an alarm when the in-wall sensor is greater than the in-room sensor by x%. This way, on cold damp winter nights, when the in-room sensor and in-wall sensor read say 93% and drop the next morning to say 70%, you know that 'normal. But I am sure over time, you will see the the difference between sensors will steadily increase as the wall accumulates more and more moisture.

Once you 'prove the system', you could have the Arduino turn on a heater, blowin(g) on the wall etc etc.

Possible Adjustments

• If during the first winter testing you find moisture collecting on the sensor PCB, increase the ventilation holes a bit at a time.

• If you find the value of the in-hole sensor is almost always the same as the in-room values (even when the wall is damp / wet), Roll up a narrow (10mm) strip of newspaper, but NOT too tight and put a pin through it to hold it together as a roll (i.e. decrease the ventilation flow, but do not block it completely). You just want a small 'roll' of newspaper to put in the hole close to the vent. This paper will act as a 'buffer' to isolate the in-hole sensor from the outside, maybe a small piece of sponge will do, but just make sure nothing touches the sensor.

I can't guarantee you this design will work, but it is how I would tackle the problem and think you will find it produce fairly useful data to make a decision with.

Good luck, and please post your progress as I'm sure others would like to know also.

Paul

@grumpazoid one thing I meant to add..

The way you propose, using a battery and regulator is the ideal path. Removing the LED is critical as the LED would probably use more power than everything else.

One thing you may not realise is the Arduino and motion sensor can run on as little as 1.8 volts, providing all regulators are removed and the battery starting voltage is no more than 3.3. If you use an alkaline battery, you can suck on those babies until they reach 1.8 volts, at which time they are pretty much empty. Whereas rechargeable lithium batteries have builtin 'over-discharge' protection which switches off the output a 3.[something] volts.

I suggest considering 2 by 'AA' cells in a holder, with the Arduino mounted on the back of the holder with double sided sticky tape, or my preference where size is important is to use one CR23 (3 Volt) battery (they are about 2/3 the height of one 'AA' ). Either option should give you over a year between replacement.

NOTE: On ALL MySensor nodes, make sure the antenna section of the (standard) RF2401 is not directly on top of anything metal. Where possible, let that antenna part overnang the battery pack for example. It's not critical, but could cost you 20% to 25% of your range IMHO, so I try to keep it clear wherever I can.

I've seen it argued that metal behind the antenna, can act as a 'ground plane' and actually boost range. I'm certainly not a radio expert, but even if that is true, it will make the antenna very directional, meaning signals to/from behind the 'ground plane' will be blocked. All I can say is I haven't had any range problems will any of my nodes, including some in another building.

Whatever battery arrangement you use, measure the voltage of a fresh set of batteries (in use), and make a note of the voltage when the node dies. This will then give you the useable voltage range which may be for example 1.83v to 3.12v. Once you know the usable range, you can then modify your code to calculate and send a very accurate "Battery Remaining %". In the meantime you can just guess the 'empty' voltage.

Paul

p.s. You don't have to wait a year, you can just put in a fairly 'empty' set of batteries just to see the point at which the node dies, if that makes sense.

@grumpazoid yes, you seem to be right on track.

One other point that may save you some grief, mount the motion sensor away from the RF2401 and gron the voltage dropping device, assuming it's a 'buck regulator' (which is more efficient).

Both the regular and the RF radio output high frequency noise which can cause false triggers by the notion sensor. But, be warned, distance is a double edge sword, the further away the motion sensor is (longer wires), the more prone it becomes to power supply noise. So just don't place the motion sensor right on top of the radio etc.

On the positive side, 'electrical noise' can be fixed with a capacitor. Try putting a 47uF capacitor on the motion sensor across the points where the positive and negative power wires connect. (Note the capacitor is polarity sensitive (look for the negative marking). If you still get false triggers, you could try increasing the capacitor to 470uf, but in my opinion, if 47 doesn't work there is another problem somewhere.

Also, from memory, those sensors need a fairly long warm up period before they stabilize, so you should get your code to ignore any readings initially. I think it's under a minute but do a google search for "HC-SR501 warm-up" to check.

You can simply sleep(xxx) in the startup loop, or ignore all triggers with a statement like "if (millis() > 30000)". The value returned by the millis() function is the number if milliseconds since startup, so you could only do a 'send' command if the milliseconds are greater then the warm up period.

Paul

I agree with the others, low cost sensors vary from one unit to another. For many, where they refer to "Accuracy", they often mean repeatable accuracy, which basically means if its calibration is out by say +5 degrees and they quote an 'accuracy' of plus/minus 1%, it will always read an extra 5 degrees plus or minus 1%.

As a result, I started paying extra for 'factory calibrated' devices, but as you have found, this appears to mean very little.

After purchasing and testing a LOT of devices and constantly being frustrated, I ended up building a test node with two each of three different sensors (6 in total) which I calibrated myself and used offsets to get them reading the same. That test node also computes and transmits average values also. Over a long period of time I found that an individual sensor will go out a bit, then return to match the others. A year later, I repeated the calibration tests and the avg value was spot on.

Now, whenever I build a new device, I build offsets into the software which I can send to the node (using MYSController) and they are stored in EEPROM. This allows me to occasionally check its value compared to my 'test rig', and correct any offsets without taking the unit apart or reburning the code.

My conclusion, after four years of using just about every reasonably priced ($2 to $12) device on the market, is that there is little difference between most of the units once you have set the correct offset. As a general rule, they all seem to drift occasionally and by similar amounts, but return again. Most importantly, by having a 'trusted' set of values to compare a new sensor to, I can recognise a faulty sensor very quickly, typical symptoms being they often need a larger than normal offset and the next day it's reading is significantly different again. At first, I tried adjusting the offset again and again, but now I toss them straight in the bin. If a new sensor (regardless of price) can stay in sync with my test rig for 48 hours, it will continue to be moderately accurate.

Cheers

Paul

Hi, Just a few comments that you may find useful. Because this is a battery powered device, I assume battery life is reasonably important and there are improvements you can make.

The IR Motion sensor you are using is actually a 3.3 volt device and has a regulator to drop the 5V input to 3.3v, so it's just a waste to use 5V only to drop it to 3.3v. Although I have not measured how much energy the regulator itself uses, but it may be more that the Motion Sensor itself which only draws 50 micro-amp (50 millionth's of an amp). The circuit for that device is available on the internet and you can actually bypass the regulator just by changing how one of the jumpers are setup, i.e. no soldering, or you will find posts here on how to remove the regulator (and a diode). Just look at the circuit, find the regulator and look at how it is connected to one of the jumpers and you should be able to work it out.

Another option is to try running the motion sensor (as it is) direct from the battery. The regulator is probably an LDO (low drop-out) meaning it will accept an input from 5V down to a little more than about 3.4 volts (as the battery drops).

If you are not already using sleep mode and interrupts, you should as it's possible to get the average power consumption to not much more than the battery's normal self discharge rate (shelf life). With that particular sensor, you should be able to achieve a fantastic battery life by putting the Arduino and radio to sleep and only waking when the motion sensor activates. You simply need to connect the motion sensor output to the Arduino pin 3 (which is an interrupt pin). There is a good example (with comments) about using interrupts in the MySensors examples folders, it's called something like "Binary Switch Interrupt". (I'm not at a computer with Arduino at the moment)

A well designed interrupt based node can easily run more than a year on a set of batteries. I have been running a node with Temp, Humidity, Pressure and digital Lux sensor reporting whenever any data changes, or after 5 minutes with no data changes. It's been running two months now and hasn't even dropped one hundredth of a volt, so far so good.

Good luck!

Paul

Hi @mfalkvidd,

Problem is, when your code can't compile because you are one (or several) bytes short of ram, nothing else matters.

As to readability, I assume you know about that rarely used compiler feature called 'comments'? I hear they use zero Arduino RAM and even less ROM memory. .

Ok, I'm just being cheeky, so don't flame me, it just seemed a good opportunity for a reminder to everybody. Point being we are all guilty of not using enough comments in our code.

You said you are worried about readability and maintainability - it's just like code backups, it's a problem only because we only worry about them 'after' a drive crash, or in the case of comments, two years later when we are trying to remember what the hell this weird code does.. THE REALITY: If we are really worried, we would add liberal comments and do regular backups - otherwise I say we're not really 'that' worried.

Cheers,

Paul

@strixx
BEFORE YOU USE analogRead()
You need to be aware that the MySensors core Ver 2.2 has code to support sensors reporting the chip VCC voltage. As I recall, this code is enabled by default and all readings of the analog port will return 65,535, -1 or hex FFFF, depending on the type of variable you read the value into regardless of what voltage is applied to the analog pin. MySensors has changed the 8266 configuration to read the chip VCC and ignore the analog input and I gather the MySensors coders decided to return 65,535 as an indicator.

You will need to do a search for "ESP analog read" or similar, to find the correct syntax of the special command to change the 8266 mode to re-enable reading of the analog input pin. Note: this analog mode command must be placed at the top of your script before any other functions.

DIFFERENT NodeMCU BOARDS
Please be aware the analog pin 'hardware' varies with different NodeMCU devices and you need to understand how the MySensors restricts how you can use this pin.

First, I have encountered three different 'NodeMcu Ver 1' boards. Traditionally the analog pin expects a range 0V to 1V max. Some docs state going over 1V can destroy the pin, others state it can tolerate 0V to 3.3V but the anagloRead() for voltages of 0V to 1V are as expected, but 1V to 3.3v returns the same value.

On the earlier boards I received, the analog pin of the PCB was wired direct to the 8266 chip (in the metal can) and not connected to anything else.

About a year ago, the boards I received had additional circuitry to protect the analog pin from excess voltage.

More recently I have received a batch of 20 boards which returned values lower than expected? Suspecting a board problem, I traced the circuit and confirmed there is a voltage divider which scales an input of 0V to 3.3V to become 0V to 1V at the actual 8266 chip. I.e. these boards requiire a 0V to 3.3V input on the analog pin. If you code reads values about one third of what you expeted, you may have a 0V to 3.3V board.

VALUES NOT CONSISTENT
As a final tip, I have noticed that no two NodeMCU's return the same value from the analog port. I.e. five 'identical' boards from the same batch will return slightly different values, unlike the Arduino devices, which I find all return accurate readings.

My assumption is, this is due to the 8266 using a different analog to digital conversion method, and the errors are 'possibly' due to some capacitive effect. The differences or minimal, can can be confusing and may need special attention if you are checking for a 'specific' value. Hint: always code analogRead comparisons to look for different 'ranges' of values, rather than "if analogRead(A0) == 350", because the value you get today could be different tomorrow or next week. This is good practice because the value read will vary slightly as your project's supply voltage changes due to changes in load (e.g. several LEDs turned on vs off), or even if your battery or even mains voltage is unstable.

Hope this saves someone banging their head against a brick wall for hours like I did.

Paul

Hi all,
I trust this post does not breach forum etiquette...

In four to eight weeks, we are launching a KickStart campaign for a specific new product and want to hear from individuals with suitable skills to take responsibility for converting our schematics into assembled prototype PCBs, assuming our campaign is successful. While you being Australia based would be convenient, we are open to hearing from anyone anywhere. Although this is our first KickStart campaign, we have a number of excellent projects ready to follow. So while this may be a relatively small project, everyone on our team intends for this to launch a full time operation for years to come. Therefor this may be an ideal opportunity for you to make the change from 'good hobbyist' to a professional career.

As a guide, our project is based around [A] a central Arduino+ESP communications controller with a variety of serial & I2C sensors. Plus [B] five smaller modules, all similar, but with small variations, being Arduino 328p modules designed to all have a common base of temp, humidity and 2 gp i/o, with 'some variation' plus option to support either RF24 or RF69 radios. These 'bare bones' modules will need to be powered by external 5v OR an optional battery. Everything we propose should be familiar to anyone who has MySensors design experience.

We anticipate up to three prototype cycles before committing to the final production run. If you have the experience to take responsibility for converting our schematics into PCB ready art and/or prototype assembly, I'd love to hear from you, please email sensors@ptit.com.au with a brief background to start the conversation.

Cheers,

Paul

TO ALL IN THIS TOPIC
I though it was appropriate I acknowledge that I now realise I misunderstood there was anti-ESP sentiment here, its more a case of just too busy to jump onto every idea mentioned. Like a few others who spoke to me, I failed to make an official request, therefore until I did and was told err.. 'where to go', I should not have assumed anything.

There was never any ill intention, just frustration as I probably love MySensors as much as anybody else here. Like everyone, I have real time restraints, but if I can conribute, I will.

My thanks to everyone who has taken the time to comment.

Paul

Thanks @scalz,
A very helpful an welcoming reply.

Im no great fan of ESP, particularly becuse of its lack of i/o but it seems ideal for a simple node wirh one switch or I2C sensir.

Here (in Australia) Adafruit and Spark fun products are 200% to 300% higher than US price. I get stuff direct from them when I need qty, but fir 1 or 2 boards, the shipping is just too expensive. So yes, an Adafruit or Spark 5x here is $65.

Anyhow, I will be checking out AliExpress - thanks!

If I can contribute, I will, I'm so happy with my HA, I want to see everyone experiencing what a truly 'smart home' is about. Hardware vendors push their own idea of smart home, but many dont want to share data with competitors products. Sharing data etc is what makes o.s. projects so great. If I can create, or help to create an ethernet based nodes, that would be fantastic as I know how good it is if a simple MySensors temp sensor could switch on a heater 'direct' without having to rely on a controller.
The reason u think this is good, is because little micro processors just seem to do their job year after year, without maintenance, as long as you feed them 'volts'. Complex controllers just are not as reliable.
My water heater is controlled by Arduino which saves me $1,200 pa at least. My hot water now costs 35 cents a day (because it knows my patterns), whereas it usdd to cost $2 to $3 per day keeping it at 55 deg c (thermostats often not adjustable in Oz).

I just need 40 deg most of the day (for hand wash etc) and a 'boost' to 55 deg just before my shower/bath. If I want a shower at an 'unusual' time, I have a 'boost' button on my phone or PC and 15 min later water is HOT!. $1200+ for the occasional inconvenience of waiting 15 min is fine 'smart' by me.

Cheers,

Paul....

@marceloaqno ppp
Thanks for the link, I really appreciate the constructive attitude. It might just be what I need to take the plunge and dive in...

I'll have a look and get back to you.

Paul

@kimot said in Would You Like Support For ESP8266 'Nodes'?:

And now have you got network, where RF nodes can directly communicate with RS485 nodes without controller?
I think no.

Where did you read that? I can't imagine anyone here making a statement like that. Certainly nobody has said that in this topic.

@scalz said in Would You Like Support For ESP8266 'Nodes'?:

which post was it ??

The post just before mine: https://forum.mysensors.org/topic/6935/esp8266-as-mysensors-nodes-instead-of-arduino-nrf24l01/4

when you say people use espeasy because esp nodes not available in mysensors (in your other post)

That's news to me, no idea where I stated that? I can only recall mentioning EspEasy when I stated a MySensors user wanting ESP nodes was told to try EspEasy (read it for yourself in the link above). Somewhere I did say the difficulty of having to use the MQTT workaround and having to setup a computer with Mosquito was causing people to abandon MySensors, which I know to be a fact and can substantiate. Personally, I can't see any reason why someone would use EspEasy, and I'd certainly discourage anyone considering it.

Regarding the AliExpress suggestion, I appreciate the tip. Not understanding the differences between the various 5x, I'm reluctant to buy something without knowing it's suitable for MySensors. The only device that I've seen that I could confirm would run MySensors core was the RedBear board and another $69 module on eBay. If you have a specific AliExpress chip number or module reference, I'd appreciate that.

Cheers,

Paul

@gohan

I understand limited resources all too well, I guess because ESP nodes was something I started chasing a couple years ago when the chip first became available, other forum users requesting the same stood out to me and the story was always the same use MQTT and more recently go try something else (which I read as 'Go Away!!'). A few months ago I attended a meeting at computer club in a different state and the topic of discussion was 'how can we make MySensors nodes without adding a radio'. However, looking back now, I realise I never made 'feature request' simply because I perceived a lack of interest when I saw others being told no.. no.. no.., I now wonder how many others gave up without asking formally? Of cause I don't know what makes 'enough interest' and I agree, there has to be sufficient demand.

As mentioned in another post, I seriously looked into the code with the view of writing it myself, but I could see the time needed to understand the 'internal layout and concepts' sufficiently, to implement a new transport without breaking any existing code, would be far greater than the time to write the actual routines required, and just too much for me to take on. I'm really passionate about MySensors and that's why it bothers me to hear others frustrated with it and realising I may have to start over with a different solution or (more likely) start from scratch and 'grow' my own node software to get what I need.

This afternoon I came up with an idea how I might be able to achieve what I want, without having to modify the core code. I'll be looking further into that tomorrow and will get back to you if I still think my idea is possible.

Regards,

Paul

@gohan
I watched man go to the moon when we hardly had calculators, so I know very well "anything is possible", but what's 'practical' is a very different matter. My objectives are 'results' based and not tied to any particular brand or technology. If my current traffic is causing problems, I have no interest in patching it up or work-around (as I think is obvious). If I'm putting more data into the transport that it can handle, I see only two 'proper' solutions, less data or a bigger pipe. Anything else would be short-sighted in my opinion, I subscribe to the 'do it once, do it right school' of thought, but I understand everybody tackles problems their own way.

My confusion was over the future direction of MySensors and I believe that's been answered very clearly. I misunderstood the focus of MySensors to be for open and effective home automation, and that's why I couldn't understand why people keen on the ESP8266 were told to go somewhere else, but now that you have told me the focus is primarily on RF and RS485, I understand and realise my mistake.

While I feel focusing primarily on one particular transport may prove detrimental for the future of MySensors, that's simply my opinion based my inability to appreciate the value of specialising on RF24/69 etc, worth no more or less than any other opinion.

So please understand, I'm not having a go at you, I was confused by the anti ESP8266 sentiment, but that was when I didn't realise I was in an 'RF24 Shop' so to speak. If I was selling RF24 and you came in promoting ESP, I would have told you to go elsewhere, so it was my misunderstanding.

Thanks for taking the time to respond and clarify,

Paul

@yveaux said in Would You Like Support For ESP8266 'Nodes'?:

I don't want to hijack your thread

Nagh, I appreciate all opinions, that what I'm here for.

I agree about the MQTT flexibility, and normally I would be the 1st one to insist on going with an established standard, but MQTT flexibility comes at the expense of bandwidth efficiency. As you pointed out, its for low volume messaging, and when I did some projected bandwidth calculations three years ago, and the numbers scared me off MQTT. Besides that, I think the underlying architecture of MySensors protocol is simply brilliant, its the perfect balance between flexibility and efficiency. As far as I know its been able to handle every requirement that has been asked of it over the years, and while it's been expanded. the basic protocol remains the same.

My power monitoring node currently transmits four channels of two floats (Current Watts and Cumulitive kWHr units) every ten seconds, and I'm about to increase that to eight channels. Add to that reasonably frequent security system status reports from eleven zone sensors, and about eight temperature/humidity/light type sensors and the traffic volume is already getting pretty high. During the night, for health reasons, I want to monitor my pulse, blood pressure and oxygen levels for real time data collection, which I would like to pass through the MySensors network simply because its all automatically logged, the data is automatically backed up etc, otherwise I'd have to duplicate those facilities for the medical data, so it makes sense to me.

While I'm unable to look at the actual RF data, just looking at the serial debug data, I can see there are already missing readings (collisions?)from my power monitor. If I increase it to eight power channels, I believe the RF network will be oversaturated. So I can't even think about the medical data, but an ethernet transport option would solve the current needs and cater for some future growth.

I've been told "the focus of MySensors is on RF and RS-485 communications", whereas I always thought MySensors was about an 'open and practical Home Automation', rather than one particular technology. Over the years I've detected an anti-ethernet / anti ESP sentiment in the forum for some reason. The whole reason I brought up this subject was after reading yet another post where a newbie wanting to use the ESP8266 without an RF device was simply told to go elsewhere. If that's the official view, then I'm concerned for the future of MySensors as I believe the current RF technology isn't able to meet the current user's expectations, much the future needs as the 'connected home' becomes a reality (for more than the technical oriented). All my friends are asking me about home automation, and I think when the latest generation of smart appliances hit the market, home automation will take off.

So, 'having been told', my choice now is do I create my own quick and dirty ethernet node transport, which will mean I will no longer be running a standard MySensors release and 'my version' will most probably fall behind, or do I go back to square one and look for a product / protocol that will cater for the future? It's going to be a difficult choice, and although I think ethernet will 'have to be incorporated' eventually, my needs for more bandwidth mean I have to find a solution now rather that in a year or two.

Regards,

Paul

Hi @gohan ,

Yes, I really like the 5x Bluetooth devices, particularly the beacon aspects, but until the prices drop a fair bit, they will be out of my 'affordable' range for general nodes.

Paul

@kimot said in Would You Like Support For ESP8266 'Nodes'?:

I think, better is, when each node with ESP8266 send messages directly to controller and controller to this node ( on its IP ).

Yes, I've had to do that for a couple of ESP8266 nodes I added recently, but the problem with that work-around is that those nodes are not really part of the network. They are 'isolated' because they bypass the gateway and cannot talk / interact with other nodes, so you no longer have an 'integrated home automation network' and it can quickly become a 'disjointed collection of random nodes'.

A lot of thought was put into the design of my system so that many of my nodes communicate direct with each other; if nodes have to depend on the controller to do their job, the system doesn't work if the controller is temporarily off-line. For example, every minute, my power monitoring node transmits total kWHr usage direct to the node in my large display panel, which displays my total power bill $'s so far this month. Most of my room lights are PIR controlled, so my outside store-room node has a PIR sensor and light relay (with manual switch also), but the PIR 'node' is smart enough to trigger a warning inside, if the PIR detects movement when my 'network' knows I'm in the house - my 'nodes' are smart enough to know which room I was last detected in, and I can't be in two places at the same time, nor can I be magically transported (yet) from one room to a non-adjacent room. So if I'm in the bathroom, and the front door opens or movement is detected in 'non adjacent' room, something is really wrong and a message 'beep twice' is sent direct to my internal siren node to alert me (unless I've told the network I have guests of cause). It's the little 'smarts' in each node that make my home automation system so personal and beneficial, that's why I am dead against 'isolated' dumb nodes. Having a PIR node send a message to the controller, then the controller send a message to the light 'relay' is dumb, the PIR node needs to talk direct to its associated relay node, which also receives regular updates, 'direct' from my outside LUX light sensor, so the 'relay node' is smart enough to know if it is appropriate to turn the light on or not.

Some people may say the controller should do this, and yes, my controller has various rules, but I prefer to add 'some' basic intelligence to the nodes so they are not dependant on the controller, simply because all my nodes are powered by a central solar charged 12V battery store, or have their own battery. However, my controller is a Windows machine because I wanted a reasonably powerful controller for data logging, statistical data, and graphs etc, so its powered from the mains. My automation/security system can function 'as normal' for over 24 hours without the controller or mains power. Each node is capable of doing its job and buffering its data while the controller is off-line, e.g. a 240V (or 12V) light will still come on when I walk into a room etc. This means I don't have to worry about my controller being off-line for maintenance, or a blackout etc, no loss of functionality or data.

Hopefully, you will see why I don't like 'isolated' nodes or 'work-arounds' that cannot be fully integrated, as the whole purpose of home automation is to integrate devices in the home.

Regards,

Paul

Hi @gohan,

I agree with you, there are many solutions to my 'node in the car' example, I can come up with all sorts of ways around the problem, but none will ever be as good as having a fully integrated node. My point is that users shouldn't have to resort to implementing work-arounds. If we were talking about some obscure requirement, I could understand, but the lack of native Ethernet access by nodes is something that has come up from users in the forum many times.

I've used MySensors as a teaching aide and several times I've had to try and explain to a new user who sees his gateway is connected to ethernet, and naturally expects his wifi node to talk to it, and just can't understand (believe) he has to setup a complete MQTT server. Several of those have abandoned MySensors and taken up alternate solutions which I know are inferior, but 'appear' better to newbies during the initial learning curve.

What I'm trying to establish by my post is a straight answer to the likelihood of an Ethernet 'node transport' being implemented in MySensors. Adding MQTT to my controller is no big deal, but I would prefer to see MySensors enhanced because I firmly believe it is the most flexible and reliable HA protocol. Based on what I see, there appears to be no interest in implementing it within the main core of MySensors developers, but rather than assume, I'd prefer to ask.

I chose not to use MQTT from the beginning, having decades experience with it and seeing the problems caused by its bandwidth inefficiency. The last thing I want to do, at a time when data is growing exponentially, is bog my network down with MQTT on all my new nodes.

isRegards,

Paul

Hi @gohan and others,

Thanks for your comments, here is further clarification on my particular config / needs...

Firstly, I appreciate the reminder about the new BlueTooth modules, I'd forgotten about them to be honest. However, at the current price of AUD$69 per node vs AUD$6 for an ESP, the ESP wins, unless its battery powered and the task requires so much on-air time that a battery powered ESP device is impractical, then the $69 price could be justified. In time I;m sure the price will come down, but I think BlueTooth will always be more expensive that WiFi.

I wrote my own 'controller' (an extension of my older custom security system) and decided to go with MySensors because its data strings / protocol are very flexible and efficient, and saw no sense having the nodes and the controller convert an efficient protocol to and from MQTT for transmission, so the controller parses and generates MySensors formatted data.

In the beginning, I had a dozen nodes transmitting via RF to an Ethernet gateway, but after the ESP devices came onto the market, I've been wanting to use them, but if you have to add a radio to each one, I may as well use and Arduino. The problem being, MySensors 'sensor nodes' can only communicate via RS232 or RF in its 'native' data format. To communicate over Ethernet, the data must be in MQTT packets, then you have to setup an MQTT server somewhere etc, and data has to be converted back and forth between the 'native' format and MQTT. Add to that, the MQTT 'bits' are another source of potential problems, degrading the reliability of the MySensors network, which is otherwise very reliable. If I'm going to add another piece of hardware/software to the process, it should offer some benefits, rather than just being a 'necessary evil', which is how I see MQTT when applied to a MySensors network. This has been a critical shortcoming of MySensors for a while now...

A Very Typical Example:
*I want a MySensors node in my car that automatically arms and disarms my security system (and switches lights etc) when I leave and return. I tried to do it, but RF24 and BlueTooth were unreliable due to the distance and metal in the car, whereas, I have great WiFi access where its parked.

To achieve my goal, I'll need a battery powered, weatherproof repeater node outside, or at best, an ESP in the car, with a matching 'ESP with RF24', in the house and write custom code for them to communicate with each other, then the inside ESP will transmit a message to the MySensors network. Like so many other things, its 'possible', but a painless and totally unnecessary 'kludge'. Why shouldn't I be able to simply flash an ESP NodeMCU with code for a 'switch node' and stick it in my car - job done - it then talks direct to my MySensors gateway? Yes, I know, an MQTT node, plus a Raspberry Pi, plus Mosquito, blah blah... This isn't the eighty's, that's the sort of thing I had to do back then.*

Gateways use an Ethernet transport, so the code is all there, but its setup as a 'gateway transport' and not a 'node transport'. It seems such a waste for nodes to communicate on any transport other than RF, the really good MySensors protocol / packet structure has to be translated into a much less efficient protocol, and back again. Why shouldn't nodes be able to at least talk to the gateway over Ethernet? And, when you consider part of the brilliant design of MySensors is that each node can act as a forwarder, an 'Ethernet node transport' would allow inter node traffic, greatly improving the range.

Suddenly, a small groups of nodes in one location could interact with nodes in another location anywhere (over a secure TCP/IP link). My home controller could then receive notifications from sensors at the office monitoring vital equipment. Likewise, when I 'arm' my home system by clicking the 'Off To The Office' button on my controller, the office MySensors network would turn on power to the coffee machine, so my hot morning cuppa is ready when I get there. Yes this 'is possible' now, but it's not 'native' to MySensors and requires custom work-arounds, often different for each person, depending on their particular setup.

The whole purpose of MySensors / Home Automation is to make life easier, my home system is pretty helpful now, thanks to the very reliable MySensors project. For example, I tap a 'Bath' button on my controller (or phone) and the bathroom towel warmer is turned on, and depending on the current temp, the room heater may be turned on as well, and finally, the water heater thermostat is given a 10 min nudge to bring the water to 'piping hot', rather than normal 'hot' for routine hand washing etc. (that little water heater 'smart' saves me enough each year on my power bill, to pay for all my home automation equipment costs).

Reading through the forum from the beginning, I've see many users stumble over why they have have to add an MQTT client, then setup something called a pie with mosquitoes? Likewise, users keep asking why they have to add a radio to an ESP, when the ESP and the gateway both already 'talk' Ethernet? It's just such an obvious 'hole' in the MySensors transport.

I feel the lack of Ethernet on nodes is truly crippling MySensors, adding an Ethernet 'node transport' would open up so many possibilities, that currently require each individual to kludge together their own solution, you just select MY_RADIO_WIFI and presto! Those that don't like exposing their HA to WiFi, simply don't have to, but I'm willing to bet it would become very popular if enabled, particular with newcomers.

My apologies for the length of this post, but I feel strongly about this and hope I've explained why.

Regards,

Paul

By ESP8266 nodes, I mean the ability to add ESP8266 'Sensor Nodes' that communicate to an Ethernet Gateway over WiFi, i.e. you don't have to have an RF radio on every node, as devices like the NodeMCU could use WiFi to transmit the sensor data to your WiFi Gateway.

It can be argued that you can do this now, but that work-around means having one additional gateway for every WiFi Sensor Node, which many controllers will not support.

For newbies, this means they can create and test a small MySensors network just by flashing the 'ESP8266 Gateway' sketch, plus one or more 'sensor sketches' onto devices like NodeMCU. I.e, no wiring radios or anything, just as long as you can plug in a USB port.

Many thanks,

Paul

@rejoe2 said in ESP8266 as MySensors nodes instead of Arduino + nRF24L01:

I personally do not like to mesh up Home-automation things with WiFi

While I understand your personal preference not to mesh Home Automation with WiFi, I've seen so many people seeking to use the ESP8266 as a node, without adding an RF device. I.e. you prefer not to, but many others (including myself) would love to have the option.

While there are 'work-arounds' to add a sensor to an ESPGateway, it's a very impractical solution if you want to have many WiFi nodes. I believe MySensors is the most complete and functional project of this type, but the lack of this feature is forcing people to use other projects like EspEasy as recommended by @ejoe2.

I've been delving into the MySensors code and the only issue I find is the need for a 'WiFi Transport' to be added to the existing RF radio choices e.g. MY_RADIO_WIFI. All the low level transport code is already written and used in the gateway transport, it just needs to be re-configured as a node transport as I see it? I have considered trying to implement it myself, but it needs a far greater knowledge of the MySensors core than I have, to implement it without breaking other transports etc.

Reading through this forum, this is something that has been sought after since the ESP8266 first appeared and I think would greatly enhance the popularity of MySensors as it would make it so easy for the novice to get a MySensors network up an running.

A typical 'starting' network of one ESP8266 Gateway, plus a few ESP8266 sensor nodes would just require flashing a few NodeMCU's and you are in business, no messing around with proto-boards, wiring radios, adding capacitors etc, which has frustrated and/or put off so many newbies before they even started. The dreaded 'wiring' would then be as simple as plugging in USB cables, opening up this very 'practical hobby' to a lot more people. you might even call it 'Plug and Play' (Jeesh.. I might patent that term ).

This would be a great way to introduce non technical users to the world of micro-processors, and Arduino boards would then be a far less scary proposition.

I'd appreciate some form of 'official' feedback as I feel I am currently at crossroads because I have a a pressing need for multiple WiFi nodes and would like to find out if there is no intention of marrying WiFi into the MySensor network.

Many thanks,

Paul

Hi All,
On a NodeMCU Ver1, I was having problems with analogRead(A0) returning 65535 no matter what voltage I applied to the ADC pin?

In researching the cause, I discovered that having MY_DEBUG and/or MY_SPECIAL_DEBUG defined causes the ADC_MODE to be configured by MySensors to read the CPU VCC and thus AnalogRead(A0) returns 65535 as a 'reminder' that the ADC port is not available, Fair enough....

However, in my reading I noted that for the ESP8266 to read VCC correctly, the ADC pin must remain unconnected (floating). Here is where I see a potential MySensors problem, all the latest NodeMCU Ver 1 boards that I have been receiving have a resistor divider, making the ADC input range 0 to 3.3 Volts, therefore the MySensors VCC reading will not be reliable on these boards and there is no config setting etc that can resolve this.

I've made this post to draw attention to this as I've not seen it addressed anywhere before (despite a full day's researching the issue (see references below).

Perhaps one of the ArduinoESP8266 core developers can shed more light on this.

Regards,

Paul

Background Reading:

Bug Issues: #338 #575 #695 #696 #2672 #3168 #4009

https://forum.mysensors.org/topic/5547/wemos-d1-mini-esp8266-mysensors-and-analog-a0/6

Hi All,

I'm currently upgrading to MySensors 2.0.0 and it would make sense to change over to the MYSBootloader as I upgrade each node. (I'd like to be able to use the remote re-boot command from MYSController).

I have been reading about the MYSBootloader and have some questions . . .

Q1 - My nodes are a mixture of Pro-Micro's, Leonardo's, Mega 2560's and the odd UNO. From what I can see, the MYSbootloader.hex file is for the Mega328p, is this correct, or can the same bootloader be adjusted (fuse settings etc) for others like the Leonardo processor?

Q2 - One post I read seemed to imply that to use the remote reboot feature you needed 'either' the MYSBootloader OR OptiBoot. In the OptiBoot readme, it doesn't mention reboot as a feature, so I am wondering if it really does support reboot - can anyone please confirm?

Many thanks,

Paul

Hi,

Yes, I use a low cost (10 cent) Light Dependent Resistor (LDR) to measure ambient light levels. The wiring is quite simple, one end of the LDR to ground and the other wire connects to a 10k Ohm resistor. The other end of the 10k resistor goes to +5 or +3 (whichever you are using). The junction of the LDR and 10k goes to an analog pin on the Arduino.

The sensitivity is quite good, covering the full spectrum from total darkness to bright sunlight. With a bit of observation I was able to determine 'value ranges' to display in my home automation as "Total Darkness", "Moonlight", "Bright Moonlight", "Dusk/Dawn", "Gloomy", "Overcast", "Bright" and "Very Bright". If you read it often enough, you can detect a dip in the value as a cloud passes over. Other motion sensor nodes (in bath, kitchen and bedroom) send read requests to an indoor LDR node every 15 minutes to know if its dark enough to turn on that room's light when motion is detected. I never have to turn an lights on or off anymore. An external motion sensor is used to detect someone approaching the front door and turns on a light and sounds a small beeper inside, negating the need for a doorbell.

I also use one with my TV and computer screen to detect when the TV and/or my PC screen is on. This data is used to record the amount of time I spend watching TV or at my PC. The LDR is mounted in a small, 7mm black plastic cap like those used to protect the end of round tubing and is pointed towards the screen but shielded from ambient and overhead lights. It's simple, cheap and very effective.

You will find ready to use code for an LDR based node in the NodeManager library (link below).

Refer: https://github.com/mysensors/NodeManager

Hope the above helps...

Paul

@Vladimir-Dobrikov

Have you adjusted the sensitivity? All of mine (10) arrived set to almost maximum sensitivity and I had false triggers in an empty room, however once I adjusted the sensitivity a low as I could, yet detect a person, they have been 100% reliable.

NOTE: These devices need to warm up, so I recommend leaving them powered up for 30 minutes before you attempt to adjust them.

Hope that helps,

Paul

Hello @dbemowsk
I don't have the specs in front of me at the moment, but the versions of this device I have (with circuit diagram) look the same and operate internally on 3.3v and have an LDO 3v3 regulator, enabling them to run off 5v+. I think you can see it it the large picture, under letters VCC (in red), it's marked "7133-1#". @Vladimir-Dobrikov is correctly powering it by providing 3.3V to pin 3 of jumper block 1, this bypasses the regulator, providing your 3.3v direct to the circuitry (on mine at least).

Refer: http://www.electrodragon.com/w/PIR_sensor#PIR_sensor_Schematic

The wiring @Vladimir-Dobrikov used looks the same as mine, i.e. the jumper and power to the pin in the upper right of the photo.

In my case, I use them to turn on several different room lights when someone enters and have not noticed any false triggers once I adjusted the sensitivity down a bit. Great value and low power - fantastic devices!!!

Paul

Hi @Vladimir-Dobrikov

A simple solution you can use is to power the LDR Sensor board (shown) from an output pin on the Arduino, turning the pin/power on briefly while you take a light sample. (An arduino pin can drive 20ma safely from memory).

For example, if you sample the light level for 10ms (0.01 sec), every 10 seconds (or 1 sec etc), your average power requirements (for the light sensor) will drop from 1.1ma to 0.00011 if I've done my maths right.

This is assuming you don't need to 'instantly' know every little change in light level. If you are recording general ambient light levels, having an interrupt for every minor change could generate excessive interrupts and data transmissions, consuming heaps of power for the RF transmission.

In my system, I measure ambient light with a 10 cent LDR and resistor, and UV levels with a UV sensor. I started sampling every 10 seconds during initial tests, but now I only wake the Arduino once a minute, take a sample and ONLY transmit data if either has changed or 15 minutes has passed.

By doing this, my light sensor module has been running 18 months with a small lithium battery, charged by a small solar panel. I checked it a few weeks ago and found the solar cell covered in cob-webs and dust etc, but it was still charging fine.

I would strongly suggest you check out https://github.com/mysensors/NodeManager as it will give you the following benefits:

• Has templates for LDR, Temp, Hum & Motion sensors.
• Looks after power management sleeping the Arduino
• Can manage turning your LDR on/off as required.
• Report current battery level.

Regards,

Paul

Hi @tekka ,

As stated, "All nodes have been running fine for two years" and were/are wired as per MySensors web wiring instructions. If I upload sketches again from my PC with MySensors 1.5 and Arduino 1.65, they init fine and work reliable as before (without any changes to wiring).

When you say "describe your HW setup", I'm not quite sure what your require? Do you need the specific configuration/wiring of the various eleven nodes, or are your referring to the development PC which the Arduino IDE is running on?

As all eleven nodes work fine when sketches are compiled with MySensors 1.5 using IDE 1.65, I'll assume you need the PC hardware config.

It's a Dell Vestro, running Win 10 - 64 bit, with 4 Gig memory. I can upload a detailed SystemInfo report if you need more info, please let me know.

As mentioned, I installed latest Arduino (1.8.2) and MySensors 2.1.1 library onto a new (virgin) laptop and got the same errors as that config produced on my main development PC.

My understanding is the wiring is the same for MySensors 1.5 and 2.x.x, is this1 incorrect?

I'm going to return the laptop to factory state with the recovery DVD and try d/loading latest 'development' branch and see if that helps.

Thanks,

Paul

Thanks @blacey, my Arduino IDE is 1.8.2 and AVR Boards is 1.6.18

I will try downgading one or two versions and see how it goes. Failing that, I will try a fresh install of everything again.

Thanks,

Paul

I'm Having The Identical Problem Too....

I upgraded my gateway (ESP8266) ok and was communicating ok with my ver 1.5 sensors.

However, all eleven sensor nodes produce the dreaded "!TSM:INIT:TSP FAIL".

My sensor nodes are a mix of Arduino 2011, Pro, Pro-Mini (3.3v and 5v). The RF24's are 4 by Sparkfun, 3 by quality radios with SMA antennas and the rest are low cost RF24's. All nodes have been running fine for two years.

Suspecting a software issue, I setup Arduino on a new laptop, installed the latest Ver 2 MySensors library and tried compiling and uploading several examples from the new library folder. This clean install, plus using library examples eliminated software / configuration issues, so I looked into the hardware...

As for power issues, three of my nodes run on 5 Amp Lipo batteries dropped to 3.3v via a 2 Amp on EACH node. I had 4.7 uf caps on them, and have now tried 47uf, 100uf and 220uf caps, but no change.

For the record, I have made nodes by selecting all 'the best bits' to produce two nodes of the best combination of radios, cpu's and power supply, but the error persists.

My key point is:
Every comment I have found re this problem indicates a power issue, but having three nodes each having their own solid 2 Amp, clean power supply, I must conclude there is another problem causing this error.

Would appreciate any advice...

Thanks,

Paul

A Short Followup

I've had this binding running 24x7 for a week or more and it has been faultless! - Thank You!

For the newbie attempting to get OpenHab up and running, this is the answer, the only answer! It's so clean and simple, download OpenHab (1.8) and this binding and run.

Cheers,

Paul

@m26872 ,

I'm sure many individuals will be wondering where the 'standard temporary' fuse fits into your chart of fuse types.

Of cause, by 'standard temporary', I refer to the ever reliable nail, often called the 'no blow' here in Oz.

Paul

What a fantastic arduino project - I love it, however...
This Project is Crying Out For Another Feature

This really needs an SD card with WAV player module (and small amplifier). At your normal 'Wake Up' time, it plays a couple rip-roaring 'cock-a-doodle-doooo' calls. On the hour there could be misc clucking and scratching sounds etc, except when the rooster is sleeping of cause. All audio accompanied by the rooster turning back and forth, if the speaker is mounted in the rooster, the sound would change as it echoed off other objects in the room.

This project has the potential for kit production, I for one would purchase a kit...

But mine would be a wall mounted 'corrugated iron coop', with the rooster popping out hourly as two big old barn doors fly open... An Aussie answer to the Swiss cuckoo's!

Paul

Hi all,

I'm currently running Ver 1.6.5 with an ESP8266 gateway {ethernet} to OpenHab 2. What I'd like to do is ADD an MQTT gateway so that I can transmit all my sensor data to OpenHab via ethernet and simultaneously to a remote MQTT monitoring app.

The obvious answer is to simply convert to an MQTT gateway only, but would mean many hours (and headaches) fiddling around with OpenHab conversion scripts etc. I never want to do that again!!!

Many thanks,

Paul

Hi @172pilot

I'm fairly certain from what you have described that you have NOT done this, but just in case I will mention it. Remember, simply renaming a folder within libraries (eg. 'MySensors' to 'MySensorsOLD') can cause grief as the old and new will both be compiled / seen by the linker.

I think your 'new user' idea will work.

FWIW: Some time ago I had a similar issue with a different library, I can't remember the details, but I found/fixed it by doing a global search of "C:" for various keywords (e.g. "ESP8" and "MySen" in your case). I ended up finding files I didn't realise were there.

Good luck!

Paul

@sundberg84 - its all about one's point of view. I recently met two English ladies on holiday here, they were on the verge of serious heatstroke, because as they said, "at home 23 degrees was a record summer for us" - it was a very pleasant pleasant 35C day. Days later we began a straight week of 40C plus. That's when all the "E's" die like flies "Electronics" & "Englishmen".

In your (truly excellent) tests, the HLK PM01's peaked at 60C under top load - but I suspect that test was performed in a veery laaaarge ice-box .

Paul

Hi all...

I've recently received 20 of these units (see picture below) and hooked all but two of them all up to 240v with a dummy load resister to test. The other two are driving MySensor nodes to make sure there are no unexplained resets etc. They are well made and are claimed to be a "Mature" and stable unit. So far, no smoke and the ones on nodes have not reset, so all looks well. They have temperature protection, overcurrent, overvoltage and short circuit protection.

I went for these rather than the HLK-PM01 because:

• Being an open PCB, i can easily attach a lead onto the low voltage AC side of the transformer for use by the EMon Energy Meter library in calculating the actual AC voltage in order to derive more accurate power usage.
• The other thing I like is they are not a 'potted blob' - while the blob is a lot safer with regard to errant fingers etc, I feel they must run a lot hotter, and heat not only causes components to die, I figure it could increase the fire risk?

And the final factor being that the price is a bit over one euro, making them the lowest cost AC power supply I've come across for nodes.

Product link: <click me>

FWIW: All the regular "Express" freight charges from China to Australia are about AUD$25 to $30, but this supplier offered an express courier for $7 (US$5) - When it sounds too good to be true. . . Well, the goods were collected from the supplier in China on Wed mid-day, and arrived at my door at noon on Friday. When you consider I live 100Km outside of the main city (Perth), which normally adds two additional days onto any delivery, this was utterly amazing!

Cheers,

Paul

Hi @172pilot

PLEASE NOTE: I gather there are three different problems which have similar results:

• A power supply with insufficient current to drive the ESP causes it to crash / reboot.
• A NULL message (somewhere in the process) can cause ESP to restart.
• Something called a 'WDT Reset' , which I have never encountered (?possibly only applies when using a Vera controller?).

Because all three produce similar looking results, I posted my fix here, even though I had not seen a 'WDT Reset' message (??possibly because I wasn't running a Vera controller??).

My Symptoms
My system appeared to have been running 'fine' for a solid week (as a test), using MYScontroller, I didn't notice anything abnormal. I also had a telnet (Potty) connection to the ESP. It wasn't until I started testing OpenHAB that OpenHab would report that it 'could not communicate'. At the same time my telnet connection and MYScontroller just stopped, no error message etc.

Then, OpenHab log reported that it was 'creating new connection', and resumed communicating, BUT both the telnet link and MYScontroller never resumed communications. I would have to disconnect / reconnect both, then they would continue for a few minutes until OpenHab reported the error again, when they would 'stall' again - this kept repeating.

If I stopped OpenHab, then the Telnet and MYScontroller worked flawlessly. At first I assumed that the OpenHab binding was the problem. Lots of testing, inserting debug 'print' statements into the drivers etc etc... Eventually I discovered that the 'MySensors ESP driver' was receiving a NULL pointer, when it was expecting a char pointer to a message, this was causing the ESP to reset.

I've since been told this problem was fixed in the MySensors 2.0 (beta) drivers and only applies to the 1.5 version (current ver at this point in time).

I hope this helps others clarify which of the three 'causes' apply to their issue. For example, my ESP was resetting, I didn't have a clue if it was a "WDT" reset, it could have been an "ABC" or "XYZ" reset as far as I knew. I still don't know what a WDT reset is?

Cheers... Paul

p.s. The first thing to check with any radio device (ESP, nRf2401 or GSM etc) is that you MUST have a good power source. When these devices transmit their current requirements go up significantly, which can cause all sorts of weird and wonderful thing to happen. Whenever I have a problem with a radio device, I will (temporarily) power the (3.3v) RF device direct from a Lipo battery (3.7v) with a 1N4001 (or similar) diode in series, this drops the voltage to 3.1v. Even though the voltage is a tad low, the Lipo (or NiCad) can deliver tremendous 'grunt' (amps) thus its a 'clean' and stable power source!

@hek

Yes, as I gathered, but I have too many sensors on 1.5.1 and don't want to upgrade them to 2.0 while its not an official release.

I posted it because there are probably others on 1.5.1 with the problem, but can't find a fix.

Cheers...

@Yveaux

Yes, I believe it happens when a client connects with no message, it causes a memory fault (loss); after several such connections the stack is exhausted and the ESP8266 crashes (and reboots).

This cured my crashes, but I'm sure there are many other possibilities for an Exception(28).

One solution - refer to: [https://forum.mysensors.org/topic/3894/esp8266-unexpected-crash-or-reset](link url)

For one possible solution - refer to: [https://forum.mysensors.org/topic/3894/esp8266-unexpected-crash-or-reset](link url)

I had problems with the ESP8266 Gateway crashing and resetting every few minutes with an "Exception(28)".

After lots of searching, I found it was a problem in the 'core driver' in the MySensors library (1.51).

The Fix:

• Open the "MyMessage.cpp" file in your "...\Arduino\libraries\MySensors" folder.
• Search for the "MyMessage& MyMessage::set(const char* value)" function (WARNING: there are several similar names).
• Comment the existing code out and add replacement as illustrated below.

/*  COMMENT OUT THE OLD FUNCTION
MyMessage& MyMessage::set(const char* value) {
	uint8_t length = min(strlen(value), MAX_PAYLOAD);
	miSetLength(length);
	miSetPayloadType(P_STRING);
	strncpy(data, value, length);
	return *this;
}
*/

/*   INSERT THE FOLLOWING IN ITS PLACE   */
MyMessage& MyMessage::set(const char* value) {
	uint8_t length = value == NULL ? 0 : min(strlen(value), MAX_PAYLOAD);
	miSetLength(length);
	miSetPayloadType(P_STRING);
	if (length) {		
		strncpy(data, value, length);
	}
	// null terminate string
	data[length] = 0;
	return *this;
}

If you compile any MySensors ESP8266 project, the library will be rebuilt and with a bit of luck the crashes will vanish.

Paul

@bkl
Just wanted to say thanks for making my wish come true!

My Experience Setting up OpenHab
If it helps others, I tried OpenHab a year ago but gave it away simply because of the instabilities associated with using MQTT, i.e. needing a server, a broker, a client and the gateway. Far too many modules to configure, making it so easy to get it wrong.

Thanks to this MySensors/OpenHab binding, the Arduino gateway talks direct to OpenHab without all the middleware, making it easier to configure and more reliable.

It took only a few minutes to install OpenHab 1.8 and this binding. Pasted the items and sitemap examples and presto - it was working! A very pleasant change from nearly three days wasted trying to get the (alternate) OpenHab2 binding working.

I'll upgrade to OpenHab2 when I'm confident it is stable and the matching binding is sorted out.

Paul

@Salmoides - I must congratulate you on a very neat and professional build.

I'm not sure if you are still hanging around this forum but even if you aren't, others may find the following suggestion helpful.

@Salmoides said*:

With it [the rain detector] I get 0.98 mA [drain] during the gw.sleep command

There is a very easy, but often overlooked, method to disable sensors to reduce battery drain that requires no additional components. Because the sensor draws approximately 1ma, that is well within the 'drive' capacity of an Arduino output pin (which is about 20ma). So, all you need to do is wire the "+" power pin of the rain sensor to a spare output pin and "digitalWrite(pin,HIGH)" to turn it on and "digitalWrite(pin,LOW)" to turn it off.

IMPORTANT: You should check the specs of the processor you are using to make sure the I/O pin can 'drive' or 'source' more than the required current of the sensor you wish to switch. I'd suggest allowing a 50% safety margin.

Paul

@TimO

Hi Tim,
Thanks for replying so promptly , trying to get this going over the weekend.

From what I can see, the fields are linked. I base this on the fact that the log file shows 'link added' and 'link removed' as I play with the 'demo.things' file.
Also, I get the same messages in the log etc, whether I create the links via the things file or with the paper-ui. I've also noticed that when I do make a typing mistake with an items or things entry, OpenHab is usually quick to spit out an error[s], implying that the corrected text is passing the syntax check.

I have stripped my demo to the bare minimum and have included my current set here. The first two (MySensors) 'items' do not update but the log file shows no error. The third item is linked to a non MySensors binding and it works regardless of whether I use to paper.ui or create the links manually (which helps me believe I am creating the link to the binding correctly.

My sitemap.demo

  sitemap demo label="Test Menu" { 
    Frame { 
        Text item=myhum01
        Text item=mytemp01 
        Text item=mytemp99 
    } 
  }

My items.demo

Number myhum01 "Humidity Test (22:2) [%.1f RH]" { channel="mysensors:humidity:gateway:myhum01:hum" }

Number mytemp01 "Temperature Test (22:3) [%.1f] °C" { channel="mysensors:temperature:gateway:mytemp01:temp" }

Number mytemp99 "Printer queue [%.0f jobs]" {channel="ipp:printer:Brother_MFC_8510DN:waitingJobs"}

QUESTION:
In the following things entry, should the first line start with "Bridge" or without? The binding setup notes appear to show both with and without?

My things.demo

Bridge mysensors:bridge-eth:gateway [ ipAddress="192.168.1.70",   tcpPort=5003, sendDelay=200 ] {
    /** define things connected to that bridge here */
    humidity        myhum01   [ nodeId="22", childId="2" ]
    temperature     mytemp01  [ nodeId="22", childId="3" ]
}

I always look for 'what I am doing wrong', but I have been on this for days with no joy, I've reached the point where I am really starting to suspect there may be a bug.

Once again, I would appreciate suggestions from anybody...

Thanks,

Paul

@TimO

ALMOST WORKING

Hi,
Ive been trying for ages to get a stable OpenHab + MySensors setup going. Your new binding is exactly what I've been hoping for and I'm so close to having it working, but can't see what I am doing wrong???

I've installed OpenHab2 plus your MySensors binding. I tried to follow your setup guide / otes, but I suspect a lot has changed since you wrote it.

What Works

• OpenHab runs without any errors in the log file {Yay!}

• My sensor data appears in the OpenHab log - ok.

• In OpenHab, my individual sensors are there and 'linked' to sensor channel.

• The date/time in browser from the NTP binding updates as expected.

Whats Wrong

• The items (in demo.items) appear in the browser, but no data values?

• I can see data from sensor changes in OpenHab log, but still NOT displayed?

Can anybody post an items, things and sitemap example file, or spot an error in mine?

My demo.items:

Number mywatts2 "Watts 2 [%.1f W]" <temperature> {channel="mysensors:power:503a021b:Power_21_6:watt"}

Number  mywatts1 "Watts 1 [%.1f W]" <temperature> {channel="mysensors:power:503a021b:Power_21_2:watt"


Number myhum01 "hum 1 [%.1f %RH]" <temperature> {channel="mysensors:humidity:7fbda972:hum"}

Number mytemp01 "Temp [%.1f C]" <temperature> {channel="mysensors:temperature:503a021b:Temperature_22_3:temp"

My demo.things:

yahooweather:weather:Dawesville [ location=28584781 ]
astro:sun:home  [ geolocation="-32.634619,115.638888", interval=60 ]
ntp:ntp:demo [ hostname="nl.pool.ntp.org", refreshInterval=60, refreshNtp=30 ]

Extract from my demo.sitemap:

  sitemap demo label="Main Menu" { 
    Frame { 
        Text item=mywatts1
        Text item=mywatts2 
        Text item=myhum01
        Text item=mytemp01 
    } 
  }

Initial startup from my openhab.log (apologies for the length)

2016-05-14 09:49:21.749 [DEBUG] [org.openhab.binding.mysensors       ] - BundleEvent STARTING - org.openhab.binding.mysensors
2016-05-14 09:49:21.760 [DEBUG] [org.openhab.binding.mysensors       ] - BundleEvent STARTED - org.openhab.binding.mysensors
2016-05-14 09:49:21.770 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.mysensors.internal.MySensorsHandlerFactory, component.id=2, service.id=104, service.bundleid=10, service.scope=bundle} - org.openhab.binding.mysensors
2016-05-14 09:49:32.367 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'ipp:printer:Brother_MFC_8510DN' has been added.
2016-05-14 09:49:32.383 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=197, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.398 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:bridge-eth:503a021b' has been added.
2016-05-14 09:49:32.410 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:humidity:503a021b:Humidity_22_2' has been added.
2016-05-14 09:49:32.411 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:bridge-eth, thing.id=mysensors:bridge-eth:503a021b, service.id=198, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.436 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:humidity, thing.id=mysensors:humidity:503a021b:Humidity_22_2, service.id=199, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.438 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:humidity:7fbda972' has been added.
2016-05-14 09:49:32.441 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:power:40868d6c' has been added.
2016-05-14 09:49:32.444 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:power:503a021b:Power_21_1' has been added.
2016-05-14 09:49:32.447 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:power:503a021b:Power_21_2' has been added.
2016-05-14 09:49:32.448 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:power:503a021b:Power_21_3' has been added.
2016-05-14 09:49:32.452 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:power:503a021b:Power_21_4' has been added.
2016-05-14 09:49:32.455 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:power:503a021b:Power_21_5' has been added.
2016-05-14 09:49:32.456 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:power:503a021b:Power_21_6' has been added.
2016-05-14 09:49:32.458 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:temperature:503a021b:Temperature_22_3' has been added.
2016-05-14 09:49:32.459 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'mysensors:temperature:522d430d' has been added.
2016-05-14 09:49:32.460 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'ntp:ntp:local' has been added.
2016-05-14 09:49:32.477 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:humidity, thing.id=mysensors:humidity:7fbda972, service.id=200, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.497 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:power, thing.id=mysensors:power:40868d6c, service.id=201, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.500 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:power, thing.id=mysensors:power:503a021b:Power_21_1, service.id=202, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.502 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:power, thing.id=mysensors:power:503a021b:Power_21_2, service.id=203, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.505 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:power, thing.id=mysensors:power:503a021b:Power_21_3, service.id=204, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.511 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:power, thing.id=mysensors:power:503a021b:Power_21_4, service.id=205, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.514 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:power, thing.id=mysensors:power:503a021b:Power_21_5, service.id=206, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.520 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:power, thing.id=mysensors:power:503a021b:Power_21_6, service.id=207, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.523 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:temperature, thing.id=mysensors:temperature:503a021b:Temperature_22_3, service.id=208, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.525 [DEBUG] [org.openhab.binding.mysensors       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:temperature, thing.id=mysensors:temperature:522d430d, service.id=209, service.bundleid=10, service.scope=singleton} - org.openhab.binding.mysensors
2016-05-14 09:49:32.673 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-eth:503a021b' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:32.699 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:humidity:503a021b:Humidity_22_2' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:32.712 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - Initialization of the MySensors Bridge
2016-05-14 09:49:32.714 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:humidity:7fbda972' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:32.756 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - Connecting to bridge ...
2016-05-14 09:49:32.899 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:40868d6c' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:32.901 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - Connection to ethernet gateway successful!
2016-05-14 09:49:33.053 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:humidity:503a021b:Humidity_22_2' changed from INITIALIZING to ONLINE
2016-05-14 09:49:33.081 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:humidity:7fbda972' changed from INITIALIZING to ONLINE
2016-05-14 09:49:33.121 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-eth:503a021b' changed from INITIALIZING to ONLINE
2016-05-14 09:49:33.123 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_2' changed from INITIALIZING to ONLINE
2016-05-14 09:49:33.178 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:temperature:503a021b:Temperature_22_3' changed from INITIALIZING to ONLINE
2016-05-14 09:49:33.106 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 0;0;3;0;14;Gateway startup complete.
2016-05-14 09:49:33.200 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 0;0;3;0;2;1.5.1
2016-05-14 09:49:33.203 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_1' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:33.205 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_2' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:33.213 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_3' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:33.217 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_4' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:33.235 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_5' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:33.237 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_6' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:33.239 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:temperature:503a021b:Temperature_22_3' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:33.240 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:temperature:522d430d' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:33.242 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'CurrentDate-ntp:ntp:local:dateTime' has been added.
2016-05-14 09:49:33.254 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'hum01-mysensors:humidity:503a021b:Humidity_22_2:hum' has been added.
2016-05-14 09:49:33.255 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'mywatts1-mysensors:power:503a021b:Power_21_2:watt' has been added.
2016-05-14 09:49:33.256 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'mywatts1-mysensors:power:503a021b:Power_21_4:watt' has been added.
2016-05-14 09:49:33.263 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'mywatts2-mysensors:power:503a021b:Power_21_5:watt' has been added.
2016-05-14 09:49:33.264 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'temp01-mysensors:power:503a021b:Power_21_5:watt' has been added.
2016-05-14 09:49:33.268 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'watts1-mysensors:power:503a021b:Power_21_5:watt' has been added.
2016-05-14 09:49:33.304 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'watts1-mysensors:power:503a021b:Power_21_6:watt' has been added.
2016-05-14 09:49:33.305 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'watts2-mysensors:power:503a021b:Power_21_2:watt' has been added.
2016-05-14 09:49:33.534 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'ipp_printer_Brother_MFC_8510DN-ipp:printer:Brother_MFC_8510DN' has been added.
2016-05-14 09:49:33.593 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:49:33.884 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:49:34.272 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_1' changed from INITIALIZING to ONLINE
2016-05-14 09:49:34.274 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_bridge_eth_503a021b-mysensors:bridge-eth:503a021b' has been added.
2016-05-14 09:49:34.275 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_humidity_503a021b_Humidity_22_2-mysensors:humidity:503a021b:Humidity_22_2' has been added.
2016-05-14 09:49:34.277 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_humidity_7fbda972-mysensors:humidity:7fbda972' has been added.
2016-05-14 09:49:34.278 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_power_40868d6c-mysensors:power:40868d6c' has been added.
2016-05-14 09:49:34.278 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_power_503a021b_Power_21_1-mysensors:power:503a021b:Power_21_1' has been added.
2016-05-14 09:49:34.279 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_power_503a021b_Power_21_2-mysensors:power:503a021b:Power_21_2' has been added.
2016-05-14 09:49:34.279 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_power_503a021b_Power_21_3-mysensors:power:503a021b:Power_21_3' has been added.
2016-05-14 09:49:34.280 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_power_503a021b_Power_21_4-mysensors:power:503a021b:Power_21_4' has been added.
2016-05-14 09:49:34.280 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_power_503a021b_Power_21_5-mysensors:power:503a021b:Power_21_5' has been added.
2016-05-14 09:49:34.281 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_power_503a021b_Power_21_6-mysensors:power:503a021b:Power_21_6' has been added.
2016-05-14 09:49:34.284 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_temperature_503a021b_Temperature_22_3-mysensors:temperature:503a021b:Temperature_22_3' has been added.
2016-05-14 09:49:34.295 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_temperature_522d430d-mysensors:temperature:522d430d' has been added.
2016-05-14 09:49:34.347 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'ntp_ntp_local-ntp:ntp:local' has been added.
2016-05-14 09:49:34.557 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'ipp_printer_Brother_MFC_8510DN' has been added.
2016-05-14 09:49:34.560 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_bridge_eth_503a021b' has been added.
2016-05-14 09:49:34.576 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_4' changed from INITIALIZING to ONLINE
2016-05-14 09:49:34.581 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_humidity_503a021b_Humidity_22_2' has been added.
2016-05-14 09:49:34.584 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_humidity_7fbda972' has been added.
2016-05-14 09:49:34.589 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_power_40868d6c' has been added.
2016-05-14 09:49:34.589 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_power_503a021b_Power_21_1' has been added.
2016-05-14 09:49:34.591 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_power_503a021b_Power_21_2' has been added.
2016-05-14 09:49:34.592 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_power_503a021b_Power_21_3' has been added.
2016-05-14 09:49:34.593 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_power_503a021b_Power_21_4' has been added.
2016-05-14 09:49:34.594 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_power_503a021b_Power_21_5' has been added.
2016-05-14 09:49:34.596 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:temperature:522d430d' changed from INITIALIZING to ONLINE
2016-05-14 09:49:34.597 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_power_503a021b_Power_21_6' has been added.
2016-05-14 09:49:34.597 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_temperature_503a021b_Temperature_22_3' has been added.
2016-05-14 09:49:34.599 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:40868d6c' changed from INITIALIZING to ONLINE
2016-05-14 09:49:34.880 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_temperature_522d430d' has been added.
2016-05-14 09:49:35.059 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'ntp_ntp_local' has been added.
2016-05-14 09:49:35.093 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_5' changed from INITIALIZING to ONLINE
2016-05-14 09:49:35.099 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_6' changed from INITIALIZING to ONLINE
2016-05-14 09:49:35.190 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:power:503a021b:Power_21_3' changed from INITIALIZING to ONLINE
2016-05-14 09:49:42.498 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:49:43.626 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;174
2016-05-14 09:49:43.972 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2076
2016-05-14 09:49:44.806 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /ui
2016-05-14 09:49:45.008 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start
2016-05-14 09:49:45.503 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'ntp:ntp:local' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:45.976 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'ntp:ntp:local' changed from INITIALIZING to ONLINE
2016-05-14 09:49:46.283 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'ipp:printer:Brother_MFC_8510DN' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:46.285 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'ipp:printer:Brother_MFC_8510DN' changed from INITIALIZING to OFFLINE
2016-05-14 09:49:46.979 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2016-05-14 09:49:47.057 [INFO ] [assic.internal.servlet.WebAppServlet] - Started Classic UI at /classicui/app
2016-05-14 09:49:47.812 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'demo.sitemap'
2016-05-14 09:49:48.239 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'demo.things'
2016-05-14 09:49:48.414 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'logging.persist'
2016-05-14 09:49:48.425 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'yahooweather:weather:Dawesville' has been added.
2016-05-14 09:49:48.726 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'rrd4j.persist'
2016-05-14 09:49:48.749 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'demo.script'
2016-05-14 09:49:48.983 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'yahooweather:weather:Dawesville' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:48.984 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'yahooweather:weather:Dawesville' changed from INITIALIZING to ONLINE
2016-05-14 09:49:48.985 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'astro:sun:home' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:49.390 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'astro:sun:home' has been added.
2016-05-14 09:49:49.473 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'demo.items'
2016-05-14 09:49:49.566 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'ntp:ntp:demo' changed from UNINITIALIZED to INITIALIZING
2016-05-14 09:49:49.737 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'ntp:ntp:demo' has been added.
2016-05-14 09:49:49.742 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'mywatts2-mysensors:power:503a021b:Power_21_6:watt' has been added.
2016-05-14 09:49:49.743 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'mywatts1-mysensors:power:503a021b:Power_21_2:watt' has been added.
2016-05-14 09:49:49.743 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'myhum01-mysensors:humidity:7fbda972:hum' has been added.
2016-05-14 09:49:49.744 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'mytemp01-mysensors:temperature:503a021b:Temperature_22_3:temp' has been added.
2016-05-14 09:49:50.090 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'astro:sun:home' changed from INITIALIZING to ONLINE
2016-05-14 09:49:50.608 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'ntp:ntp:demo' changed from INITIALIZING to ONLINE
2016-05-14 09:49:53.619 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;70
2016-05-14 09:49:53.853 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1737
2016-05-14 09:49:54.166 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'ipp:printer:Brother_MFC_8510DN' changed from OFFLINE to ONLINE
2016-05-14 09:50:02.663 [WARN ] [stence.jpa.internal.JpaConfiguration] - Connection url is required in openhab.cfg!
2016-05-14 09:50:02.663 [WARN ] [stence.jpa.internal.JpaConfiguration] - Empty connection url in openhab.cfg!
2016-05-14 09:50:02.663 [WARN ] [stence.jpa.internal.JpaConfiguration] - Driver class is required in openhab.cfg!
2016-05-14 09:50:02.666 [WARN ] [stence.jpa.internal.JpaConfiguration] - Empty driver class in openhab.cfg!
2016-05-14 09:50:02.666 [INFO ] [stence.jpa.internal.JpaConfiguration] - user was not specified!
2016-05-14 09:50:02.673 [INFO ] [stence.jpa.internal.JpaConfiguration] - password was not specified!
2016-05-14 09:50:02.673 [INFO ] [stence.jpa.internal.JpaConfiguration] - syncmappings was not specified!
2016-05-14 09:50:02.724 [INFO ] [core.karaf.internal.FeatureInstaller] - Installed 'openhab-persistence-jpa'
2016-05-14 09:50:03.283 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;0;1;0;37;0
2016-05-14 09:50:03.591 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:50:03.856 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:50:08.636 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:50:13.592 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;167
2016-05-14 09:50:13.859 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2095
2016-05-14 09:50:23.600 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;71
2016-05-14 09:50:23.861 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1744
2016-05-14 09:50:33.595 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:50:33.855 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:50:34.786 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:50:43.593 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;170
2016-05-14 09:50:43.862 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2113
2016-05-14 09:50:53.596 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;69
2016-05-14 09:50:53.860 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1751
2016-05-14 09:51:00.926 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;12
2016-05-14 09:51:03.595 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:51:03.860 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:51:09.380 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;1;1;0;37;17
2016-05-14 09:51:13.594 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;170
2016-05-14 09:51:13.855 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2131
2016-05-14 09:51:23.597 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;71
2016-05-14 09:51:23.862 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1758
2016-05-14 09:51:29.115 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:51:31.920 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;255;0;0;17;1.5.1
2016-05-14 09:51:32.131 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;255;3;0;6;0
2016-05-14 09:51:32.520 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;255;0;0;17;1.5.1
2016-05-14 09:51:32.732 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;255;3;0;6;0
2016-05-14 09:51:33.958 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;255;3;0;11;Lounge Environs
2016-05-14 09:51:34.219 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;255;3;0;12;1.1
2016-05-14 09:51:34.478 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;2;0;0;7;
2016-05-14 09:51:34.739 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;3;0;0;6;
2016-05-14 09:51:35.000 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;1;1;0;43;2.5 ppm
2016-05-14 09:51:35.264 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;255;3;0;11;Energy Meter
2016-05-14 09:51:35.525 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;0;0;13;
2016-05-14 09:51:35.787 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;0;0;13;
2016-05-14 09:51:36.049 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;43;KwHours
2016-05-14 09:51:36.313 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;43;KwHours
2016-05-14 09:51:36.570 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;43;Watts
2016-05-14 09:51:36.831 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;3;1;0;0;24.1
2016-05-14 09:51:55.263 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:51:55.833 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;69
2016-05-14 09:51:56.094 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1698
2016-05-14 09:52:05.837 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:52:06.104 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:52:15.832 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;171
2016-05-14 09:52:16.093 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.1998
2016-05-14 09:52:21.403 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:52:25.833 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;68
2016-05-14 09:52:26.099 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1704
2016-05-14 09:52:35.837 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:52:36.102 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:52:37.110 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;0;1;0;37;0
2016-05-14 09:52:45.833 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;167
2016-05-14 09:52:46.095 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2016
2016-05-14 09:52:47.542 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:52:55.838 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;70
2016-05-14 09:52:56.108 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1711
2016-05-14 09:53:05.835 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:53:06.105 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:53:13.694 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:53:15.836 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;174
2016-05-14 09:53:16.097 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2034
2016-05-14 09:53:25.839 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;70
2016-05-14 09:53:26.099 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1718
2016-05-14 09:53:35.835 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:53:36.096 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:53:39.845 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:53:45.835 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;172
2016-05-14 09:53:46.095 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2053
2016-05-14 09:53:55.836 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;68
2016-05-14 09:53:56.098 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1724
2016-05-14 09:54:05.837 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:54:06.100 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:54:08.040 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:54:14.044 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;0;1;0;37;0
2016-05-14 09:54:15.840 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;174
2016-05-14 09:54:16.102 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2071
2016-05-14 09:54:25.839 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;68
2016-05-14 09:54:26.100 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1729
2016-05-14 09:54:34.176 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:54:35.836 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:54:36.096 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:54:45.843 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;173
2016-05-14 09:54:46.105 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2089
2016-05-14 09:54:49.812 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;2;1;0;1;55.3
2016-05-14 09:54:55.837 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;68
2016-05-14 09:54:56.102 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1734
2016-05-14 09:55:00.313 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:55:05.851 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:55:06.117 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:55:15.837 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;166
2016-05-14 09:55:16.107 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2108
2016-05-14 09:55:25.836 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;68
2016-05-14 09:55:26.108 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1739
2016-05-14 09:55:26.463 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:55:35.838 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:55:36.098 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:55:45.838 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;170
2016-05-14 09:55:46.106 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2126
2016-05-14 09:55:50.716 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 22;0;1;0;37;0
2016-05-14 09:55:52.609 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 50;0;1;0;37;11
2016-05-14 09:55:55.839 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;1;1;0;17;67
2016-05-14 09:55:56.101 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;4;1;0;18;93.1743
2016-05-14 09:56:05.838 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;2;1;0;17;0
2016-05-14 09:56:06.098 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;5;1;0;18;32.4534
2016-05-14 09:56:15.839 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;3;1;0;17;168
2016-05-14 09:56:16.099 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - 21;6;1;0;18;345.2144

All suggestions appreciated...

Thanks,

Paul