MQTT Wildcards (what's the point)?

[sk]

I have home assistant publishing all the house sensors for non-loxone devices via an MQTT broker to the loxone miniserver.  I have setup a wild card for the home assistant sensors but I think the subscription only outputs the values and not the keys/paths of the topic. 

For example:

I have a topic called HA/sensor/<a bunch of various sensors>/state

I entered a wildcard in the Loxone subscription so that I can extract the full path (in theory).  HA/sensor/#  then I wanted to use the command recognition block. However, the subscription only pumps out the values and not the path so I can't then split the output of the subscription to many command recognition blocks to get a finer grain control of the sensors.   I am also aware that the miniserver can only handle 16 subscriptions. 

Does anyone know of a workaround to get data from home assistant into the miniserver?

thanks!

[duncan]

mine doesnt work like this

each sensor or group of sensors i want to send to loxone via mqtt has an entry in the configuration.yaml

eg 

mqtt_statestream:
  base_topic: homeassistant
  publish_attributes: true
  publish_timestamps: true
  include:
   entity_globs:
   - cover.duncan_s_autodoor*
   - sensor.duncan_s_auto_door_fault*
   - cover.*
   entities:
   - binary_sensor.octopus_intelligent_slot

an entilty_glob sends all sub-components of the entity as separate mqtt entries

an entitiy sends the value of a specific entity as a single mqtt entry 

for each of these you wish to send to loxone, you create a matching virtual input in loxone (thats assuming you are using a loxberry / mqtt)

so in the above example of cover.duncan_s_autodoor* i get 22 separate entries in mqtt and i create a virtual input in loxone for each one i wish to see updated in loxone 

homeassistant_cover_duncan_s_autodoor_door_state is an example of one of the mqtt entries and i have a virtual input in loxone with the same name which is updated by the loxberry mqtt gateway

[Jonathan Dixon]

Think OP was asking about the (new) Loxone native mqtt support, not using loxberey

We previously discussed the uselessness of the wildcard subscription (and the client in general) back when it was announced in December:

https://groups.google.com/g/loxone-english/c/Waba_swIVkw/m/9dYkvv7QAQAJ?utm_medium=email&utm_source=footer&pli=1

Tldr, yes.

--
You received this message because you are subscribed to the Google Groups "Loxone English" group.
To unsubscribe from this group and stop receiving emails from it, send an email to loxone-englis...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/loxone-english/99d10e05-4123-4c24-840d-01cd78672504n%40googlegroups.com.

[duncan]

oops sorry i misunderstood the original question...