-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tahoma 2.16.0: "ImportError: cannot import name 'SUPPORT_ALARM_ARM_AWAY' from 'homeassistant.components.alarm_control_panel.const' (/usr/src/homeassistant/homeassistant/components/alarm_control_panel/const.py)" #861
Comments
Duplicate of #860. Can you move to the official Overkiz integration in core? |
Same for me (I have a Connectivity Kit from Somfy, And Overkiz integration doesn't support it yet) |
@qlaffont which device is not supported on your installation? We do support the Connectivity Kit. |
Yes i know ! And it was working before this error ! (It was an information about last comment about official overkiz integration) |
I don't understand. Why can't you use the Overkiz integration from core? |
I can't use core version because it needs to activate developer mode on the device (it is not possible with connectivity kit) |
@qlaffont you can use the Cloud API in core.. This works the same as this deprecated integration. |
@iMicknl sorry it doesn't work :
|
Overkiz from core still doesn't work, home-assistant/core#128438 hasn't been touched. Is there any chance you have a look at this issue or the official integration? |
Any update on this one @iMicknl ? |
No updates planned to this custom component at the moment. Focus is on fixing bugs / adding features to the core integration. |
And for core integration is it planned to support connectivity kit ? |
Connectivity Kit is already supported since day one... What is your issue? Are specific devices not supported perhaps? |
I've modified the core integration and it now works for me, although I'm still not able to change the operation mode. I've changed the call to always set the mode to the mode (manual eco inactive) in which I can control the device, as I don't want it to start heating when energy prices are high and I want it to use the coil (State electric) when Im generating a lot of solar power. I've enabled debugging, but I'm only getting the following error : Error fetching device events data: Too many requests, try again later. If I set the mode in the call below, that I've changed, the 'human readable' mode is reflected correctly in Home Assistant as eco, electric, performance or heat_pump. In : await self.executor.async_execute_command I can't find where operation_mode is mapped to the modes from the water_heater component. |
Did you read the instructions?
The problem
The HA log throws this error, what can I do about this error?
What version of this integration (ha-tahoma) has the issue?
2.16.0
What version of Home Assistant Core has the issue?
2025.1.1
Which gateway / hub do you use?
Somfy Tahoma, TaHoma Security Short Channel von Somfy Firmware: 2024.5.4
Device model
TaHoma Security Short Channel von Somfy Firmware: 2024.5.4
Home Assistant log
Logs
The text was updated successfully, but these errors were encountered: