Replies: 1 comment 1 reply
-
Hi,
Not for the moment, as these wildcards are hard coded. They enable to setup multigateways installation with several Theengs Gateway and/or OpenMQTTGateway. For example: {"stat_t":"+/+/BTtoMQTT/112233445566","dev_cla":"temperature","unit_of_meas":"°C","name":"IBT-4X(S/C)-tempc","uniq_id":"112233445566-tempc","val_tpl":"{{ value_json.tempc | is_defined }}","state_class":"measurement","device":{"identifiers":["112233445566"],"connections":[["mac","10082C40ABE6"]],"manufacturer":"Inkbird","model":"IBT-4X(S/C)","name":"iBBQ-40ABE6","via_device":"OMG"}} For example this sensor entity definition can be fed by either instance of OpenMQTTGateway or Theengs Gateway, even if each republish a discovery topic. If we replace the wildcard by |
Beta Was this translation helpful? Give feedback.
-
Hi,
Is there a way to disable using wildcards in the status topic properties?
I am trying to get TheengsGateway to connect to Domoticz via the homeassistant autodiscovery feature and I think the problem I have is down to the use of wildcards.
I think it looks like domoticz is subscribing to the wildcard topic (and is receiving the messages fine via MQTT) but the messages come back with the full topic name rather than the wildcarded version and the Domoticz code is using a match on the topic string to link the internal sensor properties with the incoming message.
The alternative is adding a new bit of code to do wildcard matching in Domoticz but if it is easy in some way to disable it in TheengsGateway then that might be an easier route!
Fantastic app by the way!
Thanks
Stephen
Beta Was this translation helpful? Give feedback.
All reactions