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).
You're right. Updated codebender library just now to the most recent on github/master
Not sure if codebender autodetects this if you already cloned it to your local account.
@canossa Sorry for the late response.
yeah, since is so compact and you can get it for relatively cheap I opted in for the NRF52.
For home automation, I merged MySensors with Domoticz and it works for months now.
https://forum.mysensors.org/topic/7836/what-did-you-build-today-pictures/738
Hi all,
Should anyone face the same problem, I found the root cause: brownout threshold. I burned a new bootloader (Optiboot 8.0) without such trigger and the node has been working with used batteries (~2.7V) since May.
Hope this helps.
@A3V such a feature would definitely make sense now that gateways can have local sensors. But no-one has added it unfortunately.
A solution could be to use the code at https://github.com/mysensors/MySensors/blob/2e00bf6a10f76d6aaa1999e12313237bc3edabd3/core/MyTransport.cpp#L446 as inspiration and do something similar at https://github.com/mysensors/MySensors/blob/2e00bf6a10f76d6aaa1999e12313237bc3edabd3/core/MyGatewayTransportEthernet.cpp#L175
Hi @berkseo. Thanks for the suggestion, but could you describe in more detail? As for my TODO list, there is already a task to add 485 interface to the gateway. My latest device "xRoom" have this interface.
ps/ Where have you gone?
I have been working on "xRoom" shield. A small announce:
Do you remember the discussion about multinode? So, it will be available soon))