Posts made by LastSamurai

@sergio-rius A little late, sorry, but that depends on the mosfets you are actually using. I am driving ~5m strips of white leds with most of my controllers and they don't even really get hot.

There is also a big(ish) update from my side concerning this project: I have designed, 3d printed and tested my own case for the controllers and they work great. I have just added the stl files and some images to the project page!!
For now this project is done from my side. The controllers have been working great for the past 2 years but due to the "huge" (~1s) delay with my Mysensors network (with signing and openhab on a raspi) when switching the leds I am currently testing some MQTT and wifi based RGBWW controller boards as an alternative.

I only had Home Assistant installed for some days (did not really like it at the time) so I can't tell you that it works 100% but it did back then. You have to add some strange additional messages but I tried to integrate that into my code.
I am using my RGBW controllers with openhab 2 in one location and with domoticz in another. As it is controlled by MySensors it works (and looks) pretty much like any other mysensors node. Both installations run on 2.2. Hope this helps

I never tried that but as far as I know you have to tell Mysensors to use a different kind of radio by adding a define like:

#define MY_RADIO_RFM69

Just do a quick search on this forum though

Well great to hear that you solved the problem. There are version 2.1 and 2.2 of mysensors as of now that can be used too so maybe update again?

Do you still have an older version of Mysensors installed? Thats the only time I had such behaviour

@TimO I finally got around to testing my pureWhite RGBW code and at least for me its working like it should be. I saw you already merged this so I guess others can use it too very soon.
What is still not working is the acknowledgment feature. I have one node that only gets about 90% of the messages without error, so I tried activating it there and on some other nodes too for testing. Result: success rate is down to ~50% for each node and I get messages about some acknowledgment on the console when no message has even been sent (nothing about a message from mysensors on the console and no rx/tx leds on the gateway). When I tested this some months ago I also saw no message at the client so I am pretty sure none gets send.
So I guess this issue is still unresolved I have no clue why on a first glance but if I can help just send me a message.

Sounds nice! I wish you the best of luck with your project(s) and keep us updated!
I might do some project report like this too soon, so I will follow yours

You can also use the security features of mysensors so that your node doesn't connect to your neighbors gateway even if it uses the same channel. Using a different channel would be easier though i guess.

Did anyone try the Anet A8? I am currently thinking about buying one. It would be my first 3D printer and I do not want to spend more than ~150€ (at least initially). It seems to be a clone of the Prusa i3 and quite capable if add some cheap/self printed parts and invest some time. I don't have the time/knowledge to build a printer on my own from scratch but I am pretty sure that I can those upgrades.

Or are there any alternatives in that price range that you guys can recommend? Main idea is to print cases for my electronics projects and some small other stuff from time to time.

@TimO I saw that you fixed some other bugs too in the repo. Will you create a new version 2.3 of the binding soon? Or will there be more changes first?
As most of the changes (at least also) concern RGBW lighting I would really like to use it but I can't seem to build the binding locally (I postet the error in the git pr).

