Welcome to the club!
Regarding radio's: The RFM69's with a C in the type have a smaller form factor (which is pin compatible with the predecessor RFM12B). The the 'W' and "HW' versions are larger in size and have more programmable pins (which MySensors does not use) but have exactly the same functionality within MyS.
All the footprints on the boards available in OpenHardware.io are for the 'W' and 'HW' versions so I'd go with one of these.
The 'W' uses way less power than the 'HW' which would be good the for the battery life of your nodes. Sensors powered by the grid can be 'HW', but usually, in the house a 'W' delivers enough TX power to get the message across. It might be a good idea to make your gateway with a 'HW'.
Hope this gets you a bit further. Good luck and show us your results!
I will answer myself after some testing done today:
How can I change network id for gateway (mysgw)?
It is possible to change MY_RFM69_NETWORKID for mysgw by exporting CPPFLAGS variable with the option set before running ./configure:
example:
export CPPFLAGS='-DMY_RFM69_NETWORKID="101"'
./configure --my-gateway=serial --my-transport=rfm69 --my-rfm69-frequency=868 --my-is-rfm69hw --my-serial-is-pty --my-serial-port=/dev/ttyUSB-MysGW --my-serial-groupname=dialout
make
Is it possible to create another RFM69 network on new hardware, just for the test, while my current RFM69 network keeps running on current gateway/controller?
As soon as I started another RFM69 gateway (mysgw) on new hw, even with different network id (101), most of the sensors connected to my other (production) gateway running on old hw with default network id (100) stopped communicating... so it seems it is not possible to run multiple RFM69 gateways in the same range (on the same freq).
@yury said in Wall Socket Insertable Node:
Looks cool! Do you have experience with capacities switches? I did not play much with them. afraid to use close to AC interference though...
You need to use a capacitive IC with active shielding, basically you have an extra electrode around your touch electrode and the touch IC will compare capacitive change of the touch electrode with capacitive change from the shield electrode. If the change is due to electrical interference then both electrodes will be changed in a similar way and the IC will not trigger.
Hi PJR,
now it is working with this code in the MyTransportRS485 without any changes on MySensors.h:
#if defined(MY_RS485_SWSERIAL)
SoftwareSerial& _dev = MY_RS485_SWSERIAL;
#elif defined(__linux__)
SerialPort _dev = SerialPort(MY_RS485_HWSERIAL);
#elif defined(MY_RS485_HWSERIAL)
HardwareSerial& _dev = MY_RS485_HWSERIAL;
#else
AltSoftSerial _dev;
#endif
As far as I can interpret the peace of code, the
#include "hal/transport/MyTransportRS485.cpp"
is active as soon as the MY_RS485 layer is defined.
This is a great step, I can use all my nodes from now on!
Thank you very much for your support!
By Kduino
@NeverDie said in LCDUINO:
the LCD components don't appear to be named, not even on the schematic
Looks like a typical text LCD like 1602 on the picture.