Thank you, @Burningstone, however… it doesn’t appear to work
It first fusses about the /local folder. Tried white-listing it, that didn’t work (not a path, apparently). Then tried /config/www/, but that didn’t work either. The image will write, but it doesn’t get attached in the notification.
@pergola.fabio, how are you uploading your images to a URL?
Updates for the WiFi sensor seem to be really good for my wife’s Samsung Galaxy S8, but when I change the WiFi on my OnePlus 6, it can take upwards of 10 minutes before this change is reflected in the sensor.
I had previously rolled my own WiFi sensor using LlamaLab’s Automate and a webhook (which I’d like to dump), but that one updates nearly instantly for both of us. Should I create a bug for this?
Yeah, I would say each respective sensor would update either on a schedule or when it has new data, while respecting a rate limit to keep battery usage low.
Personally, I am not concerned with any of the attributes on the WiFi sensor. I just want to know when I’ve joined or left a network. I’m using this as one of the home/away binary_sensors rather than have to have an arp or ping sensor.
Is it Normal that the notifications don’t wake up your phone. Is this being fixed as. I using the Notifications when I arrive to the shops an sometimes I don’t open my phone.
This is (most likely) a doze issue, and disabling battery optimisation for the app does resolve it for the Pixel phones that I and my wife use.
Unless I’m mistaken, you’ll need to look at the app’s permissions for background processing and battery usage within the Samsung menus and options (I’m not familiar with them) - this may include ‘sleeping apps’.
You can validate this by checking whether notifications are received promptly.
With the phone awake (i.e. screen on) and the app completely closed.
With the app running in the foreground (i.e. open on screen).
With the phone asleep and app closed.
If 2 only, then it’s (probably) a background processing limitation on the phone to adjust.
If 1 only, then battery optimisation for the HA app still needs looking at.
If 3, then it should be working correctly.
You can also test with the ttl and priority elements discussed here
This doesn’t seem right to me. Why aren’t they prefixed with the device name? sensor.battery_level_N is just too generic a name. This isn’t a complaint just about the Android app, naming of entities in HA has always annoyed me.
This is probably just an oversight in the app integration. It doesn’t sound like an intentional thing, but maybe it is. Regardless it’s not that hard to rename entities.