Not with logging turned up? Come on, the community depends on people debugging.
For anyone else who runs into this problem, it was because I only had the camera stream defined, and not the still image URL. You need both now apparently.
Fully agree, and since its āHome Assistantās Year of the voiceā, adding ālabelsā to the favourites would then also enable speech control. Letās talk
Finally got around to running the upgrade today - absolute disaster but in a really weird wayā¦
HA upgraded from 2023.5.4 to 2023.6.2 fine but then all hell broke loose on my network. My Draytek 2762 (central hub for my network and gateway to my ONT fibre connection) started boot looping so my LAN is going up and down like a yo-yo making access even to HA difficult as heck. I started unplugging things one by one and eventually noticed this only occurred when I plugged in my RPI4 which runs HASSOS and HAā¦ What the heck?
Through sheer persistence I managed to stay connected to HA long enough to issue and restore core to 2023.5.4 and instantly the problem is goneā¦ So itās definitely HA causing this - but I assume somehow through a network traffic change that the Draytek doesnāt likeā¦
Not sure how to proceed because itās obviously difficult to analyse anything with the LAN dropping every few seconds!
The moment HA rebooted to restore the backup the Draytek stabilised.
Edit: Saw the github bug reports seems itās everyone with Draytek kitā¦
I donāt run Draytek gear, but Iām always curious about problems like this. Next time it could be my router.
Any chance of posting a link to the Github bug reports?
UPnP seems one reason, but not solely
Sorry for the delay replying. I checked out that thread and the one thing I noticed was that everyone else having the issue has a Draytek router. I also have one. So this thread completely fixed the issue for me!
Incidentally, it seems thereās something in the HA codebase which seems to interfere quite badly with UPnP on Draytek routers. Turning off UPnP on the router seems to resolve the issue (and probably should be off anyway since itās a bit of a security concern) but it may be worth looking into what is causing it to be flooded in the first place, as I suspect there may be other headaches itās causing that arenāt revealing themselves quite as noticeably as I saw
Not sure if this is the proper way to ask a question but here we go!
I have multiple drives in my server and I cannot figure out the syntax for the remote share. How do I specify the drive my share is in?
Thank you!
What type of server is it? Windows (you would use Samba/Windows/CIFS), linux based or hardware NAS (usually NFS but can also be Samba)? If itās windows and you didnāt specifically create any network shares or share anything out, to access a drive it would be the drive letter followed by a dollar sign (C$ for example). So if youād want to access a specific folder on C: it would be C$/folder/to/data. But in order to access that the user would need to have administrator rights. Youāre better off sharing out the folder you want to access. If you donāt know how to do this, it can be done via a right click, but a quick google will help you as well.
I tried to update an entry helper type: schedule but the GUI seems not showing any possibility to modify anymore.
Someone in 2023.6.2 can check if have the same issue ?
[edit] seems also applicable to numbers, switches, input select
My add Helper button stopped working at some point, canāt be 100% certain it is with the June Release since I havenāt used it fie a while.
Re-load your browser
Not related to that. In private mode, itās the same.
Can you share a screenshot of your Synology NFS share config for this one?
Itās not in the 3 dot menu, itās in the cog. You can edit helpers anywhere in the UI.
Interested to know if anyone else is having issues with this release and using FullyKiosk Browser on an older tablet (i.e., an Amazon Fire HD)?
For some reason, it wonāt move past āinitializingā and wonāt prompt for the oauth login credentials. This only started when I upgraded to 2023.6 - anyone else?
EDIT: this is actually on any of the browsers that use the built-in WebView I think (so, WallPanel, the official HASS app), but not on something like Edge when thatās installed. Hence me wondering what changed in this release?
When I updated to 2023.6.x, port 8123 would not open so nothing would connect. After tearing my hair for weeks an reverting to 2023.5.0, which worked, I did āapk updateā at the CLI (read some random comment and thought it wouldnāt hurt), and, voila, the update happened and port 8123 opened.
Pity about the hair though.
Iām keen to know as well as I canāt get it to work.
Host logs for 2 attempts at mounting NAS share
Jun 21 02:51:45 homeassistant systemd[1]: Mounting Supervisor nfs mount: NAS_Music...
Jun 21 02:51:45 homeassistant systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
Jun 21 02:51:45 homeassistant systemd[1]: Started NFS status monitor for NFSv2/3 locking..
Jun 21 02:51:45 homeassistant mount[1397254]: Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service ā /usr/lib/systemd/system/rpc-statd.service.
Jun 21 02:51:45 homeassistant systemd[1]: Reloading.
Jun 21 02:51:45 homeassistant systemd-timesyncd[499]: Network configuration changed, trying to establish connection.
Jun 21 02:51:45 homeassistant systemd-timesyncd[499]: Contacted time server 162.159.200.1:123 (time.cloudflare.com).
Jun 21 02:51:45 homeassistant kernel: audit: type=1334 audit(1687315905.643:1134): prog-id=331 op=LOAD
Jun 21 02:51:45 homeassistant kernel: audit: type=1334 audit(1687315905.643:1135): prog-id=58 op=UNLOAD
Jun 21 02:51:45 homeassistant kernel: audit: type=1334 audit(1687315905.644:1136): prog-id=332 op=LOAD
Jun 21 02:51:45 homeassistant kernel: audit: type=1334 audit(1687315905.644:1137): prog-id=54 op=UNLOAD
Jun 21 02:51:45 homeassistant kernel: audit: type=1334 audit(1687315905.647:1138): prog-id=333 op=LOAD
Jun 21 02:51:45 homeassistant kernel: audit: type=1334 audit(1687315905.647:1139): prog-id=144 op=UNLOAD
Jun 21 02:51:45 homeassistant kernel: audit: type=1334 audit(1687315905.648:1140): prog-id=334 op=LOAD
Jun 21 02:51:45 homeassistant kernel: audit: type=1334 audit(1687315905.648:1141): prog-id=42 op=UNLOAD
Jun 21 02:51:45 homeassistant kernel: audit: type=1334 audit(1687315905.650:1142): prog-id=335 op=LOAD
Jun 21 02:51:45 homeassistant kernel: audit: type=1334 audit(1687315905.650:1143): prog-id=8 op=UNLOAD
Jun 21 02:51:56 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-0c1540a26e70afb958f98e5bfa068cd62c01d15fa3eeaa8d3c1bc0d76ceb5506-runc.WaAoKK.mount: Deactivated successfully.
Jun 21 02:52:02 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-0c1540a26e70afb958f98e5bfa068cd62c01d15fa3eeaa8d3c1bc0d76ceb5506-runc.dEMBAI.mount: Deactivated successfully.
Jun 21 02:52:07 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-0c1540a26e70afb958f98e5bfa068cd62c01d15fa3eeaa8d3c1bc0d76ceb5506-runc.s820sd.mount: Deactivated successfully.
Jun 21 02:52:15 homeassistant systemd[1]: Requested transaction contradicts existing jobs: Transaction for mnt-data-supervisor-mounts-NAS_Music.mount/stop is destructive (mnt-data-supervisor-mounts-NAS_Music.mount has 'start' job queued, but 'stop' is included in transaction).
Jun 21 02:52:27 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a2decc7a162524cb397791f6b44a8fcef144d7151f61e14374392e5ed9fc5ca7-runc.KDrhS1.mount: Deactivated successfully.
Jun 21 02:52:32 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-0c1540a26e70afb958f98e5bfa068cd62c01d15fa3eeaa8d3c1bc0d76ceb5506-runc.JxPmcx.mount: Deactivated successfully.
Jun 21 02:52:37 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-0c1540a26e70afb958f98e5bfa068cd62c01d15fa3eeaa8d3c1bc0d76ceb5506-runc.tLnmcq.mount: Deactivated successfully.
Jun 21 02:52:41 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-79a677a5f100eedcd7855c8fe5e227dcd151b1f130eabdf5d68445b58c52798a-runc.0cUCie.mount: Deactivated successfully.
Jun 21 02:52:53 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-0c1540a26e70afb958f98e5bfa068cd62c01d15fa3eeaa8d3c1bc0d76ceb5506-runc.6qZ8rU.mount: Deactivated successfully.
Jun 21 02:52:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-22f9e8a89c284087ba116055a19e5e5aad7782984bae2a42d12188120942eac5-runc.4eYOgl.mount: Deactivated successfully.
Jun 21 02:53:15 homeassistant systemd[1]: mnt-data-supervisor-mounts-NAS_Music.mount: Mounting timed out. Terminating.
Jun 21 02:53:15 homeassistant systemd[1]: mnt-data-supervisor-mounts-NAS_Music.mount: Mount process exited, code=killed, status=15/TERM
Jun 21 02:53:15 homeassistant systemd[1]: mnt-data-supervisor-mounts-NAS_Music.mount: Failed with result 'timeout'.
Jun 21 02:53:15 homeassistant systemd[1]: Failed to mount Supervisor nfs mount: NAS_Music.
Jun 21 02:53:23 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-0c1540a26e70afb958f98e5bfa068cd62c01d15fa3eeaa8d3c1bc0d76ceb5506-runc.5VA4kU.mount: Deactivated successfully.
Jun 21 02:53:27 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a2decc7a162524cb397791f6b44a8fcef144d7151f61e14374392e5ed9fc5ca7-runc.mMH7fj.mount: Deactivated successfully.
Jun 21 02:53:34 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-0c1540a26e70afb958f98e5bfa068cd62c01d15fa3eeaa8d3c1bc0d76ceb5506-runc.3fSJrK.mount: Deactivated successfully.
Jun 21 02:53:41 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-79a677a5f100eedcd7855c8fe5e227dcd151b1f130eabdf5d68445b58c52798a-runc.6gh7Q4.mount: Deactivated successfully.
Jun 21 02:53:54 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-0c1540a26e70afb958f98e5bfa068cd62c01d15fa3eeaa8d3c1bc0d76ceb5506-runc.v7tsMm.mount: Deactivated successfully.
Jun 21 02:53:59 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-0c1540a26e70afb958f98e5bfa068cd62c01d15fa3eeaa8d3c1bc0d76ceb5506-runc.GfECPN.mount: Deactivated successfully.
Jun 21 02:54:04 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-0c1540a26e70afb958f98e5bfa068cd62c01d15fa3eeaa8d3c1bc0d76ceb5506-runc.4loaXd.mount: Deactivated successfully.
Here you go.
Control Panel Shared Folder
Edit NFS Permissions Create
Screenshot for NFS settings:
Iām using 10.0.0.0/8 because Iāve got quite a few hosts on my network and Iām using the 10.*.*.* subnet.
As a quick rule of thumb,
- if your network is on 192.168.*.*, use 192.168.0.0/16
- if your network is on 192.168.X.*, use 192.168.X.0/24, where X is your own subnet.
Hereās the corresponding entry in HA: