Make sure you are using a long range adapter. The effective range on these locks is ~20ft or worse without one.
1 Like
since update yesterday to Home Assistant 2022.9.0, Node Red is broken. all nodes report api error when attempting to inject node manually or scheduled.
edit: upon further testing turn off inject node worked, but turn on gives api error. thatâs just weird.
I have updated mine and mqtt.publish on an automation still works.
Post the flow thatâs giving you problems. I probably have a hundred inject nodes in my many dozens of flows in Node Red and I havenât seen a problem.
Iâm having the same issue except I have an ecobee thermostat.
1 Like
Also I have that error, even after updating to 2022.9.1 They do not fix it yet
Bluetooth Proxy setup page doesnât support wifi fast connect for hidden SSIDs yet.
As my IOT wifi is hidden, Iâm not able to join an Esp32 device as bt proxy.
I just tried the new ZHA backup feature and for me it creates json file which only have about 40 lines of data 
So this backup feature will not save the devices on Zigbee network? Only the coordinator settings?
Lets say I need to change my coordinator from Conbee 2 to Sonoff zigbeee 3.0. I could just use the migrate function and the devices can connect to coordinator thus can be seen on HA?
Firmware updates were already possible, but I interpreted the release notes as that the new firmware update support was limited to ZHA. Am I mistaking in that? I was contemplating moving to zigbee2mqtt too, but this made me doubt, besides the fact Iâm in no hurry because deconz just works for me.
Ok so I do have a Bluetooth dongle and the Bluetooth integration. Also setup a Bluetooth proxy via the new functionality with BLE devices in range. However nothing gets picked up. Was trying to look for logs (ESPHome end or HA end) but not sure where I would go to further troubleshoot this.
1 Like
As far as I know you do not need the bluetooth integration for bluetooth proxy on esp, only for bluetooth adapters connected to HA itself. But youâre not providing much information. What devices are you hoping to discover? Xiaomi plant sensors autodiscovered fine for me. And esphome config yaml are you using?
Not sure where to report this, but is does seem that some important functionality is broken in various parts of the app, for instance, I want to create a Helper Group but the Member input field has gone. I have tried on different Browsers and OSâs, I also saw some similar behavior on Automation Triggers:
Same problem here mqtt.publish and mqtt.* are no longer present under call-service automation so the automations notifies an error.
Restoring the previous release everything workss fine
Mine does that if there is an automation running and restarting very quickly. I use a blueprint that cycles my RGB LED lights behind my screen which works well but seems to re-run the automation every half a second to force the lights to change. When this is running, my automations panel behaves in this way. Itâs a bit irritating, especially on a mobile device.
This new UI still has the issue bt at least I can just click on the automation now and it opens it up and from there everything works as expected. Before, I had to click the Dots on the right and click edit in the dropdown menu within the 0.5 second gap which was pretty frustrating.
I checked things like that, and no scripts or automations are causing this. Its just always.
also notice the flickering of the script line itself
btw, I now notice the hover on the 3 dots is actually displaying âOverflowâ, which ofc is rather nonsensical and meaningless to a user. Should be called Options or Settings or smoking like thatâŚ
also:
so that is not to be ignored at all, it blocks true functionality. In this menu, only on Scripts, not Automations or Scenes. Or Blueprints. In the others its also only happening on the 3d or 4th tab
fear its got to do with custom-ui though, need some extra time to investigate this.
Really would appreciate some extra eyes from JS expertsâŚ
But, that is actually called an âoverflow menuâ, in some companies I have seen it referred to as a kebab menu, which is as you say non-sensical
1 Like
what I mean is, it should popup useful info on what is behind those 3-dots. We all know its technically called an overflow menu.
And thatâs were the issue comes in.
I checked the docs, the docs donât seem to be updated, or it is a bug.
But it isnât working, and like you see the exact syntax I am using is the ones from the docs, that worked up to today:
service: notify.mobile_app_mar_lx1a
Hi all, many of us still have faith that the previous History behavior comes back as it was before the 2022.7 release. If you also want the option to have the capability to see all entities without have to pick them individually go to View All Option in History and vote. Thank you.
1 Like
Much more likely is that if you check the logs then itâs likely that your MQTT is using the deprecated - platform: mqtt which was warned about since 2022.6 and was removed in 2022.9 - thus your configuration would be invalid and the MQTT platform could not be loaded until you fix this and move to the new format expected for mqtt.
1 Like