MQTT connection to HomeAssistant not working

[admin]

yeah, thanks
i will add it and also make the Config tool configurable to use also this binding

[code_talker]

(01-25-2017, 11:17 AM)admin Wrote: thanks, when i was reading the docs, i found only the MQTT method but not hte HTTP
i will add it.
currently there is no support for arbitrary headers just the content type, i will add also an option to specify generic headers
here is how currently the custom HTTP config has to look like for more details
{"method":"POST","url":"http://things.ubidots.com/api/v1.6/devices/dsds?token=sadssads","ct":"application/json","pay":"{\"sdsd\":%TEMP%}"}

Hi,

I have been running my vair monitor with homeassistant without problems for the last months. Works great :-)

But now, that I've started integrating other hardware into home assistant, I come to the point where I do not want to to operate it without password access. Unfortunately, enabling password requries the password to be send in the HTTP header when sending sensor data from vair to home assistant.

Do you have any news if configuring custom http header is possible now? I could not see any information about it in the change log.

[admin]

aaaa yeah.. i had forgotten about this feature, sorry. I will add it in the next few days

[admin]

(05-22-2017, 08:49 AM)code_talker Wrote: Do you have any news if configuring custom http header is possible now? I could not see any information about it in the change log.

i just added it, please give it a try as i am not at home, and do not have a device with me to test it.
update to the latest version and add two attributes to the json config
"hn1":"header_name", "hv1":"header_value"

only one header is supported

[code_talker]

(05-23-2017, 02:59 AM)admin Wrote:

(05-22-2017, 08:49 AM)code_talker Wrote: Do you have any news if configuring custom http header is possible now? I could not see any information about it in the change log.

i just added it, please give it a try as i am not at home, and do not have a device with me to test it.
update to the latest version and add two attributes to the json config
"hn1":"header_name", "hv1":"header_value"

only one header is supported

Works like a charm! Perfect. Thanks again for the great support.