Indigo Domotics

Ah, that explains all the buttons on that device ID.

Yeah, and I think you're the first tester with a Smart Hub Pro, rather than an RRa2 repeater. It's looking like the Smart Hub doesn't like the query command.

I don't know how firmware updates work with the Caséta stuff - but maybe check for an update if the battery status is a new feature?

Good idea.

I don't know how updates for the Smart Hub Pro (SHP) work, either. I looked in the IOS app and didn't see any way to check for updates or force an update.

As for how to possibly get the plugin to work with SHP and/or with my particular model of remote, I'd like to help if I can. I can telnet to the hub and send it commands.

Thanks.

First thing to try is to disable the remote in Indigo (uncheck the comm enabled box) and try the poll command again. That'll determine if it's just the remote or any device causing issues.

I'll see if anyone on the Lutron forums I frequent know if this is supposed to work.

In the Lutron app, I have currently 8 shade devices and one shade remote device.

In Indigo, each of the shades has a corresponding device. I have a device for the Smart Bridge Pro. I don't have a single device for the remote; instead I have a large number (~25) Indigo devices of type "Lutron Pico Button". These were originally created by the Plugins>Lutron RRA/Caseta>Create Devices from Caseta Smart Bridge Pro. (At this time, I'm not actually using the buttons for anything in Indigo.)

FlyingDiver, are you suggesting that I un-check the "comm enabled" button for each of the 25 pico button devices, then re-try the poll command and capture the logs - would that help?

Yes, exactly. I want to be sure that the hub is reporting the error for both the shades and the remote buttons.


Sent from my iPhone using Tapatalk

... with plugin set for "detailed debugging messages", I first unchecked "comm enabled" box for all of the Lutron Pico Button devices. I then reloaded the plugin. Then executed the poll command.

Resulting logs attached.

Yeah, same error. I found a reference to the exact same error message on the Lutron forums, except in that case it was a RRa2 Select system erring when certain telnet commands were sent. So I'm thinking that it does that whenever it gets a command it doesn't support.