Agreed, I don’t see the big deal in a new model coming out, I look forward to the new UX and future software updates.
2 Likes
the most beautiful remote isn’t bring you anything unless the software is working correctly. Why not work on that in the first place?
2 Likes
Hi Lutz,
let me add, I wish IP support for:
- Emotiva RMC1 / XMC2
- Panasonic DP-UB90004
- Linn DS ==> simple solution, send any command via netcat like: ‘echo Action Ds/Playlist 1 Play | nc 192.168.2.13 23’ I
Markus
1 Like
Hi,
what is wrong with the Shield IP integration? I cannot see a problem.
Ralf
I will side with the ppl who are outraged. Basically six months after receiving the remote 2, the resale value of it was just smashed to bits by introducing a successor that early, apparently also for far less money than the remote 2 kickstarter buyers paid. It just feels totally wrong to me and I will not buy from this company again.
1 Like
There is an external ip integration for Panasonic (UHD) Blu-Ray players but you need to modify the player firmware for the newer UB models: GitHub - albaintor/integration_panasonicbluray: Panasonic Bluray integration for Unfolded Circle Remote Two
But this is a general problem with these players and not releated to the integration api.
Regarding the netcat commands I could look into integrating this into my requests integration (GitHub - kennymc-c/ucr2-integration-requests: Integration for Unfolded Circle Remote 2 to send HTTP get/post/patch/put requests and Wake on LAN magic packets to a specified url or mac address)
1 Like
It seemed flakey to me.
Perhaps it was because I cannot adequately run Activities as my other media devices currently can only be controlled by IR and are are not being acitvated due to the weak IR blaster on the R2 hub.
When uploading integrations to the remote becomes possible and someone (certainly not me as my coding skills are virtually nil) creates IP integrations for my media devices, I hopefully can give it another try.
1 Like
May I ask again?
Is it possible for existing R2 owners to get a discount towards purchasing the R3? Or perhaps a trade-in option?
We’ve shown loyalty, patience and I, for one, still don’t have a fully functioning remote. I think we should be recognised and rewarded.
5 Likes
Hi Kennymc,
I will try it with your http integration ! i think it should work
But… ho will I get an external integration into my remote ? Is there a how to ?
Markus
4 Likes
You can create a simple activity only with the Shield and no start/end actions. Do not forget to assign commands to buttons/display. Then start your Shield as you did it before without R2. After that start the R2 Shield activity and you can test it.
I already use Android TV everyday with my Philips TV for several weeks and in my eyes it is more reactive than my Harmony with BlueTooth.
I have to stress that again that we are not dropping support for Remote Two and software development has never stopped. Both remotes run the same exact software. In fact, features will be delivered to Remote Two owners earlier before Remote 3 has finished production.
We have received so much interest for Remote Two, that we could not keep up with the production and we had to look for a solution. We have improved a few things for the assembly and during the process also adjusted things on the remote. But in its core, it’s the same as Remote Two. Remote 3 is a necessary and logical step for us to solve the production difficulties (components suddenly becoming NRND) and to be able to scale up production and keep up with demand.
Once again, Remote Two will be supported, with new features coming soon. We’re working hard to finish the Bluetooth support, then third party integrations on the remote. Next to this we’re revamping the Web configurator to make it easier to configure the remote. And that is coming at the end of summer. For Remote Two.
7 Likes
Yes we have something special also for Remote Two owners. We have a lot going on, but by the time Kickstarter goes live you should know about it.
5 Likes
Could you explain why you choose an lcd display instead of OLED? I think it’s buying like an SE device with less features with the same price ….
The software is not abandoned, is it? They’re working on the bugs and have to keep working even on the revised hardware. So… things will keep improving. I note the price quoted is noticeably lower than the R2 which can only be great news - far easier to get adoption if the product is not priced fully at enthusiast-only-level. I presume that is one reason for a model 3, and probably lessons learned getting the R2 manufactured/shipped.
As a waitlister I consider this great news. Price seems lower, and though I’m a bit less thrilled about an LCD over an OLED, realistically a nice LCD is quite good in this day and age. Feature set in general looks good, should be a great way to dip toes into voice controlling Home Assistant which I haven’t bothered with yet. I’m definitely picking one up.
You can just find a different way to work the problem. A Broadlink RM4 Pro for instance is a tenth of the price of the R2; integrate that with Home Assistant, and control your stuff via Home Assistant and the R2. For example. You can also then automate (obviously) completely aside from the R2.
1 Like
Hi @KimmoJ,
the Broadlink RM4 in conjunction with Home Assistant is really an interesting approach.
Do you know whether the RM4 Mini is just as powerful as the RM4 Pro for pure IR control? Or should you generally consider the Pro? How well is the optional sensor cable for temperature/humidity detection implemented in the Home Assistant integration?
I purchased the Remote Two. I plan to also upgrade to the Remote 3, knowing this is not required, and that the Remote Two will still be improved upon.
Look, they had a massive demand for more remotes. They had three options:
- Ignore the demand and keep developing Remote Two
- Manufacture another batch of Remote Two devices to sell
- Integrate user feedback to improve upon Remote Two and manufacture a new model
If they ignored demand, they’d be accused of not listening, not being a successful team because they couldn’t make more product. If they had announced more Remote Two devices, people would complain that it was still flawed and they wouldn’t buy it until it was a new version. And since they chose to update the hardware design with the new batch, people are mad because they just bought Remote Two less than a year ago.
They chose the right option. Always look forward, not back. The Remote Two is still a very capable device and will continue to improve alongside the Remote 3. Nobody is forced to upgrade their hardware. Nothing is becoming obsolete. There is simply another option for current owners.
I am opting to upgrade.
And the resale value? That would’ve dropped regardless of what new hardware they announced. It was the lack of availability propping up the resale value of the Remote Two.
3 Likes
I have seen a few suggestions to use a BroadLink as an in-cabinet blaster. While that is a great idea, it sure would be nice to see some kind of native solution rather than coding around it in HomeAssistant. Maybe this has been asked/stated already - Can the addition of a second Dock 3 be placed in a cabinet and used as an IR blaster? And to be clear, I am not looking to place the dock outside of a cabinet and run a line into it for a blaster. I would like something that is fully contained within the cabinet.
1 Like