Hi Joe!
Thanks!
When you say ânot configured correctlyâ, what exactly do you mean? ![]()
Could you please follow the âGathering device information for troubleshootingâ for the affected devices so that I can troubleshoot?
Hi Joe!
Thanks!
When you say ânot configured correctlyâ, what exactly do you mean? ![]()
Could you please follow the âGathering device information for troubleshootingâ for the affected devices so that I can troubleshoot?
I know, Iâm having luxury problems again.
Is there a way to connect two Homeys to HA at the same time? As soon as I log in to Homey 1, Homey 2 gets kicked out and vice versa.
Thanks for the extensive explanation. I will dig into it. Many thanks!
Yes, itâs theoretically possible. Should already work actually.
To connect two Homey hubs at the same time, you must create a separate Homey API key on each Homey and add the integration twice in Home Assistant - one entry per Homey (different host/IP + token).
If you reuse the same token/session, one Homey will kick the other out.
I have tried several times with different IP addresses and tokens. I even changed Homeyâs name. As soon as I register another Homey, the first Homey I registered is kicked out.
Please donât stress. Thereâs no rush to solve the problem. It would just be nice if I could also switch off Homey 2 MQTT when I get the chance.
Do you get any debug messages when you get kicked out? Good to know, and Iâll keep this in mind for troubleshooting later.
Also, make sure that the Homeys do not report the same internal ID. The name does not matter.
No, unfortunately not. Iâll sit down again at the weekend and test it. Perhaps the error is also in front of the screen.
What I meant was that not all sensors are being detected. Anything related to the heat pump compressor is not being detected. I already ran a troubleshooting step in my original post.
You are welcome to try the latest dev release [v1.1.6-dev.1]. Please let me know if that solved your issues. Should be visible in HACS as you go to âRedownloadâ and select version.
I added compressor counters (compressor_hours, compressor_starts) as sensors for heat pumps, and fixed lights to expose color temperature mode even when saturation isnât present (so color + temp lights show both modes).
FYI (Everyone)
This includes the real-time update over Socket.io. So no more polling. You will now get updates INSTANTLY (milliseconds).
Iâve also added a huge amount of changes, fixes and additions.
Please let me know if anything doesnât work. And if you can, please create an issue on the GitHub. This helps me keep track of what is working and not. Always specify what version you are using before posting.
I will continue to update. And things will update in dev constantly until Iâm happy. Things will crash. Things will be broken. But things will eventually be right.
I would love to get your feedback on things that could improve, things that are missing etc.
My biggest issue right now is to get all devices and capabilities in order. Since there is no âbig list of all existing devicesâ this requires me to google everything or get feedback from the community.
Not really sure about the best approach here. Would be awesome if I could automate this somehowâŚ
Thank you all for downloading and trying/testing this integration. I made this for myself initially, because I needed it. But I have come to realize that I was not the only one.
I am not a company, Iâm not doing this for any kind of profit. Iâm just âone guy with too much time on his handsâ - but I love it. So thank you for your patience and I hope that this integration helps in your future smart home projects - just as it has helped me!
Iâv been a Homey user since the first launch of the âwhite orbâ
, and to be honest, the biggest reason Iâm still sticking with Homey is the ease of use even though Iâm âsomewhat technicalâ
. What really made me continue to stick with this ecosystem was when they launched âAdvanced Flowâ. A UX game-changer - and every product should start and end with UX design involved.
All the love from Sweden,
Mike
Hi Mike,
I installed the latest dev.
The following strings are missing for the heat pump.
string"compressor_active"
string"Heizkreispumpe"
string"Kompressor-Status"
string"Kompressor beginnt"
string"Einmalige Warmwasserbereitung"
The button for the temperature is now available for the lamps, but the control is reversed. By that I mean that when I set the temperature to warm, it is actually set to cold.
What is the brand of the lights? Hue, Govee etc etc.. Does this happen for ALL different lights?
I anyone else experiencing this? I canât seem to replicate this issue. Asking everyone that reads this.
Homey devices probably donât all expose color temperature the same way. Some drivers use a normalized 0â1 scale, others use Kelvin, and at least a few drivers interpret the normalized value in the opposite direction (0=cold, 1=warm vs 0=warm, 1=cold). Home Assistant assumes 0=warm â 1=cold, so when a device uses the opposite convention the slider feels âreversed.â Thatâs why it only affects some users/devices.
Add an option so users can invert normalized colorâtemperature values:
Settings â Devices & Services â Homey â Configure â Connection & Polling
Toggle for:
âInvert normalized light temperature (fixes warm/cold reversal)â
This should then only affect normalized light_temperature (0â1 range), not Kelvin devices.
Iâve changed the default inversion, so install the new dev and test before you toggle anything.
There was an indentation bug in binary_sensor.py that prevented generic boolean capabilities from being created at all. Thatâs why compressor_active, circulation_pump, hot_water, etc. never showed up. (#Google Translate as I donât speak German) ![]()
Fixes applied in v1.1.6-dev.2
Fixed the indentation so generic boolean capabilities are created.
Added explicit mappings for:
This should make those heatâpump entities appear.
Added:
Fixed:
If the integration detects a new Homey capability it doesnât recognize, Home Assistant will show a notification with a oneâclick link that opens a GitHub issue already filled in and tagged as âenhancement,â so you can report it without writing everything manually. I think this can improve future situations and improvements quite a lot.
True, I grabbed a random Tuya RGBW light: the lightâs temperature responds inverted to the temperature slider.
Version 1.1.6-dev.2
Hmm, even in the dev.2, thatâs weird. I changed the default and for me everything is as it should.
Just to be 100%, after installing dev.2 (please redownload again as you might have caught the dev.2 release that I messed up for 5 minutes) - can you restart and reload the integration and test again when you have the time.
And if it does not work, then try the toggle in the settings and tell me which case is correct. (On/Off)
I wonder if this is for all brands or if just some has it inverted in Homey.
It affects all my lights, regardless of whether theyâre Hue, Govee, etc. My lights are also grouped together in Homey. Iâm installing the new dev version and testing it.
After updating to version 2, the lights are now working for me. Thanks, Mike.
Glad to hear it! Iâll bring that fix into the stable version when I have the time!
I missed the update about the toggle, Mike ![]()
Itâs a Kelvin 6500-2000 operated light.
Enabling the inverse toggle (turned on) solved the issue, even before redownloading v1.1.6-dev.2 (and after
).
Observation: once enabled, the inverse toggle canât be disabled anymore. It toggles off when operating it, but itâs back on again when opening the settings again.
Reload and H.A. restart doesnât make a difference.
First of all I agree this issue has no priority, as long as the integration is being tested & improved.
But I also tested with a second Homey with itâs own API key, and can confirm a similar phenomenon, but:
It doesnât get kicked out, only the devices disappear, the flows donât
When I enable Homey1 devices again, the situation reverses
When I donât enable Homey2, after a H.A. restart Homey1 has dissappeared devices (except for flows) as well.
Reconfigure solves it, but itâs peculiar