Olivier ARCHER

Hello, I'm using Ubuntu 12.04.1 LTS with kernel 3.2.0-32-generic x86_64, and afuse 0.2-3. I've set up my lxc container with https://help.ubuntu.com/community/LXC, but this is probably not relevant, as the error...

I've try with 0.4.1 and user_allow_other in /etc/fuse.conf, and I've got the same unexpected behaviour.

Here is my /proc/mounts: note that my mountpoint is now /mntfuse instead of /home in my previous post: # cat /proc/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs...

Many thanks, you are not "so slow" ;-) do you mean that changing 0700 to 0755 should fix the permissions issue ? I've just try it, by with no success...

I've also noticed that not using default_permissions let me enter the fuse mountpoint, but i cant create new file. And what about: if (!(mount_point_directory = mkdtemp(temp_dir_name))) ? mkdtemp create directory...

> oceanographers/meteorologists and probably many other fields often use compass direction as angle (i.e., 0 degrees is North, 90 degrees is East) At least, it would be a good thing...

If the URL is behind a proxy (specifically the Nginx Proxy Manager HA add-on), the query takes longer and the watchdog is often triggered. I've encountered this issue for `ota_http`...

see https://github.com/microsoft/vscode-java-debug/issues/1244#issuecomment-1902423133. The workaround might be to declare your array as `double array[][]` (not `double[][] array`).

It would be nice to make the function `std::unique_ptr make_ota_backend()` become a public method of `OTAESPHomeComponent`, so other platforms can get the backend easily. in https://github.com/esphome/esphome/pull/5586, I had to copy/paste...

I've tried to turn `ota_http` in a platform component, and it worked ! My yaml was: ```yaml ota: - platform: esphome password: "xxxxxxxxxxxxxxxx" num_attempts: 3 safe_mode: no - platform: ota_http...