Can you tell me, what I’m doing wrong, when I get the error "Try setup again: ‘index-vel_v2’?
I’ve a MCZ EGO Hydromatic 12 M2 which is connected successfully to the cloud (APP works fine)
Here’s a part of the debug log:
File "/config/custom_components/maestro_mcz/__init__.py", line 77, in _async_update_data
await self._maestroapi.Refresh()
File "/config/custom_components/maestro_mcz/maestro/__init__.py", line 175, in Refresh
self._state = await self.StoveState()
File "/config/custom_components/maestro_mcz/maestro/__init__.py", line 166, in StoveState
return State(
File "/config/custom_components/maestro_mcz/maestro/responses/state.py", line 50, in __init__
self.index_vel_v2 = json["index_vel_v2"]
KeyError: 'index_vel_v2'
2023-04-16 04:08:33.032 WARNING (MainThread) [homeassistant.config_entries] Config entry '[email protected]' for maestro_mcz integration not ready yet: 'index_vel_v2'; Retrying in background
The above exception was the direct cause of the following exception:
2023-04-16 04:08:52.439 ERROR (MainThread) [custom_components.maestro_mcz] Unexpected error fetching MCZ Stove data: 'index_vel_v2'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 250, in _async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/maestro_mcz/__init__.py", line 77, in _async_update_data
await self._maestroapi.Refresh()
File "/config/custom_components/maestro_mcz/maestro/__init__.py", line 175, in Refresh
self._state = await self.StoveState()
File "/config/custom_components/maestro_mcz/maestro/__init__.py", line 166, in StoveState
return State(
File "/config/custom_components/maestro_mcz/maestro/responses/state.py", line 50, in __init__
self.index_vel_v2 = json["index_vel_v2"]
KeyError: 'index_vel_v2'
Hello there, would you be able to make an issue on Github with a diagnostic attached?
You can find the Diagnostic on the device page. I can’t quite tell if you can access that on your screenshot, or if the integration fails to setup entirely.
If you can’t, can you provide the stove model info as shown in the system info page in the app? I’ll make a model specific config for you that doesn’t have the index_vel_v2 so we can move from there.
Although it allowed me to switch to local connection instead of cloud
About that, I tried to make a fork of your add on to add the possibility to reduce the refresh interval on the local version, but I have no idea how to publish a package …-_-
I’m really not a dev, do you think you could implement it ?
I’ve published an update with this new parameter, however I haven’t tested it… Since it was quite a small change I took the risk to just modify the code on the fly but would still be good to confirm that it doesn’t break anything else ^^
thanks for the answer: but shouldn’t we
install the addon
then go to integrations page
add the stove from there?
if I do “+ integration” and select your mcz maestro addon it gives me the Host of the stove, the port and the seconds between the updates. Then I press send and ha core restarts. I have to do this, right? or do I have to create the stove by hand in the yalm? Thank you
@Kykkus I looks like your using the add-on from @Seb_Lz AND another integration.
The add-on from Seb, does you need you to go to the integration page, after installing the add-on you need to configure it in the Add-on page to connect your stove