Entity sanity check
-
Just before I break everything, can someone confirm for me that this should add another binary device with the same proerties?
- id: mqqt enabled: true implementation: MQTTController name: Mosquito config: source: "mqtt://192.168.70.249:8883/" username: xxxxx password: *********** entities: catman_iphone: name: "Catman Phone" topic: catmaniphone user: catman uses_template: owntracks_in_region regionName: Home2 rachel_iphone: name: "Rachel Phone" topic: racheliphone uses_template: owntracks_in_region regionName: Home user: rachelWith the caveats that her username is "rachel", DeviceID is "racheliphone" and her region is set to "Home"
TIA!
C
-
This is the way.
-
C CatmanV2 has marked this topic as solved on
-
Fab so I have an entity. I had to make some changes to the Owntracks config so there was no stored message. Time will tell. Thanks for all the help
C
-
None at all. As far as I know, this was the id line with the distribution. There's no editing of that required (although with my editing skills, who knows)
I think the
id:Value can be anything you like, it just shows up in the Controller drop down in the Entities area.
Could be wrong though
C
-
That's correct. You set the ID. It just needs to be unique in its context*, and alphanumeric only (no punctuation/special characters or Unicode).
* By "in its context", I mean that if you are supplying an ID for a controller, it must be unique among controllers; if for an entity, it must be unique among entities (for the controller the manages it — it's fine for two controllers to have an entity with the same ID, that's why Reactor uses canonical IDs (the
controllerID>entityIDform) in most places to disambiguate that similarity.@CatmanV2 I note that the ID in your snippet above is "misspelled" (if it's possible to misspell an ID)...
mqqtinstead ofmqtt. This makes no difference, but you did send me to the package files to make sure I hadn't made that typo in the source material (I didn't). If you change it, it will break any rules or reactions you have created for its entities, FYI. -
That's correct. You set the ID. It just needs to be unique in its context*, and alphanumeric only (no punctuation/special characters or Unicode).
* By "in its context", I mean that if you are supplying an ID for a controller, it must be unique among controllers; if for an entity, it must be unique among entities (for the controller the manages it — it's fine for two controllers to have an entity with the same ID, that's why Reactor uses canonical IDs (the
controllerID>entityIDform) in most places to disambiguate that similarity.@CatmanV2 I note that the ID in your snippet above is "misspelled" (if it's possible to misspell an ID)...
mqqtinstead ofmqtt. This makes no difference, but you did send me to the package files to make sure I hadn't made that typo in the source material (I didn't). If you change it, it will break any rules or reactions you have created for its entities, FYI.@toggledbits thanks for the heads up! Out of curiousity, I assume it's
mqttpackage files? Lord alone knows what I was doing
Thanks as ever!
C
-
@toggledbits thanks for the heads up! Out of curiousity, I assume it's
mqttpackage files? Lord alone knows what I was doing
Thanks as ever!
C
@catmanv2 said in Entity sanity check:
Out of curiousity, I assume it's mqtt package files?
Yes. There's a sample config in the package, and I had to check it. All
extraswill be getting sample configs like that, and the documentation will in future likely also be moved or duplicated into the package as well. -
T toggledbits locked this topic on






