2023.6: Network storage, favorite light colors, new integrations dashboard

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

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&param=switchlight&idx=27&switchcmd=On"'
      command_off: '/usr/bin/curl "http://192.168.1.6:8080/json.htm?type=command&param=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&param=switchlight&idx=27&switchcmd=On"'
      command_off: '/usr/bin/curl "http://192.168.1.6:8080/json.htm?type=command&param=switchlight&idx=27&switchcmd=Off"'
  - switch:
      name: light_12
      command_on: 'curl "http://192.168.1.6:8080/json.htm?type=command&param=switchlight&idx=13&switchcmd=On"'
      command_off: 'curl "http://192.168.1.6:8080/json.htm?type=command&param=switchlight&idx=13&switchcmd=Off"'
2 Likes

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

solution found.

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/

Mounted my NAS…to home assistant

Is ist possible to record the Frigate files to the NAS?

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.

  1. There are no instructions on how to do this upgrade.
  2. The link to the current Nest Integration Documentation displays a ‘Configuration.Yaml’ at the end of the process.Google Nest - Home Assistant
    image

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

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?

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 :slight_smile:

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.

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

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?

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…

I can use some assist with this, please :wink:

EDIT:

Looks very similar to this:

So I’m not the only one…

1 Like

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