@masmat As far as I know .cfg files are only the config files fpr your installed addons and are located in the service directory (see TimO's post above). And they indeed only contain the settings you want to use, which can be 4 lines only. Depends on the addon

@TimO Today I decided to finally read into how Openhab binding development works. And just when I started I saw that you finally fixed some of the problems that I reported via github (thank you very much for that). Had to laugh a little at that coincidence

I just started a pullrequest where I tried to implement pure white colors for RGBW values fixing one of my problems left open. If you find the time please have a look at it. I did not yet write any tests for it or test it on my actual RGBW nodes but I will do that as soon as possible

I have just updated to the stable openHAB 2.2 Version and everything seemed to be working just fine in the beginning but after the next restart I got this error:

10:31:19.727 [WARN ] [fig.xml.osgi.XmlDocumentBundleTracker] - The XML document '/ESH-INF/binding/binding.xml' in module 'org.openhab.binding.mysensors' could not be parsed: The XmlConfigDescriptionProvider must not be null!

It seems like I can still control my devices just fine but I just wanted to make sure that this doesn't cause errors down the line. So @TimO any idea where this error is coming from?

@TimO Thanks for your help though I am afraid you mixed something up there. The channel linking to the item itself doesn't really make sense
Not 100% sure why it did not work earlier for me but I now got it to work like this:

// thing
multimeter		voltTHWohnzimmer	[nodeId=1, childId=2]
// item
Number 	voltageSensorWZ 		"Spannung [%3f mV]" 		<poweroutlet_eu> 	(grVolt, grWZ)	{ channel="mysensors:multimeter:gwSerial:voltTHWohnzimmer:volt" }

My error in the code above seems to have been that I defined most as customSensor instead of multimeter.

@TimO I am not sure what you mean.
My sketch sends a presentation:

 present(CHILD_ID_BATTERY, S_MULTIMETER);

and in openhab I added these (tried both sensor kinds)

// things
customSensor abc [nodeId=26, childId=1]
multimeter def [nodeId=17, childId=1]
// and items
Number 	voltageSensorWZ ... { channel="mysensors:multimeter:gwSerial:def:volt" }
//...

Is there anything i am missing here?

I am the one from your post and the capacitors only helped a little. One of my molgans simply doesn't seem to work.
But you are right sending takes a lot of energy (vs doing nothing) so a bigger capacitor and/or pauses in between definitely should help!

@TimO My sketches are sending the nodes remaining battery power to the controller via a V_VOLTAGE. Openhab 2 with your binding doesn't seem to be able to read these values. Is this an error (possibly on my side) or does the not yet support this?

@ThetaDev Maybe you you could get away with it but especially the radio is very sensitive concerning the power supply. Cheap pro minis often use very cheap regulators too and then this might become a problem.
I also wanted to support the high power version of the NRF and that definitly needs more power than provided by the onboard regulator.

I am not sure but I don't think so. All controllers I have used yet give incrementing auto Ids though. So if you have less than 100 (auto id) nodes you can simply set the id in code for your test nodes.

Serial Gateway is the easiest I guess but you can use every gateway that Home Assistant supports. Mainly depends on the physical position of the gateway I guess (if you can use serial or need a networked one).

@TimO Thank you again for the help. Everything is now back up and running With the new jar my node could finally get a new id and after also enabling signing again everything worked as expected.
Can I see anywhere that you updated the jar file? I am using the current beta of mysensors mostly so I would also need to use an updated version of the openhab plugin.

I don't know if someone ever used an arduino as a controller (not just as a gateway) but in theory it should be possible. Mysensors uses a relatively simple textbased API that you could use to control your devices. Maybe something like an ESP8266 on some kind of development board would be a good fit for you. They can already be used as a gateway and should be strong enough to already do some simple controller work I guess.

I see no reason why it could not be done with mysensors. The gateway is needed as a bridge between the controller (something like a raspberry pi) and the actual network. If you need a controller you also need a gateway.

@TimO Ahh thank you! I am using version 2.2 linked in the first post of this thread though. Where do I get a newer version? Maybe I overlooked it but I am not seeing any newer releases.

@gonzalonal I saw it earlier but did not understand it fully. I will take another look at it later.

@TimO I might have found the error... maybe. I reflashed the motion sensor (with cleared eeprom before) and removed the static id and signing. Now I see that the problem seems to be that the node is unable to get an ID. Any idea what's happening herer? Is there a setting concerning that somewhere?

Log from the node:

...
102477 TSM:FAIL:RE-INIT
102479 TSM:INIT
102488 TSM:INIT:TSP OK
102490 TSM:FPAR
102492 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
103426 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0
103432 TSF:MSG:FPAR OK,ID=0,D=1
104501 TSM:FPAR:OK
104503 TSM:ID
104503 TSM:ID:REQ
104507 TSF:MSG:SEND,255-255-0-0,s=55,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
106516 TSM:ID
106516 TSM:ID:REQ
106520 TSF:MSG:SEND,255-255-0-0,s=20,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
108529 TSM:ID
108529 TSM:ID:REQ
108533 TSF:MSG:SEND,255-255-0-0,s=241,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
110542 TSM:ID
110542 TSM:ID:REQ
110546 TSF:MSG:SEND,255-255-0-0,s=206,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
112556 !TSM:ID:FAIL
112558 TSM:FAIL:CNT=6
112560 TSM:FAIL:DIS
112562 TSF:TDI:TSL
...

Log from the openhab server:

15:21:32.127 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 255;34;3;0;3;
15:21:34.135 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 255;0;3;0;3;
15:21:36.147 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 255;221;3;0;3;
...

and lots more similar requests with different ids.

@gonzalonal said in openHAB 2.2 binding:

Yes, sure. I'll do that to keep track.

By the way, I have RGBW led strip and I am using it with mysensors with no issues. Would you mind telling me what's wrong so I can recreate the scenario?

You can find the issues here. Basically you (I ;)) can't set RGBW nodes to display pure white colors via openhab, dimming is not working (error confirmed by TimO) and most importantly ACK isn't working properly (for me at least). If you can help with any of this (especially the conversion HSB <=> RGBW) you are most welcome.

The problem is that the motion sensor still doesn't show up at the gateway although it gets an answer from it. I disabled domoticz though so I need to find another reason ;( Earlier it showed up in domoticz ... strange. I will try to change the id and see if OH picks it up then.
Btw @TimO Any idea yet when you will be able to work on the github issues I posted?

Sorry for bothering you guys, I figured out the problem: I have installed domoticz on the same raspberry and after a restart I forgot to turn it off. So all the missing data was "hidden" away by domoticz instead of openhab.

So I disabled debug output on the gateway to avoid the error messages but I still have problems with my setup. I used to have a motion sensor that worked with openhab. Now when the sensor sends a motion event to the gateway nothing happens in openhab.

Part of the log of the motion sensor:

6236 TSF:MSG:SEND,11-11-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:1
6307 MCO:SLP:MS=30000,SMS=0,I1=255,M1=255,I2=255,M2=255
6367 TSF:TDI:TSL
6385 MCO:SLP:WUP=-1
6406 TSF:TRI:TSB
6424 MCO:SLP:MS=86400000,SMS=0,I1=1,M1=1,I2=255,M2=255
6481 TSF:TDI:TSL
6500 MCO:SLP:WUP=1
6520 TSF:TRI:TSB
6541 TSF:MSG:SEND,11-11-0-0,s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:1
6612 MCO:SLP:MS=30000,SMS=0,I1=255,M1=255,I2=255,M2=255
6670 TSF:TDI:TSL

So it seems like the message gets send succesfully but on the openhab log I see no mentioning of that (although I enable debug output for mysensors and I can switch on/off some led nodes). Any ideas why? I really want to get this working again.

Idk if the theory is true but for me it definitly is. The reason for me is that I build everything that I could (easily) build for now. Also I think there is currently a big shift in home automation from different (not interoperable) systems to voice assistant based systems that finally interconnect different systems. So the "normal" user doesn't need to build as much by himself anymore. Even prices go down (although it's still much cheaper to build stuff by yourself).

Would be interesting to see some number on this though. Also there is a thing called "hype cycle" perhaps IoT in general just hit another phase?

Wow, you are right of course. Debugging is indeed enabled... but than I can just ignore the errors, thank you.
@TimO said in openHAB 2.2 binding:

Hi @LastSamurai !

You've debug enabled on the gateway, have you? Looks like the binding does not like the (debug) output from the gateway.
But the binding should recover just fine from the exception, only the (debug) message that has lead to this exception won't be parsed.

