Lee Thompson

@ZeliardM Ok ran the new_klap_test and it worked fine with the HS300 (as well as my other devices). ``` DEBUG Discovered 6 devices discover.py:531 Found 6 devices (python-kasa) MINGW64 /c/source/_contrib/python-kasa...

> PR [[#1606](https://github.com/python-kasa/python-kasa/pull/1606)] has been created to add the fixture file for the Firmware 1.1.2 for HS300 (US) Hardware 2.0. I have not seen firmware 1.1.3 come across my devices...

As far as I can tell, sending notifications from HA to Apprise doesn't actually work as of Core 2025.7.3 (20250702.3). The original poster, those configuration urls are for Apprise, not...

HA using Apprise to send notifications is completely broken.

Your syntax doesn't seem to match HA, did you mean something else? Most of the information you're giving is for **Apprise**, not HA. My Apprise instance works **outside** of _Home...

> Try changing your `url` defnition to `http://notify.local/get/apprise` (note the `/get`) That causes the integration to fail to load. Trying again with the `config:` url removed. UPDATE: Yeah this configuration...

@caronc I'm back to this in my HA configuration.yaml: ``` notify: - platform: apprise name: apprise url: http://notify.local/notify/apprise config: http://notify.local/get/apprise ``` Changing `url` to `http://notify.local/get/apprise` causes the HA Apprise integration...

This is still broken. I cannot get HomeAssistant to send a notification using Apprise no matter what.

I've already done all that. I can use curl on a bash terminal in the Home Assistant container and have it work successfully. From within Home Assistant it does not...

> Error 405 sounds like your Apprise configuration has the environment variable `APPRISE_CONFIG_LOCK` set, see [here](https://github.com/caronc/apprise-api?tab=readme-ov-file#environment-variables). `APPRISE_CONFIG_LOCK` is not set. Env for the container are as follows; `PATH` `LANG` `GPG_KEY`...