| 3 Feb 2025 |
 @hexa:lossy.network | but you can clearly see the color indication that older values are thinned out | 16:21:56 |
|  @pederbs:pvv.ntnu.no changed their display name from pbsds (FOSDEM) to pbsds. | 16:25:34 |
| @hexa:lossy.network | 
Download image.png | 16:30:32 |
 @adam:robins.wtf | that's quite the downsampling :) | 16:45:03 |
| @hexa:lossy.network | after ~10 days apparently | 16:45:52 |
| 4 Feb 2025 |
|  @qfe6mwof7:matrix.org left the room. | 14:28:41 |
| 5 Feb 2025 |
| @hexa:lossy.network | home-assistant esphome ble support is broken on unstable right now | 18:41:25 |
| @hexa:lossy.network | 2025-02-05 18:40:35.272 WARNING (MainThread) [aioesphomeapi.connection] esphome-e1c450 @ 192.168.120.107: Connection error occurred: ESPHomeBluetoothDevice.async_update_ble_connection_limits() takes 3 positional arguments but 4 were given
2025-02-05 18:40:35.272 INFO (MainThread) [aioesphomeapi.reconnect_logic] Processing unexpected disconnect from ESPHome API for esphome-e1c450 @ 192.168.120.107
2025-02-05 18:40:35.278 INFO (MainThread) [aioesphomeapi.reconnect_logic] Successfully connected to esphome-e1c450 @ 192.168.120.107 in 0.006s
2025-02-05 18:40:35.298 INFO (MainThread) [aioesphomeapi.reconnect_logic] Successful handshake with esphome-e1c450 @ 192.168.120.107 in 0.020s
2025-02-05 18:40:35.387 ERROR (MainThread) [homeassistant] Error doing job: Fatal error: protocol.data_received() call failed. (None)
Traceback (most recent call last):
File "/nix/store/29a6wlyr860xg3i9n3pzavrlggmyxzkr-python3-3.13.1/lib/python3.13/asyncio/selector_events.py", line 1019, in _read_ready__data_received
self._protocol.data_received(data)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
File "aioesphomeapi/_frame_helper/plain_text.py", line 65, in aioesphomeapi._frame_helper.plain_text.APIPlaintextFrameHelper.data_received
File "aioesphomeapi/_frame_helper/plain_text.py", line 93, in aioesphomeapi._frame_helper.plain_text.APIPlaintextFrameHelper.data_received
File "aioesphomeapi/connection.py", line 956, in aioesphomeapi.connection.APIConnection.process_packet
File "aioesphomeapi/client_callbacks.py", line 77, in aioesphomeapi.client_callbacks.on_bluetooth_connections_free_response
TypeError: ESPHomeBluetoothDevice.async_update_ble_connection_limits() takes 3 positional arguments but 4 were given
| 18:41:51 |
| @hexa:lossy.network | api breakage I missed in the last aioesphomeapi update | 18:42:03 |
| @hexa:lossy.network | but I'm preparing 2025.2.0 right now | 18:42:10 |
| @hexa:lossy.network | so maybe wait a day or two until you update unstable | 18:42:22 |
 dotlambda | In reply to @hexa:lossy.network
api breakage I missed in the last aioesphomeapi update Can we add upstream tests that would have caught this? | 19:04:58 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/378833 this was the PR | 19:05:24 |
| @hexa:lossy.network | we certainly could | 19:05:40 |
| @hexa:lossy.network | https://www.home-assistant.io/blog/2025/02/05/release-20252/ | 19:27:53 |
| @hexa:lossy.network | Currently out grabbing dinner | 19:28:20 |
| @hexa:lossy.network | Very backup component heavy release | 19:30:39 |
| dotlambda | In reply to @hexa:lossy.network
api breakage I missed in the last aioesphomeapi update Weirdly https://github.com/home-assistant/core/commit/48a91540 didn't change any actual code | 19:48:06 |
| @hexa:lossy.network | hrm | 19:48:44 |
| @hexa:lossy.network | so where is the caller? | 19:49:01 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/379685 | 19:50:46 |
| @hexa:lossy.network | > Executing pytestCheckPhase
> ImportError while loading conftest '/build/source/tests/conftest.py'.
> tests/conftest.py:1240: in <module>
> @pytest_asyncio.fixture(autouse=True, scope="session", loop_scope="session")
> /nix/store/nvqmkrjzzbrzyhgym70530w06vmqad85-python3.13-pytest-asyncio-0.23.8/lib/python3.13/site-packages/pytest_asyncio/plugin.py:151: in inner
> return fixture(fixture_function, **kwargs)
> /nix/store/nvqmkrjzzbrzyhgym70530w06vmqad85-python3.13-pytest-asyncio-0.23.8/lib/python3.13/site-packages/pytest_asyncio/plugin.py:145: in fixture
> return pytest.fixture(fixture_function, **kwargs)
> E TypeError: fixture() got an unexpected keyword argument 'loop_scope'
For full logs, run 'nix log /nix/store/g9p6k7j61axy1ck6i2ph0zp69z4baxx4-homeassistant-2025.2.0.drv'.
| 19:54:55 |
| @hexa:lossy.network | fml | 19:54:57 |
| @hexa:lossy.network | depends on pytest-asyncio>=0.25.0 | 19:56:58 |
| @hexa:lossy.network | currently on staging-next | 19:57:02 |
| @hexa:lossy.network | rebasing onto staging-next | 20:01:18 |
| dotlambda | In reply to @hexa:lossy.network
rebasing onto staging-next That's probably a good idea anyway cause some of those updates might conflict with changes made in python-updates | 20:06:13 |
| @hexa:lossy.network | yep\ | 20:09:56 |
| @hexa:lossy.network | not sure the staging people are going to like me for it 😄 | 20:10:08 |
| @hexa:lossy.network | dotlambda: hm, there is something off with the component tests | 21:43:18 |
