@insectteam I did not understand what you mean about the diods. Could you please clarify or show with pictures?
I have not used the device since it does not feel saft to put in an enclosure if the diods burns hot.
And also, please share your stl files for the enclosure, here or on thingiverse
@tbowmo said in node-red-contrib-mysensors release thread:
That being said, if you only need to convert your serial mysensors gateway into mqtt, I do have a small python script that I use for that particular case, as my nodered instance can't access the serial Ports from my docker swarm setup. So this script is running besides everything else. I can post it tomorrow if interested, as my pc is closed for the night now.
/ Thomas
I'd love to try the script! /Magnus
@tbowmo I feel a little confused on how to use this node-red plugin. Is this something like "a node-red plug-in framework", but you have to invent the wheel yourself kind of solution?
I have just opted for the Home assistant (hass.io) system as the hub for my home automation.
Home assistant, according to documentation, is mysensors enabled, but compared to other add-ons, like zigbee2mqtt, zwave2mqtt, the mysensors implementaton is like a child's tricycle, while the others are sports cars.
The zigbee2mqtt, you just turn on and off the IKEA light buld six times and it is added, whereas the mysensors you have to type configuration files and have limited graphical administration possibilities.
So I thought, what if the mysensors could talk to mqtt and get into home assistant that way (my gateway is serial).
I understand the node-red implementation enables you to decode the messages as you like, but do I really need to invent how it should decode it and send it to mqtt?
Are there any ready to use implementations of the plug.in?
Could it support "auto discovery"? So you just have to turn the device on, and voila, it appears in home assistant (if mqtt auto discovery is turned on)?
@jens-jensen said in [Solved] Device and gateway see each other, but not regestering:
@magpern glad to see you got it fixed, however I don't think wifi channel 11 interferes with channel 76, which is at 2476 MHz.
Maybe there are some other sources of interference on nrf channel 76 in your environment?
I don't know. Wifi channel 12 is in the channel 76 nrf rage though, maybe they bleed?
Except from getting a Mesh network and three pairs of bluetooth headphones there is nothing new.
@mfalkvidd said in What multimeter should i wish for?:
@magpern totally agree. Myplan is to work through this playlist so I learn how to use mine. https://www.youtube.com/playlist?list=PLwOVNTOStjiCmxCFX91MZYP7wL8dfy1tB
Today Iearned to save screen shots and csv files to a usb stick. No snow, but lots of rain today
Nice.. "a snowy day" is more realistic then a "rainy day", but I guess, a snowy day means playing with the kids in the snow.. rain they don't care for.. so I guess "a rainy day" is more realistic after all.
It was indeed a rainy day, so I got 3 of my sonoff up and running with mqtt and domoticz. Next is to try with home assistant. Still waiting for some aliexpress stuff to continue with my MySensors devices, but I guess that will be "some snowy day"
Maybe you want to check how stable signals are. Then you don't need a multimeter, you need an oscilloscope. Example: https://www.conrad.se/p/rigol-ds1054z-digitalt-oscilloskop-50-mhz-1392205
I have one... just don't know how to use it... too many buttons.... but I'll look in to that one snowy day
@mfalkvidd Thank you for you detailed reply. The question actually arose spontaneously. I said to my wife.. I know what I want as a present, a new better multimeter. Then she saw me write here, and started asking questions about what forum I wrote in (= she will look here to find the answer and buy it for me)
But, as you state.. what do I need it for? Measuring some kind of micro current is one thought. And measuring capacitors.
Will my current one work for me, most likely, it has for many years and 95% of the time it is to look for shorts. Do I need a new one..no.
I looked in your thread about the multimeters and I think the VC99 seams to be a good one. Price of 28 USD is very good too.
I'll look into the uCurrent too, that looks cool!
Today i have this cheap multimeter
Birthday is coming up... which much better should i wish for?
@stormy said in 
MySensors InCan double light switch:
No, a have no problems with sketch.
It looks like some problems with radio communication.
It was. I used the default channel and apparently it was too noicy. Changed to another channel and it worked fine!
Diodes are only for protection transistor from reverse voltage spikes. Diodes never should be even warm. Something is wrong. You can test this without diodes.
Somehow, when powered by 5V from the FTDI, the device got hot. The Hi-link maybe did not like to get power from the FTDI? The diodes got super hot, and so did the Hi-link. I removed the diodes and could continue. Today, I tried 230V. It didn't work, the thermo fuse was busted, probably from the overheating earlier.
I shorted the fuse (temporarily) and everything worked fine. Hi-link was still alive and supplied 5 Volts
And this brings me to my question...
What kind of range do you get with this device? And how accurate is it?
I tried 50 centimeters from the gateway and got a fairly decent hit rate on the on/off from domoticz.
I moved the device to about 3-4 meters, and maybe got 50% hit rate. It was almost line of sight.
If I toggle the on/off from Domotics, with 3 seconds apart, I got like 10% hit rate, maybe every 10th click toggled the relay.
Placing it inside a wall sounds like a "no go" if almost line of sight doesn't work 100%.
What is your experience?
@yveaux said in Ikea Molgan Hack:
@magpern the instructions on openhardware.io state that the Molgan must be battery powered while programming:
Well, then I can confirm that you don't have to power the Molgan from batteries just for programming. Burning the bootloader works fine with just power from the ISP port and programming it through FTDI works fine if power comes from the FTDI.
What I found wierd is that the atmega328 had power, the radio had power, it wrote debug messages to the FTDI - when powered through the FTDI, it send radio messages etc, but it just did not receive messages.
Messages where not received until I supplied power to the + / - pads (battery pads).
I did read the instructions on openhardware.io, but I didn't follow then to the t. 
@pepson said in [SOLVED] Sensbender Gateway gives a lot of "hu":
@magpern
But mysensors newer than 2.2.0 has problems with radio Rfm69hw.
That I don't know anything about. I don't have any Rfm69w for the moment, but I know I ran a rfm69 directly of a raspberry pi about 5 month ago ant that worked fine. And that was the development branch, so more than 2.2.0
@pepson said in Sensebender Gateway:
@magpern
But get this board to Arduino IDE?
Boards / Boards manager...
search for sensebender
You might have to
File / Preferences / Additional Board manager URLs
add
https://raw.githubusercontent.com/mysensors/ArduinoBoards/master/package_mysensors.org_index.json
I have finally finished the PCB of two Molgans (withou the actual Molgan). I spent several hours trying to figure out why the sensor did not register with Domoticz.
I had it plugged in to the FTDI which powered it, but nothing... device talked, gateway listened, but device ignored responses from gateway.
I just dealt with with problem on some other nodes, and it was the channel id that was inappropriate. But now I had the correct channel id, and still the same problem.
I checked for shorts, but nothing.
Measured the voltage. It says 3v3 on the FTDI but was actually 3v5. But that should be ok.
Finally I figured, power it through the + and - pads instead of FTDI. So, I set up a 3v3 power supply.. and voila.. it registered with the gateway.
I don't understand why, power is power... but apparently power is different.
So, for future builders, if you run this, you know what I did.
Need to head to IKEA and get some more Molgans!!
@pepson said in Sensebender Gateway:
hi
when i try compile sketch only with change radio to rfm69hw i have this:
Arduino:1.8.9 (Windows 10), PÅ‚ytka:"Arduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)"SensebenderGatewaySerial:95:26: error: 'LED_BLUE' was not declared in this scope
You cannot use the SensebenderGatewaySerial sketch on an Atmega2560. The SensbenderGatewaySerial sketch is for the SAMD board called Sensebender Gateway.
If you have the real Sensebender Gateway you should use this one
@pepson said in [SOLVED] Sensbender Gateway gives a lot of "hu":
Please help me what i do wrong...and how resolved this problem.
It is the exact same problem as I had. Do what @tekka said. Either put in the code he suggested, or git clone the development branch. The development branch works fine, the "hu" will go away
And if git clone is to difficult. Download the dev branch github as zip, unzip it and replace the entire "MySensors" folder on your computer. Exactly where it is, I don't know. It's in the library folder where Arduino is installed
[SOLVED]
After a one-on-one with @tekka we found that the problem was a very simple one.
The default channel 76 was noisy. I change channel to 90 and the Gateway and device could talk two-way communication
I did a WIFI scan an see that wifi 2.4g channel 11 is used by someone close to me (I am channel 2)
Wifi Channel 11 is almost in the mid of channel 76 (nRF24)
@tekka said in Device and gateway see each other, but not regestering:
@magpern One more thing - please re-run the test with my sketch uploaded to your node and adding
#define MY_NODE_ID 100before the MySensors include, and an unmodified GW serial sketch from the example folder. Please post again both logs here.
Device
Opening port
Port open
__ __ ____
| \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| | | | |_| |___| | __/ | | \__ \ _ | | \__ \
|_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/
|___/ 2.3.2-beta
18 MCO:BGN:INIT NODE,CP=RNNNA---,FQ=8,REL=7,VER=2.3.2-beta
28 TSM:INIT
30 TSF:WUR:MS=0
32 THA:INIT
32 RF24:INIT:PIN,CE=9,CS=10
36 RF24:SBY
36 RF24:WBR:REG=0,VAL=14
45 RF24:WBR:REG=3,VAL=3
47 RF24:WBR:REG=4,VAL=95
49 RF24:WBR:REG=5,VAL=76
53 RF24:WBR:REG=6,VAL=7
55 RF24:WBR:REG=29,VAL=4
57 RF24:RBR:REG=29,VAL=4
59 RF24:RBR:REG=6,VAL=7
63 RF24:RBR:REG=5,VAL=76
65 RF24:WBR:REG=2,VAL=2
67 RF24:WBR:REG=1,VAL=0
69 RF24:WBR:REG=28,VAL=3
73 RF24:FRX
73 RF24:FTX
75 RF24:WBR:REG=7,VAL=112
77 TSM:INIT:TSP OK
79 TSM:INIT:STATID=100
83 THA:SAD:ADDR=100
86 RF24:WBR:REG=2,VAL=3
88 RF24:WBR:REG=1,VAL=1
90 RF24:STL
92 RF24:WBR:REG=0,VAL=15
94 RF24:WBR:REG=10,VAL=100
96 TSF:SID:OK,ID=100
100 TSM:FPAR
100 THA:SND:MSG=6464FF020307FF
104 RF24:SPL
106 RF24:WBR:REG=0,VAL=14
108 RF24:OWP:RCPT=255
110 RF24:WBR:REG=10,VAL=255
114 RF24:WBR:REG=16,VAL=255
116 RF24:TXM:TO=255,LEN=7
118 RF24:FTX
120 RF24:WBR:REG=4,VAL=80
124 RF24:WBR:REG=7,VAL=112
129 ?RF24:TXM:MAX_RT
131 RF24:FTX
133 RF24:WBR:REG=4,VAL=95
135 RF24:STL
137 RF24:WBR:REG=0,VAL=15
139 RF24:WBR:REG=10,VAL=100
141 THA:SND:MSG LEN=7,RES=1
145 ?TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2154 !TSM:FPAR:NO REPLY
2156 TSM:FPAR
2158 THA:SND:MSG=6464FF020307FF
2160 RF24:SPL
2162 RF24:WBR:REG=0,VAL=14
2164 RF24:OWP:RCPT=255
2168 RF24:WBR:REG=10,VAL=255
2170 RF24:WBR:REG=16,VAL=255
2174 RF24:TXM:TO=255,LEN=7
2177 RF24:FTX
2179 RF24:WBR:REG=4,VAL=80
2183 RF24:WBR:REG=7,VAL=112
2187 ?RF24:TXM:MAX_RT
2189 RF24:FTX
2191 RF24:WBR:REG=4,VAL=95
2193 RF24:STL
2195 RF24:WBR:REG=0,VAL=15
2197 RF24:WBR:REG=10,VAL=100
2201 THA:SND:MSG LEN=7,RES=1
2203 ?TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4212 !TSM:FPAR:NO REPLY
4214 TSM:FPAR
4216 THA:SND:MSG=6464FF020307FF
4218 RF24:SPL
4220 RF24:WBR:REG=0,VAL=14
4222 RF24:OWP:RCPT=255
4227 RF24:WBR:REG=10,VAL=255
4229 RF24:WBR:REG=16,VAL=255
4233 RF24:TXM:TO=255,LEN=7
4235 RF24:FTX
4237 RF24:WBR:REG=4,VAL=80
4241 RF24:WBR:REG=7,VAL=112
4245 ?RF24:TXM:MAX_RT
4247 RF24:FTX
4249 RF24:WBR:REG=4,VAL=95
4251 RF24:STL
4253 RF24:WBR:REG=0,VAL=15
4255 RF24:WBR:REG=10,VAL=100
4259 THA:SND:MSG LEN=7,RES=1
4261 ?TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6273 !TSM:FPAR:NO REPLY
6275 TSM:FPAR
6277 THA:SND:MSG=6464FF020307FF
6279 RF24:SPL
6281 RF24:WBR:REG=0,VAL=14
6283 RF24:OWP:RCPT=255
6287 RF24:WBR:REG=10,VAL=255
6289 RF24:WBR:REG=16,VAL=255
6293 RF24:TXM:TO=255,LEN=7
6295 RF24:FTX
6297 RF24:WBR:REG=4,VAL=80
6301 RF24:WBR:REG=7,VAL=112
6305 ?RF24:TXM:MAX_RT
6307 RF24:FTX
6309 RF24:WBR:REG=4,VAL=95
6311 RF24:STL
6313 RF24:WBR:REG=0,VAL=15
6316 RF24:WBR:REG=10,VAL=100
6320 THA:SND:MSG LEN=7,RES=1
6322 ?TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8331 !TSM:FPAR:FAIL
8333 TSM:FAIL:CNT=1
8335 TSM:FAIL:DIS
8337 TSF:TDI:TSL
8337 RF24:SLP
8339 RF24:WBR:REG=0,VAL=12
18345 TSM:FAIL:RE-INIT
18348 TSM:INIT
18350 THA:INIT
18350 RF24:INIT:PIN,CE=9,CS=10
18354 RF24:SBY
18356 RF24:WBR:REG=0,VAL=14
18364 RF24:WBR:REG=3,VAL=3
18366 RF24:WBR:REG=4,VAL=95
18368 RF24:WBR:REG=5,VAL=76
18372 RF24:WBR:REG=6,VAL=7
18374 RF24:WBR:REG=29,VAL=4
18378 RF24:RBR:REG=29,VAL=4
18380 RF24:RBR:REG=6,VAL=7
18384 RF24:RBR:REG=5,VAL=76
18386 RF24:WBR:REG=2,VAL=2
18391 RF24:WBR:REG=1,VAL=0
18393 RF24:WBR:REG=28,VAL=3
18395 RF24:FRX
18397 RF24:FTX
18399 RF24:WBR:REG=7,VAL=112
18403 TSM:INIT:TSP OK
18405 TSM:INIT:STATID=100
18407 THA:SAD:ADDR=100
18409 RF24:WBR:REG=2,VAL=3
18413 RF24:WBR:REG=1,VAL=1
18415 RF24:STL
18417 RF24:WBR:REG=0,VAL=15
18421 RF24:WBR:REG=10,VAL=100
18423 TSF:SID:OK,ID=100
18425 TSM:FPAR
18427 THA:SND:MSG=6464FF020307FF
18432 RF24:SPL
18434 RF24:WBR:REG=0,VAL=14
18436 RF24:OWP:RCPT=255
18440 RF24:WBR:REG=10,VAL=255
18442 RF24:WBR:REG=16,VAL=255
18446 RF24:TXM:TO=255,LEN=7
18448 RF24:FTX
18450 RF24:WBR:REG=4,VAL=80
18456 RF24:WBR:REG=7,VAL=112
18458 ?RF24:TXM:MAX_RT
18460 RF24:FTX
18462 RF24:WBR:REG=4,VAL=95
18466 RF24:STL
18466 RF24:WBR:REG=0,VAL=15
18470 RF24:WBR:REG=10,VAL=100
18475 THA:SND:MSG LEN=7,RES=1
18477 ?TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20486 !TSM:FPAR:NO REPLY
20488 TSM:FPAR
20490 THA:SND:MSG=6464FF020307FF
20492 RF24:SPL
20494 RF24:WBR:REG=0,VAL=14
20498 RF24:OWP:RCPT=255
20500 RF24:WBR:REG=10,VAL=255
20504 RF24:WBR:REG=16,VAL=255
20506 RF24:TXM:TO=255,LEN=7
20510 RF24:FTX
20512 RF24:WBR:REG=4,VAL=80
20516 RF24:WBR:REG=7,VAL=112
20518 ?RF24:TXM:MAX_RT
20523 RF24:FTX
20525 RF24:WBR:REG=4,VAL=95
20527 RF24:STL
20529 RF24:WBR:REG=0,VAL=15
20531 RF24:WBR:REG=10,VAL=100
20535 THA:SND:MSG LEN=7,RES=1
20537 ?TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
22546 !TSM:FPAR:NO REPLY
22548 TSM:FPAR
22550 THA:SND:MSG=6464FF020307FF
22552 RF24:SPL
22554 RF24:WBR:REG=0,VAL=14
22558 RF24:OWP:RCPT=255
22560 RF24:WBR:REG=10,VAL=255
22564 RF24:WBR:REG=16,VAL=255
22566 RF24:TXM:TO=255,LEN=7
22571 RF24:FTX
22573 RF24:WBR:REG=4,VAL=80
22577 RF24:WBR:REG=7,VAL=112
22579 ?RF24:TXM:MAX_RT
22583 RF24:FTX
22585 RF24:WBR:REG=4,VAL=95
22587 RF24:STL
22589 RF24:WBR:REG=0,VAL=15
22591 RF24:WBR:REG=10,VAL=100
22595 THA:SND:MSG LEN=7,RES=1
22597 ?TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
24608 !TSM:FPAR:NO REPLY
24610 TSM:FPAR
24612 THA:SND:MSG=6464FF020307FF
24614 RF24:SPL
24616 RF24:WBR:REG=0,VAL=14
24621 RF24:OWP:RCPT=255
24623 RF24:WBR:REG=10,VAL=255
24627 RF24:WBR:REG=16,VAL=255
24629 RF24:TXM:TO=255,LEN=7
24633 RF24:FTX
24635 RF24:WBR:REG=4,VAL=80
24639 RF24:WBR:REG=7,VAL=112
24641 ?RF24:TXM:MAX_RT
24645 RF24:FTX
24647 RF24:WBR:REG=4,VAL=95
24649 RF24:STL
24651 RF24:WBR:REG=0,VAL=15
24653 RF24:WBR:REG=10,VAL=100
24657 THA:SND:MSG LEN=7,RES=1
24659 ?TSF:MSG:SEND,100-100-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
26671 !TSM:FPAR:FAIL
26673 TSM:FAIL:CNT=2
26675 TSM:FAIL:DIS
26677 TSF:TDI:TSL
26679 RF24:SLP
26681 RF24:WBR:REG=0,VAL=12
Port closed
Gateway
Opening port
Port open
0;255;3;0;9;56706 MCO:BGN:INIT GW,CP=RNNGS---,FQ=48,REL=7,VER=2.3.2-beta
0;255;3;0;9;56735 TSF:LRT:OK
0;255;3;0;9;56736 TSM:INIT
0;255;3;0;9;56737 TSF:WUR:MS=0
0;255;3;0;9;56742 TSM:INIT:TSP OK
0;255;3;0;9;56743 TSM:INIT:GW MODE
0;255;3;0;9;56743 TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;56743 MCO:REG:NOT NEEDED
0;255;3;0;14;Gateway startup complete.
0;255;0;0;18;2.3.2-beta
0;255;3;0;9;56744 MCO:BGN:STP
0;255;3;0;9;56744 MCO:BGN:INIT OK,TSP=1
0;255;3;0;9;56744 TSM:READY:NWD REQ
0;255;3;0;9;56747 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
0;255;3;0;9;71425 TSF:MSG:READ,100-100-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;71425 TSF:MSG:BC
0;255;3;0;9;71425 TSF:MSG:FPAR REQ,ID=100
0;255;3;0;9;71426 TSF:PNG:SEND,TO=0
0;255;3;0;9;71426 TSF:CKU:OK
0;255;3;0;9;71426 TSF:MSG:GWL OK
0;255;3;0;9;72225 !TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;73459 TSF:MSG:READ,100-100-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;73459 TSF:MSG:BC
0;255;3;0;9;73459 TSF:MSG:FPAR REQ,ID=100
0;255;3;0;9;73460 TSF:CKU:OK,FCTRL
0;255;3;0;9;73460 TSF:MSG:GWL OK
0;255;3;0;9;74245 !TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;75493 TSF:MSG:READ,100-100-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;75493 TSF:MSG:BC
0;255;3;0;9;75494 TSF:MSG:FPAR REQ,ID=100
0;255;3;0;9;75494 TSF:CKU:OK,FCTRL
0;255;3;0;9;75494 TSF:MSG:GWL OK
0;255;3;0;9;76265 !TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;77529 TSF:MSG:READ,100-100-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;77530 TSF:MSG:BC
0;255;3;0;9;77530 TSF:MSG:FPAR REQ,ID=100
0;255;3;0;9;77530 TSF:CKU:OK,FCTRL
0;255;3;0;9;77530 TSF:MSG:GWL OK
0;255;3;0;9;78291 !TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;89535 TSF:MSG:READ,100-100-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;89536 TSF:MSG:BC
0;255;3;0;9;89536 TSF:MSG:FPAR REQ,ID=100
0;255;3;0;9;89536 TSF:PNG:SEND,TO=0
0;255;3;0;9;89537 TSF:CKU:OK
0;255;3;0;9;89537 TSF:MSG:GWL OK
0;255;3;0;9;90015 !TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;91572 TSF:MSG:READ,100-100-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;91572 TSF:MSG:BC
0;255;3;0;9;91573 TSF:MSG:FPAR REQ,ID=100
0;255;3;0;9;91574 TSF:CKU:OK,FCTRL
0;255;3;0;9;91574 TSF:MSG:GWL OK
0;255;3;0;9;92042 !TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;93608 TSF:MSG:READ,100-100-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;93609 TSF:MSG:BC
0;255;3;0;9;93609 TSF:MSG:FPAR REQ,ID=100
0;255;3;0;9;93609 TSF:CKU:OK,FCTRL
0;255;3;0;9;93609 TSF:MSG:GWL OK
0;255;3;0;9;94065 !TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;95647 TSF:MSG:READ,100-100-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;95647 TSF:MSG:BC
0;255;3;0;9;95648 TSF:MSG:FPAR REQ,ID=100
0;255;3;0;9;95648 TSF:CKU:OK,FCTRL
0;255;3;0;9;95648 TSF:MSG:GWL OK
0;255;3;0;9;96093 !TSF:MSG:SEND,0-0-100-100,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
Port closed
@tekka said in Device and gateway see each other, but not regestering:
@magpern said in Device and gateway see each other, but not regestering:
I actually don't think the device and the gateway actively talk. It is more like the Gateway is listening, but not talking.
In your first post you mentioned:
I have altered the device sketch to just have the bare minimum. The gateway works with other devices.
So you can confirm that the sensebender GW communicates with other nodes? I'd like to narrow down the issue to the actual node.
Yes, that was 3 days ago. I have been trying for 3 days. I don't have many MySensors devices. But, three days ago, I was finished with the temp sensor device this and they all worked fine.
However, a temp sensor in passive mode with a set node id and it is giving the gateway data, data that shows up in eg. Domoticz. At that time I thought the gateway and device worked fine.
I continued to build two more devices, regular atmega328 devices. One is a relay with buttons. The relay is not passive and one should be able to alter its state from eg. Domoticz. So it requires two-way communication.
And it is this part that fail.
I actually don't think the device and the gateway actively talk. It is more like the Gateway is listening, but not talking.
When I tried to set the RelayActuator to passive mode, it showed up in Domoticz, but I could not change the state of the relay from domoticz. However, if I physically altered the state of the relay (with button) domoticz got updated. It's like a one-way communication
I uploaded the sketch you posted and here are the results
This is the log from the device
Port open
__ __ ____
| \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| | | | |_| |___| | __/ | | \__ \ _ | | \__ \
|_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/
|___/ 2.3.2-beta
18 MCO:BGN:INIT NODE,CP=RNNNA---,FQ=8,REL=7,VER=2.3.2-beta
28 TSM:INIT
30 TSF:WUR:MS=0
32 THA:INIT
32 RF24:INIT:PIN,CE=9,CS=10
36 RF24:SBY
36 RF24:WBR:REG=0,VAL=14
45 RF24:WBR:REG=3,VAL=3
47 RF24:WBR:REG=4,VAL=95
49 RF24:WBR:REG=5,VAL=76
53 RF24:WBR:REG=6,VAL=7
55 RF24:WBR:REG=29,VAL=4
57 RF24:RBR:REG=29,VAL=4
59 RF24:RBR:REG=6,VAL=7
63 RF24:RBR:REG=5,VAL=76
65 RF24:WBR:REG=2,VAL=2
67 RF24:WBR:REG=1,VAL=0
69 RF24:WBR:REG=28,VAL=3
73 RF24:FRX
73 RF24:FTX
75 RF24:WBR:REG=7,VAL=112
77 TSM:INIT:TSP OK
79 TSM:FPAR
81 THA:SND:MSG=FFFFFF020307FF
86 RF24:SPL
86 RF24:WBR:REG=0,VAL=14
90 RF24:OWP:RCPT=255
92 RF24:WBR:REG=10,VAL=255
94 RF24:WBR:REG=16,VAL=255
98 RF24:TXM:TO=255,LEN=7
100 RF24:FTX
102 RF24:WBR:REG=4,VAL=80
104 RF24:WBR:REG=7,VAL=112
106 RF24:WBR:REG=4,VAL=95
110 RF24:STL
112 RF24:WBR:REG=0,VAL=15
114 THA:SND:MSG LEN=7,RES=1
116 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2125 !TSM:FPAR:NO REPLY
2127 TSM:FPAR
2129 THA:SND:MSG=FFFFFF020307FF
2131 RF24:SPL
2134 RF24:WBR:REG=0,VAL=14
2136 RF24:OWP:RCPT=255
2140 RF24:WBR:REG=10,VAL=255
2142 RF24:WBR:REG=16,VAL=255
2146 RF24:TXM:TO=255,LEN=7
2148 RF24:FTX
2150 RF24:WBR:REG=4,VAL=80
2152 RF24:WBR:REG=7,VAL=112
2156 RF24:WBR:REG=4,VAL=95
2158 RF24:STL
2160 RF24:WBR:REG=0,VAL=15
2164 THA:SND:MSG LEN=7,RES=1
2166 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4175 !TSM:FPAR:NO REPLY
4177 TSM:FPAR
4179 THA:SND:MSG=FFFFFF020307FF
4182 RF24:SPL
4184 RF24:WBR:REG=0,VAL=14
4186 RF24:OWP:RCPT=255
4190 RF24:WBR:REG=10,VAL=255
4192 RF24:WBR:REG=16,VAL=255
4196 RF24:TXM:TO=255,LEN=7
4198 RF24:FTX
4200 RF24:WBR:REG=4,VAL=80
4202 RF24:WBR:REG=7,VAL=112
4206 RF24:WBR:REG=4,VAL=95
4208 RF24:STL
4210 RF24:WBR:REG=0,VAL=15
4214 THA:SND:MSG LEN=7,RES=1
4216 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6227 !TSM:FPAR:NO REPLY
6230 TSM:FPAR
6232 THA:SND:MSG=FFFFFF020307FF
6234 RF24:SPL
6236 RF24:WBR:REG=0,VAL=14
6238 RF24:OWP:RCPT=255
6242 RF24:WBR:REG=10,VAL=255
6244 RF24:WBR:REG=16,VAL=255
6248 RF24:TXM:TO=255,LEN=7
6250 RF24:FTX
6252 RF24:WBR:REG=4,VAL=80
6254 RF24:WBR:REG=7,VAL=112
6258 RF24:WBR:REG=4,VAL=95
6260 RF24:STL
6262 RF24:WBR:REG=0,VAL=15
6266 THA:SND:MSG LEN=7,RES=1
6268 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8278 !TSM:FPAR:FAIL
8280 TSM:FAIL:CNT=1
8282 TSM:FAIL:DIS
8284 TSF:TDI:TSL
8284 RF24:SLP
8286 RF24:WBR:REG=0,VAL=12
18292 TSM:FAIL:RE-INIT
18294 TSM:INIT
18296 THA:INIT
18296 RF24:INIT:PIN,CE=9,CS=10
18300 RF24:SBY
18302 RF24:WBR:REG=0,VAL=14
18311 RF24:WBR:REG=3,VAL=3
18313 RF24:WBR:REG=4,VAL=95
18315 RF24:WBR:REG=5,VAL=76
18319 RF24:WBR:REG=6,VAL=7
18321 RF24:WBR:REG=29,VAL=4
18325 RF24:RBR:REG=29,VAL=4
18327 RF24:RBR:REG=6,VAL=7
18331 RF24:RBR:REG=5,VAL=76
18333 RF24:WBR:REG=2,VAL=2
18337 RF24:WBR:REG=1,VAL=0
18339 RF24:WBR:REG=28,VAL=3
18341 RF24:FRX
18343 RF24:FTX
18345 RF24:WBR:REG=7,VAL=112
18350 TSM:INIT:TSP OK
18352 TSM:FPAR
18354 THA:SND:MSG=FFFFFF020307FF
18356 RF24:SPL
18358 RF24:WBR:REG=0,VAL=14
18362 RF24:OWP:RCPT=255
18364 RF24:WBR:REG=10,VAL=255
18368 RF24:WBR:REG=16,VAL=255
18370 RF24:TXM:TO=255,LEN=7
18374 RF24:FTX
18376 RF24:WBR:REG=4,VAL=80
18378 RF24:WBR:REG=7,VAL=112
18382 RF24:WBR:REG=4,VAL=95
18384 RF24:STL
18386 RF24:WBR:REG=0,VAL=15
18391 THA:SND:MSG LEN=7,RES=1
18393 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20402 !TSM:FPAR:NO REPLY
20404 TSM:FPAR
20406 THA:SND:MSG=FFFFFF020307FF
20408 RF24:SPL
20410 RF24:WBR:REG=0,VAL=14
20414 RF24:OWP:RCPT=255
20416 RF24:WBR:REG=10,VAL=255
20420 RF24:WBR:REG=16,VAL=255
20422 RF24:TXM:TO=255,LEN=7
20426 RF24:FTX
20428 RF24:WBR:REG=4,VAL=80
20430 RF24:WBR:REG=7,VAL=112
20434 RF24:WBR:REG=4,VAL=95
20436 RF24:STL
20439 RF24:WBR:REG=0,VAL=15
20443 THA:SND:MSG LEN=7,RES=1
20445 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
22454 !TSM:FPAR:NO REPLY
22456 TSM:FPAR
22458 THA:SND:MSG=FFFFFF020307FF
22460 RF24:SPL
22462 RF24:WBR:REG=0,VAL=14
22466 RF24:OWP:RCPT=255
22468 RF24:WBR:REG=10,VAL=255
22472 RF24:WBR:REG=16,VAL=255
22474 RF24:TXM:TO=255,LEN=7
22478 RF24:FTX
22480 RF24:WBR:REG=4,VAL=80
22482 RF24:WBR:REG=7,VAL=112
22487 RF24:WBR:REG=4,VAL=95
22489 RF24:STL
22491 RF24:WBR:REG=0,VAL=15
22493 THA:SND:MSG LEN=7,RES=1
22497 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
24506 !TSM:FPAR:NO REPLY
24508 TSM:FPAR
24510 THA:SND:MSG=FFFFFF020307FF
24512 RF24:SPL
24514 RF24:WBR:REG=0,VAL=14
24518 RF24:OWP:RCPT=255
24520 RF24:WBR:REG=10,VAL=255
24524 RF24:WBR:REG=16,VAL=255
24526 RF24:TXM:TO=255,LEN=7
24530 RF24:FTX
24532 RF24:WBR:REG=4,VAL=80
24535 RF24:WBR:REG=7,VAL=112
24539 RF24:WBR:REG=4,VAL=95
24541 RF24:STL
24543 RF24:WBR:REG=0,VAL=15
24545 THA:SND:MSG LEN=7,RES=1
24549 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
26558 !TSM:FPAR:FAIL
26560 TSM:FAIL:CNT=2
26562 TSM:FAIL:DIS
26564 TSF:TDI:TSL
26566 RF24:SLP
26568 RF24:WBR:REG=0,VAL=12
36571 TSM:FAIL:RE-INIT
36573 TSM:INIT
36575 THA:INIT
36575 RF24:INIT:PIN,CE=9,CS=10
36579 RF24:SBY
36581 RF24:WBR:REG=0,VAL=14
36589 RF24:WBR:REG=3,VAL=3
36591 RF24:WBR:REG=4,VAL=95
36593 RF24:WBR:REG=5,VAL=76
36597 RF24:WBR:REG=6,VAL=7
36599 RF24:WBR:REG=29,VAL=4
36603 RF24:RBR:REG=29,VAL=4
36605 RF24:RBR:REG=6,VAL=7
36610 RF24:RBR:REG=5,VAL=76
36612 RF24:WBR:REG=2,VAL=2
36616 RF24:WBR:REG=1,VAL=0
36618 RF24:WBR:REG=28,VAL=3
36620 RF24:FRX
36622 RF24:FTX
36624 RF24:WBR:REG=7,VAL=112
36628 TSM:INIT:TSP OK
36630 TSM:FPAR
36632 THA:SND:MSG=FFFFFF020307FF
36634 RF24:SPL
36636 RF24:WBR:REG=0,VAL=14
36640 RF24:OWP:RCPT=255
36642 RF24:WBR:REG=10,VAL=255
36646 RF24:WBR:REG=16,VAL=255
36648 RF24:TXM:TO=255,LEN=7
36653 RF24:FTX
36655 RF24:WBR:REG=4,VAL=80
36657 RF24:WBR:REG=7,VAL=112
36661 RF24:WBR:REG=4,VAL=95
36663 RF24:STL
36665 RF24:WBR:REG=0,VAL=15
36669 THA:SND:MSG LEN=7,RES=1
36671 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
38680 !TSM:FPAR:NO REPLY
38682 TSM:FPAR
38684 THA:SND:MSG=FFFFFF020307FF
38686 RF24:SPL
38688 RF24:WBR:REG=0,VAL=14
38692 RF24:OWP:RCPT=255
38694 RF24:WBR:REG=10,VAL=255
38699 RF24:WBR:REG=16,VAL=255
38701 RF24:TXM:TO=255,LEN=7
38705 RF24:FTX
38707 RF24:WBR:REG=4,VAL=80
38709 RF24:WBR:REG=7,VAL=112
38713 RF24:WBR:REG=4,VAL=95
38715 RF24:STL
38717 RF24:WBR:REG=0,VAL=15
38719 THA:SND:MSG LEN=7,RES=1
38723 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
40732 !TSM:FPAR:NO REPLY
40734 TSM:FPAR
40736 THA:SND:MSG=FFFFFF020307FF
40738 RF24:SPL
40740 RF24:WBR:REG=0,VAL=14
40744 RF24:OWP:RCPT=255
40747 RF24:WBR:REG=10,VAL=255
40751 RF24:WBR:REG=16,VAL=255
40753 RF24:TXM:TO=255,LEN=7
40757 RF24:FTX
40759 RF24:WBR:REG=4,VAL=80
40761 RF24:WBR:REG=7,VAL=112
40765 RF24:WBR:REG=4,VAL=95
40767 RF24:STL
40769 RF24:WBR:REG=0,VAL=15
40771 THA:SND:MSG LEN=7,RES=1
40775 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
42784 !TSM:FPAR:NO REPLY
42786 TSM:FPAR
42788 THA:SND:MSG=FFFFFF020307FF
42790 RF24:SPL
42792 RF24:WBR:REG=0,VAL=14
42797 RF24:OWP:RCPT=255
42799 RF24:WBR:REG=10,VAL=255
42803 RF24:WBR:REG=16,VAL=255
42805 RF24:TXM:TO=255,LEN=7
42809 RF24:FTX
42811 RF24:WBR:REG=4,VAL=80
42813 RF24:WBR:REG=7,VAL=112
42817 RF24:WBR:REG=4,VAL=95
42819 RF24:STL
42821 RF24:WBR:REG=0,VAL=15
42823 THA:SND:MSG LEN=7,RES=1
42827 ?TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
Port closed
This is the log from the gateway
Port open
0;255;3;0;9;4503 MCO:BGN:INIT GW,CP=RNNGS---,FQ=48,REL=7,VER=2.3.2-beta
0;255;3;0;9;4532 TSF:LRT:OK
0;255;3;0;9;4532 TSM:INIT
0;255;3;0;9;4533 TSF:WUR:MS=0
0;255;3;0;9;4534 THA:INIT
0;255;3;0;9;4534 RF24:INIT:PIN,CE=34,CS=29
0;255;3;0;9;4534 RF24:SBY
0;255;3;0;9;4534 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;4539 RF24:WBR:REG=3,VAL=3
0;255;3;0;9;4540 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;4540 RF24:WBR:REG=5,VAL=76
0;255;3;0;9;4540 RF24:WBR:REG=6,VAL=7
0;255;3;0;9;4540 RF24:WBR:REG=29,VAL=4
0;255;3;0;9;4541 RF24:RBR:REG=29,VAL=4
0;255;3;0;9;4541 RF24:RBR:REG=6,VAL=7
0;255;3;0;9;4541 RF24:RBR:REG=5,VAL=76
0;255;3;0;9;4542 RF24:WBR:REG=2,VAL=2
0;255;3;0;9;4542 RF24:WBR:REG=1,VAL=0
0;255;3;0;9;4542 RF24:WBR:REG=28,VAL=3
0;255;3;0;9;4543 RF24:FRX
0;255;3;0;9;4543 RF24:FTX
0;255;3;0;9;4543 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;4543 TSM:INIT:TSP OK
0;255;3;0;9;4544 TSM:INIT:GW MODE
0;255;3;0;9;4544 THA:SAD:ADDR=0
0;255;3;0;9;4544 RF24:WBR:REG=2,VAL=3
0;255;3;0;9;4544 RF24:WBR:REG=1,VAL=1
0;255;3;0;9;4545 RF24:STL
0;255;3;0;9;4545 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;4545 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;4545 TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;4546 MCO:REG:NOT NEEDED
0;255;3;0;14;Gateway startup complete.
0;255;0;0;18;2.3.2-beta
0;255;3;0;9;4546 MCO:BGN:STP
0;255;3;0;9;4546 RF24:RBR:REG=6,VAL=7
0;255;3;0;9;4547 RF24:RBR:REG=5,VAL=76
0;255;3;0;9;4547 THA:SAN:RES=1
0;255;3;0;9;4547 MCO:BGN:INIT OK,TSP=1
0;255;3;0;9;4547 TSM:READY:NWD REQ
0;255;3;0;9;4548 THA:SND:MSG=0000FF020314FF
0;255;3;0;9;4548 RF24:SPL
0;255;3;0;9;4548 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;4549 RF24:OWP:RCPT=255
0;255;3;0;9;4549 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;4549 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;4549 RF24:TXM:TO=255,LEN=7
0;255;3;0;9;4550 RF24:FTX
0;255;3;0;9;4550 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;4552 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;4552 ?RF24:TXM:MAX_RT
0;255;3;0;9;4553 RF24:FTX
0;255;3;0;9;4553 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;4553 RF24:STL
0;255;3;0;9;4553 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;4554 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;4554 THA:SND:MSG LEN=7,RES=1
0;255;3;0;9;4554 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
0;255;3;0;9;10212 THA:DATA:AVAIL
0;255;3;0;9;10212 RF24:RXM:LEN=7
0;255;3;0;9;10212 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;10213 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;10213 THA:RCV:MSG LEN=7
0;255;3;0;9;10213 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;10214 TSF:MSG:BC
0;255;3;0;9;10214 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;10214 TSF:PNG:SEND,TO=0
0;255;3;0;9;10214 TSF:CKU:OK
0;255;3;0;9;10215 TSF:MSG:GWL OK
0;255;3;0;9;11214 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;11214 RF24:SPL
0;255;3;0;9;11215 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;11215 RF24:OWP:RCPT=255
0;255;3;0;9;11215 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;11216 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;11216 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;11216 RF24:FTX
0;255;3;0;9;11216 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;11219 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;11219 ?RF24:TXM:MAX_RT
0;255;3;0;9;11219 RF24:FTX
0;255;3;0;9;11220 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;11220 RF24:STL
0;255;3;0;9;11221 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;11221 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;11221 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;11222 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;12235 THA:DATA:AVAIL
0;255;3;0;9;12236 RF24:RXM:LEN=7
0;255;3;0;9;12236 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;12236 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;12236 THA:RCV:MSG LEN=7
0;255;3;0;9;12237 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;12237 TSF:MSG:BC
0;255;3;0;9;12237 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;12237 TSF:CKU:OK,FCTRL
0;255;3;0;9;12238 TSF:MSG:GWL OK
0;255;3;0;9;13212 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;13212 RF24:SPL
0;255;3;0;9;13213 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;13213 RF24:OWP:RCPT=255
0;255;3;0;9;13213 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;13213 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;13214 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;13214 RF24:FTX
0;255;3;0;9;13214 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;13216 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;13217 ?RF24:TXM:MAX_RT
0;255;3;0;9;13217 RF24:FTX
0;255;3;0;9;13217 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;13218 RF24:STL
0;255;3;0;9;13218 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;13218 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;13219 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;13219 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;14259 THA:DATA:AVAIL
0;255;3;0;9;14259 RF24:RXM:LEN=7
0;255;3;0;9;14259 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;14259 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;14260 THA:RCV:MSG LEN=7
0;255;3;0;9;14260 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;14260 TSF:MSG:BC
0;255;3;0;9;14261 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;14261 TSF:CKU:OK,FCTRL
0;255;3;0;9;14261 TSF:MSG:GWL OK
0;255;3;0;9;15212 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;15212 RF24:SPL
0;255;3;0;9;15212 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;15213 RF24:OWP:RCPT=255
0;255;3;0;9;15213 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;15213 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;15214 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;15214 RF24:FTX
0;255;3;0;9;15214 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;15217 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;15217 ?RF24:TXM:MAX_RT
0;255;3;0;9;15217 RF24:FTX
0;255;3;0;9;15217 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;15218 RF24:STL
0;255;3;0;9;15218 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;15218 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;15218 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;15219 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;16282 THA:DATA:AVAIL
0;255;3;0;9;16283 RF24:RXM:LEN=7
0;255;3;0;9;16283 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;16284 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;16284 THA:RCV:MSG LEN=7
0;255;3;0;9;16285 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;16285 TSF:MSG:BC
0;255;3;0;9;16286 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;16286 TSF:CKU:OK,FCTRL
0;255;3;0;9;16287 TSF:MSG:GWL OK
0;255;3;0;9;17214 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;17214 RF24:SPL
0;255;3;0;9;17215 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;17215 RF24:OWP:RCPT=255
0;255;3;0;9;17215 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;17215 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;17216 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;17216 RF24:FTX
0;255;3;0;9;17216 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;17218 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;17219 ?RF24:TXM:MAX_RT
0;255;3;0;9;17219 RF24:FTX
0;255;3;0;9;17219 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;17219 RF24:STL
0;255;3;0;9;17219 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;17220 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;17220 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;17220 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;28242 THA:DATA:AVAIL
0;255;3;0;9;28243 RF24:RXM:LEN=7
0;255;3;0;9;28243 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;28243 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;28244 THA:RCV:MSG LEN=7
0;255;3;0;9;28244 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;28244 TSF:MSG:BC
0;255;3;0;9;28245 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;28245 TSF:PNG:SEND,TO=0
0;255;3;0;9;28245 TSF:CKU:OK
0;255;3;0;9;28245 TSF:MSG:GWL OK
0;255;3;0;9;28844 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;28844 RF24:SPL
0;255;3;0;9;28844 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;28845 RF24:OWP:RCPT=255
0;255;3;0;9;28845 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;28846 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;28846 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;28846 RF24:FTX
0;255;3;0;9;28847 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;28849 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;28849 ?RF24:TXM:MAX_RT
0;255;3;0;9;28850 RF24:FTX
0;255;3;0;9;28850 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;28850 RF24:STL
0;255;3;0;9;28851 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;28851 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;28851 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;28851 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;30269 THA:DATA:AVAIL
0;255;3;0;9;30269 RF24:RXM:LEN=7
0;255;3;0;9;30270 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;30270 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;30270 THA:RCV:MSG LEN=7
0;255;3;0;9;30270 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;30271 TSF:MSG:BC
0;255;3;0;9;30271 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;30271 TSF:CKU:OK,FCTRL
0;255;3;0;9;30272 TSF:MSG:GWL OK
0;255;3;0;9;30848 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;30848 RF24:SPL
0;255;3;0;9;30849 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;30849 RF24:OWP:RCPT=255
0;255;3;0;9;30849 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;30850 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;30850 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;30850 RF24:FTX
0;255;3;0;9;30850 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;30853 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;30853 ?RF24:TXM:MAX_RT
0;255;3;0;9;30853 RF24:FTX
0;255;3;0;9;30853 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;30854 RF24:STL
0;255;3;0;9;30854 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;30854 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;30855 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;30855 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;32295 THA:DATA:AVAIL
0;255;3;0;9;32296 RF24:RXM:LEN=7
0;255;3;0;9;32296 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;32296 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;32297 THA:RCV:MSG LEN=7
0;255;3;0;9;32297 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;32297 TSF:MSG:BC
0;255;3;0;9;32298 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;32298 TSF:CKU:OK,FCTRL
0;255;3;0;9;32298 TSF:MSG:GWL OK
0;255;3;0;9;32854 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;32854 RF24:SPL
0;255;3;0;9;32855 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;32855 RF24:OWP:RCPT=255
0;255;3;0;9;32855 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;32855 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;32856 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;32856 RF24:FTX
0;255;3;0;9;32856 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;32858 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;32859 ?RF24:TXM:MAX_RT
0;255;3;0;9;32859 RF24:FTX
0;255;3;0;9;32859 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;32859 RF24:STL
0;255;3;0;9;32860 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;32860 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;32860 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;32860 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;34321 THA:DATA:AVAIL
0;255;3;0;9;34322 RF24:RXM:LEN=7
0;255;3;0;9;34322 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;34322 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;34323 THA:RCV:MSG LEN=7
0;255;3;0;9;34323 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;34323 TSF:MSG:BC
0;255;3;0;9;34323 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;34324 TSF:CKU:OK,FCTRL
0;255;3;0;9;34324 TSF:MSG:GWL OK
0;255;3;0;9;34856 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;34857 RF24:SPL
0;255;3;0;9;34857 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;34857 RF24:OWP:RCPT=255
0;255;3;0;9;34858 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;34858 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;34858 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;34858 RF24:FTX
0;255;3;0;9;34859 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;34861 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;34861 ?RF24:TXM:MAX_RT
0;255;3;0;9;34861 RF24:FTX
0;255;3;0;9;34861 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;34862 RF24:STL
0;255;3;0;9;34862 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;34862 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;34863 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;34863 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;46289 THA:DATA:AVAIL
0;255;3;0;9;46289 RF24:RXM:LEN=7
0;255;3;0;9;46290 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;46290 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;46290 THA:RCV:MSG LEN=7
0;255;3;0;9;46290 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;46291 TSF:MSG:BC
0;255;3;0;9;46291 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;46291 TSF:PNG:SEND,TO=0
0;255;3;0;9;46292 TSF:CKU:OK
0;255;3;0;9;46292 TSF:MSG:GWL OK
0;255;3;0;9;46504 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;46504 RF24:SPL
0;255;3;0;9;46505 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;46505 RF24:OWP:RCPT=255
0;255;3;0;9;46505 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;46506 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;46506 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;46506 RF24:FTX
0;255;3;0;9;46506 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;46509 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;46509 ?RF24:TXM:MAX_RT
0;255;3;0;9;46509 RF24:FTX
0;255;3;0;9;46509 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;46510 RF24:STL
0;255;3;0;9;46510 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;46510 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;46510 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;46511 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;48315 THA:DATA:AVAIL
0;255;3;0;9;48316 RF24:RXM:LEN=7
0;255;3;0;9;48316 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;48316 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;48317 THA:RCV:MSG LEN=7
0;255;3;0;9;48317 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;48317 TSF:MSG:BC
0;255;3;0;9;48318 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;48318 TSF:CKU:OK,FCTRL
0;255;3;0;9;48318 TSF:MSG:GWL OK
0;255;3;0;9;48508 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;48509 RF24:SPL
0;255;3;0;9;48509 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;48510 RF24:OWP:RCPT=255
0;255;3;0;9;48510 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;48510 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;48510 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;48511 RF24:FTX
0;255;3;0;9;48511 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;48513 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;48513 ?RF24:TXM:MAX_RT
0;255;3;0;9;48514 RF24:FTX
0;255;3;0;9;48514 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;48514 RF24:STL
0;255;3;0;9;48514 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;48515 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;48515 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;48515 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;50342 THA:DATA:AVAIL
0;255;3;0;9;50342 RF24:RXM:LEN=7
0;255;3;0;9;50343 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;50343 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;50343 THA:RCV:MSG LEN=7
0;255;3;0;9;50343 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;50344 TSF:MSG:BC
0;255;3;0;9;50344 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;50344 TSF:CKU:OK,FCTRL
0;255;3;0;9;50344 TSF:MSG:GWL OK
0;255;3;0;9;50513 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;50513 RF24:SPL
0;255;3;0;9;50513 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;50514 RF24:OWP:RCPT=255
0;255;3;0;9;50514 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;50514 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;50514 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;50515 RF24:FTX
0;255;3;0;9;50515 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;50517 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;50517 ?RF24:TXM:MAX_RT
0;255;3;0;9;50518 RF24:FTX
0;255;3;0;9;50518 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;50518 RF24:STL
0;255;3;0;9;50518 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;50519 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;50519 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;50519 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;52369 THA:DATA:AVAIL
0;255;3;0;9;52370 RF24:RXM:LEN=7
0;255;3;0;9;52370 RF24:WBR:REG=7,VAL=64
0;255;3;0;9;52370 THA:RCV:MSG=FFFFFF020307FF
0;255;3;0;9;52371 THA:RCV:MSG LEN=7
0;255;3;0;9;52371 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;52371 TSF:MSG:BC
0;255;3;0;9;52372 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;52372 TSF:CKU:OK,FCTRL
0;255;3;0;9;52372 TSF:MSG:GWL OK
0;255;3;0;9;52522 THA:SND:MSG=0000FF0A2308FF00
0;255;3;0;9;52522 RF24:SPL
0;255;3;0;9;52523 RF24:WBR:REG=0,VAL=14
0;255;3;0;9;52523 RF24:OWP:RCPT=255
0;255;3;0;9;52523 RF24:WBR:REG=10,VAL=255
0;255;3;0;9;52523 RF24:WBR:REG=16,VAL=255
0;255;3;0;9;52524 RF24:TXM:TO=255,LEN=8
0;255;3;0;9;52524 RF24:FTX
0;255;3;0;9;52524 RF24:WBR:REG=4,VAL=80
0;255;3;0;9;52526 RF24:WBR:REG=7,VAL=112
0;255;3;0;9;52527 ?RF24:TXM:MAX_RT
0;255;3;0;9;52527 RF24:FTX
0;255;3;0;9;52527 RF24:WBR:REG=4,VAL=95
0;255;3;0;9;52528 RF24:STL
0;255;3;0;9;52528 RF24:WBR:REG=0,VAL=15
0;255;3;0;9;52528 RF24:WBR:REG=10,VAL=0
0;255;3;0;9;52528 THA:SND:MSG LEN=8,RES=1
0;255;3;0;9;52529 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
Port closed
@mfalkvidd @tekka Major break through! Please investigate!
I was 9 commits behind, so I updated, but that did not improve the result. Result was still the same.
So, I was thinking, what is the major differances between the NRF52832 sketch and the NRF24L01. The differance is that the NRF52 was passive. So, I put this into the MotionActuator sketch
#define MY_PASSIVE_NODE
#define MY_NODE_ID 10
Now the device registers/communicates with the gateway.
See the new log files, with the above lines
Gateway
Opening port
Port open
0;255;3;0;9;0 MCO:BGN:INIT GW,CP=RNNGA---,FQ=16,REL=7,VER=2.3.2-beta
0;255;3;0;9;6 TSM:INIT
0;255;3;0;9;8 TSF:WUR:MS=0
0;255;3;0;9;15 TSM:INIT:TSP OK
0;255;3;0;9;18 TSM:INIT:GW MODE
0;255;3;0;9;21 TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;24 MCO:REG:NOT NEEDED
0;255;3;0;14;Gateway startup complete.
0;255;0;0;18;2.3.2-beta
0;255;3;0;9;29 MCO:BGN:STP
0;255;3;0;9;35 MCO:BGN:INIT OK,TSP=1
0;255;3;0;9;39 TSM:READY:NWD REQ
0;255;3;0;9;45 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
0;255;3;0;9;8570 TSF:MSG:READ,10-10-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
0;255;3;0;9;8606 !TSF:MSG:SEND,0-0-10-10,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=NACK:0100
0;255;3;0;9;10559 TSF:MSG:READ,10-10-0,s=255,c=0,t=17,pt=0,l=10,sg=0:2.3.2-beta
10;255;0;0;17;2.3.2-beta
0;255;3;0;9;10570 TSF:MSG:READ,10-10-0,s=255,c=3,t=6,pt=1,l=1,sg=0:255
10;255;3;0;6;255
0;255;3;0;9;12558 TSF:MSG:READ,10-10-0,s=255,c=3,t=11,pt=0,l=13,sg=0:Motion Sensor
10;255;3;0;11;Motion Sensor
0;255;3;0;9;12570 TSF:MSG:READ,10-10-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
10;255;3;0;12;1.0
0;255;3;0;9;12580 TSF:MSG:READ,10-10-0,s=1,c=0,t=1,pt=0,l=0,sg=0:
10;1;0;0;1;
0;255;3;0;9;12598 TSF:MSG:READ,10-10-0,s=1,c=1,t=16,pt=0,l=1,sg=0:0
10;1;1;0;16;0
Port closed
The motionActuator
Port open
__ __ ____
| \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| | | | |_| |___| | __/ | | \__ \ _ | | \__ \
|_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/
|___/ 2.3.2-beta
18 MCO:BGN:INIT NODE,CP=RNNPA---,FQ=8,REL=7,VER=2.3.2-beta
28 TSM:INIT
30 TSF:WUR:MS=0
36 TSM:INIT:TSP OK
38 TSM:INIT:TSP PSM
40 TSM:INIT:STATID=10
43 TSF:SID:OK,ID=10
45 TSM:FPAR
47 TSM:FPAR:STATP=255
49 TSM:ID
51 TSM:ID:OK
51 TSM:UPL:DISABLED
53 TSM:READY:ID=10,PAR=255,DIS=1
59 ?TSF:MSG:SEND,10-10-255-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
2070 ?TSF:MSG:SEND,10-10-255-0,s=255,c=0,t=17,pt=0,l=10,sg=0,ft=0,st=OK:2.3.2-beta
2082 ?TSF:MSG:SEND,10-10-255-0,s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=OK:255
4093 ?TSF:MSG:SEND,10-10-255-0,s=255,c=3,t=11,pt=0,l=13,sg=0,ft=0,st=OK:Motion Sensor
4106 ?TSF:MSG:SEND,10-10-255-0,s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=OK:1.0
4116 ?TSF:MSG:SEND,10-10-255-0,s=1,c=0,t=1,pt=0,l=0,sg=0,ft=0,st=OK:
4124 MCO:REG:NOT NEEDED
4126 MCO:BGN:STP
4128 MCO:BGN:INIT OK,TSP=1
0
4134 ?TSF:MSG:SEND,10-10-255-0,s=1,c=1,t=16,pt=0,l=1,sg=0,ft=0,st=OK:0
4141 MCO:SLP:MS=120000,SMS=0,I1=1,M1=1,I2=255,M2=255
4147 TSF:TDI:TSL
Port closed
Is there a bug in the code?
@mfalkvidd Any idea?
I have now tested like this:
All sketches are original MySensors sketches only added #define MY_RF24_DATARATE RF24_1MBPS and they run the development branch
Sensebender Gateway (the original) with NRF24L01 Long Range (the one with the antenna) and the SensebenderSerialGateway sketch
Arduino Nano with a NRF24L01 and the SerialGateway sketch
Ikea Molgan Hack hardware with default MotionSenser sketch (only added #define MY_RF24_DATARATE RF24_1MBPS)
MySensors InCan double light switch hardware with default RelayActuator sketch (and the 1MBPS)
One gateway was active at a time. I have cleared eeprom on the devices. They all give the same result. device sends, gateway responds, device say no gateway (or something like that. See previous log. They all look the same).
I have also the EFEKTA Temp&Hum sensor(ver. nRF52832 )+E-Ink display and gateway, both of them respond to this and I see the device presenting itself and I see the text in the gateway log file (it also shows up in Domoticz)
I have googled !TSM:FPAR:FAIL and get multiple hits on the problem, but many refer to very old versions of MySensors. Some say downgrade the Arduino IDE or the tool chain.
Is there a preferred tool chain for building MySensors?
Why is it working with NRF52832 and nor NRF24L01? (the NRF52832 are #define MY_PASSIVE_NODE if that makes a differance)
This is the output of the build of one of the devices (the MotionSensor)
C:\Program Files (x86)\Arduino\arduino-builder -dump-prefs -logger=machine -hardware C:\Program Files (x86)\Arduino\hardware -hardware C:\Users\eu1391\AppData\Local\Arduino15\packages -hardware D:\development\Arduino\hardware -tools C:\Program Files (x86)\Arduino\tools-builder -tools C:\Program Files (x86)\Arduino\hardware\tools\avr -tools C:\Users\eu1391\AppData\Local\Arduino15\packages -built-in-libraries C:\Program Files (x86)\Arduino\libraries -libraries D:\development\Arduino\libraries -fqbn=arduino:avr:pro:cpu=8MHzatmega328 -vid-pid=0403_6001 -ide-version=10809 -build-path C:\Users\eu1391\AppData\Local\Temp\arduino_build_934684 -warnings=none -build-cache C:\Users\eu1391\AppData\Local\Temp\arduino_cache_700673 -prefs=build.warn_data_percentage=75 -prefs=runtime.tools.avrdude.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino14 -prefs=runtime.tools.avrdude-6.3.0-arduino14.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino14 -prefs=runtime.tools.avr-gcc.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\avr-gcc\5.4.0-atmel3.6.1-arduino2 -prefs=runtime.tools.avr-gcc-5.4.0-atmel3.6.1-arduino2.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\avr-gcc\5.4.0-atmel3.6.1-arduino2 -prefs=runtime.tools.arduinoOTA.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\arduinoOTA\1.2.1 -prefs=runtime.tools.arduinoOTA-1.2.1.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\arduinoOTA\1.2.1 -verbose C:\Users\eu1391\AppData\Local\Temp\arduino_modified_sketch_140208\MotionSensor.ino
C:\Program Files (x86)\Arduino\arduino-builder -compile -logger=machine -hardware C:\Program Files (x86)\Arduino\hardware -hardware C:\Users\eu1391\AppData\Local\Arduino15\packages -hardware D:\development\Arduino\hardware -tools C:\Program Files (x86)\Arduino\tools-builder -tools C:\Program Files (x86)\Arduino\hardware\tools\avr -tools C:\Users\eu1391\AppData\Local\Arduino15\packages -built-in-libraries C:\Program Files (x86)\Arduino\libraries -libraries D:\development\Arduino\libraries -fqbn=arduino:avr:pro:cpu=8MHzatmega328 -vid-pid=0403_6001 -ide-version=10809 -build-path C:\Users\eu1391\AppData\Local\Temp\arduino_build_934684 -warnings=none -build-cache C:\Users\eu1391\AppData\Local\Temp\arduino_cache_700673 -prefs=build.warn_data_percentage=75 -prefs=runtime.tools.avrdude.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino14 -prefs=runtime.tools.avrdude-6.3.0-arduino14.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino14 -prefs=runtime.tools.avr-gcc.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\avr-gcc\5.4.0-atmel3.6.1-arduino2 -prefs=runtime.tools.avr-gcc-5.4.0-atmel3.6.1-arduino2.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\avr-gcc\5.4.0-atmel3.6.1-arduino2 -prefs=runtime.tools.arduinoOTA.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\arduinoOTA\1.2.1 -prefs=runtime.tools.arduinoOTA-1.2.1.path=C:\Users\eu1391\AppData\Local\Arduino15\packages\arduino\tools\arduinoOTA\1.2.1 -verbose C:\Users\eu1391\AppData\Local\Temp\arduino_modified_sketch_140208\MotionSensor.ino
Using board 'pro' from platform in folder: C:\Program Files (x86)\Arduino\hardware\arduino\avr
Using core 'arduino' from platform in folder: C:\Program Files (x86)\Arduino\hardware\arduino\avr
WARNING: Spurious .ci folder in 'MySensors' library
WARNING: Spurious .mystools folder in 'MySensors' library
Detecting libraries used...
"C:\\Users\\eu1391\\AppData\\Local\\Arduino15\\packages\\arduino\\tools\\avr-gcc\\5.4.0-atmel3.6.1-arduino2/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fpermissive -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -Wno-error=narrowing -flto -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=8000000L -DARDUINO=10809 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\cores\\arduino" "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\variants\\eightanaloginputs" "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684\\sketch\\MotionSensor.ino.cpp" -o nul
"C:\\Users\\eu1391\\AppData\\Local\\Arduino15\\packages\\arduino\\tools\\avr-gcc\\5.4.0-atmel3.6.1-arduino2/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fpermissive -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -Wno-error=narrowing -flto -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=8000000L -DARDUINO=10809 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\cores\\arduino" "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\variants\\eightanaloginputs" "-ID:\\development\\Arduino\\libraries\\MySensors" "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684\\sketch\\MotionSensor.ino.cpp" -o nul
"C:\\Users\\eu1391\\AppData\\Local\\Arduino15\\packages\\arduino\\tools\\avr-gcc\\5.4.0-atmel3.6.1-arduino2/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fpermissive -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -Wno-error=narrowing -flto -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=8000000L -DARDUINO=10809 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\cores\\arduino" "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\variants\\eightanaloginputs" "-ID:\\development\\Arduino\\libraries\\MySensors" "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\libraries\\SPI\\src" "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684\\sketch\\MotionSensor.ino.cpp" -o nul
Using cached library dependencies for file: D:\development\Arduino\libraries\MySensors\MyASM.S
Using cached library dependencies for file: C:\Program Files (x86)\Arduino\hardware\arduino\avr\libraries\SPI\src\SPI.cpp
Generating function prototypes...
"C:\\Users\\eu1391\\AppData\\Local\\Arduino15\\packages\\arduino\\tools\\avr-gcc\\5.4.0-atmel3.6.1-arduino2/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fpermissive -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -Wno-error=narrowing -flto -w -x c++ -E -CC -mmcu=atmega328p -DF_CPU=8000000L -DARDUINO=10809 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\cores\\arduino" "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\variants\\eightanaloginputs" "-ID:\\development\\Arduino\\libraries\\MySensors" "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\libraries\\SPI\\src" "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684\\sketch\\MotionSensor.ino.cpp" -o "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684\\preproc\\ctags_target_for_gcc_minus_e.cpp"
"C:\\Program Files (x86)\\Arduino\\tools-builder\\ctags\\5.8-arduino11/ctags" -u --language-force=c++ -f - --c++-kinds=svpf --fields=KSTtzns --line-directives "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684\\preproc\\ctags_target_for_gcc_minus_e.cpp"
Compiling sketch...
"C:\\Users\\eu1391\\AppData\\Local\\Arduino15\\packages\\arduino\\tools\\avr-gcc\\5.4.0-atmel3.6.1-arduino2/bin/avr-g++" -c -g -Os -w -std=gnu++11 -fpermissive -fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics -Wno-error=narrowing -MMD -flto -mmcu=atmega328p -DF_CPU=8000000L -DARDUINO=10809 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\cores\\arduino" "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\variants\\eightanaloginputs" "-ID:\\development\\Arduino\\libraries\\MySensors" "-IC:\\Program Files (x86)\\Arduino\\hardware\\arduino\\avr\\libraries\\SPI\\src" "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684\\sketch\\MotionSensor.ino.cpp" -o "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684\\sketch\\MotionSensor.ino.cpp.o"
Compiling libraries...
Compiling library "MySensors"
Using previously compiled file: C:\Users\eu1391\AppData\Local\Temp\arduino_build_934684\libraries\MySensors\MyASM.S.o
Compiling library "SPI"
Using previously compiled file: C:\Users\eu1391\AppData\Local\Temp\arduino_build_934684\libraries\SPI\SPI.cpp.o
Compiling core...
Using precompiled core: C:\Users\eu1391\AppData\Local\Temp\arduino_cache_700673\core\core_arduino_avr_pro_cpu_8MHzatmega328_0c812875ac70eb4a9b385d8fb077f54c.a
Linking everything together...
"C:\\Users\\eu1391\\AppData\\Local\\Arduino15\\packages\\arduino\\tools\\avr-gcc\\5.4.0-atmel3.6.1-arduino2/bin/avr-gcc" -w -Os -g -flto -fuse-linker-plugin -Wl,--gc-sections -mmcu=atmega328p -o "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684/MotionSensor.ino.elf" "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684\\sketch\\MotionSensor.ino.cpp.o" "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684\\libraries\\MySensors\\MyASM.S.o" "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684\\libraries\\SPI\\SPI.cpp.o" "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684/..\\arduino_cache_700673\\core\\core_arduino_avr_pro_cpu_8MHzatmega328_0c812875ac70eb4a9b385d8fb077f54c.a" "-LC:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684" -lm
"C:\\Users\\eu1391\\AppData\\Local\\Arduino15\\packages\\arduino\\tools\\avr-gcc\\5.4.0-atmel3.6.1-arduino2/bin/avr-objcopy" -O ihex -j .eeprom --set-section-flags=.eeprom=alloc,load --no-change-warnings --change-section-lma .eeprom=0 "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684/MotionSensor.ino.elf" "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684/MotionSensor.ino.eep"
"C:\\Users\\eu1391\\AppData\\Local\\Arduino15\\packages\\arduino\\tools\\avr-gcc\\5.4.0-atmel3.6.1-arduino2/bin/avr-objcopy" -O ihex -R .eeprom "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684/MotionSensor.ino.elf" "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684/MotionSensor.ino.hex"
Using library MySensors at version 2.3.2-beta in folder: D:\development\Arduino\libraries\MySensors
Using library SPI at version 1.0 in folder: C:\Program Files (x86)\Arduino\hardware\arduino\avr\libraries\SPI
"C:\\Users\\eu1391\\AppData\\Local\\Arduino15\\packages\\arduino\\tools\\avr-gcc\\5.4.0-atmel3.6.1-arduino2/bin/avr-size" -A "C:\\Users\\eu1391\\AppData\\Local\\Temp\\arduino_build_934684/MotionSensor.ino.elf"
Sketch uses 13682 bytes (44%) of program storage space. Maximum is 30720 bytes.
Global variables use 454 bytes (22%) of dynamic memory, leaving 1594 bytes for local variables. Maximum is 2048 bytes.```@rolandow To burn a bootloader you need an ISP. I have used a cheap Chinese clone like this one
.
I have used Arduino IDE to burn the bootloader, but you can use other things too, like AVRDUDE.
A word of warning when using the Arduino IDE is that it also sets the fuses. So, you have to select the correct board type when you set the bootloader with this program (or change the fuses in the boards.txt file).
I bricked two atmega328 before I realized this.
In this post you can read a little about the flashing, or atleast it has links to other pages.
You can probably skip the bootloader all together and just upload the sketch with the ISP instead, but you wont be able to upload with serial in that case.
After the bootloader, you can upload with a FTDI. I also use a cheap clone like this one
I also use the Arduino IDE to upload the sketch, just select the correct serial/com port in the IDE.
The "InCan double light switch" does not auto-reset when upload starts, so you have to reset it manually. The white/yellow cable is connected to RESET on the ISP connector, and after I choose Upload in Arduino IDE and the build output in the IDE window is finished I touch the white/yellow cable to GND on the FTDI device, and the leds on the FTDI starts blinking.
Device is now programmed.
Good to think off is that the crypto chip is connected to A4, instead of A3. So if you use this and run the personalizer sketch, you have to set
#define MY_SIGNING_ATSHA204_PIN A4
in the sketch
Also, the original code for this device is not compatible with the MySensors development branch, but can easily be adopted, just comparing to the default MySensors RelayActuator sketch
@stormy Did you have any problems with the code? I have the Sensbender Gateway. It can read other devices fine, your device it can not read. The gateway reacts to it sending data, but the logs say the device gets no response.
I have posted a separate thread about it in Troubleshooting, but it would be nice to know if you have some idea too?
I have triple checked everything twice for shorts. There are none. The diodes however got hot as hell and so did the Hi-link, probably from shorting the reset. I have removed the diodes for now. I will get new once (of the correct footpriint) tomorrow. ). For now I run every thing from the USB port of the computer, so no 230V yet)
Is anything not standard? The Crypto chip is on A4, instead of A3, is there anything else? Bootloader and serial works fine. I can run the SecurityPersonalizer and that works fine.
I have tried to connect a 47uF to the radio, but still no dice.
I have tried the stock example of RelayActuator but that does not work either.
I just get the from the device
516950 TSM:INIT
516956 TSM:INIT:TSP OK
516960 TSM:FPAR
516962 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
518971 !TSM:FPAR:NO REPLY
518973 TSM:FPAR
518975 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
520986 !TSM:FPAR:NO REPLY
520988 TSM:FPAR
520990 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
523001 !TSM:FPAR:NO REPLY
523003 TSM:FPAR
523005 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
525017 !TSM:FPAR:FAIL
525019 TSM:FAIL:CNT=7
525021 TSM:FAIL:DIS
525023 TSF:TDI:TSL
and this from gateway
0;255;3;0;9;661854 TSF:MSG:GWL OK
0;255;3;0;9;662240 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;663828 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;663829 TSF:MSG:BC
0;255;3;0;9;663829 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;663829 TSF:CKU:OK,FCTRL
0;255;3;0;9;663829 TSF:MSG:GWL OK
0;255;3;0;9;664143 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;665804 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;665804 TSF:MSG:BC
0;255;3;0;9;665805 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;665805 TSF:CKU:OK,FCTRL
0;255;3;0;9;665805 TSF:MSG:GWL OK
0;255;3;0;9;666046 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
Is there anything one can measure with a scope or something?
@mfalkvidd
Sketch is almost as the original, but I think it I have adopted it to the development branch (not sure). Original code had mGetAck, now it is message.isEcho in the Recieve method
I have no repeters, the gateway is at the moment connected to the computer and so is the device. There are currently no other active devices in the network. Just a gateway and the InWall device. All other devices are physically turned off.
I have run the clear eeprom sketch on the device. Before it had node id 10, but after clear eeprom the id was removed.
/**
* The MySensors Arduino library handles the wireless radio link and protocol
* between your home built sensors/actuators and HA controller of choice.
* The sensors forms a self healing radio network with optional repeaters. Each
* repeater and gateway builds a routing tables in EEPROM which keeps track of the
* network topology allowing messages to be routed to nodes.
*
* Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
* Copyright (C) 2013-2015 Sensnology AB
* Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
*
* Documentation: http://www.mysensors.org
* Support Forum: http://forum.mysensors.org
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* version 2 as published by the Free Software Foundation.
*
*******************************
*
* REVISION HISTORY
* Version 1.0 - Henrik Ekblad
* Version 2.0 - dpressle
* Version 3.0 - Stormy
*
* DESCRIPTION
* Sketch for a "light switch" where you can control light or something
* else from both HA controller and a local physical button
*/
// Enable debug prints to serial monitor
#define MY_DEBUG
#define DEBUG
#define SKETCH_NAME "LightSwitch InWallCan"
#define SKETCH_VERSION "1.1"
//#define MY_NODE_ID 10
//#define MY_PARENT_NODE_ID 0
//#define MY_PARENT_NODE_IS_STATIC
//#define MY_TRANSPORT_WAIT_READY_MS 3000 // start without gateway after 3 seconds
#define DWELL_TIME 40 // this allows for radio to come back to power after a transmission, ideally 0.
#define MY_RADIO_RF24 // enable and select radio type attached
#define MY_SPLASH_SCREEN_DISABLED // disable splash screen - This saves 120 bytes of flash.
//#define MY_DISABLED_SERIAL // enable this in sketch if you want to use TX(1), RX(0) as normal I/O pin
//#define MY_RF24_PA_LEVEL RF24_PA_MAX
#define MY_RF24_DATARATE RF24_1MBPS
//#define MY_TRANSPORT_SANITY_CHECK
//#define MY_SIGNAL_REPORT_ENABLED
#include <SPI.h>
#include <MySensors.h>
#include <Bounce2.h>
#define MY_SIGNING_ATSHA204_PIN A4
#define BUTTON_PIN1 A5 // Arduino Digital I/O pin number for button
#define BUTTON_PIN2 2 // Arduino Digital I/O pin number for button
#define RELAY_PIN1 4 // Arduino Digital I/O pin number for relay
#define RELAY_PIN2 3 // Arduino Digital I/O pin number for relay
#define CHILD_ID1 0 // Id of the sensor child
#define CHILD_ID2 1 // Id of the sensor child
#define RELAY_ON 1
#define RELAY_OFF 0
Bounce debouncer1 = Bounce();
Bounce debouncer2 = Bounce();
int oldValue1 = 0;
int oldValue2 = 0;
int stateRel1;
int stateRel2;
bool initialStateSent = false;
MyMessage msg1(CHILD_ID1, V_STATUS);
MyMessage msg2(CHILD_ID2, V_STATUS);
void changeState(int childId, int newState) {
switch(childId){
case CHILD_ID1:
digitalWrite(RELAY_PIN1, newState);
send(msg1.set(newState), true);
wait(DWELL_TIME);
stateRel1 = newState;
break;
case CHILD_ID2:
digitalWrite(RELAY_PIN2, newState);
send(msg2.set(newState), true);
wait(DWELL_TIME);
stateRel2 = newState;
break;
default:
break;
}
}
void before() {
// Setup the button
pinMode(BUTTON_PIN1, INPUT_PULLUP);
pinMode(BUTTON_PIN2, INPUT_PULLUP);
// Activate internal pull-up
digitalWrite(BUTTON_PIN1, HIGH);
digitalWrite(BUTTON_PIN2, HIGH);
// After setting up the button, setup debouncer
debouncer1.attach(BUTTON_PIN1);
debouncer1.interval(5);
debouncer2.attach(BUTTON_PIN2);
debouncer2.interval(5);
// Make sure relays are off when starting up
digitalWrite(RELAY_PIN1, RELAY_OFF);
digitalWrite(RELAY_PIN2, RELAY_OFF);
// Then set relay pins in output mode
pinMode(RELAY_PIN1, OUTPUT);
pinMode(RELAY_PIN2, OUTPUT);
}
void setup() {
}
void presentation() {
// Send the sketch version information to the gateway and Controller
sendSketchInfo(SKETCH_NAME, SKETCH_VERSION, true);
wait(DWELL_TIME);
// Register all sensors to gw (they will be created as child devices)
present(CHILD_ID1, S_BINARY);
wait(DWELL_TIME);
present(CHILD_ID2, S_BINARY);
wait(DWELL_TIME);
}
void loop() {
if (!initialStateSent) {
send(msg1.set(RELAY_OFF), true);
wait(DWELL_TIME);
send(msg2.set(RELAY_OFF), true);
wait(DWELL_TIME);
initialStateSent = true;
}
debouncer1.update();
int value = debouncer1.read();
if (value != oldValue1 && value==0) {
changeState(CHILD_ID1, stateRel1 ? RELAY_OFF : RELAY_ON);
#ifdef DEBUG
Serial.println("Relay #1 state change from button #1");
#endif
}
oldValue1 = value;
debouncer2.update();
value = debouncer2.read();
if (value != oldValue2 && value==0) {
changeState(CHILD_ID2, stateRel2 ? RELAY_OFF : RELAY_ON);
#ifdef DEBUG
Serial.println("Relay #2 state change from button #2");
#endif
}
oldValue2 = value;
//sendHeartbeat();
}
void receive(const MyMessage &message) {
// We only expect one type of message from controller. But we better check anyway.
if (message.isAck()) {
#ifdef DEBUG
Serial.println("This is an ack from gateway");
#endif
}
if (message.type == V_STATUS && !message.isEcho()) {
#ifdef DEBUG
Serial.print("Incoming change for sensor:");
Serial.print(message.sensor);
Serial.print(", New status: ");
Serial.println(message.getBool());
#endif
changeState(message.sensor, message.getBool() ? RELAY_ON : RELAY_OFF);
}
}
I have no idea where to look. I have a device (The device) and a Sensebender Gateway.
They are on the same network (76) and on the same bitrate (1MBPS).
I have altered the device sketch to just have the bare minimum. The gateway works with other devices.
When the device starts, I see movement in the Gateway trace files and the leds blink. So some kind of connection is present.
This is the trace file from the device
0 MCO:BGN:INIT NODE,CP=RNNNA---,FQ=8,REL=6,VER=2.3.2-beta
4 MCO:BGN:BFR
6 TSM:INIT
8 TSF:WUR:MS=0
14 TSM:INIT:TSP OK
16 TSM:FPAR
18 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2027 !TSM:FPAR:NO REPLY
2029 TSM:FPAR
2031 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4040 !TSM:FPAR:NO REPLY
4042 TSM:FPAR
4044 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6053 !TSM:FPAR:NO REPLY
6055 TSM:FPAR
6057 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8067 !TSM:FPAR:FAIL
8069 TSM:FAIL:CNT=1
8071 TSM:FAIL:DIS
8073 TSF:TDI:TSL
This is from the Gateway
0;255;3;0;9;479819 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;479819 TSF:MSG:BC
0;255;3;0;9;479820 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;479820 TSF:PNG:SEND,TO=0
0;255;3;0;9;479820 TSF:CKU:OK
0;255;3;0;9;479820 TSF:MSG:GWL OK
0;255;3;0;9;480439 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;481794 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;481795 TSF:MSG:BC
0;255;3;0;9;481795 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;481795 TSF:CKU:OK,FCTRL
0;255;3;0;9;481796 TSF:MSG:GWL OK
0;255;3;0;9;482341 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;483770 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;483770 TSF:MSG:BC
0;255;3;0;9;483771 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;483771 TSF:CKU:OK,FCTRL
0;255;3;0;9;483771 TSF:MSG:GWL OK
0;255;3;0;9;484243 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;485745 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;485745 TSF:MSG:BC
0;255;3;0;9;485746 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;485746 TSF:CKU:OK,FCTRL
0;255;3;0;9;485746 TSF:MSG:GWL OK
0;255;3;0;9;486145 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
What next?
@tekka Thanks! Development branch worked
@stormy Yes, it is a chinese USPasp clone, but I think it is working now. Atleast I could upload a bootloader (i think) and I can use a FTDI to upload a sketch.
But, I can only upload a sketch once. Directly after the bootloader, I can upload a sketch, but on next atempt it will not accept a new sketch.
Do I have the wrong bootloader? What bootloader should I use? I just selected "Board: ATmega328p (8 MHz internal clock" and pressed "Burn bootloader" (with the USBAsp)
Switched cables to a FTDI device, pressed "Upload"
All works fine.
Press "Upload" again, and nothing will be sent to the device. But, if I "Burn bootloader" again, I can upload a new sketch.
There is no DTR, is that a problem?
EDIT: Manual reset makes it possible to upload sketch multiple times
I connected the RESET from the ISP to ground and released it right before the upload starts
@stormy I have soldered one of these together. I hooked it up to a USBAsp and with AVRDUDE burned the fuses. When it reads the fuses back the extended fuses are not set, the others are.
Then I try and burn a bootloader. And it says "cannot set SCK period". And from this point on, I can no longer identify the MCU with AVRDUDE, and even less set the fuses again.
Any ideas?
I'm fairly sure there are no solder bridges. I have checked it several times, and even measured it.
avrdude.exe: set SCK frequency to 1500000 Hz
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: error: program enable: target doesn't answer. 1
avrdude.exe: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.
avrdude.exe done. Thank you.
EDIT: Fixed the problem
The problem was that I had "Arduino Mini" as board in Arduino IDE, and it probably changes the fuses to "use external crystal" when burning bootloader. I desoldered the chip replaced it with a new one, selected "Atmega328p (8MHz internal clock)" as board and burned that bootloader. Now chip is responding.
EDIT 2: Diode any diode 0805/SOD-80
A 0805 diode will not fit on the footprint. I ordered 0805, and they will not even touch the pcb pads. Fortunately I had some 1N4148 (through hole) and if I cut them really short, they could fit.
So for future builders, go with a SOD-80
EDIT 3: The radio
For future revisions of the pcb, add some 0.5mm space between the radio and the Hi-link. It is really tight fit today. Almost to close together.
I'm trying to revive my MySensors network, and started by flasking a new GatewaySerial to the Sensbender Gateway. I have the NRF24 long range version connected to it.
When the sketch starts this is what I get and it looks wrong to me. A lot of "hu".
I have cleared eeprom, but still the same. I ave not changed anything, it is stock 2.3.1 and stock GatewaySerial.
Any idea what I should try next?
0;255;hu;0;hu;3 MCO:BGN:INIT GW,CP=RNNGS---,REL=hu,VER=2.3.1
0;255;hu;0;hu;3 TSF:LRT:OK
0;255;hu;0;hu;3 TSM:INIT
0;255;hu;0;hu;3 TSF:WUR:MS=0
0;255;hu;0;hu;3 TSM:INIT:TSP OK
0;255;hu;0;hu;3 TSM:INIT:GW MODE
0;255;hu;0;hu;3 TSM:READY:ID=hu,PAR=hu,DIS=hu
0;255;hu;0;hu;3 MCO:REG:NOT NEEDED
hu;hu;hu;hu;hu;�
hu;hu;hu;hu;hu;�
0;255;hu;0;hu;3 MCO:BGN:STP
0;255;hu;0;hu;3 MCO:BGN:INIT OK,TSP=hu
0;255;hu;0;hu;3 TSM:READY:NWD REQ
0;255;hu;0;hu;3 TSF:MSG:SEND,hu-hu-hu-hu,s=hu,c=hu,t=hu,pt=hu,l=hu,sg=hu,ft=hu,st=�:�```Edit: After I posted this the device has worked for 2 days. But still, the capasitors are they correct?
@berkseo I have a wierd problem with the SHT20 sensor. It stops working after a few reads. Then the device hangs and goes into battery draining mode with atleast 8mA constant current. I have localized it to the SHT20, because if I comment out the init and read temp/humidity of the SHT20 the device boots up.
The wierdest is that the SHT20 stops responding for quite some time, even if I power cycle the device, it is still not responding.
Last night I had it running for 1 hour, powered with 3.3V directly. Turned power of, had some sleep, turned power on SHT20 not responding. Turned power of, played with the kids, 3 hours later turned power on, the SHT20 is now responding. Now it's been going for 20 minutes and is still responding. But I bet if I let it run, it will stop.
I am fairly sure the SHT20 is soldered to the board correctly. I used reflow (heatgun) and solder paste was liquid and I could poke the SHT20 and it popped back automatically by surface tension.
I have also tried to replace the SHT20, but the result is the same. the device when hung)
Anything you recognize?
I have not yet successfully been able to debug the device, if i compile with the MY_DEBUG active, the device does not come on and the led shines constantly and I'm not sure how to connect the FTDI, should Vcc on the SWD provide power or not?
I have checked the capasitors C12, C13 and C14 since they have been talked about before and differ from the BOM list and the real board.
C12 is 10uF
C13 is 100uF (100uF is very big, only had a 1206 size, but I got it in place, will get 47uF 0805 for next iteration, waiting for a solder paste dispenser from China)
C14 is 100nF
@berkseo Thanks! Hopefully I can finish my project of automating my radiators. Project has been ongoing for many years.
Btw, any chance you could upload the gerber for the newest version of the board, the one with the inductor placed more centered on the board and with a hole in the power board? I see now the boards sandwich better if the hole is there.
(and ofcourse of you have a newer version of the code, that too)
@berkseo said in EFEKTA Temp&Hum sensor(ver. nRF52832 )+E-Ink display:
TTL Converter.
Thanks! I found in another thread one could use a FTDI, I will try that!
It sure is lonely in here... but finally SUCCESS!!!!
After days of googling and checking and rechecking the board for shorts, I found the problem. The 68uH was dead. Maybe damaged when soldering it. It did not conduct anything. After changing it to a new one, the display started working.
Any idea how battery can be at 60% on more or less fresh batteries... anyway, that is another problem.
I still have one question, if anyone can chip in that would be great.
On the SWD connector it says, TX and RX, how do I use them?
Or really what I mean, how do you debug the device? I use a ST-Link V2, but I am not getting any COM-port so I cannot start the serial debugger. Is the TX/RX used for the serial debugging? Can I use ST-Link V2 for this or do I need a separate device?
I have tried to change the driver with ZADIG, but still no COM-port. As for now I have only connected 4 of the 6 pins in the SWD.
Please @berkseo help me!
@berkseo is the device programmed when output says this?
Open On-Chip Debugger 0.10.0-dev-00254-g696fc0a (2016-04-10-10:13)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
debug_level: 0
0x4000
adapter speed: 10000 kHz
nrf52.cpu: target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc
** Programming Started **
auto erase enabled
nrf52.cpu: target state: halted
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x2000001e msp: 0xfffffffc
wrote 102400 bytes from file C:\Users\eu1391\AppData\Local\Temp\arduino_build_38086/epd1in54-demo.ino.hex in 2.178483s (45.904 KiB/s)
** Programming Finished **
** Verify Started **
nrf52.cpu: target state: halted
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x2000002e msp: 0xfffffffc
verified 100668 bytes in 0.296666s (331.378 KiB/s)
** Verified OK **
** Resetting Target **
shutdown command invoked
The only thing happening when I turn it on, is that the LED flashed once. Then occasionally the LED flashed sporadically.
The e-paper is just white.
Questions?
Can you power the board from another source then the battery pcb?
The board needs to be powered when programming it, right? I'm using a ST-LINK V2 with the SWD pins connected.
How do you debug the board? I use Arduino IDE
Could you please update the description with what component goes where on the pcb?
@berkseo @heinzv I finally got around to solder one of these together. It was not easy, placing the components was kind of a guessing game, but I think I got it right. When I put two batteries in and turn it on there is a buzzing noise, maybe normal? Anyway... I never realized programming this thing would be a problem.
What equipment is needed to program it? I don't recognize the labeling on the pcb (gnd/vcc sdo/sclk rx/tx)
@berkseo Do you have a what goes where description? like this but with a number instead of x
And the code, could you upload the code for this and for the SHT20 version?
@berkseo I'm trying to reverse engineer the BOM of this board, but I am quite unsuccessful. Could you please upload a BOM with (R1 = xxx k) or something similar, or Upload high-res closeups of the board so one can read the resistor values? Capacitors are a little harder, maybe you could share those values?
I have started on a BOM list, if you could help me fill it out, that would be much appreciated. I want to start soldering!!
Front
Back
@jrbenito I did jump the gun a little early. Sure, the gateway works, if you have externally connected devices, like an external MySensors gateway, but it does not work if you have the radio wired directly onto the RPi. It cannot fint the SPI.
Basically I did this:
A DockerFile (the .configure section needs to be modified to personal preferences)
FROM balenalib/raspberrypi3-debian
RUN apt-get update && apt-get install -y --no-install-recommends git bash make g++ \
&& cd /root \
&& git clone https://github.com/mysensors/MySensors.git --branch development \
&& cd /root/MySensors \
&& mkdir -p /data \
&& LDFLAGS="-static" ./configure --my-transport=rfm69 --my-rfm69-frequency=868 --my-is-rfm69hw --my-gateway=ethernet --my-port=5003 --my-leds-err-pin=29 --my-leds-rx-pin=31 --my-leds-tx-pin=33 --my-rfm69-encryption-enabled --my-signing-request-signatures --my-signing=software --my-config-file="/data/mysensors.conf" \
&& make \
&& cd /root \
&& apt-get remove -y git make g++ && apt-get autoremove -y
EXPOSE 5003
ENTRYPOINT ["/root/MySensors/bin/mysgw"]
And a Docker-compose.yml file (ports needs to be configured. I think 5003 is not needed, since 5003 would be used if the gateway was handling the radio wired to the pins of the pi. Run with serial instead)
version: '3'
services:
portainer:
container_name: portainer
image: portainer/portainer:arm
restart: always
volumes:
- '/var/run/docker.sock:/var/run/docker.sock'
expose:
- 9000
ports:
- 9000:9000
mysensors:
build:
context: .
dockerfile: Dockerfile
container_name: mysensor_eth
restart: unless-stopped
privileged: true
devices:
- /dev/ttyACM0:/dev/ttyACM0
ports:
- 5003:5003
volumes:
- /mnt/usb1/mysensorsd/data:/data:rw
- /sys:/sys:rw
- /tmp:/tmp
The config file needs to be on a exposed volume and have the eeprom file pointed to the same volume
File mysensors.conf and it needs to be modified for signing keys and path to log aqnd eeprom
i had everything on /mnt/usb1/mysensors and folders data created within that path. I set access to full RW for everyone
# Logging
# Verbosity: debug,info,notice,warn,err
verbose=debug
# Enable logging to a file.
log_file=1
# Log file path.
log_filepath=/mnt/usb1/mysensors/data/mysgw.log
# Enable logging to a named pipe.
# Use this option to view your gateway's log messages
# from the log_pipe_file defined bellow.
# To do so, run the following command on another terminal:
# cat "log_pipe_file"
log_pipe=1
log_pipe_file=/tmp/mysgw.pipe
# Enable logging to syslog.
syslog=0
# EEPROM settings
eeprom_file=/mnt/usb1/mysensors/data/mysensors.eeprom
eeprom_size=1024
# Software signing settings
# Note: The gateway must have been built with signing
# support to use the options below.
#
# To generate a HMAC key run mysgw with: --gen-soft-hmac-key
# copy the new key in the line below and uncomment it.
soft_hmac_key=****************
# To generate a serial key run mysgw with: --gen-soft-serial-key
# copy the new key in the line below and uncomment it.
soft_serial_key=*******************
# Encryption settings
# Note: The gateway must have been built with encryption
# support to use the options below.
#
# To generate a AES key run mysgw with: --gen-aes-key
# copy the new key in the line below and uncomment it.
aes_key=**************
I do not use the MySensors on a docker. I had som many problems with it, SPI beeing one, and the LEDs an other.
It literally takes 3 minutes to set it up and run nativelly on a Pi, and this gives you full access to everything.
I run everything else in a docker.
@gahlawathome said in Help! openHAB 2.4 binding MQTT:
I have exactly same problem. Does it work for anyone not using the system broker?
Both binding and openhab are 2.4.
Googleing this problem at it is quite reoccurring that the questions are about "How to get mysensors mqtt gateway online". Something must be wrong with it, otherwise so many cannot report the same thing.
@TimO as the developer, do you have any leads?
@waspie said in Help! openHAB 2.4 binding MQTT:
yeah, mysensors in 2.4+ is very touchy.
Have you restarted the openhab service lately?
Try deleting your mysensors gateway then restart openhab and re-add the mysensors mqtt gateway. Just for grins...
I did that now... same thing...
So, The "Mysensors Binding" creates a Thing, "Mysensors MQTT Gateway".
The "Mysensors MQTT Gateway" needs a "MQTT Broker" Thing. This thing is called "mosquitto". The mosquitto thing is configured to connect to 127.0.0.1:1883
In "Mysensors MQTT Gateway" I say "Broker Name" is "mosquitto".
In log "Mysensors MQTT Gateway" says "No connection to broker: mosquitto"
Maybe I should just revert back to Ethernet. I have spent 3 days with this, and somthing that "mysterious" can just not be right.
@waspie said in Help! openHAB 2.4 binding MQTT:
i dont know what folder path your stuff would be in exactly but can you list openhab???/userdata/config/org/openhab/
Looks like this:
I tried some experiments. I made a simple flow in node-red. Listen to "mysensors-out/#" then print it to debug. And yes, it works.
I also tried to add a channel to the "MQTT Broker" thing, also "mysensors-out/#"
It showed up without any problems... not very usable, but can see the connection...
But the "Mysensors MQTT Gateway"... just dead in the water...
@waspie said in Help! openHAB 2.4 binding MQTT:
this is 2.4.0 and not a 2.5.x build, right?
Yes it is the 2.4 build. Both OH is 2.4 and mysensors is 2.4 (any newer is not available to my knowledge)
OH is an installation from a docker image (openhab/openhab:2.4.0)
Trace file does not look very healthy...
@waspie said in Help! openHAB 2.4 binding MQTT:
fd3193ea
OK, thanks. I changed the "Broker name" in Mysensors MQTT Gateway in OH to fd3193ea.
The Mysensors thing is still "Offline" though... I rebooted every thing... but still offline...
@waspie said in Help! openHAB 2.4 binding MQTT:
I dont see a broker in your things view. Please re-snip and post
@waspie said in Help! openHAB 2.4 binding MQTT:
what is the name of that broker?
I don't know how to answer that.... You vitually see my screen (all the screen shots).. What you see is what I have. Where do I see the name of the broker?
@waspie But if I install a normal "MQTT broker", I can enter an IP adress to my mosquitto server. And I can see that the thing connects to the server
If I can use the "MQTT Broker".. how do I get Mysensors MQTT Gateway thing to connect to it?
@waspie Thanks, but that did not help me either.
If I Install a "System MQTT Broker" it has one, and only one option.. "Broker ID"
I don't know what to write here.. but I can try to write "mosquitto"
Then I get this:
I have removed the file in services
Has anyone successfully used Mysensors MQTT gateway with Openhab2.4?
I have tried and I have followed "How to's" but nothing work. I have googled and search, but only found people trying and failing, or showing things that does not exist.
Does anyone have a working set up and can share it? Visually if possible? And for starters, just through PaperUI.
OpenHab is 2.4.0 and mysensors is development branch
This is what I have done and where I have failed.
I have created a MySensors MQTT Gateway thing in OH
When I click on the Mysensors MQTT Gateway I can set some settings.
I set the topic to the same as in the config of the mysensors gateway, but what is "Broker Name"
It refers to a file, org.eclipse.smarthome.mqtt.cfg, that does not exist. Somewhere I have read you just create the file and past this in it.
mosquitto.url=tcp://127.0.0.1:1883
mosquitto.retain=false
Everything is still offline... nothing happens... The mqtt however is full of messages from sensors, I see this in MQTT.fx
How do I get the Mysensors MQTT Gateway ONLINE in Openhab?
And what do I write in "Broker name".. that feels kind of important
Mosquitto and Openhab run in separate docker containers
mosquitto:
image: eclipse-mosquitto:1.5
restart: unless-stopped
container_name: mosquitto
expose:
- 1883
ports:
- 1883:1883
volumes:
- /mnt/usb1/mosquitto/config/mosquitto.conf:/mosquitto/config/mosquitto.conf:ro
- /mnt/usb1/mosquitto/data:/mosquitto/data
- /mnt/usb1/mosquitto/logs:/mosquitto/log:rw
openhab:
image: openhab/openhab:2.4.0
container_name: openhab
restart: always
network_mode: host
devices:
- /dev/ttyACM0:/dev/ttyACM0
volumes:
- /etc/localtime:/etc/localtime:ro
- /etc/timezone:/etc/timezone:ro
- /mnt/usb1/openhab2/addons:/openhab/addons
- /mnt/usb1/openhab2/conf:/openhab/conf
- /mnt/usb1/openhab2/userdata:/openhab/userdata
environment:
OPENHAB_HTTP_PORT: "8080"
OPENHAB_HTTPS_PORT: "8443"
EXTRA_JAVA_OPTS: "-Duser.timezone=Europe/Berlin"
USER_UD: "9001"
GROUP_ID: "9001"
I have made no changes to mosquitto. It is a standard installation, without any changes to config
If anyone is interested.. I got MySensors Ethernet Gateway working in a docker container on a RPi, with a radio connected physically to the Pi.
Has anyone successfully installed a raspberry pi Mysensors MQTT Gateway in a docker container?
There is a docker file with a mysensors mqtt online, but it does not work.
And if it where, it is lacking personalization files and config files.
@therik No, I haven't solved it. But I haven't tried much either. The IKEA Molgan piggy-back-pcb is a openhardware device used by many people. One would think it either works as designed or does not work. If the radio is broken, that is one thing, but I have tried two radios. And the sensor can send data, the gateway responds, but the sensor does not recieve.
I have also tried to changed the radio to a RFM69H... that works. I get no errors. The RFM69H is a Rasperry Pi gateway, the NRF24 is the Sensbender Gateway designed my the MySensors people.
I will try on the NRF24 to add a capacitor, but again, if it is not there on original design and original design works for others, why would I need one?
I have the Sensebender Gateway with a NRF24 long range. No signing, no encryption, just the SerialGateway sketch uploaded.
I have a node (IKEA Molgan) with the sketch uploaded (NRF24 and also no signing/encryption).
There is only one gateway and one node. No other NRF24 devices in range.
The GW and node doesn't communicate, but when one sends the other response (the log files grow and leds blink). This is what I get, and question is how do I fix it?
GW
0;255;3;0;9;12390 MCO:BGN:INIT GW,CP=RNNGS---,REL=1,VER=2.3.2-alpha
0;255;3;0;9;12420 TSF:LRT:OK
0;255;3;0;9;12420 TSM:INIT
0;255;3;0;9;12421 TSF:WUR:MS=0
0;255;3;0;9;12427 TSM:INIT:TSP OK
0;255;3;0;9;12427 TSM:INIT:GW MODE
0;255;3;0;9;12428 TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;12428 MCO:REG:NOT NEEDED
0;255;3;0;14;Gateway startup complete.
0;255;0;0;18;2.3.2-alpha
0;255;3;0;9;12429 MCO:BGN:STP
0;255;3;0;9;12429 MCO:BGN:INIT OK,TSP=1
0;255;3;0;9;12429 TSM:READY:NWD REQ
0;255;3;0;9;12465 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
0;255;3;0;9;23256 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;23257 TSF:MSG:BC
0;255;3;0;9;23257 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;23258 TSF:PNG:SEND,TO=0
0;255;3;0;9;23258 TSF:CKU:OK
0;255;3;0;9;23258 TSF:MSG:GWL OK
0;255;3;0;9;24023 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;25252 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;25253 TSF:MSG:BC
0;255;3;0;9;25253 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;25254 TSF:CKU:OK,FCTRL
0;255;3;0;9;25254 TSF:MSG:GWL OK
0;255;3;0;9;25967 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;27252 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;27252 TSF:MSG:BC
0;255;3;0;9;27253 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;27253 TSF:CKU:OK,FCTRL
0;255;3;0;9;27253 TSF:MSG:GWL OK
0;255;3;0;9;27919 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;29249 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;29250 TSF:MSG:BC
0;255;3;0;9;29250 TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;29251 TSF:CKU:OK,FCTRL
0;255;3;0;9;29251 TSF:MSG:GWL OK
0;255;3;0;9;29867 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
and node
__ __ ____
| \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| | | | |_| |___| | __/ | | \__ \ _ | | \__ \
|_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/
|___/ 2.3.2-alpha
34 MCO:BGN:INIT NODE,CP=RNNNA---,REL=1,VER=2.3.2-alpha
55 TSM:INIT
57 TSF:WUR:MS=0
65 TSM:INIT:TSP OK
67 TSM:FPAR
71 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2088 !TSM:FPAR:NO REPLY
2093 TSM:FPAR
2097 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4110 !TSM:FPAR:NO REPLY
4114 TSM:FPAR
4118 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6131 !TSM:FPAR:NO REPLY
6135 TSM:FPAR
6139 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8153 !TSM:FPAR:FAIL
8155 TSM:FAIL:CNT=1
8159 TSM:FAIL:DIS
8163 TSF:TDI:TSL
@berkseo said in EFEKTA Temp&Hum sensor(ver. nRF52832 )+E-Ink display:
@magpern said in
Seriously!!!!!!!!!!!!! It cannot be true!!! I have just ordered PCBs and all needed stuff to assemble it, and now the code is gone!!! Please post the code again, or make it available on alternative sites.. please. It is hundreds of dollars to waste otherwise!
The project will remain open, like others. I was in a bad mood that day:)... The rules of the site administration are reasonable, and the decision to open the project was mine.
Code for Arduino IDE - https://drive.google.com/file/d/13wmxCt9XehJr1E2eyG1RnYsQTMb9A2LR/view?usp=sharing
Thank you! You scared me big time!
Bad ting without links is that eg. clock button 2 pcs... there are millions of clock buttons and to pick the right one with out a link.. well, almost impossible.
Thanks again!
@berkseo Seriously!!!!!!!!!!!!! It cannot be true!!! I have just ordered PCBs and all needed stuff to assemble it, and now the code is gone!!! Please post the code again, or make it available on alternative sites.. please. It is hundreds of dollars to waste otherwise!
I am about to try some nRF52832 sensors. Can I use the Sensebender Gateway with NRF2401+ to communicate with the sensors?
@berkseo said in EFEKTA Two channel Pulse Counter | nRF52:
I’ll download everything, but I don’t know when. In the queue updating the documentation for other popular projects
OK, thanks. Hope it is soon! In the mean time, I was hoping to order most of the components. Could you help me identify these?
@berkseo said in EFEKTA nRF5 Temperature & Humidity mini sensor:
@magpern said in
Could you upload the schematics or some guide of what component goes where?
Hello, now quite there is no time to do scheme. A very simple scheme is used. Specification on the project page.
Ok, problem is that the only device you have made that has any kind of specification is the e-paper temp device with nRF52 chip. It has like "R1, Resistors 1K" then one knows that R1 on circut board is the 1K resistor.
On your other uploaded projects it only says "Resistors 1K" - that makes it hard to know where to put the 1K resistor.
With some process of elimination one might be able to place the components for the "EFEKTA BME280 Sensor" and this sensor based on the pictures of the competed device on the project page. It is possible to read most of the resistor values from the picture.
But for instance the "Temperature & Humidity mini sensor" you can not tell from the pictures what resistor goes where. The pictures are blurry. Could you perhaps upload a better detailed picture of the front and back?
@berkseo said in EFEKTA BME280 Sensor:
@magpern said in
I had the same problem.
What kind of problems?
That the vias where 0.2mm drill and the fab houses I tried charged 10 times extra for 0.2 drill than 0.3.
But I don't think it is a problem changing them to 0.3 (I changed it in the drill file). The copper pads on the vias are 0.5mm in diameter, and a drill with 0.3 will still work.
Green 0.2mm drill, yellow 0.3mm drill, red is copper.
"L1, Inductance 4.7uh 1210 1 pcs", the text says 4.7uh but link goes to a store that sells 47uh. Which should it be?
@thecricketer I had the same problem. It looks like @berkseo is uskng 0.2mm holes for vias. I simply changed the drill file. The T01C0.2 I changed to T01C0.3. Then I checked all the gerbers in a gerber viewer and the slightly larger holes does work.
Pcbway can read the russian file names. 5 usd for 10 pcs.
But, do you have the schematics? If you have the board it would be a guessing game to know that component goes where.
Me again, I just realized it is a "work in progress", but anyway, I ordered some pcbs, could you, despite it beeing a work in progress, upload the BOM and a "what goes where" description?
Could you upload the schematics or some guide of what component goes where?
Could you upload the schematics or some guide of what component goes where?
I checked your drill files. You do have 0.2mm drills for vias, and it looks they could be changed to 0.3mm without impacting anything. I suggest you change that, it would make it easier to produce.
@berkseo I am interested in this one. I uploaded the gerber files to a fab-house I usually use. The normally charge 5 usd for 5-10 pcbs, but for this one (and your e-paper device), they want over 50 usd. They say it uses minimum hole size is 0.2, which makes it expensive to produce.
Is this correct? If so, what pcb manufacturer do you recommend?
@kontrollable Wow.. the lead times in this conversation.. I saw your answer now. I had about a million other projects going on and havn't taken on mysensors yet. I had some problems with the radio and was about to switch to rfm69, but never got around to it.
Now I started thinking about it again. But, I actually am thinking somewhat in the line of discontinuing mysensors network. It is to much, hacks and tricks, and I forget everything in between sessions. In all the years I have not yet one single mysensors device running. I would love to see more of your set up, maybe it could sway me to try it for the radiator relay setup.
@ahmedadelhosni I had the same problem with serial speed on a few PCBs that I designed myself, design was based on existing mysensors PCBs. I could only run on 38k baud.
In my case it turned out to be a problem with the with of signal lines and power lines on the PCB. They where to small, and probably caused noise and bad through put, because when I widened the lines on the PCB, reordered them from fab house, then 115k baud worked again.
@Anticimex @alexsh1 It's working now! In one of you replies (@Anticimex ), you misspelled the flag name, and I copy / pasted what you wrote. So all this time, signing was never activated. Now it is and gateway works as expected!
@Anticimex @alexsh1 yes should be in other thread. It started with a gateway question and migrated to a signing question. This will be the last one here, since I give up now. I will focus on building a network, and secure it later.
I'm on development branch, so I guess I just need that "specific flag". Couldn't find it in the documentation. I have it set up as the document in doxygen says, and GW should reject unsigned messages or wrong signing, documentation says, but it doesn't... Even nodes that have a different key and MY_SIGNING_ATSHA204 set, talks to the GW and reports temp.
I'll wait until beta is released
@Anticimex Thanks again. So, really, to have hardware and software at the same time exposes the hardware key in the nodes that have soft signing, since all nodes need same HMAC, regardless of HW or SW.
I enabled MY_SIGNING_ATSHA204 and MY_SIGNING_REQUEST_SIGNATURES in the gateway
What I understand, this should activate signing (https://www.mysensors.org/about/signing and the "How to use this" part)
I then took a bender with the same ATSHA keys, but without "MY_SIGNING_ATSHA204". It showed up in MYSController and reported temp. I changed the key in ATSHA to something other then the GW, it still shows up and reports the temp. So, clearly there must be something else to change as well?
I read this in the documentation: "If this [MY_SIGNING_REQUEST_SIGNATURES] is set in a gateway, it will NOT force all nodes to sign messages to it. It will only require signatures from nodes that in turn require signatures."
I intemperate this as, the gateway will require signatures, if the node says so, but it will talk to nodes that don't require signing too.
All sketches are the default example sketches, except for the setting of the MY_SIGNING...
Maybe I am over-shooting the target? What I'm after is: my devices are mine alone and they should only report to me. My receiver (GW) should only listen to my devices and ignore the neighbor's devices. The neighbor should not be able to talk to my devices.
@tbowmo Ah, found a setting ""Accept new hardware/sensors" and a button for "allow for 5 minutes" that could be used as a global "include"-button
@alexsh1 well, maybe, maybe not. Don't know if I agree about not having an inclusion. Almost every device you buy you have to "pair" with something. Anyway, for now disable "allow new hardware/sensors" will do.
@Anticimex I will re-read everything and test stuff now when I have a GW and two nodes to play with.
A quick question - Is it possible to have the gateway to allow soft signing for some nodes (those without a ATSHA) and hardware signing for those with and reject everything else?
I found this sentence:
It is legal to mix MySigningAtsha204 and MySigningAtsha204Soft backends in a network. They work together.
The word backend is in plural, does it mean I need one GW with ATSHA and another with soft signing?
@Anticimex Thanks. Yes I have read it and read it and read it... doesn't mean I understand it or know what to do, unfortunately. At this point I am only using the standard examples, the standard GWserial and standard sensebender micro sketch. Without modifications, except for the MY_SIGNING_ATSHA204.
It is so much to go through.
@alexsh1 Feels like this could be changed, so inclusion also would work for domoticz. A also have a z-wave module hooked up to domoticz and for the z-wave there is inclusion. Just have to find the right person for it
Yes the signing. I have tried. I want everything on the mysensors network to use signing, I have enabled the MY_SIGNING_ATSHA204, all sensors have the same keys in the chip. Is it using the signing if I have done this? I will try and hook up a sensor without the correct keys and see what happens. Just have to solder it first.
@hek Thanks, I'll try that. The controller is Domoticz. Does Domoticz have a flaw when it comes to inclusion? (I guess it must have, since any random sensor gets included automatically).
Is it really correct that orange, green and red led should light constantly when powered on. On some activity from the sensors the leds blink, but goes to full constant light directly.
An other thing, inclusion button. In sketch this is commented out, should it?
// Digital pin used for inclusion mode button
//#define MY_INCLUSION_MODE_BUTTON_PIN 3
For me it is like GW is in constant inclusion mode. Gateway seams to work, it shows up in controller, and as soon as a sensor is powered up, it automatically also appears in controller... feels very unsecure. Just give power to a random sensor and it is in my controller.
@Anticimex @tbowmo an #ifndef made it work and sketch compiled.
@Anticimex I'm sorry, my vacation brain just cannot comprehend all these terms (I don't think it would even if I wasn't on vecaction My four hour experience with c/c++ surely has its limits).
Is it safe to say, the GW sketch does not use the ATSHA chip, and the sketch needs some modification for it to start using it?
In the mean-time, I'll try it out with the default sketch. It looks like the GW and the bender are talking to each other
@Anticimex Ah, I was under the impression that the SenseBender Gateway, came with default serial sketch without signing and you had to enable signing by your self if you want it. And some how in MyConfig.h (not MySensors.h) this sounded like something that needs to be changed (comment said so).
/**
* @def MY_SIGNING_ATSHA204
* @brief Enables HW backed signing functionality in library.
*
* For any signing related functionality to be included, this define or @ref MY_SIGNING_SOFT has to
* be enabled.
*
//#define MY_SIGNING_ATSHA204
So after configuring the ATSHA chip and uploading the serialgateway to the GW, without altering any code, it will start using the ATSHA chip and reject those without?
Is it the same with Sensebender Micro? If it has a ATSHA chip it will use it, if it doesn't it will not?
I run the development branch code, 2.2.2-beta
Is it correct, that if you want to enable ATSHA204A chip in gateway, you need to enable this in MyConfig.h?
//#define MY_SIGNING_ATSHA204
If I do, I get a lot of compile errors, see below, if I don't enable it, it compiles fine. It is development branch (I guess...). Setting up the environment is quite the trial and error
In file included from C:\Users\aaa\Documents\Arduino\libraries\MySensors\examples\SensebenderGatewaySerial\SensebenderGatewaySerial.ino:86:0:
C:\Users\aaa\Documents\Arduino\libraries\MySensors/drivers/ATSHA204/ATSHA204.cpp:6:16: error: redefinition of 'uint8_t device_pin'
static uint8_t device_pin;
^
In file included from C:\Users\aaa\Documents\Arduino\libraries\MySensors/MySensors.h:166:0,
from C:\Users\aaa\Documents\Arduino\libraries\MySensors\examples\SensebenderGatewaySerial\SensebenderGatewaySerial.ino:84:
C:\Users\aaa\Documents\Arduino\libraries\MySensors/drivers/ATSHA204/ATSHA204.cpp:6:16: error: 'uint8_t device_pin' previously declared here
static uint8_t device_pin;
^
In file included from C:\Users\aaa\Documents\Arduino\libraries\MySensors\examples\SensebenderGatewaySerial\SensebenderGatewaySerial.ino:86:0:
C:\Users\aaa\Documents\Arduino\libraries\MySensors/drivers/ATSHA204/ATSHA204.cpp: In function 'void swi_set_signal_pin(uint8_t)':
C:\Users\aaa\Documents\Arduino\libraries\MySensors/drivers/ATSHA204/ATSHA204.cpp:23:13: error: redefinition of 'void swi_set_signal_pin(uint8_t)'
static void swi_set_signal_pin(uint8_t is_high)
^
and a lot more...
@Anticimex I'll start living on the edge immediately. It's the way to go!
I switched to develop and could change the band rate, however develop version skips UART confirmation by default so I never had the problem there. Never needed to send any keys. Got the chip configured atleast.
I kind of started in the wrong end - designed my own pcbs, then start to know the development environment.
But I'll figure it out... just takes time.. thanks for the help!!
@Anticimex hehe, true... but I am a developer by trade, and bypassing something just because it would be easier, feels so wrong. I might end up doing so, but I'll give it some more tries first. Problems are a very good way to learn, and in arduino development I am a total noobie, more used to C# and the .NET world.
@Anticimex I am so not familiar with the arduino/mysensors development yet, but I guess I use 2.1.1, since i used "Sketch / Include Library / Manage Library" and it had 2.1.1
@mfalkvidd Since I have the line Serial.begin(115200) I assume it is 2.1.1, but changing it to 9600 and uploading the sketch does nothing. I still need to open serial window with 115200, else I just see garbage as output from the mini pro.
I will try the development version and see if that helps.
I cannot get my china USB to Serial device to work with the arduino boards, so I cannot program the board to run the personalization. As a work around a use a Arduino Uno board as the "USB to Serial" and now I can upload the sketch and the personalizer writes to serial output fine at 115200 baud.
But, when it wants me to press SPACE, it responds with "Unexpected answer. Skipping lock."
I tried an other sketch that does Serial.read() and echos back the result. It does not work at 115200 but works at 9600 baud. At 9600 I get char 32 back as SPACE, but 160 or 130 or 254 at 115200. Maybe the Uno board cannot handle 115200?
So, question: Can the personalizer sketch be changed to use 9600 (or something slower than 115200)? I tried to change the Serial.begin(115200) to 9600, but it is still 115200.
(of course, I can alter the code to bypass the press SPACE to press any key, but I want to get to the bottom with the problem)
Hi, I saw this project today.... It is like I wrote it myself. I also have IQTherm on my radiators and it was also my goal to replace them with something. I started thinking about it and experimenting with the triac a year ago, but I had to shift focus to something completely different and my project became dormant. Now I am about to start it up again.
How far have you come with your project?
My initial thought was to turn the triac into a mysensor enabled relay and have the temperature sensor in a separate module and let them communicate over the mysensor network.
The triac is as you say 240/400 Volt and quite limited space. I tried to squeeze in a arduino but ofcourse it cannot fit safely. I started drawing a smaller pcb that would custom fit the triac, but I ran into some problems and the I had to stop the project... My thought was to control the optocoupler chip from the arduino and take the power from the dirty 12VDC available in the triac.
Please share your thoughts if you have gotten any further /Magnus
@tbowmo Thanks! Yes. I read that it was not needed, but since it said "if you want higher precision" I though that, higher is good, and it would not hurt to place one there. But the crystals I have are 12.5pf so I guess I can't use them, but on the other hand I don't need to buy any other
HI, I'm about to experiment with a modded version of the sensebender and I while looking at the schematics of the original sensebender, I see that the crystal does not have any pf capasitors and not connected to GND. Why is that?
All other schematics of atmega or any microprocessor I've seen has dual 22pf caps over the crystal and connected to ground.
@tbowmo what type of capacitors do you use for the sensebender? The 100nf are ceramic I suppose, but what about the 4.7uf for radio?
This project of mine pretty much has one major use case.
Total automation of all radiators in the house.
The hardware to do this is quite simple, a triac controlled by an Arduino + nRF and a separate temperature sensor located on the wall with its own Arduino + nRF.
I have eight radiators I want to control. I might have eight temperature sensor or have one that controls two radiators. That is not yet decides.
I have a mysensors gateway (TCP/IP connected) linked to a Vera Edge.
What I need?
I need help with the design or ideas how to realize this. Do you have any ideas? See my details below. Assume the hardware exist already, what I need is ideas of how to connect everything.
I want to control each radiator or group of radiators. Eg.
In one room I might want:
06.00-08-00 I want 22C
08.00-17.00 I want 16C
17.00-23.00 I want 22C
23.00-06.00 I want 16C
And different in other room and on weekends some other setting.
Where should this logic be? Should the temperature sensor have this logic or should the Vera have this logic. Is that doable with already existing plugins? If logic in the temperature sensor, how could this data be set? By Vera or do I need an other way of setting the data in the sensor memory (separate webinterface / MYSController or from a LCD with buttons (self developed))
I would also be able to temporarely override current settings like if temp currently is 16C I want to set it to 22C manually till next fixed intervall gets active. Any ideas about this?
The current room temperature should be visible in a smart way, Vera dashboard (and possibly on a LCD on the sensor). I guess this is the easiest thing. All that already exists.
Its daily usage must be wife-friendly as well...
Thanks!
Thanks @tekka that did it. I didn't have a capacitor on the gateway. I added a 4.7uF and now the sensor pops up in MYSController. (The capacitor recommendation was not in the ESP8266 setup, hense lack of one)
Thank you so much. One less thing to loose sleep over.
Hi @tekka. I just took a ESP8266 NodeMcu V0.9 and connected a NRF24L01+ radio to it. Uploaded sketch according to instructions found about this gateway.
Then I did the same thing with a Mini Pro, hooked up a NRF and uploaded the RelayActuator.
I didn't change any code, more then the LED pin on the gateway, SSID and password for WIFI.
Applyed power to gateway, started MYSController, applyed power to sensor.
And this is what I get
2015-10-14 22:30:13 STARTUP Initialize message logging
2015-10-14 22:30:13 STARTUP MYSController 0.1.2.282
2015-10-14 22:30:13 STARTUP FPC 2.6.4 / Lazarus 1.4.2
2015-10-14 22:30:13 STARTUP still under development :) tekka 2015
2015-10-14 22:30:13 STARTUP Load INI file...
2015-10-14 22:30:13 STARTUP INI version 0.1.2.282
2015-10-14 22:30:13 INFO *** Logging START ***
2015-10-14 22:30:13 VERSION MYSController 0.1.2.282
2015-10-14 22:30:13 STARTUP INI file loaded
2015-10-14 22:30:13 STARTUP Loading FW repository...
2015-10-14 22:30:13 REPO FW "Blink" loaded. t=10, v=1, blocks=72, crc=0xD098
2015-10-14 22:30:13 REPO FW "TimeReporter" loaded. t=20, v=1, blocks=840, crc=0x4AC5
2015-10-14 22:30:13 REPO FW "Sensebender Micro" loaded. t=100, v=1, blocks=1344, crc=0x3482
2015-10-14 22:30:13 REPO FW "Sensebender Blink" loaded. t=110, v=1, blocks=768, crc=0x1314
2015-10-14 22:30:13 REPO FW repository loaded. Items=4
2015-10-14 22:30:13 STARTUP Initialize message types
2015-10-14 22:30:13 NODE New node discovered, node id=0
2015-10-14 22:30:13 NODE New node discovered, node id=255
2015-10-14 22:30:17 INFO Connected to 192.168.0.250:5003
2015-10-14 22:30:17 CHILD New child discovered, node id=0, child id=0
2015-10-14 22:30:17 RX 0;0;3;0;14;Gateway startup complete.
2015-10-14 22:30:25 UPDATE 4295098650
2015-10-14 22:30:38 CHILD New child discovered, node id=255, child id=internal
2015-10-14 22:30:38 TX 255;255;3;0;4;1
2015-10-14 22:30:38 RX 255;255;3;0;3;
2015-10-14 22:30:39 TX 255;255;3;0;4;1
2015-10-14 22:30:39 RX 255;255;3;0;3;
2015-10-14 22:30:41 TX 255;255;3;0;4;1
2015-10-14 22:30:42 RX 255;255;3;0;3;
2015-10-14 22:30:43 TX 255;255;3;0;4;1
2015-10-14 22:30:43 RX 255;255;3;0;3;
Yet again thanks @Dwalt.
I guess I'll have to wait for the Vera Edge to arrive. Can't make head or tail out of this.
I don't get anything useful out of MYSController. I have tried to read about it, but I can't find anything but the forum thread about it. Everybody seams to already have it running and have other problems (and talk about MYSBootloader alot)
MYSController connects to my gateway at 192.168.0.250:5003. It says
0;0;3;0;14;Gateway startup completed
when I power up my sensor, MYSController does some TX and RX (I also see thing happen in telnet client).
2015-10-14 22:05:23 TX 255;255;3;0;4;1
2015-10-14 22:05:23 RX 255;255;3;0;3;
But that's about it. Nothing more. Nodes does not update, routing table is the same
it just say this in the nodes list
0 - Gateway
Broadcast
Thanks @Dwalt . I was looking at the MYSController and I got the impression you need to have special bootloader. Is that so? I have searched for how-to's for this but I can't find anything. Do you know where I can find something where I can start?
I did download it and ran it, entered the ip of the gateway, if found it.. but it kind of stops there... next step is unclear.
Hi,
I am a total newbe at arduino and mysensors, but I am trying.
Is there any complete guide of how to set up a gateway and sensors?
I have searched and searched but I only find pieces. I end up with more questions each time.
My problem is: I have wired up a ESP8266 with NRF24L01+ as gateway and installed the sketch ESP8266Gateway. It connects to to my WIFI and gets a ip adress. I can connect to it with putty, it responds that gateway is running.
I also wired up a arduino mini pro and a NRF24L01+ and a LED that I can control and installed the RelayActuator sketch.
When the latter powers up, I see lights flashing on the ESP8266
But now what? What do I do now?
How do I know if they have found each other?
Aren't you supposed to trigger some inclusion?
Can I send commands through putty or do I need something else? (will get a Vera Edge tomorrow).
Really, what is my next step?
Thanks!