domoticz auto add device (mysensors) even if disable "Accept new Hardware Devices"
-
@Reza The community cannot focus all energy on supporting your case. Many if not all of your questions are answered in the howtos & forum - why don't you take advantage of the search function, enter "rf channel" and read some of the posts?
@tekka
this is a general issue . not just my problem ! if this issue resolved so can help to many people in future ! the reason of that i question this issue in this forum is after resolved , can help to many. so if you sad from this , ok i will silence in this forum.
thank you -
@Reza
sad from this, is not needed :)
the thing is : this is not a big bug!! generally the big bug is elsewhere ;) Here you have two issues.You are using radios which are on the same frequency. Not a bug. That makes sense that a fresh node for your network can talk with others. If you don't want them on same freq, just change the freq/band using the right define (i don't remember).
It also has been suggested encryption or signing. And that can help you too. Encryption can't help you for this. It just hides crypt the text if you want. It does not authenticate anything. Signing is authentication. But you would need this for all your nodes.
Finally, the inclusion mode. That's mostly the feature you need, because it could help you to block new nodes. I think this is a feature that the controller has to implement. I don't use inclusion mode in mysensors (not tried yet),
but in the controller I'm using (jeedom), it works well. There is one inclusion button (I don't advice you to use jeedom, it's french! and not 2.0 full compliant). As you can see this is possible to have a working inclusion button in controller :)On my side, I actually miss time to do tests or doc on this...but i'm pretty sure all is in main doc, or with the right keyword in the forum...i understand this is not an "out of the box" solution, but temporarily, and maybe with luck and spare time there might be a dedicated doc for inclusion even if it's quite simple..
-
@Reza
sad from this, is not needed :)
the thing is : this is not a big bug!! generally the big bug is elsewhere ;) Here you have two issues.You are using radios which are on the same frequency. Not a bug. That makes sense that a fresh node for your network can talk with others. If you don't want them on same freq, just change the freq/band using the right define (i don't remember).
It also has been suggested encryption or signing. And that can help you too. Encryption can't help you for this. It just hides crypt the text if you want. It does not authenticate anything. Signing is authentication. But you would need this for all your nodes.
Finally, the inclusion mode. That's mostly the feature you need, because it could help you to block new nodes. I think this is a feature that the controller has to implement. I don't use inclusion mode in mysensors (not tried yet),
but in the controller I'm using (jeedom), it works well. There is one inclusion button (I don't advice you to use jeedom, it's french! and not 2.0 full compliant). As you can see this is possible to have a working inclusion button in controller :)On my side, I actually miss time to do tests or doc on this...but i'm pretty sure all is in main doc, or with the right keyword in the forum...i understand this is not an "out of the box" solution, but temporarily, and maybe with luck and spare time there might be a dedicated doc for inclusion even if it's quite simple..
@scalz said:
@Reza
Finally, the inclusion mode. That's mostly the feature you need, because it could help you to block new nodes. I think this is a feature that the controller has to implement. I don't use inclusion mode in mysensors (not tried yet),
but in the controller I'm using (jeedom), it works well. There is one inclusion button (I don't advice you to use jeedom, it's french! and not 2.0 full compliant). As you can see this is possible to have a working inclusion button in controller :)You have to use whitelisting to block nodes. 'Signing' in GateWay does not work as it accepts non signed nodes. Signing primarily is used for nodes receiving info.
-
@Reza
sad from this, is not needed :)
the thing is : this is not a big bug!! generally the big bug is elsewhere ;) Here you have two issues.You are using radios which are on the same frequency. Not a bug. That makes sense that a fresh node for your network can talk with others. If you don't want them on same freq, just change the freq/band using the right define (i don't remember).
It also has been suggested encryption or signing. And that can help you too. Encryption can't help you for this. It just hides crypt the text if you want. It does not authenticate anything. Signing is authentication. But you would need this for all your nodes.
Finally, the inclusion mode. That's mostly the feature you need, because it could help you to block new nodes. I think this is a feature that the controller has to implement. I don't use inclusion mode in mysensors (not tried yet),
but in the controller I'm using (jeedom), it works well. There is one inclusion button (I don't advice you to use jeedom, it's french! and not 2.0 full compliant). As you can see this is possible to have a working inclusion button in controller :)On my side, I actually miss time to do tests or doc on this...but i'm pretty sure all is in main doc, or with the right keyword in the forum...i understand this is not an "out of the box" solution, but temporarily, and maybe with luck and spare time there might be a dedicated doc for inclusion even if it's quite simple..
-
@scalz said:
@Reza
Finally, the inclusion mode. That's mostly the feature you need, because it could help you to block new nodes. I think this is a feature that the controller has to implement. I don't use inclusion mode in mysensors (not tried yet),
but in the controller I'm using (jeedom), it works well. There is one inclusion button (I don't advice you to use jeedom, it's french! and not 2.0 full compliant). As you can see this is possible to have a working inclusion button in controller :)You have to use whitelisting to block nodes. 'Signing' in GateWay does not work as it accepts non signed nodes. Signing primarily is used for nodes receiving info.
@Nicklas-Starkel
are you sure about whitelisting? this problem resolved with whitelisting??? -
@Nicklas-Starkel
are you sure about whitelisting? this problem resolved with whitelisting???@Reza
From what I understand the GateWay will add all nodes even if you do not want them to. But not to the controller if you have "inclusion option" on the GateWay.
There is a possibility that if you use the "inclusion option" maybe it will pick up all sensors not already added (ie your neighbour) if they are sending while inclusion is looking for new sensors.
If you want to stop this you will have to use whitelisting on MAC adress. But this requires you to reprogram GateWay everytime you want to add new sensor (or maybe it is possibility to have same MAC for all?).
And of course you will have to program a MAC adress for all sensors/per sensor the first time as well.
I thought this problem would be solved with only using Signing, but because of backwards compability the creators did not enable this in the GateWay.
If you only would want signing, you could make all nodes connect via a repeater node.
Because between repeater nodes and regular nodes signing is enabled and no other nodes is accepted which aren't signed with correct signing :)
And if you use Whitelisting only between GateWay and repeater node, you are set.Note: I could be wrong ;)
-
@Reza
From what I understand the GateWay will add all nodes even if you do not want them to. But not to the controller if you have "inclusion option" on the GateWay.
There is a possibility that if you use the "inclusion option" maybe it will pick up all sensors not already added (ie your neighbour) if they are sending while inclusion is looking for new sensors.
If you want to stop this you will have to use whitelisting on MAC adress. But this requires you to reprogram GateWay everytime you want to add new sensor (or maybe it is possibility to have same MAC for all?).
And of course you will have to program a MAC adress for all sensors/per sensor the first time as well.
I thought this problem would be solved with only using Signing, but because of backwards compability the creators did not enable this in the GateWay.
If you only would want signing, you could make all nodes connect via a repeater node.
Because between repeater nodes and regular nodes signing is enabled and no other nodes is accepted which aren't signed with correct signing :)
And if you use Whitelisting only between GateWay and repeater node, you are set.Note: I could be wrong ;)
@Nicklas-Starkel repeater nodes will just forward signed messages. It will only verify messages addressed directly to it like all nodes. Signing is end to end.
-
@Nicklas-Starkel repeater nodes will just forward signed messages. It will only verify messages addressed directly to it like all nodes. Signing is end to end.
@Anticimex yes. But since his neighbours nodes aren't signed (or with wrong signation), the repeater will not forward them to his gateway.
Or am I totally wrong? -
@Anticimex yes. But since his neighbours nodes aren't signed (or with wrong signation), the repeater will not forward them to his gateway.
Or am I totally wrong?@Nicklas-Starkel repeater forwards what is sent to it. But if your gw is set to require signatures and your node has presented itself as a node that require signatures, gw will not accept unsigned messages from that node. If the message passes through a repeater or not does not matter.
-
@Nicklas-Starkel repeater forwards what is sent to it. But if your gw is set to require signatures and your node has presented itself as a node that require signatures, gw will not accept unsigned messages from that node. If the message passes through a repeater or not does not matter.
can i use a specific range "node_id" for my gateway? for example my gateway just add device that range of node id is between 5000 until 5500 ? and out of range dont detect and add ?!
-
The Gateways doesn't care at all by nodeId's. It only acts as a Gatteway, and retransmits the signal received on air, to the controller on the computer.
There is no pairing mode, or inclusion mode, implemented in the gateway.
The INCLUSION_FEATURE will send a command to the controller and instruct it to turn on inclusion mode (if implemented correct)
That is, all inclusion mode specifics are made on the controller side (Vera, Domoticz, OpenHab etc). All the gateway are doing is sending the data from nodes, to the controller, and from the controller, to the nodes.
The Gateway can not reserve a number of node ID's (and specially not id 5000, because mysensors only supports up to 255 nodes on the network, all with 255 child sensors attached). As the reservation is done on the controller level.
-
The Gateways doesn't care at all by nodeId's. It only acts as a Gatteway, and retransmits the signal received on air, to the controller on the computer.
There is no pairing mode, or inclusion mode, implemented in the gateway.
The INCLUSION_FEATURE will send a command to the controller and instruct it to turn on inclusion mode (if implemented correct)
That is, all inclusion mode specifics are made on the controller side (Vera, Domoticz, OpenHab etc). All the gateway are doing is sending the data from nodes, to the controller, and from the controller, to the nodes.
The Gateway can not reserve a number of node ID's (and specially not id 5000, because mysensors only supports up to 255 nodes on the network, all with 255 child sensors attached). As the reservation is done on the controller level.
-
The Gateways doesn't care at all by nodeId's. It only acts as a Gatteway, and retransmits the signal received on air, to the controller on the computer.
There is no pairing mode, or inclusion mode, implemented in the gateway.
The INCLUSION_FEATURE will send a command to the controller and instruct it to turn on inclusion mode (if implemented correct)
That is, all inclusion mode specifics are made on the controller side (Vera, Domoticz, OpenHab etc). All the gateway are doing is sending the data from nodes, to the controller, and from the controller, to the nodes.
The Gateway can not reserve a number of node ID's (and specially not id 5000, because mysensors only supports up to 255 nodes on the network, all with 255 child sensors attached). As the reservation is done on the controller level.
-
If your neighbor knows your network frequency / network address, he can potentially add your nodes to his network. That is why signing is there for sensitive nodes, like locks etc.
@tbowmo said:
If your neighbor knows your network frequency / network address, he can potentially add your nodes to his network. That is why signing is there for sensitive nodes, like locks etc.
1.so with signing this problem can resolved? i use a signing for my WSN and i told to my neighbor that use a signing for his WSN . Will solve it?
2.also suppose a thief come near my home door , and he has a domoticz with a mysensors gateway ! so if i use a mysensors relay (signing) for electric door lock , he can add my relay to his controller and open my home door ?please first told me about 1 , and about 2
-
@tbowmo said:
If your neighbor knows your network frequency / network address, he can potentially add your nodes to his network. That is why signing is there for sensitive nodes, like locks etc.
1.so with signing this problem can resolved? i use a signing for my WSN and i told to my neighbor that use a signing for his WSN . Will solve it?
2.also suppose a thief come near my home door , and he has a domoticz with a mysensors gateway ! so if i use a mysensors relay (signing) for electric door lock , he can add my relay to his controller and open my home door ?please first told me about 1 , and about 2
@Reza Read the documentation please. https://www.mysensors.org/about/signing