Ok I reflashed the gateway and it's gotten a little better. Still have some errors though.

@TimO Hope you had a nice vacation!
Is there already some new version of the binding to test?

I was on vacation too lately and when I powered my openhab system back on I got lots of problems with my gateway and sensor connections. First I got a never ending circle of failing startup checks (although I could already switch lights). After I disabled the check it seemed to work. But when restarting a sensor node (that did not send any values after the controller restart) I got this error:

16:55:54.552 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;9;159004 Skipping security for command 3 type 16
16:55:54.604 [DEBUG] [rsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;9;159011 TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=16,pt=0,l=0,sg=0,ft=0,st=OK:
16:55:54.747 [WARN ] [rsAbstractConnection$MySensorsReader] - Exception on reading from connection
java.io.IOException: Underlying input stream returned zero bytes
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:288)[:1.8.0_144]
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)[:1.8.0_144]
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)[:1.8.0_144]
        at java.io.InputStreamReader.read(InputStreamReader.java:184)[:1.8.0_144]
        at java.io.BufferedReader.fill(BufferedReader.java:161)[:1.8.0_144]
        at java.io.BufferedReader.readLine(BufferedReader.java:324)[:1.8.0_144]
        at java.io.BufferedReader.readLine(BufferedReader.java:389)[:1.8.0_144]
        at org.openhab.binding.mysensors.internal.protocol.MySensorsAbstractConnection$MySensorsReader.run(MySensorsAbstractConnection.java:335)[205:org.openhab.binding.mysensors:2.2.0.201707241115]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_144]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_144]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_144]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_144]
        at java.lang.Thread.run(Thread.java:748)[:1.8.0_144]

Any idea why or how to fix this? Everything was working fine before

PS I also just got another error while switching a light (the light still worked though):

17:08:31.549 [WARN ] [rsAbstractConnection$MySensorsReader] - Exception on reading from connection
java.text.ParseException: class java.text.ParseException : Message length is not > 4
        at org.openhab.binding.mysensors.internal.protocol.message.MySensorsMessage.parse(MySensorsMessage.java:337)[205:org.openhab.binding.mysensors:2.2.0.201707241115]
        at org.openhab.binding.mysensors.internal.protocol.MySensorsAbstractConnection$MySensorsReader.run(MySensorsAbstractConnection.java:345)[205:org.openhab.binding.mysensors:2.2.0.201707241115]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_144]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_144]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_144]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_144]
        at java.lang.Thread.run(Thread.java:748)[:1.8.0_144]
17:08:31.678 [WARN ] [rsAbstractConnection$MySensorsReader] - Exception on reading from connection
java.io.IOException: Underlying input stream returned zero bytes
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:288)[:1.8.0_144]
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)[:1.8.0_144]
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)[:1.8.0_144]
        at java.io.InputStreamReader.read(InputStreamReader.java:184)[:1.8.0_144]
        at java.io.BufferedReader.fill(BufferedReader.java:161)[:1.8.0_144]
        at java.io.BufferedReader.readLine(BufferedReader.java:324)[:1.8.0_144]
        at java.io.BufferedReader.readLine(BufferedReader.java:389)[:1.8.0_144]
        at org.openhab.binding.mysensors.internal.protocol.MySensorsAbstractConnection$MySensorsReader.run(MySensorsAbstractConnection.java:335)[205:org.openhab.binding.mysensors:2.2.0.201707241115]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_144]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_144]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_144]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_144]
        at java.lang.Thread.run(Thread.java:748)[:1.8.0_144]

@krejcarek I haven't heard anything from @TimO recently but have you tried it without ACK enabled? In my case the rate of success increased visibly. There are still some cases where the message doesn't get send successfully though, so I am still waiting for the working ACK feature

Wow nice! Might take me some time, but I will take a look at your code (and maybe add some of its features back to my sketches if that fine with you).

@Sergio-Rius Nice to hear! And good idea with the test sketch.

What exactly did not work with my sketch? I would really like to fix it (for others too).

I have added 2 more issues in github. Most importantly there seems to be an issue with ACK right now. So if you have enabled acknowledgment on one of your things and sometimes see no reactions from your leds (or whatever you are using) try disabling ACK. I helped in my case.

@ikjes said in openhabian +mysensors binding 2.2:

[ nodeId="1" , childId="11" ]

Imho this needs to be

[ nodeId=1 , childId=11 ]

Read the patchnotes from the latest mysensors binding update

@Anticimex I am using software based signing on atmega 328p based nodes.
I guess I'll wait for the new methods then and just ignore the delay

I am using signing and whitelisting (the gateway, not all nodes) on all my nodes at the moment as I feel that security really is important. That way noone but me should be able to switch on/off my devices. My problem is that signing used in my RGBW controllers makes them react pretty slow.
With signing enabled its about 0.5-1s between clicking "on" in domoticz and the light turning on. Without signing the reaction is pretty much instant.
In most cases this is no problem but with light(switches) I am used to instant reactions so this gets really annoying really fast.

I know this has to be a little slower because several messages are send back and forth but is there any way to make this faster?

What do you mean by "I also try to click on the arduino itself"?
What does the serial output of the node say? Does it receive a message or not?

What does the domoticz and the nodes log say? Did it work on an earlier version?

@TimO Thank you! You already solved one of my problems. I'll try to also look into the dimming problem although I first need to understand the openhab structure.

I just added another issue in github as sometimes my nodes don't seem to update.

Also I really want to be able to only activate the white part of the node when needed (as mixed white just looks bad, afterall thats why you use RGBW leds). I can change the level of the white leds via my openhab android app but I have found no way to set the leds to 00 00 00 FF. The RGB part always stays on. Should I add another gitHub issue for this or is there just some other kind of control I need to use?

Ok I'll answer my question here as I found the error with some help:
it has to be

nodeId
// not nodeID

I just reported some of my issues in the github repo. There might still be some errors there.
I'll try to help solving them as best as I can as @TimO 's work with the integration into openhab 2 seems pretty awesome too me
I am trying to switch to openhab anyways and am not that bad at developing in java. Perhaps I can be of some help there.

Here are the gitHub issues
Dimmer not working
Things definition not working

@Jan-Gatzke Ah ok nice to know. I am facing the same problem. RGBW is not that well supported in domoticz. I am currently trying to switch to openhab2 but having some problems with my RGBW nodes there too. Development on the plugin seems to be very active though. If you want to follow the discussion have a look at the forum thread here or on github
Once I got everything up and running in openhab I'll post an update here.

Meanwhile the newest sketch from my github should work with Home assistant too.

@Jan-Gatzke Thanks, I'll try that later although it doesn't look much different from mine. May I ask why you are using V_VAR1/2 types in your sketch? And why you send answer messages? Are you using home assistant (thats the only one where this is need imho)?

@Jan-Gatzke Did you ever manage to get your non-linear fading to work? I used the predefined values from your sketch and added them to my newer one but whenever I use that the sketch stops working and only rubbish is shown on the serial port.
Here is my new version: github

@Stuart-Middleton It really shoudn't be. Just follow the pictures in the project. There are also updated project/gerber files in my github for anyone wanting to order new ones. Once I have used all of the Version 1.3 ones I will order new ones from dirtyPCBs and add the link here.

Ok small update to my post above: I can add an RGBW node via the paperUI and then control it via items defined in the items file.
But why does the same thing not work for things defined via the things file? Is something wrong with:

Bridge mysensors:bridge-ser:gwSerial [ serialPort="/dev/ttyUSB0", sendDelay=100 ] {

    /** Lights */
    rgbwLight 		LichtKuecheUnten	[nodeID=4, childId=1, requestAck=true]
    //...
}

The thing created by the paperui is called

mysensors:rgbwLight:gwSerial:rgbwlight_4_1:status / rgbw / ....

so my settings are correct.

Also is there a way to control the white part of the light? I have a colorpicker for that item linked to the rgbw channel but this seem to only change the color and brightness, ignoring the white part of the RGBW.

PS I also sometimes get an acknowledgment message when no actual messages from/to the gateway and node are in the logs and the node doesn't react at all. Any idea how that can happen? It seems to mainly happen when switch very fast but I am not 100% sure about that.

19:47:18.881 [INFO ] [rsAbstractConnection$MySensorsWriter] - ACK received for message: 4;1;1;1;2;1

Should I report these error in a github issue?

What does the nodes and/or the gateways log say?
It might not change in domoticz if you just send on but no off signals but it should still be visible in the nodes log (arduino and in domotizc)

After I fixed the initial errors with the help from this thread I am now trying to use my RGBW nodes with openhab. I have had several issues with that though:

• If I add the item via the paperUI:
  • On/Off (status) works just fine
  • Setting a color at full saturation/brightness works well too
  • I am not sure if that is intended but I want to use only the white leds on the RGBW strip sometimes. Mixed white values just look very bad. I can't seem to be able to do this with openhab. Settings the saturation slider to 0 sends ffffffff and sometimes just 00000000. Is there any way to just send 000000ff? Domoticz does this automatically when setting the color to white and home assistant has a seperate white slider that should allow the same thing
  • When trying to change the brightness the node only receives a new color value of length null (no dimmer message) and I get the following error message in the openhab log:

21:51:17.801 [ERROR] [nternal.event.MySensorsEventRegister] - Event broadcasting throw an exception
java.lang.StringIndexOutOfBoundsException: String index out of range: 2
        at java.lang.String.substring(String.java:1963)[:1.8.0_131]
        at org.openhab.binding.mysensors.converter.MySensorsRGBWTypeConverter.fromString(MySensorsRGBWTypeConverter.java:27)
        at org.openhab.binding.mysensors.converter.MySensorsTypeConverter.stateFromChannel(MySensorsTypeConverter.java:33)
        at org.openhab.binding.mysensors.handler.MySensorsThingHandler.handleChildUpdateEvent(MySensorsThingHandler.java:275)
        at org.openhab.binding.mysensors.handler.MySensorsThingHandler.sensorUpdateEvent(MySensorsThingHandler.java:198)
        at org.openhab.binding.mysensors.internal.event.MySensorsEventRegister.lambda$4(MySensorsEventRegister.java:129)[190:org.openhab.binding.mysensors:2.2.0.201707241115]
        at java.lang.Iterable.forEach(Iterable.java:75)[:1.8.0_131]
        at org.openhab.binding.mysensors.internal.event.MySensorsEventRegister.notifyNodeUpdateEvent(MySensorsEventRegister.java:125)[190:org.openhab.binding.mysensors:2.2.0.201707241115]
        at org.openhab.binding.mysensors.internal.gateway.MySensorsGateway.handleSetReqMessage(MySensorsGateway.java:566)[190:org.openhab.binding.mysensors:2.2.0.201707241115]
        at org.openhab.binding.mysensors.internal.gateway.MySensorsGateway.handleIncomingMessage(MySensorsGateway.java:461)[190:org.openhab.binding.mysensors:2.2.0.201707241115]
        at org.openhab.binding.mysensors.internal.gateway.MySensorsGateway.messageReceived(MySensorsGateway.java:372)[190:org.openhab.binding.mysensors:2.2.0.201707241115]
        at org.openhab.binding.mysensors.internal.event.MySensorsEventRegister.lambda$1(MySensorsEventRegister.java:85)[190:org.openhab.binding.mysensors:2.2.0.201707241115]
        at java.lang.Iterable.forEach(Iterable.java:75)[:1.8.0_131]
        at org.openhab.binding.mysensors.internal.event.MySensorsEventRegister.notifyMessageReceived(MySensorsEventRegister.java:81)[190:org.openhab.binding.mysensors:2.2.0.201707241115]
        at org.openhab.binding.mysensors.internal.protocol.MySensorsAbstractConnection$MySensorsReader.run(MySensorsAbstractConnection.java:365)[190:org.openhab.binding.mysensors:2.2.0.201707241115]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_131]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_131]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_131]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_131]
        at java.lang.Thread.run(Thread.java:748)[:1.8.0_131]

