freshlybrewedcode / hacs-homee Goto Github PK
View Code? Open in Web Editor NEWa Home Assistant custom component to integrate the homee smart home platform
License: MIT License
a Home Assistant custom component to integrate the homee smart home platform
License: MIT License
Is your feature request related to a problem? Please describe.
The latest fixes for the garage door are awesome. Thank you very much @Taraman17 for your work.
I've encountered one problem with my hörmann garage door series4.
After using a remote control to control the garage door, the state of the garage position is not updated inside the app itself. (a bug homee just doesn't fix..) therefore I've to go inside the official app to click on the three dots in the upper right corner from the garage door to use "Werte aktualisieren" (update values) to let homee pull the latest status of the garage door.
Describe the solution you'd like
It would be awesome if hass would automatically request the "update values" every x minutes to solve the problem.
Describe alternatives you've considered
Expose the "update values" as a button to solve the problem.
Additional context
Is it only my version, or do you have the same problem as me @Taraman17 @godza ?
PS: I hope someone hacks the bisecure from hörmann for local usage of their garage doors
v2.5
After the update to V2.5, the position 99% is displayed for all shutters, no matter in which position they actually are.
no error logs
Is your feature request related to a problem? Please describe.
So far some devices already work great. Including more device profiles such as Roller shutters Would be great
Describe the solution you'd like
Inclusion of new devices or
Describe alternatives you've considered
A description how others could help/ assist in doing so. „How to add device profiles“ so that other users could test and create pull requests
Unable to prepare setup for platform homee.sensor: Platform not found (No module named 'custom_components.homee.sensor')
Checked the custom_components folder. There is no /custom_components/homee.sensor file.
Version v1.5.0
Home Assistant 2022.10.3
Supervisor 2022.10.0
Operating System 9.2
2.5
When starting HA I get the error below for most of the devices.
This only happens in my dev-container, so it is not a real life bug yet. But i fear it might be connected to one of the latest changes, so it should be addressed.
But until now, I could not find any cause for it and debugging brought me no further, so I hope to get some more information here.
2023-08-13 21:01:44.337 ERROR (MainThread) [homeassistant.components.switch] homee: Not adding entity with invalid device info: Invalid device info {'default_manufacturer': 'unknown', 'default_model': 'IMPULSE_RELAY', 'identifiers': {('homee', 9)}, 'name': 'Hoftor', 'sw_version': 'undefined', 'via_device': ('homee', '81887f8b4e4c8f11969524f98154a4fc')} for 'homee' config entry: device info needs to either describe a device, link to existing device or provide extra information.
Home Assistant 2023.8.4
My AEON Labs ZW095 Home Energy Meter Gen5 couldn´t be found in Home Assistant.
is there a way to integrate it?
2023-09-06 07:32:06.672 ERROR (MainThread) [homeassistant.components.sensor] Ignoring invalid device info: Invalid device info {'default_manufacturer': 'unknown', 'default_model': 'ENERGY_METER', 'identifiers': {('homee', 116)}, 'name': 'AEON Labs ZW095 Home Energy Meter Gen5', 'sw_version': 0.0, 'via_device': ('homee', 'xxx')} for 'homee' config entry: device info needs to either describe a device, link to existing device or provide extra information.
2023-09-06 07:32:06.676 ERROR (MainThread) [homeassistant.components.sensor] Ignoring invalid device info: Invalid device info {'default_manufacturer': 'unknown', 'default_model': 'ENERGY_METER', 'identifiers': {('homee', 116)}, 'name': 'AEON Labs ZW095 Home Energy Meter Gen5', 'sw_version': 0.0, 'via_device': ('homee', 'xxx')} for 'homee' config entry: device info needs to either describe a device, link to existing device or provide extra information.
2023-09-06 07:32:06.680 ERROR (MainThread) [homeassistant.components.sensor] Ignoring invalid device info: Invalid device info {'default_manufacturer': 'unknown', 'default_model': 'ENERGY_METER', 'identifiers': {('homee', 116)}, 'name': 'AEON Labs ZW095 Home Energy Meter Gen5', 'sw_version': 0.0, 'via_device': ('homee', 'xxx')} for 'homee' config entry: device info needs to either describe a device, link to existing device or provide extra information.
2023-09-06 07:32:06.685 ERROR (MainThread) [homeassistant.components.sensor] Ignoring invalid device info: Invalid device info {'default_manufacturer': 'unknown', 'default_model': 'ENERGY_METER', 'identifiers': {('homee', 116)}, 'name': 'AEON Labs ZW095 Home Energy Meter Gen5', 'sw_version': 0.0, 'via_device': ('homee', 'xxx')} for 'homee' config entry: device info needs to either describe a device, link to existing device or provide extra information.
2023-09-06 07:32:06.693 ERROR (MainThread) [homeassistant.components.sensor] Ignoring invalid device info: Invalid device info {'default_manufacturer': 'unknown', 'default_model': 'ENERGY_METER', 'identifiers': {('homee', 116)}, 'name': 'AEON Labs ZW095 Home Energy Meter Gen5', 'sw_version': 0.0, 'via_device': ('homee', 'xxx')} for 'homee' config entry: device info needs to either describe a device, link to existing device or provide extra information.
2023-09-06 07:32:06.697 ERROR (MainThread) [homeassistant.components.sensor] Ignoring invalid device info: Invalid device info {'default_manufacturer': 'unknown', 'default_model': 'ENERGY_METER', 'identifiers': {('homee', 116)}, 'name': 'AEON Labs ZW095 Home Energy Meter Gen5', 'sw_version': 0.0, 'via_device': ('homee', 'xxx')} for 'homee' config entry: device info needs to either describe a device, link to existing device or provide extra information.
Is your feature request related to a problem? Please describe.
A new option introduced in v1.2.0 allows the user to select which groups should be imported. The integration will only import devices that are in any of the selected groups. This behaviour will cause devices that are not assigned to a group to never be imported.
Describe the solution you'd like
Add an option to import all devices regardless of what groups are selected.
Describe alternatives you've considered
Move all devices to at least one group.
Additional context
The option should be added to the get_data_schema
function in config_flow.py
and get_imported_nodes
in helpers.py
should return all nodes if the option is enabled.
In core version 2022.7.1, Home Assistant OS 8.2 the latest version of this homee integration (1.4.1) does not load because the configuration fails:
"TypeError: As of 3.10, the loop parameter was removed from Queue() since it is no longer necessary"
As a result, the config flow can't be loaded
This is a new issue likely introduced with HA 8 since the Homme integration worked just fine in versions 6 and 7
In cover.py the following line should be corrected:
@Property
def is_closed(self):
"""Return the state of the cover."""
return True if self.attribute(AttributeType.POSITION) == 100 else False
2.1.0
After a while of running hacs-homee, I get lots of errors from websockets in the log and the integration stops working.
Reloading it gets it back to work for a while, but errors persist.
Disabling Integration makes errors disappear, so I'm pretty sure it's this one, although the logs don't say it directly.
I'm not sure if it is related to the last change or not. I can't test without it, since I only have devices that depend on that change.
2023-02-23 23:26:41.232 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [1476499464] Client unable to keep up with pending messages. Stayed over 512 for 5 seconds. The system's load is too high or an integration is misbehaving
2023-02-23 16:53:42.928 ERROR (MainThread) [homeassistant] Error doing job: Future exception was never retrieved
websockets.exceptions.ConnectionClosedError: received 4404 (private use) TOKEN_INVALID; then sent 4404 (private use) TOKEN_INVALID
2.0.2
I added my Homee (Hörmann Homee Cube).
It has 2 devices:
These are in 1 Group ("Tore"). The group is sucessfully discovered, but if I add it, only the homee cube itself is discovered.
On the first try, the Garage door was found, but after deleting and reinitialisizing, both devices are not discovered.
edit: The garage door is only found after the area is set for the homee base.
The Log does not show any errors.
2023-02-15 14:46:29.558 INFO (MainThread) [custom_components.homee.config_flow] got access token for homee
2023-02-15 14:46:29.559 INFO (MainThread) [custom_components.homee.config_flow] homee task created
2023-02-15 14:46:29.698 INFO (MainThread) [custom_components.homee.config_flow] homee connected
2023-02-15 14:46:29.699 INFO (MainThread) [custom_components.homee.config_flow] homee disconnecting
2023-02-15 14:46:29.722 INFO (MainThread) [custom_components.homee.config_flow] homee config successfully tested
2023-02-15 14:46:29.723 INFO (MainThread) [custom_components.homee.config_flow] created new homee entry with ID 00055112EACA
Is your feature request related to a problem? Please describe.
The integration imports all recogniced devices from homee. This can create a lot of clutter if the user does not want to import all homee devices into HA.
Describe the solution you'd like
Allow the user to specify which devices should be imported by selecting one or more homee groups in the configuration options.
Describe alternatives you've considered
Additional context
This will probably require a change to pymee because groups are not fully integrated yet.
Currently I have set up the Z-Wave siren SHSG10000 from ABUS. However, the device is not displayed in Home Assistant. The associated group has been activated in the configuration.
Is it possible to implement the device?
The following notes are in the log:
2023-04-14 21:38:31.216 INFO (MainThread) [homee] Found node ABUS Sirene, with following Data: {'id': 15, 'name': 'ABUS%20Sirene', 'profile': 4027, 'image': 'default', 'favorite': 0, 'order': 9, 'protocol': 1, 'routing': 0, 'state': 1, 'state_changed': 1681497629, 'added': 1681497601, 'history': 1, 'cube_type': 1, 'note': '%23%20ABUS%20Z-Wave%20Innensirene', 'services': 4, 'phonetic_name': '', 'owner': 2, 'security': 0, 'attributes': [{'id': 185, 'node_id': 15, 'instance': 0, 'minimum': 0, 'maximum': 1, 'current_value': 1.0, 'target_value': 1.0, 'last_value': 0.0, 'unit': '', 'step_value': 1.0, 'editable': 1, 'type': 385, 'state': 1, 'last_changed': 1681497601, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '', 'name': ''}, {'id': 186, 'node_id': 15, 'instance': 0, 'minimum': 0, 'maximum': 1, 'current_value': 0.0, 'target_value': 0.0, 'last_value': 0.0, 'unit': '', 'step_value': 1.0, 'editable': 1, 'type': 13, 'state': 1, 'last_changed': 1681499575, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '', 'name': '', 'options': {'automations': ['toggle'], 'history': {'day': 35, 'week': 5, 'month': 1, 'stepped': True}}}, {'id': 187, 'node_id': 15, 'instance': 0, 'minimum': 0, 'maximum': 0, 'current_value': 0.0, 'target_value': 0.0, 'last_value': 0.0, 'unit': 'text', 'step_value': 1.0, 'editable': 0, 'type': 44, 'state': 1, 'last_changed': 0, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '5.03', 'name': ''}, {'id': 188, 'node_id': 15, 'instance': 0, 'minimum': 0, 'maximum': 0, 'current_value': 0.0, 'target_value': 0.0, 'last_value': 0.0, 'unit': 'text', 'step_value': 1.0, 'editable': 0, 'type': 45, 'state': 1, 'last_changed': 0, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '1.02', 'name': ''}, {'id': 189, 'node_id': 15, 'instance': 0, 'minimum': 0, 'maximum': 100, 'current_value': 10.0, 'target_value': 10.0, 'last_value': 7.0, 'unit': '%25', 'step_value': 1.0, 'editable': 0, 'type': 8, 'state': 1, 'last_changed': 1681499346, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '', 'name': '', 'options': {'history': {'day': 182, 'week': 26, 'month': 6}}}]}
Haven't found a thread in the Home Assistant community; therefore I ask here.
I have imported my devices from Homee to Home Assistant and - not sure - but I think my Fibaro wall plug switch worked well at the beginning. Now, after about one day, I can't swich on (or off) from Home Assistant. When I toggle the switch - i.e. switch off - it is switched on again after a view seconds.
When I switch off in the Homee web ui, it works well.
After I restarted Home Assistant, it worked again well, but again only for a while.
How would I debug what causes this behavior?
v2.3.0
Hi, thanks for this add-on. I really appreciate that!
I'm using a WAREMA WMS cube for a slat roof with vertical shutters and LED's. In sum 4 covers and 2 lights.
All my Warema covers are working correct except one. The failing one is a slat roof which is equal to a regular blind. Every time the cover gets restored in Home-Assistant but did not work.
New since version v2.3.0 is that both lights are not function as before this version.
Lights and the failing cover are working correctly within the homee app.
It would be nice if the cover.lamellendach (slat roof) and both light.led would work as expected.
2023-03-12 18:36:26.276 ERROR (MainThread) [homeassistant.components.light] Error while setting up homee platform for light
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 289, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/homee/light.py", line 107, in async_setup_entry
devices.append(HomeeLight(node, light_set, index, config_entry))
File "/config/custom_components/homee/light.py", line 153, in init
self._supported_features = get_light_features(self)
File "/config/custom_components/homee/light.py", line 42, in get_light_features
features |= ColorMode.BRIGHTNESS #
TypeError: unsupported operand type(s) for |=: 'int' and 'ColorMode'
2023-03-12 18:36:26.316 WARNING (MainThread) [custom_components.reolink_dev.base] Port 80 is used, USE_HTTPS set back to False
2023-03-12 18:36:26.330 ERROR (MainThread) [homeassistant.components.cover] Error adding entities for domain cover with platform homee
Traceback (most recent call last):
File "/config/custom_components/homee/init.py", line 222, in attribute
return self._node.get_attribute_by_type(attributeType).current_value
File "/usr/local/lib/python3.10/site-packages/pymee/model.py", line 200, in get_attribute_by_type
return self._attribute_map[type]
KeyError: 135
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 438, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 709, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 804, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 556, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 597, in _async_write_ha_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 562, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/cover/init.py", line 268, in state
if self.is_opening:
File "/config/custom_components/homee/cover.py", line 108, in is_opening
return True if self.attribute(AttributeType.UP_DOWN) == 3 else False
File "/config/custom_components/homee/init.py", line 224, in attribute
raise AttributeNotFoundException(attributeType)
custom_components.homee.AttributeNotFoundException: 135
2023-03-12 18:36:26.340 ERROR (MainThread) [homeassistant.components.cover] Error while setting up homee platform for cover
Traceback (most recent call last):
File "/config/custom_components/homee/init.py", line 222, in attribute
return self._node.get_attribute_by_type(attributeType).current_value
File "/usr/local/lib/python3.10/site-packages/pymee/model.py", line 200, in get_attribute_by_type
return self._attribute_map[type]
KeyError: 135
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/hom
Thanks,
Juergen
(Edit pictures)
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
translate the strings in Homee Integration to German.
Describe alternatives you've considered
None - really.
Additional context
As Homee is a product that is used in Germany a lot, I think it would be a good thing to a have a german translation
Is your feature request related to a problem? Please describe.
Smart covers/shutters, gates, garages and similar devices are currently not supported.
Describe the solution you'd like
Implement the homee platform for the Home Assistant cover component.
Describe alternatives you've considered
Use the Home Assistant template platform in combination with webhooks or switches to control unsupported devices.
Additional context
Possible related homee node profiles:
ENTRANCE_GATE_OPERATOR = 2010
GARAGE_DOOR_OPERATOR = 2012
GATE_OPERATOR = 2013
INNER_DOOR_OPERATOR = 2014
GARAGE_DOOR_IMPULSE_OPERATOR = 2015
SHUTTER_POSITION_SWITCH = 2002
i noticed this today in the home assistant logs:
2021-05-15 14:11:09 ERROR (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'homee'. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of 'homee'
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
update dependencies for new version of pymee
Describe alternatives you've considered
none
Additional context
none
The newest version changes logging, so we can filter the HA logs better to get information on what is going on .
How would I configure how a sensor get's imported.
I.e. my Fibaro wall plug is shown like this.
Entity state attributes:
current_power_w: 0
today_energy_kwh: 1.94
homee_data:
id: 11
name: FIBARFO Wall Plug
profile: 13
attributes:
- id: 100
type: 1
- id: 101
type: 44
- id: 102
type: 45
- id: 103
type: 4
- id: 104
type: 47
- id: 105
type: 48
- id: 106
type: 3
- id: 107
type: 347
friendly_name: FIBARFO Wall Plug
file core.entity_register:
"entity_id": "switch.fibaro_wall_plug",
"config_entry_id": "7cc80fde59fca178fd33364",
"device_id": null,
"area_id": null,
"unique_id": "11-switch-100",
"platform": "homee",
"name": "Fibaro Wall Plug",
"icon": null,
"disabled_by": null,
"capabilities": {},
"supported_features": 0,
"device_class": "outlet",
"unit_of_measurement": null,
"original_name": "FIBARO Wall Plug",
"original_icon": null,
"entity_category": null
I would like to i.e. the unit_of_measurement: kWh
(uppercase W) and maybe set the state_class: total_increasing
.
I would hope, that this device than is available to the new energy dashboard.
v1.2.0-beta.3 and lower
Currently it is not possible to use more than one configured homee at the same time. Only devices from one homee will work as expected. Removing one of the configurations will cause the other to break until HA is restarted.
The problem occurs because the homee.set_value
service is registered/unregistered for every config entry and does not take into account the homee cube that should be targeted.
2.1.0
hacs-homee detects two of my garage doors properly, but there are no commands for opening/closing, only the position slider which does not work. By that I mean, I can drag the slider, but the gate does not move.
Logbook shows the history of opening/closing doors, so it works properly, and there is open/closed sensor with % open and that works properly.
Unfortunately, there are now warnings/error logs. I have logger: in my configuration file and there are logs by other components but none from hacs-homee
Is your feature request related to a problem? Please describe.
Numerical sensors like temperature, humidity, motion or light sensors are currently not supported.
Describe the solution you'd like
Implement the homee platform for the Home Assistant sensor component.
Describe alternatives you've considered
Additional context
Possible related homee node profiles:
see https://github.com/stfnhmplr/homebridge-homee/blob/master/lib/node_types.js
Possible related attribute types:
see https://github.com/stfnhmplr/homebridge-homee/blob/master/lib/attribute_types.js
Reloading the 1.5.0 integration disables all Homee entities in Homeassistant. HA needs restart to get them re-enabled.
Homee integration 1.5.0
HA Core 2022.10.2
HA Supervisor 2022.10.0
1.5.0
I have a question.
Latest
No sensors generated. I only have 2 garage doors in my homee app, from hormann. When setting up homee integration
I check the boxes for my groups containing the garage doors, but no entities are generated.
2022-10-17 12:17:38.432 INFO (MainThread) [homeassistant.setup] Setting up homee
2022-10-17 12:17:38.433 INFO (MainThread) [homeassistant.setup] Setup of domain homee took 0.0 seconds
2022-10-17 12:17:57.685 INFO (MainThread) [homeassistant.components.light] Setting up light.homee
2022-10-17 12:17:57.690 INFO (MainThread) [homeassistant.components.climate] Setting up climate.homee
2022-10-17 12:17:57.694 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.homee
2022-10-17 12:17:57.699 INFO (MainThread) [homeassistant.components.switch] Setting up switch.homee
2022-10-17 12:17:57.703 INFO (MainThread) [homeassistant.components.cover] Setting up cover.homee
2022-10-17 12:17:57.707 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.homee
2022-10-17 12:17:57.813 ERROR (MainThread) [homeassistant.components.cover] Error adding entities for domain cover with platform homee
File "/config/custom_components/homee/__init__.py", line 205, in attribute
File "/config/custom_components/homee/__init__.py", line 152, in device_info
File "/config/custom_components/homee/__init__.py", line 207, in attribute
custom_components.homee.AttributeNotFoundException: 45
2022-10-17 12:17:58.320 ERROR (MainThread) [homeassistant.components.cover] Error while setting up homee platform for cover
File "/config/custom_components/homee/__init__.py", line 205, in attribute
File "/config/custom_components/homee/__init__.py", line 152, in device_info
File "/config/custom_components/homee/__init__.py", line 207, in attribute
custom_components.homee.AttributeNotFoundException: 45
A clear and concise description of the question/problem/bug
After upgrading HomeAssistant to 2023.9 homee lost all its entities. After clear re-install for both homee device and homee integration, I still got no entities under the homee device. I have done this several times in the past but this time it is different.
Add your logs here.
hacs-homee 2.3.2
home-asisstant 2023.4.2
During the initialization of the home assistant, there is an error regarding homee initialization
Logger: homeassistant.setup
Source: setup.py:205
First occurred: 8:59:22 PM (1 occurrences)
Last logged: 8:59:22 PM
Setup failed for custom integration homee: Requirements for homee not found: ['websockets==10.3'].
error in the log before this one is probably related
Logger: homeassistant.util.package
Source: util/package.py:107
First occurred: 8:59:19 PM (3 occurrences)
Last logged: 8:59:22 PM
Unable to install package websockets==10.3: ERROR: Cannot install websockets==10.3 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts [notice] A new release of pip is available: 23.0 -> 23.0.1 [notice] To update, run: pip install --upgrade pip
Hi,
i dont know why but my config window is empty.
Configure the homee integration. You may need to restart Home Assistant to apply the changes.
The groups that should be imported
Groups that contain window sensors
Groups that contain door sensors
this is all is get. I have only one entity and that is homee it self.
I have 4 Garage doors from Hörmann. But somehow they dont show up in the integration config.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.