ludeeus
(Ludeeus)
June 8, 2023, 7:09pm
238
I do not use frigate, but as I understand it, it has a strict path requirement of /media/frigate.
You can however add multiple mounts with different names to the same share.
2 Likes
Ok, everything seemed fine. But it is very quiet in house.
That is a major problem with this update!
VLC-TELNET quit on me. No TTS announcements. No sound from the server anymore…
investigating now, somehow i feel, this will be a tough one…
Created own topic for this…
So after yesterdays update VLC-TELNET addon does not breathe anymore.
After almost three years flawless service, we have no more TTS announcements.
The addons says this:
s6-rc: info: service vlc: starting
s6-rc: info: service nginx: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service vlc successfully started
s6-rc: info: service nginx successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: …
I can use some assist with this, please
EDIT:
Looks very similar to this:
opened 10:26AM - 07 Jun 23 UTC
closed 10:17AM - 13 Jun 23 UTC
duplicate
About one month ago my speakers does not work anymore. So I ordered new ones. Th… e new one also does not work. They were both active speakers on the output jack of the Home Assistant Yellow.
I am on home assistant OS 10.2
In the official VLC addon log when I try to play it get this error message:
```
vlcpulse audio output error: stream connection failure: No such entity
main audio output error: module not functional
main decoder error: failed to create audio output
```
I did a full backup and reset everything then I started again with the backup. On first start it works after a reboot it stopped working.
Also tried a USB soundcard which also appear on the drop-down menu in VLC, but when I select it also got the same error. So I do not think that is a hardware fault.
The logs from the audio plugin
```
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/alsa-mixer.sh
[11:50:34] INFO: Adjust ALSA mixer settings for /dev/snd/controlC0
[11:50:35] INFO: Adjust ALSA mixer settings for /dev/snd/controlC1
cont-init: info: /etc/cont-init.d/alsa-mixer.sh exited 0
cont-init: info: running /etc/cont-init.d/filesystem.sh
cont-init: info: /etc/cont-init.d/filesystem.sh exited 0
cont-init: info: running /etc/cont-init.d/pulse-config.sh
[11:50:35] INFO: Found RaspberryPi system
cont-init: info: /etc/cont-init.d/pulse-config.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun alsa (no readiness notification)
services-up: info: copying legacy longrun pulseaudio (no readiness notification)
s6-rc: info: service legacy-services successfully started
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
W: [pulseaudio] main.c: Home directory of user 'root' is not '/var/run/pulse', ignoring.
W: [pulseaudio] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support.
W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
W: [pulseaudio] module-udev-detect.c: Failed to open /proc/asound/card1: No such file or directory
W: [pulseaudio] module-udev-detect.c: Failed to open /proc/asound/card0: No such file or directory
E: [pulseaudio] module-rescue-streams.c: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
```
opened 05:34PM - 16 Mar 23 UTC
closed 10:15AM - 13 Jun 23 UTC
```
[16:59:00] INFO: Service restart after closing
s6-rc: info: service legacy… -services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/alsa-mixer.sh
[00:59:06] INFO: Adjust ALSA mixer settings for /dev/snd/controlC0
cont-init: info: /etc/cont-init.d/alsa-mixer.sh exited 0
cont-init: info: running /etc/cont-init.d/filesystem.sh
cont-init: info: /etc/cont-init.d/filesystem.sh exited 0
cont-init: info: running /etc/cont-init.d/pulse-config.sh
cont-init: info: /etc/cont-init.d/pulse-config.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun alsa (no readiness notification)
services-up: info: copying legacy longrun pulseaudio (no readiness notification)
s6-rc: info: service legacy-services successfully started
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
W: [pulseaudio] main.c: Home directory of user 'root' is not '/var/run/pulse', ignoring.
W: [pulseaudio] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support.
W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
W: [pulseaudio] module-udev-detect.c: Failed to open /proc/asound/card0: No such file or directory
E: [pulseaudio] module-rescue-streams.c: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
E: [pulseaudio] main.c: Failed to acquire org.pulseaudio.Server: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.35" is not allowed to own the service "org.pulseaudio.Server" due to security policies in the configuration file
E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
```
opened 03:46AM - 20 Apr 23 UTC
closed 10:01AM - 20 Apr 23 UTC
add-on: vlc
### Describe the issue you are experiencing
Prior to the upgrade, I used the VL… C add-on to play media out of the Home Assistant Blue's audio jack. I also used the vlc_telnet integration to play media out of the Home Assistant Blue's audio jack from automations. This worked 100% of the time until the OS 10.0 upgrade. Now, the VLC sidebar shows the plugin playing local files just as it did before but no audio is actually generated from the hardware output device.
### What type of installation are you running?
Home Assistant OS
### Which operating system are you running on?
Home Assistant Operating System
### Which add-on are you reporting an issue with?
VLC
### What is the version of the add-on?
0.1.3
### Steps to reproduce the issue
1. Install VLC add-on and Telnet_VLC (core-vlc) integration
2. Connect audio output of Home Assistant Blue to known working speaker equipment
3. Play a media file to media_player.vlc_telnet
4. Listen and you will hear no audio on the output from Hoem Assistant Blue's hardware audio jack
### System Health information
## System Information
version | core-2023.4.5
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.10.10
os_name | Linux
os_version | 6.1.24
arch | aarch64
timezone | America/Los_Angeles
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 5000
Installed Version | 1.32.1
Stage | running
Available Repositories | 1278
Downloaded Repositories | 5
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | true
-- | --
subscription_expiration | September 11, 2023 at 17:00
relayer_connected | true
relayer_region | us-east-1
remote_enabled | true
remote_connected | true
alexa_enabled | true
google_enabled | false
remote_server | us-east-1-9.ui.nabu.casa
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 10.0
-- | --
update_channel | stable
supervisor_version | supervisor-2023.04.0
agent_version | 1.5.1
docker_version | 23.0.3
disk_total | 113.9 GB
disk_used | 10.8 GB
healthy | true
supported | true
board | odroid-n2
supervisor_api | ok
version_api | ok
installed_addons | File editor (5.5.0), Samba share (10.0.0), VLC (0.1.3), chrony (2.5.0), Z-Wave JS (0.1.77), Terminal & SSH (9.6.1), Signal Messenger (0.66.0)
</details>
<details><summary>Dashboards</summary>
dashboards | 3
-- | --
resources | 0
views | 2
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | April 10, 2023 at 00:12
-- | --
current_recorder_run | April 19, 2023 at 01:19
estimated_db_size | 169.52 MiB
database_engine | sqlite
database_version | 3.38.5
</details>
### Anything in the Supervisor logs that might be useful for us?
```txt
Logger: homeassistant.components.vlc_telnet
Source: components/vlc_telnet/media_player.py:60
Integration: VLC media player via Telnet (documentation, issues)
First occurred: 01:24:50 (1 occurrences)
Last logged: 01:24:50
Command error: Parameter volume not in range(0, 500)
```
### Anything in the add-on logs that might be useful for us?
_No response_
### Additional information
_No response_
Home Assistant 2023.6.0
Supervisor 2023.06.1
Operating System 10.2
Frontend 20230607.0 - latest
It took a while for me to finally figure out why I had no microphone a few weeks ago. Found input volume was set too low. Managaged to figure out issues in the CLI volume setting. All was working great. Never had any issues with speakers until now. Then yesterday I do the new update and I lost both microphone and speakers. They still show up in the audio info. I can choose my mic and speaker (both…
So I’m not the only one…
1 Like
gerd1
(Gerd Rütten)
June 8, 2023, 7:22pm
240
Dear all
snipping from release notes 2023.6
The following integrations are now available via the Home Assistant UI:
This doesn’t work.
If i integrate it via UI a message told me, it must be done via configuration.yaml
Best regards
Gerd
frenck
(Franck Nijhof)
June 8, 2023, 7:32pm
241
Seems like you are running it as a custom integration:
And not using the one Home Assistant provides.
…/Frenck
1 Like
dlasher
(dlasher)
June 8, 2023, 7:40pm
242
I had the same issue, and a reboot solved it. (May as well update the agent before you reboot)
Has anyone that was having the issues with ZHA / Aqara Devices / HUSBZB-1 tried out 2023.6 yet?
I have been sitting back on 2023.4.6 because any version in 2023.5.X has made my Aqara devices completely unreliable. They just stop responding, but don’t even report that they’re unavailable. Re-pairing makes it work for a couple hours but then they stop again.
Everything is completely rock solid in 2023.4.6.
I’m very interested in the new NFS stuff but I spent so much time during 2023.5’s run updating and rolling back and re-pairing devices that I just want to wait until I see more discussion and confirmation of this issue. It doesn’t seem like it has much attention.
1 Like
GSzabados
(Gábor Szabados)
June 8, 2023, 8:05pm
244
As the Network storage option has been added, is there any way to create a Backup to a USB connected external drive? Not to the Data drive, not to move the Data drive, but to directly to an external USB connected drive. (HDD/SSD/Pendrive)
3 Likes
pin7of9
(Chrisandsally)
June 8, 2023, 9:08pm
245
A full restart fixed for me
crzynik
(Nicolas Mowen)
June 8, 2023, 9:16pm
246
Just set the service up in the UI and the device id is filled in automatically. Otherwise you should be using the service with the entity instead
1 Like
Yeah, it is a breaking change as noted by Frenck in the issue I linked although he seems to infer it may affect custom components only, when the reality is bluetooth_tracker is core.
I also note that in this link bdraco knew about it and commented on it on March 24th as waiting for pybluez to be updated to work with Python 3.11.x.
So, as this is a deliberate breaking change, why does it appear to have been hidden when it should have been highlighted, especially when, as reported, it causes long restart times if bluetooth_tracker is configured?
On a positive note, when bluetooth was, again, deliberately broken just under a year ago ( I am not certain but I suspect it was because of Python), it suddenly started to work about 5 months later without any acknowledgement in the release notes (unless I missed it). I hope this will be solved again with a pybluez update but this time with some form of notification!
This is a show stopper for me, as it was last year, so no update for my production system until we have a working bluetooth_tracker core integration!
4 Likes
Does this update support matter thermostats (like the nest thermostat 2020)? I saw in a reddit thread that it’d be ready in time for this release, but I don’t see anything about it in the release notes.
SamJWard
(Sam Ward)
June 8, 2023, 10:45pm
249
MQTT is dead after this update.
After the update it states “Restart(s) required” under Repairs.
Once you click Submit, MQTT is dead.
I had to restore from backup to fix it. It bricked my entire install.
The issue would be multiple notifications, we really need a way to get them to automatically +1 on the entity so when multiple notifications go off, they can all be easily referenced. Difficult to do that cleanly with everything having custom Ids
Here’s how I do the persistent notifications via once the event that’s holding them up has ended. alias: "Notification: Persistent Notification Alerts"description: Alerts me if - Pastebin.com
1 Like
Anyway, registered an issue for a weird yaml structure for command_line:
opened 11:07PM - 08 Jun 23 UTC
integration: command_line
### The problem
Not exactly a bug - but I would call it "inconsistency".
[Ac… cording to the Docs](https://www.home-assistant.io/integrations/command_line/), the new yaml structure is:
![image](https://github.com/home-assistant/core/assets/71872483/9213654c-9a3e-4cce-ad4d-489515e65aec)
Compare with a “template” platform:
![image](https://github.com/home-assistant/core/assets/71872483/8302f284-677e-4f08-be2c-db5e2597f6af)
Any special reason for this difference?
When I started to rewrite my command_line sensors, I first did this - believed this is LOGICAL:
![image](https://github.com/home-assistant/core/assets/71872483/d8330fac-ac90-4ca4-b1e9-2e8241ebd101)
But I was wrong:
```Invalid config for [command_line]: expected a dictionary for dictionary value @ data['command_line'][0]['sensor'].```
There are many posts in Community from users who tried the same structure as me - seems that this structure is EXPECTED.
That is why I wonder why another structure was chosen?
### What version of Home Assistant Core has the issue?
2023.6.0
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant Container
### Integration causing the issue
command_line
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/command_line/
### Diagnostics information
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
3 Likes
Thank you for the update.
It would be nice if new layouts like devices & entites were optional.
I find the new layout to be quite unfortunate on mobile android devices (i.e. in companion app).
Came here to say that mounting a network share was relatively easy, thanks to this new feature in the 2023.6.0 release. I’ve been rather impatiently waiting a LONG TIME for this! THANK YOU!!!
One comment: Can the front-end/GUI developers please consider adding cache control to the GUI web pages? My Settings / System / Storage page wasn’t showing any of the new features until I manually forced a page refresh with CTRL-R.
2 Likes
Hopefully someone who works on the HA companion app / UI team is in this thread:
The new favorite colors in the pop-up are super weird on the Home Assistant Android app…
You have to hold it down for like a good 10 seconds to activate drag and drop and then the delete button won’t even work for me. In fact I can’t even move around the colours with drag and drop. Weird https://photos.app.goo.gl/9hg1qehquAUfvT118
1 Like
Likewise, although I deleted the integration and started again.
I didnt spend a lot of time troubleshooting why, but it is back running. Quite sluggish to button presses though.
Somewhere in your config.yaml you use probably “platform: command_line” which you need to take out because it’s not supported anymore. Comment it out with # and see what happens after a restart. Maybe nothing maybe you need to resolve something.