I had no success at all trying to define the things via the things file. I described my setup and the problem here. (Short version: definition via node id doesn't seem to work for me and I have no idea what items/sitemaps to use to control the rgbw nodes).
Any help would be great (@TimO )

@Tommas said in Which microcontroller for Node:

Hi @LastSamurai

Thank you!

Which mini pro do you suggest? The 5V version?
What about the nano? It is about the same price as mini pro.

Have you got reliable buying source?

Thank you!
T

Thats really up to you and what sensors you want to use. My nodes are nearly all battery powered so I use 3.3V pro minis as these can be most efficient. Pro minis are a little cheaper most of the time but the nano has build in usb which makes it a little easier to work with. Use what you like more. They both use the same atmega328p so there is really no difference.
I just buy most of my stuff from aliexpress. Just find the cheapest search result from a seller that has many positive reviews. Has worked 99% of the time for me.

ESP8266 (something like nodeMCU) could be an easy alternative too if you have powerlines already. I still like the idea of not relying on wlan though (and using the nrf24l01).

Can't help you with all of it but:

• I guess the cheapest one: arduino pro mini. You don't need the usb from the mini if you have a programmer and the sensebender micros' energy saving features aren't needed if you power them directly. Having many sensors you could save some money this way
• I don't know about losses in the cables and stuff like that but beside powering leds/motors/... from the same source 5V is more than enough. Most sensors actually run fine with 3.3V
• Nice design is very subjective but ebay and asian stores like aliexpress have many many plastic and metal cases. Just browse a little until you find something you like.

Hope this helps a little

Ok, thank you!

I am currently trying to get my domoticz based network ported to openhab 2. I have installed the binding (2.2) and got openhab to connect to the serial gateway. I am struggling though to get it to use my existing nodes.

I mainly have several RGBW nodes I want to use. I am trying to configure this via the config files, not the paper ui.

Here is my .things file:

Bridge mysensors:bridge-ser:gateway [ serialPort="/dev/ttyUSB0", sendDelay=200 ] {
    /** define things connected to that bridge here */
  	rgbwLight LichtFenster [nodeID=5, childId=1]
  	rgbwLight LichtSchrank [nodeID=6, childId=1]
  	rgbwLight LichtWand [nodeID=7, childId=1]
  }

The ids are correct but they are shown as uninitialzed in the paper ui. Why is that?
When restarting one node it showed up in the paperui but as

mysensors:rgbwLight:gateway:rgbwlight_5_1

Also is this the right way to controll the lights:
.items:

Color LichtSchrank "Licht Schrank" <slider> ["Lighting"] { channel="mysensors:rgbwLight:gateway:LichtSchrank:rgbw" }
Color LichtFenster "Licht Fenster" <slider> ["Lighting"] { channel="mysensors:rgbwLight:gateway:rgbwlight_5_1:rgbw" }

.sitemap

sitemap lights label="Wohnzimmer" {

	Frame label="Licht" {
		Colorpicker item=LichtSchrank
		Switch item=LichtSchrank
	}

	Frame label="Licht" {
		Colorpicker item=LichtFenster
		Switch item=LichtFenster
	}
}

I can change the color (for the second one) but not switch them on/off. I also can't control the one only defined in the things file at all.
Thanks for any help, I am still trying to learn this stuff

I am not sure if this is already possible in some way but if so controllers (domoticz and openhab 2) doesn't seem to do it yet.

The idea is that other devices (like e.g. hues) can be instantly detected by controllers (by asking the bridge I guess?). I would love to see a similar feature for mysensors.
At the moment I have to restart every node when using a new controller so that they represent themselves. As far as I know the gateway has to keep a list of nodes in the network anyways for routing purposes. Or at least has seen any node at one point.

My idea would be to implement some kind of query that you can send to the gateway to make it return a list of all nodes on the network. That way one could connect the gateway to a new controller and instantly use every node in the network with that new controller (of course the controller has to support that feature).
It doesn't seem to hard to implement and this is the one thing thats not super easy to use with mysensors (yet). At least in my experience.

Is this already implemented somehow, or is there a technical reason why not?

@Sergio-Rius I am pretty sure the version 1.3 from the store still has the pins rotated (= wrong but you can fix it as described). There is a fixed version of the gerber files in my github repo that is linked to this project though. I just haven't ordered them from dirtyPCBs yet so they are not in the store (as I am still using the rest of the old ones).

@TimO Thank you. I installed the transport-serial feature (again... I had it installed for the last version of the binding already) and now its working.

@TimO I have a small problem here. I was trying to get into openhab (again) this time using your new 2.2 binding. I removed the old jar and installed the new one. I had also removed all things in the paper ui before. Afterwards I tried to add the gateway via things file again.

Bundle:list says:

190 | Installed |  80 | 2.2.0.201707241115     | MySensors Binding

but this things file:

Bridge mysensors:bridge-ser:gateway [ serialPort="/dev/ttyUSB0", sendDelay=200 ] {
    /** define things connected to that bridge here */
  }

Only results in an error message:

22:49:56.806 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'mysensors.things'
22:49:56.847 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model 'mysensors.things' is either empty or cannot be parsed correctly!
22:49:56.988 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'mysensors.things'

Any idea what I did wrong? The port is right I can receive messages via cat /dev/ttyUSB0.

PS also is there already a timeline for when you will be able to add this binding to the official openhab "store"?
PPS The binding also doesn't show up in the menu where you can scan for new things. Is there something more to do to install this new version? The old one was working.

Request is the way to go as far as i know. You also need to implement the method handling incoming messages though to work with the answer. There are some threads about requesting values from domoticz in this forum. (Haven't read them) but imo there are some values that can't be requested from domotizc so better check that and maybe change the variable type.

Imo in all cases the pulldown should be on the controlling pin (gate). Otherwise listen to @mfalkvidd

@NeverDie Have you tried something like this: https://ip.of.your.server/#/Dashboard ? Or with port and no HTTPS.

I am actually happy with domoticz. I have used it for about a year and its main advantage for was that it's very easy to learn and to use. Recently I discovered dzVents (which is now integrated in the domoticz beta) that allows for easier and more complex scripts. For now I was able to do anything I wanted in domoticz.
The UI isn't perfect (although openhaps is way worse imho) but it gets the job done.

I also tried to use openhab (2) earlier but thats a totally different beast. You can do awesome stuff but it's REALLY hard to get started. The new ui in openhab 2 looks great but its still a weird mix of using text files and the ui.
HA also looks great but I haven't tried it yet.

So overall I would start with domoticz and switch later if you are missing any features.

PS also domoticz updates (at least for features related to mysensors) seem to be implemented pretty slow. I have opened several tickets in their git where the answer was mostly: implemented on you own Which is fine (I dont pay them afterall) but other systems seem to be way more active.

As far as I know Mysensors is build to be used with a controller. I am using Mysensors with Domotiz and HA-bridge. That works very well with alexa to control my lights.

Ah perfect! Nice to hear that. I'll give home assistant a try then.

Hi, I am currently trying out several different controllers and saw Home Assistant in some youtube videos. It looked great and the features mentioned on the homepage as well as the huge number of integrations look very promising.
At least currently most of my "things" are MySensor nodes though and the list of supported types (from here) looks a little too small compared to domoticz, which I am using now.

Will all Mysensors types be added to home assistant? Most importantly for me: is there any way to control an RGBW mysensors node via home assistant? The type was not listet.

Thanks!

I already have (in a github issue). Didn't get any answer yet. I am currently trying to simply use some other type of sensor (as I just need to send an integer) but none of them have really worked yet.

Some really awesome winner projects!

@hek So I will get a coupon too (as I participated in the contest)? Did I get that right?

Well thats bad Thanks for the help though! I hope domoticz adds this feature soon

PS part of the problem might be that the value gets updated in the normal domoticz ui but in the hardware tab in the details of the gateway I still see no value at all for the sender child. Does anyone know if I am missing some code in my lua perhaps, or if this is a bug in domoticz or the mysensors integration?

Hi, I am currently working on a 433Mhz gateway. It is a mysensors node that has a 433Mhz sender and receiver. It presents two S_INFO/V_TEXT children: the sender and the receiver. The idea is that the receiver receives a message via 433Mhz and sends the code as text to the controller. The controller decides what to do and then sends back a text with the answer code to the node. The node than takes that code and sends it via 433Mhz.
My problem at the moment is that no message seems to get send to the node when I update the text value in domoticz. Does anyone have an idea why? I saw other people sending messages from the controller to a node.

Here is my code:

// define radio stuff
#define MY_RADIO_NRF24
#define MY_BAUD_RATE 9600
#define MY_DEBUG    // Enables debug messages in the serial log
//#define MY_NODE_ID 13

// add signing stuff
//#define MY_SIGNING_SOFT // Enables software signing
//#define MY_SIGNING_REQUEST_SIGNATURES // Always request signing from gateway
//#define MY_SIGNING_SOFT_RANDOMSEED_PIN 7 // floating pin for randomness
//#define MY_DEBUG_VERBOSE_SIGNING

#include <EEPROM.h>
#include <SPI.h>
#include <MyConfig.h>
#include <MySensors.h>
#include <Vcc.h>
#include <RCSwitch.h>

const long RECEIVER_PIN = 0;
const long SENDER_PIN = 7;
const long DEBOUNCE = 500;
const long CHILD_RECEIVER = 0;
const long CHILD_SENDER = 1;


RCSwitch wirelessSwitch = RCSwitch();


void presentation()
{
  sendSketchInfo("433 Wireless Gateway", "29062017");

  present(CHILD_RECEIVER, S_INFO); // able to receive text
  present(CHILD_SENDER, S_INFO); // able to send text
}

void setup() {
  wirelessSwitch.enableReceive(RECEIVER_PIN); // Receiver on interrupt 0 => that is pin #2
  wirelessSwitch.enableTransmit(SENDER_PIN);  // Sender on pin 7
  Serial.println("Started listening on pin 2 for incoming 433Mhz messages");
}

void loop() {
  if (wirelessSwitch.available()) {
  	// for testing
    //output(wirelessSwitch.getReceivedValue(), wirelessSwitch.getReceivedBitlength(), wirelessSwitch.getReceivedDelay(), wirelessSwitch.getReceivedRawdata(),wirelessSwitch.getReceivedProtocol());

    unsigned long received_val = wirelessSwitch.getReceivedValue();

    Serial.print("Received 433Mhz message: ");
    Serial.println(received_val);

    send(MyMessage(CHILD_RECEIVER, V_TEXT).set(received_val));

    // software debounce
    wait(DEBOUNCE);
    wirelessSwitch.resetAvailable();
  }
}

void receive(const MyMessage &message) {
  Serial.print("Sensor: "); Serial.print(message.sensor); Serial.print(", Message: "); Serial.println(message.getString()); 
  if (message.type == V_TEXT) { 
    if (message.sensor == CHILD_SENDER) {
      Serial.println("Sending message via 433Mhz");
      char * messageContent = strdup(message.getString());
      wirelessSwitch.send(messageContent);
    }
  }
}

On the domoticz side I have a piece of lua code (using dzVents) that just copies the receiver value to the sender

return {
        active = true,
        on = {
            '433Receiver'
        },
        execute = function(domoticz, sensor)

            domoticz.log("Received from gateway " .. sensor.state)
            -- check sensor values 
            domoticz.devices['433Sender'].updateText(sensor.state)
        end
    }

and its working in the domoticz ui... Is this a domoticz error or am I missing something in my code?

@Terrence The box is around 10cm by 6cm. There is an new image in the openhardware project.

I also added this image and two others (for my third version of the gateway) to the project. This one has a 433 Mhz sender and receiver on it and acts as a gateway between 433 Mhz and the MySensors protocol. That way I can control some outlets and buttons.

I am still using several temp/hum sensor and they are running great I also have just added code and pictures for my newly build light sensor (using an LDR).

I have just added picture of my next build: I have finished the ESP8266 version of the gateway

By the way has someone running openhab together with an echo (alexa)? I am currently trying to use that combination and at least with the RGBW nodes there seems to be no reaction (yet) to the commands.

@TimO So I finally got around to testing the RGBW version of the plugin. I tested it with one sensor (light and the battery voltage) and an RGBW node.

Results:

• RGBW color settings works well. Its a message of lengths 8 (e.g. 00ff5100) instead of the 9 from domoticz (#00ff5100). So I had to change my node's code. But your solution looks cleaner, so I guess thats fine What didn't work are all the other values beside "color". As you can see I changed the variable 1-4 and it gets send to the node as message type 24-27, which are custom variables... why did you use these?
• RGBW on/off did not work. The "status" button does nothing. Log below. Would be nice to have a button to send on/off commands to the nodes.
• Light and Voltage sensors seem to work just fine

By the way, short question about openhab 2: what is the difference between things and items? Seems like items/sitemaps are used in the "old" frontends to display sensors/actors. Are things the same for the new paperUI? I have just used that one yet. And why do I have to declare the gateway in a file while the rest is auto discovered (also it seems like some of you also added their sensors to the file with the gateway definition)?
Seems to be hard to find up-to-date easy information on these things, so thanks in advance for an explanation.

Log from the status button:

22:55:02.378 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'mysensors_rgbwLight_gateway_rgbwlight_10_1_status' received command OFF
22:55:02.402 [WARN ] [ensors.handler.MySensorsThingHandler] - Variable not found, cannot handle command for thing mysensors:rgbwLight:gateway:rgbwlight_10_1 of type status
22:55:02.440 [INFO ] [marthome.event.ItemStateChangedEvent] - mysensors_rgbwLight_gateway_rgbwlight_10_1_status changed from ON to OFF

I guess the easiest way would be to connect a wire to the button on your remote control and directly control that instead of tinkering with the internals of the control
PS Also have you considered just sending Teufel an email and asking them what technology their remote is using?

OK newest update: my gateway stop working at all today. I did not even get any reactions on the serial port. So I tried to reprogram it => no reaction either.
I had to manually reflash the bootloader and load the normal gateway sketch (without the 433Mhz stuff again). So I guess there is some kind of overflow somewhere caused by the code. The normal gateway sketch runs without any problems. No idea where the error is yet.

Wow, great! Its alway nice to see others using my work too. Your code improvement seem to be very helpful too.
I have most recently also integrated this directly into my gateway build (see here). I am still struggling with code there though.

@Yveaux I finally got to do some more testing. Its really strange. The voltage regulator problem never occurred again (and its an pa+lna module so the power usage is a little higher).

I did lots of tests and this is what I found:

• while I just ignore the buttons everything is working fine (no buttons pressed)
• if I press a button that does nothing on the controller everything still seems to be working just fine most of the time. Sometimes version 3 still happens
• if I press a button that runs a script on the controller everything seems to stop working after some seconds, at least most of the times. The gateway becomes unresponsive (sometimes it restarts) and the leds (RX/TX) stay on. The only thing that helps is a manual restart of the gateway

The script that is running works just fine with my external 433Mhz to Mysensors gateway and simply switches on a rgbw node if the button gets pressed.

I am out of ideas currently. Does someone have another idea how to fix or even how to test to get to the actual problem?

Ah thank you for the hint. I have changed the description. I had only been using signing so far so I overlooked that detail.

I have finally found the time to upload the project here. I really like it so far although I am still trying to make it even better

@RVMRVM Sorry I haven't had the time to test anything yet (was working on another project). Might take me a while to get to.

Create a mysensor node with 3 switches for the 3 leds. Then use domoticz to script it so that the timings are right.

Yes use sleep() . Take a look at the api.

Has anyone an idea how to fix this problem with local sensors?

So I have done some more debugging and have testend the 433Mhz receiver by flashing the advanced demo sketch from the RC library. Everything is working fine that way. Then I added a better receiver and tried again. Now the my sketch that I have postet above worked just fine (and send the wireless key's presses to my controller).

I did get another problem with that one though: the gateway kept crashing while sending/receiving message from other mysensor nodes. Randomly switching on some lights worked while others didn't. Also after some tries the RX/TX leds on my boards just stayed on. Only a hard reset of the gateway can get it in working condition again. After restarting suddenly some of the messages seem to come through (lights turning on, messages in the log of the controller). Also the voltage converter on the board got very hot, so I am guessing the radio was non-stop sending.
Reflashing the normal gateway sketch without any local sensors makes the gateway work without any problems again.

So the local sensor part must somehow interfere with the normal gateway stuff. Any idea how, or how to fix this? I have my 433Mhz bridge mysensors node running nearly the same code (just without the gateway part, its just a normal node) running without such problems...

@dirkc Thanks for your answer!
I will try you code, but doesn't mine do the same?

send(
  MyMessage(i, V_TRIPPED) // <-- same as msgRelay.setSensor(CHILD_ID_RELAY1+i)?!
  .set(true));

I have build a serial gateway based on the arduino nano that has a 433Mhz receiver connected to it. I used the same receiver connected to an arduino uno with the rc-switch library (advanced receive example) and was able to receive a signal send by a switch.
I have now connected that receiver to pin 2 (int 0) of the nano and uploaded this sketch:

#define MY_DEBUG 
#define MY_DEBUG_VERBOSE_SIGNING

// Enable leds
#define MY_DEFAULT_LED_BLINK_PERIOD 300
#define MY_DEFAULT_ERR_LED_PIN 4
#define MY_DEFAULT_TX_LED_PIN 5
#define MY_DEFAULT_RX_LED_PIN 6

#define MY_SIGNING_SOFT // Enables software signing
#define MY_SIGNING_REQUEST_SIGNATURES // Always request signing from nodes that support it
#define MY_SIGNING_SOFT_RANDOMSEED_PIN 7 // floating pin for randomness


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

// Enable serial gateway
#define MY_GATEWAY_SERIAL

// Define a lower baud rate for Arduino's running on 8 MHz (Arduino Pro Mini 3.3V & SenseBender)
#if F_CPU == 8000000L
#define MY_BAUD_RATE 38400
#endif

#include <SPI.h>
#include <MySensors.h>  
#include <RCSwitch.h>

RCSwitch wirelessSwitch = RCSwitch();
const int RECEIVER_PIN = 0;

// add the decimal codes for your switches here
unsigned long switches[] = {12587348, 12587346, 12587345};
int numberOfSwitches = 3;

void setup() { 
  // Setup locally attached sensors
  wirelessSwitch.enableReceive(RECEIVER_PIN);  // Receiver on interrupt 0 => that is pin #2
}

void presentation() {
 // Present locally attached sensors 
  sendSketchInfo("433 Wireless + Serial Gateway", "13052017");
  
  for (int i = 0; i < numberOfSwitches; i++) {
    present(i, S_DOOR); // s_door has tripped, s_binary might be a choice too 
  }
}

void loop() { 
  // Send locally attached sensor data here 
  if (wirelessSwitch.available()) {

    unsigned long received_val = wirelessSwitch.getReceivedValue();

    //Serial.print("Pressed button ");
    //Serial.print(received_val);

    for (int i = 0; i < numberOfSwitches; i++) {
      if (received_val == switches[i]) {
        //Serial.print(". Recognized! Its button ");
        //Serial.println(i);
        send(MyMessage(i, V_TRIPPED).set(true));
      }
    }

    // software debounce
    wait(500);
    wirelessSwitch.resetAvailable();
  }
}

I wasn't able to get any reaction to the switch this time though. Is there any obvious error in my sketch? Or is it not possible to use an interrupt driven lib on the gateway? I had a similar setup on a "normal" mysensors node and that one is working without problems.

PS Is there a way to enable normal serial.println() on the gateway for testing? At the moment I have no clue if the gateway receives the buttons presses at all because the (commented) print's are just ignored.

I would actually not do this in a node but in the controller (at least if I get what you are trying to do right). I have done that with some scripting in domoticz. I have lights that that are switched on for 5 minutes when motion is detected and shut down 5 minutes after the last motion stopped. Motion sensor and rgbw controller are different mysensor nodes. Much more versatile then hardcoding this in you node's code.

@gohan Ah ok, sure! I haven't used a controller without auto-assignment yet

Nice project! The code looks really clean, I might just copy some of that for the next version of firmware for my rgb(w) node. Have you looked into how to fix the non linear fading when using pwm?
I had started to but never finished that.

I just bought an ATX breakout board that can be connected to the 24 pin cable from an old power supply. It has bindings post with gnd, 3.3V, 5V and 12V. Very easy (and safe) to use and set up.

@sundberg84 Thanks, nice to know! Why the static node ids though? I get the static parent id but a node only needs to get the id once anyways, right?

I will try to make due with one high power gateway (+ possible repeaters) then. Thanks for the feedback though!
@gohan 433Mhz will be used too to control some old outlets. But most of my pcbs are designed for the nrf24 so I'll stay with that for now.

Google for "DynDNS" systems and your router (+ possible how to open ports). But this really has nothing to do with mysensors.

Hi, I am currently planning a bigger mysensors installation for a whole house (3 floors, cellar, garden...) and I was wondering about the best way to set this up. The walls in this house seem to isolate radiowaves pretty well (at least for wifi which uses the same frequency) so I am likely to at least 2-3 "gateways" for mysensors (maybe one per floor).
Whould you recommend using one gateway + repeater, or different (wlan) gateways per floor? Repeater related problems seem to be hard to debug but multiple gateways might cause problems with nodes (do they? can a node auto-connect to another gateway if it loses connection to one?).

For now I plan to use domoticz as a controller if that makes any difference. Any other tips/ideas for settings up slightly bigger installations with dozens of nodes?

For now this was just a components + wires solution but as I had some positive feedback and I am planing a new (bigger) installation of mysensors somewhere else I have created a pcb for my gateway. I have ordered it on dirtypcbs 2 days ago... so it will reach me in 2-3 weeks I guess.
I'll create a openhardware.io project once I have tested it.

Does someone know an easy to use software to create a printable (on paper for now, maybe on film/foil later) cover for the housing that adds labels and perhaps some nice graphics to the outside of the case? I am planning to do that next...