@yveaux thank you for letting me know about this great project! The thread is also very useful.
I managed to find a relatively quiet range in channels.

@mfalkvidd said in New sensor ID-s when changing network:

gateway

A network ID provided by MySensors gateway would be a good solution to solve this problem. Unfortunately I do not expect any development activity in the project. It seems to be dead in the last few years.

@ejlane
As it is mentioned above, it seems to be a new network for HA, since it has a new gateway. I also use fixed IDs in the network. It's a great feature.

I've controlled my nodes from HA in the last some years (I was happier with domoticz, anyway). After some hardware difficulties, I had to replace the Arduino in the serial gateway. Now I have a new gateway hardware and plugged into a different USB which runs Home Assistant.
The result: I have new devices and entity id-s. Great.
Do I need to rewrite all of my scripts, automations, templates, etc...?
Is there any solution to this problem?

Thank you for the new version!
I run my network on 2.3.1. Should I update the serial gateway to 2.3.2 (or stay with 2.3.1) and leave some of my nodes on 2.3.1 and the new ones on 2.3.2?
Are they compatible?

@yveaux thank you for letting me know about this great project! The thread is also very useful.
I managed to find a relatively quiet range in channels.

@skywatch said in Setting up the 2nd RF24 network..:

Thank you! It's something what I was searching for!
https://forum.arduino.cc/index.php?topic=54795.0

This is a snippet from the terminal window:

>   1 2  3 4  5  6 7 8  9 10 11 12 13  14                     <
|  .WRa**+a-:.:.....=..     :..--....                            | 19
|  :aWaWWRR.:.....:....     .....::.:                            | 21
|  :RWRaWRR......-.: ..     .:.:..::.                            | 19
|  -*WRaWW*:.:. ::-:.-.     ==.----:=                            | 15
|  :+**==-:-..-:::--.-.     +WW=***+=                            | 13
|  -RWWRRa*.==:=-:+=-::     -..::::aR                            | 10
|  :RaW++RW:.=:-+-:. ..     :.--=:.a+                            | 11
|  .*+W=*+a.+--.-:.-:..     ..=-.:*::                            | 11
|  :Waa+*-*= ...:..=:..     +:.=-*-.                             | 11
|  :+WWaRW*=+:=====-==.     :.-= ::-                             | 10
|  :+Ra+++W .:::...-:.:      :-=++::-                            | 14
|  +aRaaaRW -+--:.*-++:     ++-::.-*-                            | 8
|  aaa===aR ..=.aW+R.=      aa+: .:=:                            | 7
|   WWWW*R*:                =     :                              | 5

I start to find out and decode it. With MySensors library there are channels supported between 0-125 which means 2400MHz - 2525MHz range. I will need to map them to understand.

Hi,

I'm setting up a parallel network next to my existing one. Since I live in a dense area lot's of different equipment are being used around me. My goal is to find the best settings with the less interference. I have some specific questions about this:

• How should I choose the best MY_RF24_CHANNEL? Do you use any scanner solution? (something like wifi analyzer on Android?)
• Should I modify MY_RF24_BASE_RADIO_ID settings? Any recommendation?

I guessed with the values and it's working now, but I would like to know if there is a more scientific method used to reach a better stability.

config: MySensors 2.3.1, Raspberry Pi 3 B+, nRF24L01+ and nRF24L01+PA+LNA radios

@nca78 about my gateways:

1. an old gateway running on MySensors 1.5 for years now. There are several nodes and sensors connected through it like temperature sensors, relays, switches. It controls my heating system with heat pump, buffering, 18 circles of floor heating, garden irrigation, alarm system, and some lights just for fun.
2. the new gateway is a gateway to a Bluetooth network. Since MySensors has a great serial API and I have some experience with it I preferred to use it without a radio. I also think that it will be an interesting way of development and it could help to make MySensors even more popular. I had an idea to fork the library but unfortunately I don't have the experience and time to make it in good quality. But I'm sure letting developers to build connectors to different protocols is a very good idea. Catching Bluetooth messages from the air and decode them (with some reverse engineering) to send it through the MySensors gateway is relatively simple compared to the bidirectional communications. Processing some simple sensor data is a good first step.

@nca78 thanks for your reply.
Since serial API protocol is very flexible and capable to solve this multi-node problem it could be used as the protocol between controllers and Bluetooth gateways. The only this has to be solved is to allow developers to create "dummy" nodes on the gateway node. If the Bluetooth receiver node (the mysensors gateway) detects a device (hum-temp device in my case) and identifies it using its mac address it should be connected to the controller as a node. This node can have sensors and other parameters like battery level. It's the same as in the MySensors network.

@mfalkvidd tank you for the forum topics. I found the logic of grouping sensors in Domoticz. It quite logical. Now the temperature and humidity grouping works ok.
Unfortunately I still have a problem with the battery levels. MySensors can report it only for a node. I have tried several sensor types like S_DIMMER, S_COVER and everything which has a V_PERCENTAGE variable. Of course any of them is grouped together with tem-hum. Now it's a bit messy, but at least it works.