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

Blog
404

Just for my pride and reputation.

I do not tinker with the discovery. I am running zigbee2mqtt as recommented for Home Assistant.

But the input field for the home assistant URL (which home assistant uses to link to the z2m site) does not check the format in the UI. So I had put the IP address without http:// in front. That naturally must go wrong if everything expects a full URL.

But Home assistant should not crash the entire MQTT integration because a field does not match the exact expected format. It is normal coding practice to always check all user data (messages from MQTT must be considered user data) and handle errors properly. The code should ignore the data in the url field and issued a warning in the log and not crash the entire integration so mqtt.publish service calls that are unrelated fails.

A crash like this may even be a security issue. It is often untested user data that attackers abuse for arbitrary code execution exploits

1 Like
405

I’m sorry, I don’t follow your logic here. If you input the wrong url, the integration will not work. That’s the same for all integrations. It’s not “crashing”. And there will be an error in your log.

If you’re not referring to that field, the you should clarify because you may have found a bug. Which btw doesn’t require a “software should or shouldn’t do” dissertation on why you’re upset with functionality. It’s simply a bug that should be reported.

406

You are trolling. A moderator that trolls.

I posted my experience here not for developers (that is what bug reports are for) but for the users that reported problems with mqtt stability in recent versions.
Maybe they can make things work by checking this exact thing - zigbee2mqtt is popular. Or similar fields.

And now that I am home alone I could make my house without zigbee2mqtt to get the logs for a real bug report for the developers. I posted this earlier today.

2 Likes
407

SSL access via my DuckDNS hostname also failed after 6.1 update (6.0 is fine). I am using some port redirect on my firewall to allow outside access and I also use the external name (duckdns.org) on the LAN. This worked fine in 2023.6.0 but not in 6.1. I restored from 6.1 to 6.0 and it works again. Access to https://my.lan.ip:8123 still worked.

I’m not using the DuckDNS addon, only LetsEncrypt (I update my external IP to DuckDNS from my Firewall).

Btw HA is run on RPI 4.

408

I am not trolling I’m replying to posts that I consider trolling. It’s the same every month. You don’t raise issues when you find them and complain about it like it’s being done on purpose to make your life miserable. I’m trying to get you to just create the issues without the unnecessary complaining. That’s it

12 Likes
409

I realized that “template” platform supports both ways:

изображение
изображение475×634 12.4 KB

And the new “command_line” platform supports only the “bottom way”.
Do not find it consistent.
This issue was closed by developer, said smth like “it was discussed & agreed” (addressed to this topic).

410

That’s because it is no ‘issue’ (as in ‘bug’)

The fact you (me too) may find it inconsistent doesn’t imply a bug ……

411

Nobody said this is a bug.
There is difference between “wrong” & “inconsistent”.
As I already said, the issue was created since there is no Discussions in “core” section. Now I think that I should create a Discussion in a “architecture” section. Finally, I was addressed to a dedicated discussion.

2 Likes
412

Same issue here

413

Seems that this also broke automations where MQTT is used as a trigger, or at least that is what I can gather from the very vague error message

The mqtt platform for the switch integration does not support platform setup

I’ve already switched over to the new format for all my MQTT devices, but the old format is still used inside of automations. Is this no longer supported either?

this how I have it setup at the moment

automation:
  - id: ai_trigger_person_in_backyard
    alias: AI trigger person in backyard
    trigger:
    - platform: mqtt
      topic: "BlueIris/backyard/Status"
1 Like
414

Mine is working without a password. Here is my share from Samba:

[backups]
   comment = Backups folder
   path = /media/steve/7f9b413a-a874-7e48-9d1d-e9cb6beb0654/backups
   create mask=0777
   directory mask=0777
   read only = no
   browsable = yes
   guest ok = yes
   force group = steve
   force user = steve
415

Found same difference. I changed my template to the way of xommabd_line. Maybe in New releases this will become the way how to do.

416

I like the related info. If I use it on a helper and it is used in an automation, it isn’t shown. That is something to look at I believe.

417

Nope, you missed an mqtt entity in your switch section.

1 Like
418

A really quick way is to look at the device info page. The device id is the last part of the URL

deviceidpic
deviceidpic1010×559 57.5 KB

1 Like
419

What issues? I’m on 2023.5 without ZHA problems and am about to upgrade to 2023.6.1.

420

You know what, you are completely right not sure how I missed it but indeed I did. I was so ready to say no I didn’t :smiley: but of course before doing something stupid like that went through all of it again to make sure I was right, and I wasn’t.

I think I got stuck on the new fancy UI and somehow expected all the MQTT devices to show up there but of course they wouldn’t if they are only used in templates :man_facepalming:

421

Interesting. I don’t have force group/user in my Samba share and it’s a media server so it’s read only. HA complained about authorization when I tried guest without a password and I assumed it required a password because all my other mounts to my share are via passwordless guest. I’ll need to play around with this.

422

Looks like the previously mentioned bug with sound output is found and solved, we hope on a quick release now… :wink:

423

Hi
How add this date, time and date and time ? It is new feature ?

This was available before version 2023.6.0