rhammen
rhammen
Running 2023.11.1-Beta, I see the following 2 warnings in the logs: ``` This error originated from a custom integration. Logger: custom_components.luxtronik2 Source: custom_components/luxtronik2/coordinator.py:344 Integration: Luxtronik First occurred: 22:55:22 (1 occurrences)...
Fixes these hassfest erros: Error: R] [MANIFEST] Invalid manifest: extra keys not allowed @ data['homeassistant']. Got '2023.1.0' extra keys not allowed @ data['entity']['sensor']['error_reason']['cause']. Got {'name': 'Cause'} extra keys not allowed...
I noticed that when I change the temperature on the heating thermostat, the heatpumo correction factor is not updated. One problem was that the correction was a factor 100 too...
Hot water thermostat, which was present in the 'old' integration, is missing in the new integration. Should I add it back in, or did you remove it on purpose?
[BETA] First version of the Heating Thermostat (#3) . The Heathing Thermostat must be enabled by using "Configure" on the integration. (And can also be disabled again in the same...
successor of #390, only for error: [MANIFEST] Domain does not match dir name see [workflow action logs](https://github.com/BenPru/luxtronik/actions/runs/18265289035/job/51998730285#step:3:73)
This BenPru/luxtronik integration relies on the python-luxtronik library. Correct definition of new luxtronik parameters, calculations should preferably be done in that library, otherwise can we need to apply more and...
Add sensors indicating (True/False) if we currently inside the X hour period with the lowest average price. Implements #208 Sensors added: - in_lowest_1hour_period - in_lowest_2hour_period - in_lowest_3hour_period - in_lowest_4hour_period -...