@nca78 said in Security: 433 RFX vs Mysensors security:
@chbla said in Security: 433 RFX vs Mysensors security:
@nca78 I'm still deciding what to use. Pro Mini if I don't find anything better.
I'm interested in where you buy your BME680 breakout boards, there are not so many around
I think I bought them here: http://www.watterott.com/de/BME680-Breakout
I'm located in Austria
@nca78 I'm still deciding what to use. Pro Mini if I don't find anything better.
@nca78, unfortunately, I can't make my own boards so I have to use breakout boards.
However, it's not really a problem as I want to stay flexible anyway.
Thanks for the explanation! I will now rather invest into more Mysensor nodes + RFM69 as it's simply more flexible.
@Nca78 the reason I'm also using mysensors on the temp nodes is that it allows me to use custom sensors (for these types mostly BME280/680).
@mfalkvidd said in Security: 433 RFX vs Mysensors security:
@chbla when combined with encryption, the MySensors signing does a pretty good job of obfuscating what is going on. But since the mere existance of a radio message leaks information, encryption does not solve the problem. Sending fake radio messages at random intervals might be a good way to further obfuscate what is going on, but if an attacker sets up a camera or tracks your phone there will be information leakage again.
Do you have any links to what people use already in terms of encryption?
In any way it's a valid point to say that the likelihood of someone actually monitoring this is quite low.
However, since those chinese 433mhz devices are used so often, it's a bad feeling.
If only they weren't that cheap 
I wonder how others are doing it, or if most people just ignore that problem?
Yes I have read it, however, it does not address the problem of actually hiding what's going on.
Hi there,
I want to equip parts of house with door/window and PIR sensors.
I initially tought that I will use cheap 433mhz sensors that are integrated with RFXCOM into openhab (which is also the sink for my mysensors network).
They are around 3-4$ per sensor. I would then only use mysensors for things like temperature monitoring, some actors, etc.
However, the obvious problem is security. With those cheap 433mhz sensors it is pretty easy to just listen and tell when my basement door or a certain
window is open or not, if someone really wants to (ignoring the chances right now).
Mysensors seems to be more secure here, but I assume that there are limitations regarding encryptions.
How do you see this and how do you do it? Any suggestions appreciated..
I need help 
- I have soldered the whole thing to a prototyping board, and now the Pro Mini keeps resetting.
Does anyone see a problem in the following schematic? (sorry for the drawing, I'm a bit limited here).
As mentioned I'm using a MOSFET, switched on/off via Pin 7.
Mosfet: https://de.aliexpress.com/item/10PCS-IRLB8721-TO220-IRLB8721PBF-TO-220-free-shipping/32714364118.html?spm=a2g0s.9042311.0.0.FjZdIJ
Vreg: https://de.aliexpress.com/item/2pcs-DC-DC-Power-Supply-Converter-Step-Up-Boost-Module-1A-3V-to-5V/32598574742.html?spm=a2g0s.9042311.0.0.IFPbYZ
Lvl Converter: https://de.aliexpress.com/item/Free-shipping-1pcs-4-channel-IIC-I2C-Logic-Level-Converter-Bi-Directional-Module-5V-to-3/32670479389.html?spm=a2g0s.9042311.0.0.OAwsE9
It was working fine on the breadboard, but I have verified all the connections.
Right now it seems to reset all the time (2nd LED blinking on the arduino).
The regulator switches on and off with 1hz, the voltage between I+ and I- changes between 1.0V and 2.4V
If I connect GND to the regulator directly, bridging the Mosfet, it works.
Any idea?
@qqlapraline good to hear! Thanks for the confirmation
What I mean is, those should be connected to GNDT not GND as in your diagram - right?
GND is permanent ground.
I noticed I'm losing current through the trigger pin, the cause is apparently that if disconnected, the system is only on VCC.
Since the trigger bin is set to LOW in my previous sketch, it loses current there.
But I found out that if I set the trigger pin to HIGH before sleeping, it's fine. My sketch uses 78ua while sleeping. Using a MOSFET at the moment
to switch.
I have a working setup now, however, it seems that I lose current through the trigger pin.
If I disconnect it, it drops.
@qqlapraline what I don't get is: Do you really have GND on the high side of the LVL converter connected to GND as in your schematic?
Since the GND sides on the converter are connected, this closes the loop for the regulator, thus it would be turned on all the time?
Same for the HC-SR04
Thanks!
@gohan is that possible with mysensors and the RFM69s? (I have it open, but did not yet read the security docs)
That's a good and valid point speaking for mysensors - right now I only use them for my weather sensors so I did not look into security with the RFM69s yet.
@gohan Can you elaborate? You mean as a reason against the chinese ones? And due to what?
Hi there, I need your opinion:
Say you want to equip a room with 2 reed switches (2 windows), 1 Temp/Humidity sensors and a PIR.
For temperature I'm using DIY mysensors nodes (433mhz), and I could do the same for the windows and PIR.
However, I also have a RFXTRX433e for my blinds, and the price for 433mhz sensors is so extremely cheap these days
I wondered if I shouldn't just combine/mix those in addition to my mysensors nodes.
Reasons for chinese sensors:
Reasons against:
I'm interested in opionions, I assume some people had this decision as well - what are the pros and cons you
determined?
Thanks,
Christoph
I was referring to the TX power, right.
Thanks a lot for the answers! I guess in this case it's much more more flexible to go with the HCW layout.
Hi there,
A quick question: Does anyone know if the libraries for the RFM69 allow to use the HCW in low power mode?
I would prefer to use boards with HCW layouts instead of 2 separate ones for HCW and CW to be more flexible.
But I'm not sure if
a) the HCW can be used in low power mode and b) if it equals the power consumption of the CW (or if there are any benefits
using the CW).
I heard that some libraries allow auto adjusting the transmission power based on the RSSI - does anyone know something about this?
Thanks a lot,
Christoph
I tried this with a similar setup but RFM95 for LoRaWan and without the transistor as I'm testing it directly on USB.
A pololu 5V stepup regulator does not even work directly on VCC - if I connect the HC-SR04, voltage drops from 5V
to 1.2V after the regulator.
I then tried a different regulator from aliexpress, this setup works with the regulator on VCC, but if I try to control it through a
Pin, Voltage also drops and does not even power the regulator (it has a LED)
Thanks for the suggestions! I think I will first try the LED stripe way, it's probably the easiest for now.
@Koresh would it be possible to sell this without the sensor part and RFM69? How many orders would it need?
I don't have the possibility to produce it myself, don't need the sensors part and have a lot of RFM69s lying around..
Thank you,
Christoph
@yury said in 
Button size radionode with sensors swarm extension:
@chbla said in
multimeter
You should be fine even with a cheap multi-meter as long as it has uA scale.
should be around 7-10 uA and if you do not send JDEC to sleep it is 17 -19 uA.
to send JDEC to sleep\wakeup I use
_flash.wakeup();
_flash.sleep();light sensor should be sent to sleep explicitly also.
Right - but this is all in your sketch right? This is what I used:
https://gist.github.com/solars/a5302f1cb60d90f89d7e37d5e23f8c4d
@gohan I only have a normal multimeter - what's the best way to do this?
I came across https://www.eevblog.com/projects/ucurrent/ a while ago, is it worth it?
@gohan said in Button size radionode with sensors swarm extension:
is it sleeping 5 seconds only?
You are right, that was my mistake after testing it. However, the consumption still seems high.
For example I'm right now testing a BME280 which I want to use in the future, with the following sketch:
https://gist.github.com/solars/a5302f1cb60d90f89d7e37d5e23f8c4d
It's connected to SDA/SCL and GND/V - somehow the voltage it receives with a fresh battery is already quite low, and it also doesn't last very long.
What's the typical time you get with the default node, coin cell and the sketch on github?
https://gist.github.com/solars/6116b78ea7ee581ecfafddb8da4a9610
It drained within only 1 day for me
Hi there,
I have two sheds (3x3m each) that have no electricity so I plan to add solar lights (switch, not motion triggered).
I figured it makes sense to start with the leds so I can test and see what kind of battery and solar panel I need.
Can anyone suggest efficient (but not too expensive) LEDs for this purpose? I have absolutely no experience here.
Aliexpress preferred
Thank you,
Christoph
Thanks, I'll try that!
@mfalkvidd Thanks a lot for trying this out! I wondered if it is interpreted or used in a special way by the gateway already.
But in this case I can do that myself.
Thanks again!
Sorry I mixed up things - what I mean is, if I have a gateway that forwards to MQTT - regardless of the controller - how does the sendBatteryLevel data end up in the queue? Obviously it has different semantics that "normal" messages sent with send() ?
Hi there,
Quick question, I read a lot about using sendBatteryLevel() on my nodes, however, I cannot find any information on how this is actually used on the controller side.
My gateway forwards to MQTT, will it just generate a message for the battery level or how is it used?
With the default sensor and sketch I only get integer values - shouldn't this be decimals with 2 digits after the . ?
Not sure if I have a different lib or missed something
@chbla said in Button size radionode with sensors swarm extension:
Maybe a stupid question but how do you connect the FTDI adapter? I only know the ISP pins
Can anyone quickly tell me how to do it correctly? I thought it didn't work but I'm unsure.
Maybe a stupid question but how do you connect the FTDI adapter? I only know the ISP pins
@Koresh said in Button size radionode:
@chbla Thank you for your attention to this project. The project button size node with extension is improved version of these project. So those project implements all of features. Moreover last week I ordered improved version of those pcb. If you do not need extention you can just cut it. I plan to place order in the local factory in a week. So if you want I can make some boards without battery holder and extra sensors.
Thanks! I found it meanwhile great work
Any news on this? I would be interested in the design
Thanks a lot for the clarification @mfalkvidd that helps!
Hi there,
I noticed mysensors now also supports LoRa as the transport layer.
Can anyone outline what the benefits are in comparison to the existing ways?
I'm using RFM69s at the moment.
Thanks a lot
Christoph
Can anyone suggest a source for the parts? Are there any sources that you can upload the files by any chance?
Please make it available for purchase
I figured out it seems to be the voltage regulator - if I connect directly or with a 3.3v power supply, it works... very weird
@Reza it depends on the use case I think, peope are using both, both are working. NRF24 is easier to set up and seems to have more support. Just try it
I'm using RFM69 yes, and it has no problems.
I don't need repeaters at the moment, as far as I know it's software based?
It is not based, you can use a RFM69
Hi there,
I'm experimenting with different setups, and for a door sensor tested:
I noticed after a while the arduino LED (outer, marked with L) starts flashing at around 1HZ and it doesn't transmit anymore.
The voltage is at 3.3V, battery voltage around 1.4V.
Does anyone know what causes this? Is it maybe not getting enough power?
A supercapacitor with a small solar cell would be interesting - does anyone have experience (3.3/5v size of capacitor, solar cell, etc)?
Why based on nrf24? I came to the party late, but started with RFM69/433 - you are not bound to 2.4ghz in any way, it's just what people used to start with.
Thanks, the adapter boards look nice. I'm still not sure what I should use, experimenting with a single AA cell at the moment.
Does anyone know how 2xAA compares to 1xAA + good regulator that can squeeze the maximum out of a battery?
Is it a huge difference?
I also considered it .. I'm not sure yet what the best - and most compact solution is..
Hi there,
I'm experimenting with pro minis and RFM69 433mhz at the moment.
It's working great so far and I'm very impressed by mysensors.
I now want to add more sensors in my house (PIR, Reed for Doors, BME280 for room temperature) - some combined, some individual.
Ideally, they should be as compact as possible and use AA/AAA, one 18650 or even CR2032 (not sure about the runtime) -
I'd like to stay away from lipo due to safety concerns.
As I don't have experience in creating my own boards, I'm looking for complete solutions right now.
I came across the Adafruit Feather 32u4 with RFM69HCW 433 and the Talk2 Whispernode.
Another alternative I saw is the Pro Mini 3.3V + regulator + RFM69
Any recommendations? Whispernode looks pretty cool, does anyone know typical run times?
Thanks a lot,
Christoph
@Fabien said in Receiving but !TSM:UPL:FAIL and no communication? 2.1.1 issue?:
In your gateway your don't
#define MY_RFM69_FREQUENCY RF69_433MHZ. By default it sets to RF69_868MHZ
Oh my god! What an incredible stupid mistake!
I wasted all this time trying to get the NodeMCU to work only because I forgot that setting in my initial Wemos Sketch...
It's finally working now.. haha. Let me know when you're in Austria @Fabien you deserve a beer
@Johannes-Hodne thanks for the suggestion but it's finally working now
@Fabien thanks a lot!
I've set it up like you now, but now the GW doesn't seem to read any messages... damn
https://gist.github.com/solars/823bc62306909efd3fbb1a66b5211b31
Any idea what's wrong again now?
@Fabien I have now used a second power supply for the RFM69 (5V), USB for the Nodemcu, connected grounds together. But it's still the same..
I also tried a different radio.
Do you maybe have a picture how you connected the Wemos D1 Mini and sketch used? I guess I just had a wiring problem with the wemos.
I would like to try again.
VIN on the Nodemcu produces WDT resets, not sure why.
I've now connected the RFM69 to the 5V output of a Wemos D1 Mini, and the board via USB.
I'm still getting the same results: https://gist.github.com/solars/7ed4541372f37166910ca4d1842d8c32
Trying to use a regulator I have for the breadboard if I find a suitable power supply.
This is really frustrating.
I tried with a Wemos D1 Mini earlier - only produces WDT resets.
Then tried with Arduino Uno + W5100 Ethernet shield, only to find out it's quite complicated
to get this to run with an RFM69 due to soft spi.
All I want is get this communication to work..
@Fabien, thanks for your help!
The antenna is 164.7mm yes.
Regarding VIN - what's ideal to use here? I'm not sure how much power it needs, I've got a bunch of USB power supplies
that I tried.
Pictures of the GW and RFM69 Module:
https://www.dropbox.com/sh/txuqvkk1di9awj9/AABpvof5jKt2nq5Vd2rvFrn4a?dl=0
I would really appreciate if anyone could help me get this to run 
Thanks for the reply @Fabien
I'm using this breakout board: https://www.adafruit.com/product/3071 - as far as I understood it has a regulator, is this not sufficient?
Hi there,
I want to get started with mysensors but it doesn't want to work. GW is a Nodemcu with MQTT, Client is a Pro Mini clone. Radio is Adafruit 433Mhz breakout board.
Gateway log:
1384, room 16
0;255;3;0;9;MCO:BGN:INIT GW,CP=RRNGE--,VER=2.1.1
0;255;3;0;9;TSF:LRT:OK
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
scandone
f 0, .0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
...scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 3
cnt
connected with wlanbt, channel 1
dhcp client start...
.0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
....ip:192.168.1.57,mask:255.255.255.0,gw:192.168.1.1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
.IP: 192.168.1.57
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
IP: 192.168.1.57
0;255;3;0;9;Attempting MQTT connection...
0;255;3;0;9;MQTT connected
0;255;3;0;9;Sending message on topic: mygateway1-out/0/255/0/0/18
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
pm open,type:2 0
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
Client log:
MCO:BGN:INIT NODE,CP=RRNNA--,VER=2.1.1
10 TSM:INIT
12 TSF:WUR:MS=0
16 TSM:INIT:TSP OK
18 TSM:INIT:STATID=1
20 TSF:SID:OK,ID=1
22 TSM:FPAR
22 TSM:FPAR:STATP=0
26 TSM:ID
26 TSM:ID:OK
28 TSM:UPL
161 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
2168 TSM:UPL
2299 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=1,st=NACK:1
4308 TSM:UPL
4440 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=2,st=NACK:1
6447 TSM:UPL
6578 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=3,st=NACK:1
8585 !TSM:UPL:FAIL
8587 TSM:FPAR
8587 TSM:FPAR:STATP=0
8589 TSM:ID
8591 TSM:ID:OK
8593 TSM:UPL
8726 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=4,st=NACK:1
10733 TSM:UPL
10864 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=5,st=NACK:1
12871 TSM:UPL
13004 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=6,st=NACK:1
15011 TSM:UPL
15142 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=7,st=NACK:1
17152 !TSM:UPL:FAIL
17154 TSM:FPAR
17154 TSM:FPAR:STATP=0
17158 TSM:ID
17158 TSM:ID:OK
17160 TSM:UPL
17295 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=8,st=NACK:1
19302 TSM:UPL
19435 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=9,st=NACK:1
21442 TSM:UPL
21573 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=10,st=NACK:1
23580 TSM:UPL
23711 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=11,st=NACK:1
25718 !TSM:UPL:FAIL
25720 TSM:FPAR
25720 TSM:FPAR:STATP=0
25724 TSM:ID
25724 TSM:ID:OK
25726 TSM:UPL
It seems the GW receives data, but something fails. Can anyone tell me what causes this?
Maybe a 2.1.1 issue?
GW and Client code is here: https://gist.github.com/solars/8644c5e310c63cecf93d86dc76955d68
@gohan thanks, stupid question: where can I get it? https://www.mysensors.org/controller/myscontroller is only an image
Clearing didn't help - could it be a RF module issue as well? As I was not sure if wired correctly..
@gohan I've tried setting the child ID, but it still does not work, updated the output:
https://gist.github.com/solars/920dd3151356f6c5795169a36bb01d9a
Any idea?
@gohan, but the Node ID defaults to AUTO as far as I can see (https://www.mysensors.org/download/sensor_api_20).
I'm also sending it in the presentation, right?
What exactly are you referring to or how do you see that?
Thank you @TheoL is it possible to determine whether this is a problem in the client or the gateway?
Hi there,
I'm lost with my setup:
Both have an Adafruit RFM69HCW see here
According to the Adafruit samples the boards need to be reset, which I'm doing.
The first try delivers a lot of output which I cannot really decode yet,
it seems as if they are not talking to each other, but I'm not sure if that's correct and what
all the messages mean.
The output as well as code is here: https://gist.github.com/solars/920dd3151356f6c5795169a36bb01d9a
Could anyone please help me getting started with mysensors?
Did you add an attachment? Can't see anything.
I tried various combinations, if I add DI00 to D4, I cannot seem to flash it, getting errors while uploading.
Whatever combination I used on D2 also didn't work.
The RFM69 settings can be set for the mysensors lib with MY_RF69_IRQ, etc
Did you also connect RST?
Hi everybody,
Is anyone using a Wemos D1 Mini as gateway and can tell me how the wiring looks like for a RFM69 (adafruit breakout board)?
Right now I have:
MISO > D6
MOSI > D7
NSS > D8
SCK > D5
DI00 > D2
But always get resets...
Thanks for your help!