Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Homeassistant Notifications fail with 400 error

See original GitHub issue

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn’t find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

With the most recent update of Home Assistant Kuma notifications fail with error 400 bad request. Was working and I updated HA to the latest version and now using TEST in the notications dialog cause 400 error bad request.

👟 Reproduction steps

Triggered the bug using the TEST button when setting up the Notification for Home Assistant.

👀 Expected behavior

Expected Home assistant to send notification to my mobile device.

😓 Actual Behavior

causes 400 error bad request Uptime Kuma log shows details but there are no entries in the Home Assistant log of even receiving the request attempt This was working before I updated Home Assistant to the latest version.

🐻 Uptime-Kuma Version

1.18.4

💻 Operating System and Arch

Docker Container running on Unbuntu Server

🌐 Browser

106.0.5249.103

🐋 Docker Version

20.10.14

🟩 NodeJS Version

No response

📝 Relevant log output

Error: Error: AxiosError: Request failed with status code 400 400: Bad Request
uptime-kuma    |     at HomeAssistant.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15)
uptime-kuma    |     at HomeAssistant.send (/app/server/notification-providers/home-assistant.js:33:18)
uptime-kuma    |     at processTicksAndRejections (node:internal/process/task_queues:96:5)
uptime-kuma    |     at async Socket.<anonymous> (/app/server/server.js:1150:27)

Issue Analytics

State:
Created a year ago
Comments:10 (6 by maintainers)

Top GitHub Comments

2reactions

nickm324commented, Oct 13, 2022

What the hell! That was it. I’m not sure how I didn’t find that before posting, I must have tried this 1000 times before opening this issue.

Thanks for you help.

1reaction

louislamcommented, Oct 13, 2022

I should asked you to provide the actual reproduction steps too.

Thanks @rmtsrc’s help.

Close as resolved.

Top Results From Across the Web

Response status code was unacceptable: 400

the app consistently fails with: Error - Response status code was unacceptable: 400 *

Nest Integration Failure (Error 400: Invalid Request) - Reddit

Going through the setup I hit error 400 when trying to authenticate with the Nest integration. Turns out there's been a known problem....

400 errors when using Frigate Proxy and Home Assistant OS ...

I'm using the recommended Blueprint for HA notifications and the notification part works; I get alerts for different events. But, no image shows ......

Home Assistant - Request failed Error code 400 - Stack Overflow

I found my error. I used the wrong api link. here is the correct way to call it. function ttsGoogleHome(text) { var ttsUrl ......

Home Assistant: Add Camera Snapshots to Push Notifications

If the HTTP request succeeds, the image is saved to local storage and sent out as a push notification. If the request fails,...