looked at r_volution, no power API . dealbreaker imho IP Codes :
https://docs.google.com/document/d/1qYRtRwmH58PKp7ym9qvJ6jDE-2Djq2AoxxwSTGmu06E/edit?usp=sharing
>>> The IP Codes for Power ON and Power OFF are currently not worning but will be added in a future firmware version.
Apologies if this has already been discussed. I received my remote this week and am just getting started setting it up. Is there any central repository for custom integrations? Similar to HACS in Home Assistant.
For a start
A bit more on discord.
Ralf
Awesome! Thank you!!
@kennymc.c keep a repo with most integrations. kennymc-c's list / UC Remote Integrations · GitHub
@M.a.S.e Thanks for looking into R_Volution. I know about no API for Power Command. For this command IR could be used. All other should work via IP…
BR Peter
Any R_Volution users who want to help debug/test a potential new integration? if so, please DM me or better yet, find me on Discord
R_Volution integration is done: R_Volution Integration
What other cool integrations people want/need that can expend this remote capabilities?
How about tp-link devices? TP-Link Smart Home - Home Assistant I can help test the P100 and P110 smart plugs however I don’t have any of the other tp-link smart devices. With Home Assistant I use the P110 to monitor the current on appliances and send me notifications when certain current criteria are met. So if the current drops right down on a dehumidifier I get a notification to check it, which either mean it’s full or the timer has run out. For simpler things I just use the P100 to switch on things like subwoofers when I need them for an activity.
interesting, cool idea.
Question: other then the obvious that not all uses Home Assistant, what’s the benefit of integrations i’ve built so far that are also offered via Home Assistant?
For me the obvious is that not all uses Home Assistant, but also directly on the remote is one less layer for network potential latency, what other benefits are that folks request directly on remote isntead of HA?
i do not have any TPLINK devices, so definitely will need help testing/debugging if/when ill take that on. need to also check TPLINK API as they have MANY devices, need to see how robust this can be.
Yeah, from my perspective it’s having one less layer of complexity so for simple things like switching on and off a plug it would be good to be able to do that directly from the remote whilst still using HA for the more complex automations.
I have a TP-Link smart power strip if that helps. I’m happy to test with that.
Another potential integration could be with Tuya devices which seem quite widespread.
Unfortunately(!) I’ve still got a few of those as well. Happy to test.
i hate Tuya with a passion LOL. I do use Toya Devices but Hate Tuya as a whole… lol… i’ll explore.. good ideas…
This forum REALLY need an LOL emoji quick reply 
Another integration that would be popular with Europeans is the LG Horizon Settop box. See here: Sholofly/lghorizon: Custom integration to control LG Horizon settop boxes for Ziggo(NL), Magenta(AT), UPC(CH), Virgin(GB, IE), Telenet(BE). I’ve got a Virgin Media box so I can help test that one. I’ve seen a few other mentions of the box on Discord so there are probably other testers available in the other countries.
I think this is a very fair point. But I actually like the idea of porting entities from HA. It means I only have to maintain an integration in one place. Instead of potentially having to keep up with updates or issues in multiple places.
It also acts as a layer of abstraction. So I can name something a little more generically in HA and then port it over to the remote. And when I eventually replace that device with a newer one in the future, I won’t need to change anything in the remote. I will just name the new device constantly in HA and it should just work in the remote.
So far I haven’t experienced any noticeable latency. But I have a pretty fast network and HA is running on a Mac Mini M4, so I might be in the minority.
I worked on Tuya, code is complete but i cant make it work free of charge (Tuya will want us to pay monthly fee for API), so i consider this a deal breaker and stopped development. HA implementation for Tuya work. i can work on Local Tuya but it will be limited to only WiFi devices, so i dont see the point in doing that and spending time developing it. Putting this project aside (similar to the Nintendo and Playstation projects, hopefully in the future an API will be available which is free and usable). Moving to find other ideas.