Eckart
(Severing)
June 8, 2023, 4:56pm
221
After the update to version 2023.6 I have a problem: No restart possible. I have an entry webostv with 1 connected device - it works after the update but when I want to do a HA restart then I get the error message
“error restarting home assistant
‘webostv’”
When I want to check the configuration via the developer tools, it just goes round and round forever.
Should I deactivate webostv and shut down HA or do I risk that nothing works anymore?
Regards, Eckart
pumo
June 8, 2023, 4:58pm
222
Thanks! I am pretty sure that I tested that format. so now its working in configuration.yaml
(I wont even test in switch.yaml anymore)
command_line:
- switch:
name: light_11
command_on: '/usr/bin/curl "http://192.168.1.6:8080/json.htm?type=command¶m=switchlight&idx=27&switchcmd=On"'
command_off: '/usr/bin/curl "http://192.168.1.6:8080/json.htm?type=command¶m=switchlight&idx=27&switchcmd=Off"'
multiple lights it must put this way
command_line:
- switch:
name: light_11
command_on: '/usr/bin/curl "http://192.168.1.6:8080/json.htm?type=command¶m=switchlight&idx=27&switchcmd=On"'
command_off: '/usr/bin/curl "http://192.168.1.6:8080/json.htm?type=command¶m=switchlight&idx=27&switchcmd=Off"'
- switch:
name: light_12
command_on: 'curl "http://192.168.1.6:8080/json.htm?type=command¶m=switchlight&idx=13&switchcmd=On"'
command_off: 'curl "http://192.168.1.6:8080/json.htm?type=command¶m=switchlight&idx=13&switchcmd=Off"'
2 Likes
Zoriontsu
(Zoriontsu)
June 8, 2023, 5:01pm
223
Same question here. I would like to be able to point my DeepStack save_file_folder: to a Share.
I have tried several iterations without luck.
Imho this is a kind of inconsistency.
First wanted to report about it on Github, but this is not a bug; and there is no a Discussion section for a Core.
Im still On 2023.4.6 due to ZHA issues
I’ve gotten the same error, but trying to connect to NAS storage exposed from my router running FreshTomato. I have tried both with and without authentication enabled, with no luck either way.
I’ve also gotten a different error (“Mounting backup did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-backup.mount for details.” ), but regardless I’ve so far been unable to connect to the shares, though I can connect fine from my Windows machines and Mac on the same network.
Synology NAS too, I set my shared folder NFS to allow all local traffic R/W access without authentication.
Works for me.
Path: /volume1/My Share Folder Name/
fisch55
(Fisch55)
June 8, 2023, 6:07pm
229
Mounted my NAS…to home assistant
Is ist possible to record the Frigate files to the NAS?
crzynik
(Nicolas Mowen)
June 8, 2023, 6:08pm
230
yes, you need to create a media volume named frigate
Regarding deprecation of Google Nest - I am totally confused. The deprecation reads: The Google Nest YAML configuration has been fully removed. You should ensure you have imported your configuration and credentials into the UI before upgrading.
There are no instructions on how to do this upgrade.
The link to the current Nest Integration Documentation displays a ‘Configuration.Yaml’ at the end of the process.Google Nest - Home Assistant
So… Who needs to upgrade? Apparently even if we’ve upgraded we still have a reference to Configuration.Yaml on our integrations page? How do we tell if we need to upgrade, and how do we do it?
4 Likes
fisch55
(Fisch55)
June 8, 2023, 6:23pm
232
mmmmm something went wrong…
Just did the update, but somehow my MQTT is not working correct. I’ve seen the braking change about last_reset_value_template, but in my configuration I don’t use that.
Am I the only one or do more people have problems with MQTT after updating?
wmaker
(Tommy Long)
June 8, 2023, 7:02pm
234
Samsung TV Remote -
From the release notes: " The Samsung TV now has a remote entity, allowing you to send remote key presses directly to your TV!"
Thought I would give it a try. The samsung doc has an example:
service: remote.send_command
target:
device_id: 72953f9b4c9863e28ddd52c87dcebe05
data:
command:
- KEY_MENU
So my first problem was trying to determine what the device id should be in my case.
I found it in .storage/core.device_registry
......
"id": "9da6e65f04777cf3468579811960d198",
"identifiers": [
[
"samsungtv",
"08f0d180-0077-1000-877d-4844f777bb7c"
]
],
"manufacturer": "Samsung",
......
the device_id is: 9da6e65f04777cf3468579811960d198
.
With that, the service call worked!!
If there is a better way to find out what the device_id is, I would be happy to know
pjn77
June 8, 2023, 7:03pm
235
I’m lost with network storage.
I want to mount the external drive i already have exposed as a SAMBA share through the official addon (which works fine). I want to use this extra space to store frigate recoardings.
Ive been able mout it as a media folder but…now what? Does this mean it becomes ‘the’ media storage? Or additional storage that can be used for media? No folders or files have been created in the share, and HA is working as normal.
ludeeus
(Ludeeus)
June 8, 2023, 7:05pm
236
It create a new folder under /media with the same name as you gave the mount.
For frigate, you have to name it “frigate”.
1 Like
pjn77
June 8, 2023, 7:07pm
237
Yeah ive just seen you can browse the share under ‘local storage’.
If I name it frigate does that mean it can be only used for frigate? Is the idea to have one share dedicated to frigate in addition to ones for other media?
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