In the GIT you can add a bug and the author will answer.
Ralf
If you look the the available integrations (link at the start of this thread) there is already Kodi. It is not perfect yet but it is there.
R2/R3 will share 99% the same code so what is wrong with this decission? They want to produce more Remotes so why not react on the demands of the current users?
I think you did not bake the Neeo.
Ralf
If I’m understanding the scenario correctly there are 2 wake on lan options for Home Assistant. The RPC Shutdown add on and the one below. RPC Shutdown only works on windows but the one below works on any OS.
This below works for sleep and to shut the PC on/off and if you have some programs running and only put it into sleep then it should work… if you completely shutdown the HTPC then you would need to launch them using windows schedular to run batch files or open programs on boot that need to be opened. Depending on your HTPC it would take a few seconds longer to boot completely though. Just a thought.
I couldn’t agree more. This remote is beautiful and they should be spending every moment on integrations and nothing more. Without 1000’s of integrations it is nothing more than a sexy paperweight, unless you are willing to spend all your free time programming. Remote 3; please…Remote 2 is already almost perfect.
I think the underlying issue is that Unfolded Circle has adopted a fundamentally flawed bushiness plan.
They have no method to generate ongoing revenue that we know of to fund the cost of continuing software development. So the solution seems to be to churn out another product to make more crowdfunding money to keep the lights on.
I worry that the company will fail in the coming few years and we will be left with an unsupported and only partially finished product. Either that, or there will be continual ‘new’ releases of hardware to keep the motor running and all their time will be focused on that, rather than fulfilling the feature/function promises of the R2.
What they need is a consultant and a better business plan to get them sorted out.
Just one man’s opinion, of course. Make of it what you will.
I remember it was said by them that they would open source all code if that would happen. That is of course to be seen, hopefully this is not needed 
What would be the alternative? A paid subscription service for the software? They could also introduce paid software upgrades in the future but for now I think they first needed a bigger user base which is why the introduces Remote 3. Producing more Remote Two models wasn’t possible as some parts where unavailable as I heard.
Much as I have suggestions, as a business and marketing consultant, I’m not in the habit of giving out free advice. However, I think we can all agree that the pace of development has not risen to the level of expectation UC set and we believed.
It’s a shame, really. Very nicely made (but for my current issue) but something of a disappointment in terms of functionality and ease of use.
Just my two cents…
Not all “only” most of the source code and they made a new step last week by publishing roon source. Because of the API the R2 can live forever as long as the hardware lasts. Harmony, Neeo and still Cantata rely on a cloud connection.
Ralf