Are you calling out the exact hardware/serial/usb port or are you using one of the autodetecting alias’s?
Hmm I tried a bunch of different ports and could not get it to work again, had to roll back to 2023.1 something is definitely messed with this release and the conbee2
The assist feature is hinting at something super cool coming. I’ll need to brush up on what’s currently implemented (or not) right now.
I have an LED light in zone “garage entry”, intuitively named “garage entry LED”. Entering “turn on the garage entry light” returns and error, entering “turn on the garage entry LED” turns the light on. The entity is a switch so hopefully there will be (or is) a way to correlate this with “light”, “LED”, “switch” etc. in commands.
I can see a microphone in every room in my future…
@petro: I don’t know. I’m just a beginner with Home Assistant.
@JeffreyHA: I tried also an other solution, because zigbee isn’t working that well with usb3.0. I took an older usb extention cable and connected the conbee 2 with that cable to one of the front usb ports. This also solves the problem.
Thanks, Ya I tried USB 2 ports and 3.0 ports. Spent 2hrs trying to diagnose it and ran out of time so I restored a backup. I imagine my Unraid - passthrough setup also complicates it, but it all works perfectly fine on 2023.1
It’s best to call out the actual usb serial id. You can find that in your home assistant hardware page. It’ll be the one that’s super long. Something like /dev/serial/by-id/usb-1a86_TubesZB_971207DO-if00-port0
1 Like
The OpenAI Assist chat integration replies are about 5 to 8 degrees higher than actual with every one of my temperature sensors. Anyone else notice a similar issue?
That is a very weird thing to say. Shouldn’t be documented? What rubbish.
There is also the data site which does indeed document some things like tables and columns. Like here is the one for the states table
Typically things that aren’t meant to be touched aren’t documented. Turns out, I was mistaken about this.
That only encourages people to fiddle themselves to see what happens!
I am glad for the people that enjoy all the work being done around voice control, but I feel ambivalent about it. “The year of the voice” seems like a very strong emphasis on something that is just another form of manual control. I can’t help to always remember Paulus’ famous blog post on the goal for home automation. I know it’s been a while since that was written, but I still build by this motto.
Honestly, I’m not complaining: I’m setting that context so that I can ask: Why is this so useful? I do use voice commands, but very rarely. It’s usually when my hands are tied (pun not intended) and I want to open or close a gate or garage door. Maybe I’ve turned a light on or off that way.
I can go read the voice YAML definitions to see what actions can be performed (and I have). That’s not what I’m looking for. I really want to understand better where people find practical use for this where you cannot automate the effect.
With others around, I don’t particularly enjoy talking with computers.
Change the volume of your music while being in the shower? I can see that one… 
11 Likes
Will the Assist button will be possible to put directly on dashboard? I have theme which disables the top menu on mobile so I don’t have the button there 
Unfortunately you didn’t mention that in this release the modbus version got a mayorupdate. That would be a breaking change in my opinion!
greetz
I think if you create a navigation button to ?conversation=1 appended to any dashboard it should open it
https://www.home-assistant.io/dashboards/actions/#navigation_path
on android you can create a shortcut from the app and be able to launch from the home screen
Same is happening to me for quite a while, not only with 2023.2. It happens only on one tablet, which is turned off until i turn on the lights in the room and turns off when i turn off lights again - in this case it wakes up, but often stays on white page with HA logo. I solved it in a way that when HA sends wakeup command after that also sends reload page to fully (via rest command).
My issue is not on FullyKiosk wake-up, but simply when I launch it manually.
It was working like a charm on previous HA Versions since years. Since 2023.2.0, i got this strange behavior. Restoring my system back to 2023.1 solve the issue (FullyKiosk displaying properly HA dashboard), but that’s not the solution as I want to maintain by HA System up to date.
Hope developpers will find the root cause & post a fix
I tried the navigation to ?conversation=1 but it does not open the assist pop up
Make sure you add that to the end of the dashboard path like the example in the link. For example /lovelace/home?conversation=1
1 Like
I did: /lovelace-pragrhouse/home?conversation=1 yet it just do nothing. It only adds the ?conversation=1 to the url but thats all