2023.7: Responding services

[masman (MichaelAAMI)]

Hi @BertrumUK I had been using the HACS version for quite a long time. I tried deleting my existing Fully integration and installing again but an error was thrown. This evening I will try again after turning on additional logging. I wonder if there was some cleanup that didn’t happen when the HACS version was uninstalled.

[zigomatic]

Hello, What are your cpu usage after updating to 2023.7 ?

Mine increase from -+ 9% to 35%. Nothing special in logs.
HA core python3 process is taking 100% cpu.
I shutdown / restart but still facing the same after some minutes. It’s like having a loop somewhere but
take time to find the root cause of this.

[haip]

How do you update that image entity? I tried an image template with my doorbell snapshot image. But it is not updated automatically after a new snapshot image is created.

[Mariusthvdb (Marius)]

Your best bet would be a trigger template in that case?

otoh, I cant even figure out how to get the correct url there:

      - unique_id: last_snapshot_oprit_camera
        name: Last snapshot oprit camera
        url: 'http://<my_server>.local:<port>/media/local/snapshots/camera_oprit.jpg'
        verify_ssl: false

wont show anything

[lugolven (Lucas GOLVEN)]

I’m seeing the same issue on iOS too. The app is freezing after 3-4 seconds after I made the update.

[Holdestmade]

This url is working for me for images in www folder:

url: http://xxxxxxxxxxxx.local:port/local/platerecogniser/platerecognizer_drive_last_motion_latest.png

[Mariusthvdb (Marius)]

just got my self auto banned…

thing is I create those images using:

      - service: camera.snapshot
        data:
          filename: >
            /media/snapshots/camera_oprit.jpg
        target:
          entity_id: camera.oprit
      - service: notify.mobile_app_marijn
        data:
          message: '📸 Snapshot: Iemand bij de Oprit! 🔔'
          data:
            image: /media/local/snapshots/camera_oprit.jpg

so I have 2 folder with those images. neither of them works in that new template image yet…

[petro]

@Mariusthvdb

/media/local/snapshots

That doesn’t seem right.

[Mariusthvdb (Marius)]

yes I know that seems odd. However, it is the correct path to have the IOS app serve that image to a notification, I just went outside to check it once again.

The image is written in /media/snapshots/camera_oprit.jpg

and the notification just sent it fine using that /media/local/snapshots/camera_oprit.jpg path containing the additional /local/

the other images are created using a date template, full disclosure:

script:

  create_snapshot_poort:
    alias: Create snapshot Oprit
    mode: restart
    sequence:
      - service: camera.snapshot
        data:
          filename: >
            /media/snapshots/oprit_{{now().strftime('%Y_%m_%d_%H_%M')}}.jpg
        target:
          entity_id: camera.oprit
      - service: camera.snapshot
        data:
          filename: >
            /media/snapshots/camera_oprit.jpg
        target:
          entity_id: camera.oprit
      - service: notify.mobile_app_marijn
        data:
          message: '📸 Snapshot: Iemand bij de Oprit! 🔔'
          data:
            image: /media/local/snapshots/camera_oprit.jpg

what’s more, that image does not show in the Dashboard, using the type: picture-entity and gets the Computer banned because of: with invalid authentication

otoh services:

      - service: camera.play_stream
        target:
          entity_id: camera.oprit
        data:
          media_player: media_player.googlehome_hub
          format: hls

and even:

      - service: browser_mod.more_info
        data:
          entity: camera.oprit

work without issue, so its the authorization of that actual image in the media folder causing the problem, even though set ssl to false

[bdraco (J. Nick Koston)]

Shelly has their own development cycle which isn’t tied to HA. If they add support for grouping advertisement data, we will be happy to update HA to consume that change.

[sophof]

Seems it’ll be fixed in 2023.7.1

Fix state of slimproto players

[tom_l]

Yeah I saw that. Just waiting for '7.1 now.

[Cadster]

I have got the same issue, my miscale does not work with esphome since my upgrade to 2023.7 docker.
My mi temp/hum sensors still work as are my miflora sensors. Until it’s fixed i go back to OpenMQTT Gateway wich simply works.

update:
miscale issue is solved by esphome 2023.6.5

[jimmyz51501 (JZIoT)]

@disforw … Thanks for the hard work you guys did for the QNAP … Awesome finally via UI

[Ildar_Gabdullin]

Upgrading 2023.6.4 → 2023.7.0 went rather smooth.
So far only one issue was observed - “Demo” platform causes errors & creates plenty of entities:

"Demo" integration: errors & undesired entities after 2023.7

[adorobis]

Check out this issue:

Xiaomi LYWSDCGQ and CGDK2 no longer report Temerature and Humidty.

Seems that for now you can’t have both bluetooth_proxy and esp32_ble_tracker on the same device. At least removing the proxy setting from my device solved it for the Miscale.

[Cadster]

Thanks, will check if it also solves my issue. I didn’t read anyting in the breaking changes though.

[adorobis]

It is rather a bug, not a breaking change

[Bergtatt (Anders Kvernberg)]

Great update!

Still unable to mount my SMB v.1.0 network share. Anyone else made it work?

[pergola.fabio]

Smb 1 ??? I think it’s time you update your storage :+)