10+ Firmware and Roomie Remote

[SSS]

7 minutes ago, Michel Kohanim said:

@SSS,

Please upgrade to 5.3.1 so that we have the same point of reference .

With kind regards,

Michel

Sorry I cannot as my entire HA will be impacted...heavily dependent on multiple rooms with controls for iPADs dedicated to each room with activities that are used to control devices, AV systems, etc...

[MrBill]

6 minutes ago, SSS said:

Thanks and agreed...again as I said very clearly l am not going say who should own it and or take the lead l can only express my desire. If both companies don’t see any mutual benefit so be it....what l am sure is l or any other user like me shouldn’t be involved in this compatibility testing porting of latest version, etc...I hope you agree to this...?

Dude.... you're not getting it.... @lilyoyo1 has spelled it out for you many times over the last 2 days.   The comparative explanation I liked best was Apple puts out a new version of iOS, and the developers then have to fix apps to work wherever Apple's release broke them.  Apple can't possibly test the new iOS against all 1.96 million apps in the app store and you don't expect them to either.  UDI is a small company that produces a product.  Version 5 was a major upgrade and change to the framework, they can't test it against the products that developers have developed.  In this case that's RR... and RR website claims compatibility as of 2018:

Also, as I pointed out to you in a different thread the other day, the cross section of users between the two worlds seems to be very small. 

 

[oberkc]

52 minutes ago, SSS said:

what l am sure is l or any other user like me shouldn’t be involved in this compatibility testing porting of latest version, etc...I hope you agree to this...?

I suppose that would depend on whether one of the companies offered you something of value to be a part of this, or how badly you wanted it.?  If this was the only option to keep your system, into which you have committed significant resources, running, I could see that it might be worth doing for some.  

 

 

Edited January 5, 2021 by oberkc

[lilyoyo1]

1 hour ago, SSS said:

Thanks and agreed...again as I said very clearly l am not going say who should own it and or take the lead l can only express my desire. If both companies don’t see any mutual benefit so be it....what l am sure is l or any other user like me shouldn’t be involved in this compatibility testing porting of latest version, etc...I hope you agree to this...?

I don't agree. If you buy a new cadillac and decide to run aftermarket stuff on it, are you going to blame Cadillac for not testing the aftermarket equipment with their car? That's what you're doing here.

Now if the Isy doesn't work with Polisy or there are bugs which prevents it from running, then it is on them to fix. A 3rd party deciding to connect to it is on that 3rd party. Not UDI. UDI has NOTHING to do with RR and their product. 

[SSS]

On 6/17/2020 at 10:48 AM, Rob said:

That seems to be an issue for several of us. Opening a ticket with the Roomie dev proved futile. I found if I only have a single Roomie instance open it works fine. Now I only keep my wall-mounted ipad on Roomie and use Alexa most of the time.

Hi Rob it seems you are on ver 5.x and experiencing the same slow lag response. I managed to open a ticket and the two companies are talking to each  other but they want me to submit RR diagnosis using 4.x then move to 5.x then submit the diagnostic report. Problem is I cannot go to 5.x I tired few time and it breaks down all my setup. Also no guarantee that I will be forced to go back and forth between the two.

How about you submit 5.x and I submit 4.x simple Insteon light on off command executed from RR activity on an iPad 

[fahrer16]

I've run into the issue with RR as well and the problem is totally on RR's side.  An alternate way of allowing RR to interact with the ISY is using homebridge rather than having RR talk to the ISY directly.

[SSS]

1 hour ago, fahrer16 said:

I've run into the issue with RR as well and the problem is totally on RR's side.  An alternate way of allowing RR to interact with the ISY is using homebridge rather than having RR talk to the ISY directly.

Please inform RR open a ticket, hope with all of us requesting they might look into this

[SSS]

On 1/5/2021 at 11:47 AM, Michel Kohanim said:

@SSS,

Please upgrade to 5.3.1 so that we have the same point of reference .

With kind regards,

Michel

Finally I decided to give it a try myself, when I upgrade to 5.0.10 all good the moment I try 5.0.13  / 5.0.16 / 5.3.x the lag symptoms appear immediately 
 

[lilyoyo1]

I don't see anything in their release notes in the past year saying anything about bug fixes for the Isy so I'm not surprised. 

[Rob]

I ditched RR well over a year ago due to the issue and after getting nowhere w/ the developer. Been on Home Assistant  it's way more flexible and powerful than RR is/was.

[fahrer16]

I still use RR, with Home Assistant exposing the ISY devices over HomeKit.  The RR interface looks nice with minimal config and it's easy to use for my wife.  It also has the ability to issue voice commands to Siri on Apple TV, which is lacking from Home Assistant.

Using Home Assistant to make ISY devices accessible over HomeKit is a pretty nice solution, actually better than using RR directly interfaced to the ISY.

[SSS]

Finally I decided to give it a try myself, when I upgrade to 5.0.10 all good the moment I try 5.0.13 / 5.0.16 / 5.3.x the lag symptoms appear immediately
 

[SSS]

On 12/20/2021 at 3:30 PM, fahrer16 said:

I still use RR, with Home Assistant exposing the ISY devices over HomeKit.  The RR interface looks nice with minimal config and it's easy to use for my wife.  It also has the ability to issue voice commands to Siri on Apple TV, which is lacking from Home Assistant.

Using Home Assistant to make ISY devices accessible over HomeKit is a pretty nice solution, actually better than using RR directly interfaced to the ISY.

Yes same reasons love to continue to use RR…I used Hoobs 4 to find a way to get ISY devices into HomeKit and then to RR, but direct native integration is the best if it can work without the issues outlined,  not sure what has broken from 5.0.10 onwards!

[wintermute]

I found the same solution as Fahrer16, I just run Home Assistant to expose Insteon devices as HomeKit devices and use Roomie Remote as the user-side interface. Then you're not tied to just Insteon or Z-wave, either.

Home Assistant works well as a bridge. I have lights using many protocols now that all work within one interface. HomeBridge can be used, too, but I have found HomeAssistant to have more integrations and it seems to be more actively developed. One protocol that isn't yet supported is Yolink. That's too bad since Yolink uses LoRa which has amazing range, is really power efficient, and is very inexpensive.

In addition to Roomie, I also load up the Apple Home app for when I just want simple lighting controls without having to launch Roomie and bringing-up the pop-up bar. I have found that just migrating everything toward HomeKit compatibility through Home Assistant makes things a lot simpler. For my tastes, the Home Assistant app interface is not as sleek as Roomie and is a bit kludgey, especially for AV.

Hopefully, ISY-on-Polisy will allow the same ease of integration as HA and allow bridging to HomeKit at some point so I can just use the UD box for all home automation.