Any idea on if it’s possible to integrate the new feather door with home assistant? Would love to get the on/off added in for security
We (and now a new dev who has taken over) have figured out every device so far. You need to provide dumps as documented in the github.
Any interest in making some of these devices work over local bluetooth?
Not sure if the integration could support both.
It would be super awesome if you can add that capability! I think it would need to be a different integration due to the way Home Assistant integrations work. I tried intercepting the BLE traffic for the door lock, but I could not figure out the encryption. Please report back as you make progress.
Thanks so much to the developers for this integration. I just finished installing these Hampton Bay permanent outdoor mini-LED string lights, and they are well controlled through the integration. I can choose brightness, color, and even the preset scenes. Individual light control is missing, but not important to me, as I can use the Hubspace app for that and then turn the scene on/off via Home Assistant.
The GitHub README says that RGBW isn’t supported, but these pucks are RGBW and work just fine. I’m happy to download the json config files if needed, but the current function is good enough for me! Thanks again!
Issues with Fan: Fan not being added. · Issue #125 · jdeath/Hubspace-Homeassistant
homeassistant | Traceback (most recent call last):
homeassistant | File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 608, in _async_add_entities
homeassistant | await coro
homeassistant | File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 927, in _async_add_entity
homeassistant | await entity.add_to_platform_finish()
homeassistant | File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1384, in add_to_platform_finish
homeassistant | self.async_write_ha_state()
homeassistant | ~~~~~~~~~~~~~~~~~~~~~~~~~^^
homeassistant | File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1023, in async_write_ha_state
homeassistant | self._async_write_ha_state()
homeassistant | ~~~~~~~~~~~~~~~~~~~~~~~~~~^^
homeassistant | File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1148, in _async_write_ha_state
homeassistant | self.__async_calculate_state()
homeassistant | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
homeassistant | File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1087, in __async_calculate_state
homeassistant | if state_attributes := self.state_attributes:
homeassistant | ^^^^^^^^^^^^^^^^^^^^^
homeassistant | File "/usr/src/homeassistant/homeassistant/components/fan/__init__.py", line 406, in state_attributes
homeassistant | data[ATTR_PRESET_MODE] = self.preset_mode
homeassistant | ^^^^^^^^^^^^^^^^
homeassistant | File "/config/custom_components/hubspace/fan.py", line 68, in preset_mode
homeassistant | if self.resource.preset.enabled:
homeassistant | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant | AttributeError: 'NoneType' object has no attribute 'enabled'
Did something change recently in this integration? I have combo ceiling fan lights and they have been stellar for month - showing status almost instantly in HASS. Recently (past week or two) they have not shown properly in HASS or, if turning on a light with the remote for example, have not updated in HASS at all. Curious if I missed something that I need to tweak on my end. TIA!
If you have not updated, you should not have an issue. If you updated, there is a chance something broke between versions. Update to latest version and post an issue on github. Sometimes the API gets overloaded, but 2 weeks of issues is probably not the API.
Okay thanks. I was on 4.1.1 still but just updated so I’ll see how it goes for a few days. Appreciate it.
Hello! Thanks for this integration! I’ve been using a bond bridge for the past year or so to control my fan through HA. This adds a lot more functionality even if it isn’t local. From now on I’ll yse the bond as a failsafe in case the hubspace servers are not responding. Great work!!!
One small feature request: The fan light has presets at 2700k, 3000k, 3500k, 4000k, 5000k and 6500k. Currently, only the 2700k, 4000k, 5000k and 6500k are exposed as presets in the UI. Would it be possible to add the other two? Using the slider is possible but a little tedious since 2700-4000 is a relatively small range out of 2700-6500k (34%).
I can do try to do this in a separate automation and custom card but would love it if it were incorporated into this amazing integration.
My fan is a driskol fan from home decorators if that info is relevant.
post an issue on github. that is where you’ll get the best support.
1 Like
Kingfisher group (Brico dépôt, Castorama, B&Q, Koçtaş) is selling devices based on Afero tech too. The brand is Myko.
Someone made a fork of the project Hubspace Homeassistant: GitHub - dvd604/Myko-Homeassistant: Myko Integration for Home Assistant
It works great for me, I take a fast look at the code and there isn’t so much differences from the original project (mainly endpoints API).
I think it will be a good thing if the hubspace homeassistant project includes this feature (maybe we can choose hubspace or myko at the start of the configuration).
The Myko android app is developped by Afero: https://play.google.com/store/apps/details?id=io.afero.partner.kfi&hl=en
That is pretty cool. If the author of the myko version wants to do that, they should do PRs to the hubspace project which allow it to work for both.
Hello,
I have some myko lights.
It seems like this github is not a available anymore, could you share the code with us ?
Thanks a lot !
1 Like
I have been playing with this. I was able to mitm the Hubspace app and capture the traffic, but I am a novice at decoding the API with mitmproxy. I see the commands to turn off/on the light, but failing at getting the access token.
@jaaem So what settings did you use for mitmproxy? I tried with the Hubspace App on iOS and a proxy on a raspberry pi, but I don’t see any of the traffic.
The Hubspace API is figured out. The latest version of the integration (which I no longer develop) has capability to dump the API. If there is a capability not supported, make an issue on github. The new developer is awesome.
You are not seeing traffic because most newer apps need a way to “unpin” the SSL certificate to accept mitmproxy’s certificate. Without that step, mitmproxy can not see the traffic. It wasn’t needed before, but now it is.
I wrote a tutorial a while back (because of another app, not Hubspace), but it is probably out of date. It can get you started. Be prepared to waste hours of time because some methods will not work, but you do not know until you try! MITM Tutorial - #2 by jaaem
Something went wrong with my mesh network which caused a large hiccup across all network devices. Now it appear that the Hubspace integration lost all of the device names. It’s just showing “Unnamed device” for everything that used to be setup?
I’ve tried restarting HA, reloading the integration multiple times, triple checked all of my LAN settings, and confirmed that the Hubspace app works ok.
Is there a chance the integration lost auth with the API somehow? I’m not sure why these devices are all suddenly Unnamed / unknown.
I just realized that I changed the polling from 30 seconds to 10 seconds… so maybe I got API rate limited?
@llealloo It could be due to rate limiting. Can you create a GitHub issue for me to check out? I need to update the readme to point to GitHub issues instead of this thread.
Is anyone else seeing issues with “Helpers” where you’ve changed the type of a sensor in recent versions of HA? I have a set of landscape lights set up through this integration, and I had changed them using the “Show As” option, from “Switch” to “Light”. In the 2 most recent HA updates (2025.7.2 and 2025.7.3 I think), those mappings/helpers seem to have disappeared.