Hi guys,
I’m fairly new to this and need help with getting IFTTT talking to hass to output MQTT.
I’m using IFTTT to trigger a webhook which goes into home assistant.
The way I’ve configured the webhook is as follows:
URL:
https://MYHASSCLOUDURL/api/services/mqtt/publish
BODY:
headers = { ‘Authorization’: “Bearer MY LONGLIVEDACCESSTOKEN”, } BODY: {“payload”: “1”, “topic”: “immersiveroom/turnon”, “retain”: “True”}
When I trigger the IFTTT I get
“Login attempt or request with invalid authentication from 127.0.0.1”
I have tried so many different ways around this but can’t seem to find one. Any help is hugely appreciated. Thanks.
Why are you not using the ifttt integration ? Is much easier then, you can call the service then with an automation
See here for an example I use with ifttt to call a service…
# hass-google_keep
Custom component for [Home Assistant](https://home-assistant.io/) to enable adding to and updating lists on [Google Keep](https://keep.google.com/).
## Installation
Add the `google_keep` folder and its contents to the `custom_components` folder in your Home Assistant configuration directory, and add the `google_keep` component to your `configuration.yaml` file.
### Example configuration.yaml entry
```yaml
google_keep:
username: "[email protected] "
password: "this_is_my_Google_App_password"
list_name: "Grocery"
```
`list_name` is an optional configuration key that sets a default name for the Keep list to update.
### Dependencies
This component relies on [gkeepapi](https://github.com/kiwiz/gkeepapi), an unofficial client for the Google Keep API.
## Usage
The original intended use of this component was to restore the capability of Google Assistant to add things to Google Keep lists.
This file has been truncated. show original
Thanks for your reply - I did spot that integration and have a fiddle with it but I got confused;
After going through hass, the payload needs to go to Node Red somehow. The full workflow looks like this:
Google Assistant command triggers IFTTT -> IFTTT sends payload webhook to Hass -> Hass publishes payload to MQTT-> Node Red sees this & sends payload using OSC via UDP to my software which turns on projectors.
If you can see an easier way I’d be over the moon - this workflow does seem very stretched. I think this is because its going from Internet -> local signal.