Announcement

**DonMor** · May 25, 2020, 05:12 AM

Your second repeater is stand along or it is the extension of the main repeater?

**nofriday** · May 25, 2020, 11:22 AM

Thanks for the quick reply - it is a standalone main repeater.

-joe

**nofriday** · May 25, 2020, 11:57 AM

Also, I played around a bit more this morning, and thought I would share the additional information:
* As I noted earlier, I am able to import the devices, and add additional ones (via refresh) if I add new devices to the repeater
* If I telnet to the repeater directly, I am able to manipulate the devices via direct commands
* If I change the status of the device, either directly (turning a dimmer on) or via telnet command, it appears the plugin gets the update from the repeater. E.g. Here is the result of changing the shade to 50%: "

May-25 9:48:18 AM

LutronRA2 Debug

Receive: ~OUTPUT,42,1,50.00

Re-reading the logs from yesterday, it appears the problem might be sending the string "Output", instead of the device # that is intended to be controlled. E.g. this is my attempt to turn the device (42) on:
#OUTPUT,Output,1,100,0,00:00:00

Hope this helps and if I can provide any more information please let me know. Thanks again,

-joe

**nofriday** · May 28, 2020, 12:51 AM

OK, I think I figured out the problem!

For context, I had two repeaters configured:

“Original” – this is the one that had previously been set up in HomeSeer and working fine
“New” – this is the new one that I was trying to get working and was exhibiting the problems I posted about.

I believe there might be an issue with what the "New" instance profile is named in HomeSeer. When I set up the New instance, I chose "LutronRA2 - 1st Floor" as the name of the instance to correspond to its intended use. This is the set up that led to the earlier posted errors.

I was curious whether something was wonky with my installation, so I decided to start a clean install of HomeSeer on my laptop. I then installed the RadioRA plugin. I then configured “New”, and was able to manipulate the switches. So then I added “Original” as the second instance (effectively reverse of my existing setup), but for no particular reason, called the instance “LutronRA2” when setting it up. Using this, I was able to control switches in both the Original repeater and the New repeater. Cool!

I thought maybe this had something to do with the ordering I had used, so I decided to uninstall HomeSeer, and re-do the setup. This time, I added “Original” as the first repeater in HomeSeer, and then added “New”, again using “LutronRA2” as the instance name. Again, I was able to control switches in both repeaters from HomeSeer.

So then I wondered – is something different about the new HomeSeer install on my laptop, or did I change names? So then, I removed the configuration for the “New” repeater (the second instance), and then re-added that, but used the name I had previously used as the instance name (“LutronRA2 - 1st Floor”). And when I did this, was able to re-create the problematic behavior, namely that I could control switches on Original repeater, but got errors (and no activity) when I tried to control switches on the New repeater.

Incidentally, I tried the same set up and then used “1st Floor” (success) and then “1st-Floor” (reproduced failure). So…maybe there is a parsing bug that doesn’t handle the more complex name that I tried to use, specifically the hyphen (“-“)?

At this point, I think I have unblocked myself and am perfectly fine using a simpler name for my second repeater. Please let me know if you need more information that would be helpful.

Thanks!
Joe

Announcement

Error controlling devices with multiple repeaters

Error controlling devices with multiple repeaters

Comment

Comment

Comment

Comment