domoticz auto add device (mysensors) even if disable "Accept new Hardware Devices"
-
@Reza please read replies carefully. You need to make sure you enable the feature. That is the first define. Most if not all defines have a default value. Just search the code.
Press the button (assuming it is connected properly) and the gateway will accept new nodes for the duration specified by the third define. I am no specialist on how this works so someone else can probably give better details on how node-gw-controller handle additions of new nodes. But my Vera won't add devices unless I put my GW in inclusion mode and boot up nodes so they send their presentation data to the gw. But if it is the gw or the controller that decides if the device should be added or not based onthe gw inclusion mode I don't know, but it would seem to me pretty obvious that it would be the gw that decides that.
In other words, inclusion mode is used to add new devices. And as far as I know it is the only way (once you enable that feature). I don't know if that is the solution to your problem as I don't fully understand what your problem really is, but it will not prevent any others from listening in on your sensors.
Enabling encryption will obfuscate the data you transmit from eavesdroppers, but any reasonably intelligent attacker will anyway be able to guess what data you transmit.@Anticimex said:
please read replies carefully. You need to make sure you enable the feature. That is the first define. Most if not all defines have a default value. Just search the code.
Press the button (assuming it is connected properly) and the gateway will accept new nodes for the duration specified by the third define. I am no specialist on how this works so someone else can probably give better details on how node-gw-controller handle additions of new nodes. But my Vera won't add devices unless I put my GW in inclusion mode and boot up nodes so they send their presentation data to the gw. But if it is the gw or the controller that decides if the device should be added or not based onthe gw inclusion mode I don't know, but it would seem to me pretty obvious that it would be the gw that decides that.
In other words, inclusion mode is used to add new devices. And as far as I know it is the only way (once you enable that feature). I don't know if that is the solution to your problem as I don't fully understand what your problem really is, but it will not prevent any others from listening in on your sensors.
Enabling encryption will obfuscate the data you transmit from eavesdroppers, but any reasonably intelligent attacker will anyway be able to guess what data you transmit.thank you my friend . i test serial gateway with vera . exactly. in vera there is inclusion button and dont add auto device... but in domoticz is not...
so thank you for help. if you found any solution please help me. -
@Anticimex said:
please read replies carefully. You need to make sure you enable the feature. That is the first define. Most if not all defines have a default value. Just search the code.
Press the button (assuming it is connected properly) and the gateway will accept new nodes for the duration specified by the third define. I am no specialist on how this works so someone else can probably give better details on how node-gw-controller handle additions of new nodes. But my Vera won't add devices unless I put my GW in inclusion mode and boot up nodes so they send their presentation data to the gw. But if it is the gw or the controller that decides if the device should be added or not based onthe gw inclusion mode I don't know, but it would seem to me pretty obvious that it would be the gw that decides that.
In other words, inclusion mode is used to add new devices. And as far as I know it is the only way (once you enable that feature). I don't know if that is the solution to your problem as I don't fully understand what your problem really is, but it will not prevent any others from listening in on your sensors.
Enabling encryption will obfuscate the data you transmit from eavesdroppers, but any reasonably intelligent attacker will anyway be able to guess what data you transmit.thank you my friend . i test serial gateway with vera . exactly. in vera there is inclusion button and dont add auto device... but in domoticz is not...
so thank you for help. if you found any solution please help me. -
@Reza This is the MySensors forum, not the Domoticz forum. If you have issues with Domoticz, I suggest you post your questions there. MySensors provide a set of features. It is up to the controllers to make use of them.
-
@Anticimex
in domoticz forum told me this issue is related to mysensors gateway and here told me this issue is related to domoticz :) -
@Reza Well, you said it yourself. It works with Vera. So it is obviously not a MySensors issue.
-
@Anticimex
but in vera , there is a device(gateway) with inclusion button but in domoticz my gateway dont have a inclusion button , so this is related to domoticz? -
@Anticimex said:
Well, of course it is! MySensors cannot control what Domoticz UI shows.
right :( so i must change my controller ? i want a open surce controller and a good controller :(
-
@Anticimex said:
Or you get the Domoticz people to fix their shit.
but they told me this problem is related to mysensors gateway ! :|
one more question. can i use static id between my device and gateway? and i disable feature inclusion mode ? so my gateway dont auto add other devices... -
@Anticimex said:
Or you get the Domoticz people to fix their shit.
but they told me this problem is related to mysensors gateway ! :|
one more question. can i use static id between my device and gateway? and i disable feature inclusion mode ? so my gateway dont auto add other devices... -
@Reza So convenient for them. But we at MySensors cannot change how domoticz works so I if they don't want to fix it, well, that is just too bad.
@Anticimex
yes , also i explain to them that this problem is related to domoticz because mysensors gateway is working well with vera controller and there is a inclusion button in vera dashboard , but in domoticz... -
Another solution, could be to change the default rf channel, and have the two houses on different frequencies.
-
@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..
