Felenasoft

Hello,

I have just today purchased a Xeoma licence and I'm very impressed so far!

I am having one small issue though trying to get motion events to trigger an http request to homeassistant api - I have the module setup as per instructions but no request is being made.

The only thing I can think is that the one of my request params requires an exclamation mark - I have tried %21 to URL encode as I thought this may be an issue if curl is used behind the scenes but to no avail.

I have the server component installed on Ubuntu 16 server if that helps diagnose the issue.

Thanks

Carl

Had some more time to test things.

Its not the exclamation mark I tried without this - I am sending the request over http to localhost:8123 now rather than via the Apache proxy on port 443 and Home assistant is getting the request as I an see a lot of Authentication errors now.

The API password in the Xeoma URL is definitely correct, I'm sending as POST not get as this is what home assistant requires.

Without a detailed log from Xeoma I'm not sure if it is a header issue or what.

Does anyone have a successful http post setup to the Home assistant API?

Thanks

Carl

Ran across this link earlier today, may help you:

https://github.com/dewgenenny/trigger-sensor

Hello! There is a known issue with POST that includes additional symbols in the command - this may cause authentication errors. Could you please check the exact command Xeoma sends to your Home Assistant (e.g. using Wireshark)? Is it consistent with the one you input?

I have switched to using node-red to translate the command to an mqtt message instead.

It actually gives more control anyway as I can rate limit Mqtt messages.

I'd recommend this approach as the post request headers are obviously not great from Xeoma.

Thanks

Admin_P Wrote:Hello! There is a known issue with POST that includes additional symbols in the command - this may cause authentication errors. Could you please check the exact command Xeoma sends to your Home Assistant (e.g. using Wireshark)? Is it consistent with the one you input?

This is the only issue I'm having with Xeoma. It's not that big of a deal, but a solution would be great. Any plans of fixing this in an update or something?

Of course, this is part of our Development Plan. All the new features and bug fixes are posted here for every new version and sent to our subscribers.