Hello folks,
I cannot seem to find newly introduced fit-mode in picture-entity card.
Was it forgotten to merge?
when I add it via YAML I get following
Also the image is not being scaled as intended
Edit: tested all the fit mode, none have an effect
If you have an old backup of the Mosquitto add-on and you decide to roll back to it, be aware of that all retained messages is also in that backup. If you have some counters (gas meter, electricity meter), they will have the old value until it is updated by the meter. That can create some issues for you if you do some calculation on those values.
Hi,
After the update it seems that Honywell Evohome does not work anymore. On startup I get this error message:
Unable to connect with the vendor's server. Check your network and the vendor's service status page. Message is: Cannot connect to host tccna.honeywell.com:443 ssl:default [Connect call failed ('131.201.64.94', 443)]
However, when I check manually from a browser tccna.honeywell.com is working perfectly. Also for a friend, who has not updated yet, evohome has no issues at all.
Since I can still control everything locally using ramses_cc, itâs not a big issue for now, but it would be nice if this could be fixed.
Same here. Iâve upgraded two Home Assistant Core installations and both have this issue.
didnt spot this during last week of betas, but when I scroll any view now from max top to max bottom or vv the menu bar âshakesâ a bit for a moment
Can anyone see that too?
at first I figured this might have to do with a theme, or a camera as background, but even in default as shown here, this is very obvious
Thanks, without my âcount: 2â config lines, Modbus works again, indeed.
Wonder why it isnât listed in the breaking changes, while it couldnât be any more breaking, as it stops the Modbus integration 
Also warning about the âretry_on_empty: trueâ modbus config line, to be removed before 2024.04
EDIT > This was something my end, I havenât had this problem before so will leave it here. My DNS on my router is pointing to a secure DNS over TLS. This is what seemingly caused the problem, changed my router back to normal 8.8.8.8 port53 and now HA can resolve stuff properly.
I am getting an error, tried to downgrade to 2023.9.3 and then upgraded again but got the error on either version.
Frigate and Dreame integrations not working
* Unable to install package py-mini-racer: WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f388750a650>: Failed to establish a new connection: [Errno -3] Try again')': /packages/50/97/a578b918b2e5923dd754cb60bb8b8aeffc85255ffb92566e3c65b148ff72/py_mini_racer-0.6.0.tar.gz WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f388750af90>: Failed to establish a new connection: [Errno -3] Try again')': /packages/50/97/a578b918b2e5923dd754cb60bb8b8aeffc85255ffb92566e3c65b148ff72/py_mini_racer-0.6.0.tar.gz WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f388750b850>: Failed to establish a new connection: [Errno -3] Try again')': /packages/50/97/a578b918b2e5923dd754cb60bb8b8aeffc85255ffb92566e3c65b148ff72/py_mini_racer-0.6.0.tar.gz WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f3887584210>: Failed to establish a new connection: [Errno -3] Try again')': /packages/50/97/a578b918b2e5923dd754cb60bb8b8aeffc85255ffb92566e3c65b148ff72/py_mini_racer-0.6.0.tar.gz WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f3887584a10>: Failed to establish a new connection: [Errno -3] Try again')': /packages/50/97/a578b918b2e5923dd754cb60bb8b8aeffc85255ffb92566e3c65b148ff72/py_mini_racer-0.6.0.tar.gz ERROR: Could not install packages due to an OSError: HTTPSConnectionPool(host='files.pythonhosted.org', port=443): Max retries exceeded with url: /packages/50/97/a578b918b2e5923dd754cb60bb8b8aeffc85255ffb92566e3c65b148ff72/py_mini_racer-0.6.0.tar.gz (Caused by NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f38875852d0>: Failed to establish a new connection: [Errno -3] Try again'))
If I go to the URL in my browser it works
Seems to be something odd, on the command line in HA I cant ping files.pythonhosted.org, comes back with bad address. But I ping -v4 files.pythonhosted.org it resolves and pings.
Just checked my network settings and IPv6 is disabled, just tried enabling it but still doesnt work.
If I do NSLookup on I can see it resolves a IPv4 and IPv6 address.
After the update, got modbus integration error:
Invalid config for [modbus]: Komfovent AHU Consumption Day, kWh:
count: 2cannot be combined withdata_type: uint32@ data[âmodbusâ][0][âsensorsâ][33]. Got {ânameâ: âKomfovent AHU Consumption Day, kWhâ, âaddressâ: 926, âdata_typeâ: âuint32â, âinput_typeâ: âholdingâ, âcountâ: 2, âprecisionâ: 2, âscaleâ: 0.001, âunit_of_measurementâ: âkWhâ, âdevice_classâ: âenergyâ, âstate_classâ: âtotal_increasingâ, âscan_intervalâ: 30}
And the sensor itself is like this:
- name: "Komfovent AHU Consumption Day, kWh"
address: 926
data_type: uint32
input_type: holding
count: 2
precision: 2
scale: 0.001
unit_of_measurement: kWh
device_class: energy
state_class: total_increasing
scan_interval: 30
Maybe try whatâs mentioned 2 posts up ? That seems to solve it (it did for me)
comment count worked for me, but is the best way?
I think thereâs a problem with the mobile Device Tracker on 2023.10.
Now it returns âunavailableâ instead of ânot_homeâ.
Anyone else has this issue?
The new tile card is nice however having the thermostat room temperature displayed after âHeat -â is better in the existing card . Existing climate and new card underneath shown
Itâs been 1 hour installing⌠still just saying âInstallingâ.
Who knows what itâs doing.
What do you mean existing? The top one you are showing is the mushroom climate card. A custom component you installed. It doesnt come natively with homeassistant.
If you also have card mod installed through hacs then just add this to the bottom of your card.
card_mod:
style:
ha-tile-info$: |
.secondary:after {
content: "- {{state_attr(config.entity,'current_temperature')}}°C";
margin-left: 3px;
}
Make sure your climate entity has the current_temperature attribute, else this wont work. If its a different attribute just change it in the code.
Wow⌠this took close to 2 hours to upgrade (running on a high-power VM, not a Pi) - in case anyone else comes here wondering about how long it is taking.
How large is your DB? What kind of DB? Have you checked your logs?
Nothing in any of the logs at all during the upgrade other than usual HA running entries. DB is a fair size - 8Gb 
Upgrades normally take 5 to 10 mins, this one was very different.
I have noticed this but on the unifi network integration, all the not-connected devices used to show not_home (or away) but now they say unavailable (and can be deleted). Bit annoying as I have a sensor to show unavailable entities and now I have lots. I also use the state in automations
EDIT: Once the unavailable device has joined the network after this update, it works as before, ie with a not_home state when disconnected
Not happening here. Windows/Chrome. iOS/Safari. iOS/App. Probably related to something custom you have?
Yes exactly, same here! I forgot to mention that it was on the unifi integration.