Thanks very much for the detailed responses! I’ll give it some thought.
1 Like
I have an extensive Rako install which I planned myself and installed with the help of an electrician as part of a complete rewire. I have found the hardware to be high quality and reliable - the dimmers are smooth and work well. The cost is high to the extent that I ended up sourcing from ebay. I do think I would go down this route again even knowing that I could replace with Shelly (or other) products for a much lower cost. I like that I can fall back on the switches and native Rako controls. I recently swapped out some Shelly RGBW controllers (excellent) with Rako ones I got cheaply because I wanted to keep the Rako ecosystem whole.
As has been mentioned Rako support is excellent - they know their products and go above-and-beyond to help. The Rakosoft software is fine for configuration once you understand how the system works. The Rako native app is also ok and reliable but won’t win any prizes. The product line continues to evolve and improve which gives the impression that they will be around in the future.
I use Rako with HA via the custom integration written by marengaz. This works but I am acutely aware that it may not unless someone else picks up ongoing maintenance. When it works the response is instant and I have PIRs and other automations triggering the Rako lights. However there are also times when it doesn’t work and I end up reloading. I suspect there may be a challenge integrating with the Rako bridge which sits with Rako - I am not sure their bridge is always correct when it reports the status of a Rako control such as a dimmer. The native app does seem to handle this better than the HA integration and I haven’t got to the bottom of why and can’t afford the time now to debug.
Tom
I’ve got rako in several rooms and really like it - as others have said it’s rick solid and does a great job.
I’ve tried to get it working with HA but so far drawn a blank.
What you can do very easily though is use the http interface of the rako hub to set scenes so depending on what you want to do you might well be able to use that to control via HA. I can’t see current levels with this but I can easily set scenes, turn off etc.
I just have buttons on my dashboard which set the various scenes I want:
1 Like
Happy to help if you want to more complete solution?
Do you have the bridge that allows apple homekit and Alexa control?
1 Like
That would be great!
Yep, I’ve got one of get new bridges so my lights all show in HomeKit
OK, I am away on hioliday at the moment so will give you a few pointers.
I think you have two options
-
Use the homekit integration . I believe you may have to remove Rako from your apple homekit and then it will be discovered by the Home assistant integration where you can use the apple homekit credentials. This should then bring in all your lights as devices and entities. You can then share them back to Apple Homekit using homekit bridge. I think it is best to remove them from other smart hubs like Alexa or Google and add them directly from Home Assistant.
-
Use RakotoMQTT which still works despite it not being under development. I wrote a beginners guide when I was trying to get it working. if you use this method I can try to give you some tips depending on your current set up.
Thanks for taking the time here - really appreciate it (especially when you’re away!)
I tried the HomeKit method at first but just couldn’t get it to link for some reason.
Will try the mqtt version but am using HA on a raspberry pi so not sure if the issues there might get in the way… will report back!
For the homelink method, did you use the key that is on the back of the rako hub?
I’m not sure what the problem is supposed to be with a Raspberry pi, definitely worth a try.
I’ve just fully moved to HA and been getting my Rako working with the Rako2MQTT integration. Does anyone know if there is anyway to configure a power on level for the lights?
Hi, my attempted install of the hacs-rako integration is failing
I’ve cloned the files at github /boshjosh1918/hacs-rako/ to a folder created in the HA install on my pi /homeassistant/custom_components/rako
When I add the integration and click on the link within HA
i get the error " Error Config flow could not be loaded: {“message”:“Handler does not support user”}"
I’ve tried this with and without “rako:” in the configuration.yaml file
This is within a relatively fresh HA installation where everything else is working fine
Any idea what I’m doing wrong please?
This is the first I have heard of that HACs integration. I get the same error. The only ways I have found to get Rako to work with HA are the ones mentioned here here Rako Lighting - #172 by ShawWellPete
Hello,
Sorry for any confusion. boshjosh1918/hacs-rako was a clone of some code I found in a Home Assistant pull request/issue. I only cloned it to make it easier for me to install with HACS and test on my installation.
It never worked for me. Even though I am familiar with Rako’s web API, I have no experience with Home assistant Integrations. I had no idea how I would even start to fix it.
In the end I just decided to use the simple HTTP Request module over Rako’s local API as it seemed like an easier option. I can send you what I did in my configuration.yank if you want.
EDIT: I got the repositories mixed up. boshjosh1918/hacs-rako is just a shell of an integration I began working on but was never able to finish. It doesn’t work because most of the functionality isn’t there.
Thanks for clarifying Josh, I’d be interested to see what you did with http request. I still used rakmqtt as described above but keen to learn other options.
@ShawWellPete per your remarks regarding other options, there is still the implementation that @marengaz wrote using his own python-rako library. The PR for this against home assistant core was never merged and @marengaz lost access to his Rako installation and consequently stopped maintaining it: https://github.com/home-assistant/core/pull/45915
I think there are a number of people in this thread who have got this code to work, but when it breaks, we end up with “change line xxx in init.py manually” type resolutions which are obviously not sustainable.
I was really quite unsure the best way to continue @marengaz work but I have decided that what would be optimal for me would probably suit others.
I’ve started the work to move this into a form that can be consumed via hacs as a custom repository and should also enable this codebase to be more easily maintained and distributed in future.
I’m happy to take feedback from anyone on the right way to do this - I don’t feel great lift and shifting someone else’s code from the PR into a new repo but I could not figure out a better way to achieve the end goal.
It is not yet able to be imported via hacs but the rako integration works if manually copied into custom_components in a HA installation.
Worth noting that this uses the “legacy” API from the Bridge, not the new API on the Hub.
1 Like
Good idea! Let me know if I can help, not a coder so may be restricted to testing.
The repo should now be in a state where it can be be added to HACS as a custom repository (using the github repo) and tested. v0.3.1 should function and not give any warnings about deprecated features in HA.
It should auto-detect your bridge if it’s on the same subnet but if not, you can configure the integration and input the IP address and MAC address in the config window.
Happy to get any feedback. I will work in due course on improving the docs.
1 Like
Hi Simon,
I tested the HACs repository and it works really well and is very easy to set up and all lights are immediately imported.
The benefit of RakoMqtt is that I can get access to the button presses from the Rako switches. I prefer to use home assistant scenes rather than Rako Scenes, and I can even use a rako button to control a non rako light. I’m guessing this functionality is impossible to include in the integration?
Hey Pete,
Glad it works for someone else.
Funny you mention that - being able to use the physical Rako switches to control other lights in HA is something that’s high on my list… struggling with WAF for a proliferation of other “smart switches” in the house, and this would help.
I did some testing a couple of days ago and the underlying Python library does receive the messages from the Rako Bridge that the switches have been pressed but decoding them and surfacing to HA is not implemented.
Since it matters to me, I will take a look at the mqtt implementation and see how hard it would be to move across.
Does the mqtt implementation create switch entities in HA or are you just taking the messages straight from the mqtt topic to handle your automations?
It looks like you’re using NodeRed for the automations. I’d be interested in doing it all in HA native automations so I need to investigate how to create the switch entities separately from the light entities in HA - as only the light entities are implemented in the library at present.
Simon
