Light’s white_value was deprecated in Home Assistant Core 2021.4 by PR #47720 and replaced by color mode white in Home Assistant Core 2021.7 by PR #51411.
Which is kind of awkward since white value was used for rgbw light in mqtt template light.
Mentioned PRs points to new modes which are going to support light based on strictly defined light modes. However I cannot find rgbw supported by mqtt template light
Can some with expertise comment on this oversight?
Afaik the custom component used another bluetooth stack, are you sure you’re using the original stuff now? It should be these:
esp32_ble_tracker:
bluetooth_proxy:
Also be aware, I used to see all ble macs logged at the esp32 at the default logging level. I do not see that anymore, maybe because the proxy is handling them, maybe because they changed the log level, I don’t know. But the proxy it is working for me, HA is seeing my plant sensors and inkbird temp sensor, also the ones definitely not in range of HA itself.
As for the ignored devices, make sure the bluetooth integrations/devices are not ignored in the past (chosen one is just an example of course):
Thanks again for everything that’s been done! It’s so great to enjoy such a lively support base and community behind one of the most sleek and flexible smart home platforms out there.
Using HA extensively for the past 2+ years, I can also share some well meant feedback, if it helps; I know there are so many different ways people want things to work and different ways to solve things from a user point of view. I am not particularly excited about the way certain options are moved around the interface or tucked away in a context menu. I’m all for simplicity, but I don’t feel something as key as a description for an automation is in the way and should be moved inside a menu. That’s a click too far IMO. The same goes for the system health; while a bit more technical perhaps, keeping this one click away instead of three doesn’t obstruct anything. If there is one thing HA could benefit from, it’s keeping the interface consistent and avoid moving around options on a regular basis as much as possible.
But really I’m not complaining. Just sharing out of caring
I really don’t like how my picture glance cards when tapped for live view now have all the settings in the popped up dialog box as an artifact of combining them in this release. There’s no way to hide the settings right?
yes I know it’s not supported (anymore). But at first mentioned message mentions color mode ‘white’ only. So the information is incomplete.
At second I don’t understand how devs can afford to cannibalize some existing and working methods without providing a working replacement. For this instance strict light modes have been invented (which is good and I support that) but not reflected in mqtt light template. Instead, part of the functionality of the latter has been removed
Json schema is IMO useless since it defines the strict protocol, compatible only with devices that do implement it. It’s useless to communicate with devices that use different json structure. There is option of templating the received message (which could help with one direction), but there is no option to create specific json needed by the device. Let me know if I’m wrong.
I have a Chipolo CARD in my wallet and the MAC address appears to be fixed on that, so you might find the Chipolo ONE tags are the same.
(I’m pretty sure this can’t be done on iOS, but it can on Android).
I ceated a template binary sensor using the bluetooth connection sensor from the Home Assistant app, to know when it’s connected, as follows:
template:
binary_sensor:
# Bluetooth Connection binary sensors
# Rob's Galaxy S21 Bluetooth Wallet Connection binary sensor
- name: "Rob's Galaxy S21 Bluetooth Wallet"
device_class: connectivity
icon: mdi:wallet
state: "{{ 'XX:XX:XX:XX:XX:XX (Chipolo)' in state_attr('sensor.rob_s_galaxy_s21_bluetooth_connection', 'connected_not_paired_devices') }}"
You could potentially put a couple of CARD or ONE tags dotted about your house (for coverage) and when your phone is connected to at least one of them, you know it’s at home.
Having said that, have you considered looking at whether your phone is connected to your home WiFi, which you can do various ways. Either with a specific integration such as DD-WRT that looks at what’s connected to your router, or simply look at the WiFi SSID, again from the Home Assistant app, to see what it’s connected to.
Appreciation for the efforts that was put into this release!
However, the way that the time-of-day is displayed in the “Create Schedule” using a single “a” or “p” looks really… amateurish? To me using “am” or “pm” would just look that much better, in addition to being one of the two formal time standards being used. There is lots of real estate available (and/or the font can be made smaller), so shortage of space should really not be a reason.
Tried.
MQTT does not start normally.
And everything related to MQTT does not work.
Tasmota, zifbee2mqtt and all their sensors are not working.
But the broker works.
The network client monitors sensor changes.
I have a supervised installation which is flagged unsupported ( HA supervisor )
You are running an unsupported installation
Below is a list of issues found with your installation, click on the links to learn how you can resolve the issues.
connectivity_check
After you re-enable the connectivity check you have to wait for HA to update it’s cache of host info. Or you can force it by doing ha host reload. Then it will see it’s enabled again
hello Petro, i have the same issue and i trying to install flux from Integration but the error appears: “This integration does not support configuration via the UI”
so, how to install it?
I am using the last version HA 2022.9.2
Thanks in advance.
Gaby
After doing “ha host reload” there is still the error
You are running an unsupported installation
Below is a list of issues found with your installation, click on the links to learn how you can resolve the issues.
connectivity_check
