The question is really if the limitation is in the state of the sensor or in the general handling of MQTT messages and events.
If the size limitation is only in the sensor, then you could bypass the sensor altogether by using the automation and sending the data in an event to appdaemon.
I have heard of people sending images via MQTT from HA, so I would be surprised if there is a significant limit on the size of data there, but the event bus I don’t know too much about.
Now I get your point, and yes you right about using an event. I will test that now and get back to you. Kind regards
Its me again. I have created the automation that triggers when a mqtt message is retrieved on my said topic, and my custom event is triggered. But no idea how to place the payload_json generated on the mqtt bus in my event; for I do understand that custom events don’t support templating yet.
So pls how do I transfer the data?
Thanks
I think that rather scuppers the whole idea. One of the reasons I hated all that yaml stuff in the first place.
Your stuck with your five different sensors I’m afraid.
I implemented event_data_template to help with this so the data just gets handed directly to the event. I am unsure what limitation you are running into with sensors holding the data, is it just too many fields?
I have a pull request in. Hopefully get this merged at some point since I think it would be really useful to avoid the kludging of setting sensor states.
@Odianosen25 @gpbenton so I just tested this config in my automations and it worked for me. This reads the topic off mqtt and passes the entire payload to appdaemon
- alias: intentNotParsed
trigger:
platform: mqtt
topic: hermes/nlu/intentNotParsed
action:
event: APP_INTENT_NOT_PARSED
event_data_template:
payload: '{{ trigger.payload }}'
AppDaemon get this
LOG INFO myapp: myapp_nluIntentNotParsed: {‘payload’: “{‘intent’: ‘this_intent’}”}
@ReneTode @aimc figure you guys might like this as well since it will greatly simplify getting external data into an app. Now just need to get Paulus to accept it 
Thanks for this, and I am also trying to use it to process snips data in AppDaemon .
So is there something I need to do to activate the templating or is it a custom component or something? I went to your link, but I really don’t know how to pull stuffs in except via custom component.
Hope this will also work for the json payload too?
Kind regards
@Odianosen25 you would need to do a git checkout and merge which is a bit of a bear and would get overwritten next upgrade if it doesn’t get merged. An easy cheat if you want to test is to do a git clone and copy these 4 files
homeassistant/helpers/template.py
homeassistant/helpers/script.py
homeassistant/helpers/service.py
homeassistant/helpers/config_validation.py
Into wherever your home assistant libs are, mine is /srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers with the standard virtualenv install. Docker or hassio you are on your own!
Not sure what you mean about json payload since that is one. Here is an example of literally just sending the entire intent to appdaemon
automations.yaml
- alias: snips_intent
trigger:
platform: mqtt
topic: hermes/intent/#
action:
event: JARVIS_INTENT_NOT_PARSED
event_data_template:
payload: '{{ trigger.payload }}'
INFO jarvis: jarvis_intent_not_parsed: {'payload': '{"sessionId":"6bbd31e1-8168-4ee0-bdcc-20073c313b10","customData":null,"siteId":"default","input":"turn christmas lights on","intent":{"intentName":"user_rZEKlr8M7M3__lightsTurnOnSet","probability":0.7173734},"slots":[{"rawValue":"christmas","value":{"kind":"Custom","value":"christmas"},"range":{"start":5,"end":14},"entity":"house_room","slotName":"house_room"}]}'}
With this, the intent was parsed properly in HASS (my christmas lights came on) and the full json intent was also passed to app daemon as you can see in the log.
for me there is no advantage, because i dont use mqtt, but the question is what the real advantage is.
the mqtt gives raw data that you translate to sensors.
those sensors can be used to make actions inside AD.
if i want the raw data into AD i wouldnt go through HA, but write an app that can read out mqtt data.
so i see only 2 real use cases:
but i gladly hear what your usecase for it is.
Ok many thanks for that and will do as said. I am new to git so no clue what “git checkout” means though know git clone.
Will just copy the files into the directory. But I believe that will still wipe it out after the next updates anyway.
Hopefully it will be merged in during the next update as it will really make things easier.
Kind regards
But why go through the extra step of putting data into sensors to get it into AD? Parsing the data in yaml and mapping values is a pain and much easier to do in AD IMO. Plus then you have extra sensors cluttering things up.
And yeah, I could write an app to listen to mqtt events as well and had one running but why have another daemon when HA is already there? And there is also the benefit as you say of having the data split.
A use case for that is that I will do will be having HASS/AD/Snips be able to initiate conversations off of events, and to do so I need the full data that comes across MQTT. And again, yeah I could have a separate listener.
Yep that was my initial thought, until I figured out there was no way to listen for mqtt messages which @gpbenton did confirm was true. That was the only way I could get around the issue so it wasn’t intentional as per say. if you know otherwise, pls advise as I had tried this
self.listen_event(self.mqttEvent, "mqtt", topic= "hermes/nlu/intentParsed")
But nothing worked even though the event trigger was triggering in yaml on the same topic.
The next option was to use custom event which I couldn’t until you came up with this template of event data. My use case is actually to communicate with snips over chatbot on telegram and create like a little “chatbot” for the home (as I refused to expose my system to the internet due to some limitations and other stuffs). For this I needed full access to the data on mqtt.
Regards
I also tried implementing a listener in appdaemon and it would start and connect but I couldn’t get the loop to run. But that felt like a kludge anyway since I have a perfectly good listener in hass.
Well at least you got the skill to develop the event_data_template. I am no programmer so was stuck 
. Will test your software and get back to you if any issues.
Thanks again for the help
This is also my thinking. I hope you progress your event_data_template through to a full HA release.
maybe my failing understanding from MQTT.
i just see it as entity communication. so for me the raw data is just something that needs to be translated to entities.
i see not much value from pulling raw data through my HA only to give it to something else.
then again, i dont also think of sensors cluthering things up, but as something to give me a view on things.
in AD i create sensors like last motion, last value changed, etc to view things in 1 view, without going through logs or history.
i guess we look at things differently 
Oh sensor are perfect for something I want to keep a state of but a lot of what I will do is just pass one time info to AD in which case having a sensor isn’t a good fit since it is a static thing.
But everyone has their own ideas on how to implement things so having more options is always better.
Well I finally solved my issue by coping a cue from how the Alexa and Google API is handled. I created a python script that subscribes to the topic of interest, and made it a service so it starts at boot up. This then sends the data to AD using “requests.post”. In AD I just registered an endpoint and I get all the raw data without getting HA involved.
I think this helps me with extra flexibility, without using sensors and making it independent of HA is actually a plus as I don’t need to cluster it just because I need to pass data.
Kind regards everyone for all the help and suggestions.
Hi,
@Odianosen25 can you give me more details or is there event the code of your python script available? Working on the same thing and this would save a lot of time
Thank you