Announcement

Collapse
No announcement yet.

Lutron Aurora not recognized.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    BTW, below is the JSON for my "Home Theater Aurora" (as it is named in my Philips v2 Hue bridge), but the plug-in had mis-named as "Lutron Aurora 16":

    **************************** Object info *****************************
    {
    "state": {
    "buttonevent": 1002,
    "lastupdated": "2022-09-04T04:04:16"
    },
    "swupdate": {
    "state": "noupdates",
    "lastinstall": "2022-09-03T18:49:04"
    },
    "config": {
    "on": true,
    "battery": 100,
    "reachable": true,
    "pending": []
    },
    "name": "Lutron Aurora 16 Switch",
    "type": "ZLLSwitch",
    "modelid": "Z3-1BRL",
    "manufacturername": "Lutron",
    "productname": "Lutron Aurora",
    "diversityid": "2c3a75ff-55c4-4e4d-8c44-82d330b8eb9b",
    "swversion": "3.8",
    "uniqueid": "ff:ff:00:0f:e7:fd:d2:45-01-fc00",
    "capabilities": {
    "certified": true,
    "primary": false,
    "inputs": [
    {
    "repeatintervals": [
    800
    ],
    "events": [
    {
    "buttonevent": 1000,
    "eventtype": "initial_press"
    },
    {
    "buttonevent": 1001,
    "eventtype": "repeat"
    },
    {
    "buttonevent": 1002,
    "eventtype": "short_release"
    },
    {
    "buttonevent": 1003,
    "eventtype": "long_release"
    },
    {
    "buttonevent": 1010,
    "eventtype": "long_press"
    }
    ]
    }
    ]
    }
    }
    ************************* End Object info ***************************

    Comment


      #17
      randman

      There is a new version of the plugin published that resolves the Object reference issue and a RGB issue.
      As for the Aurora devices, the plugin is not making up the name, but it is presented by the bridge. The point is that the bridge delivers three entries for one Lutron Aurora. A switch, as rotary device and a battery. The rotary device will probably hold the name you see on the Hue app. But the switch and battery will hold a different name, probably the Lutron Aurora nn name. And as the plugin is not recognizing the rotary part correctly, it is following the name of the swtich. Philips is working on a new api and is messing with the aurora device currently, causing issues on these devices. I will surpress the aurora device completely I think - at least until Philips starts to deliver the aurora in a manageble way in their API.

      If you rename the device of the Aurora, both the switch and battery feature will be renamed accordingly on the bridge and in HS. If you rename the features only, there will be no renaming on the bridge.

      Wim
      -- Wim

      Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

      1210 devices/features ---- 392 events ----- 40 scripts

      Comment


        #18
        Originally posted by w.vuyk View Post
        If you rename the device of the Aurora, both the switch and battery feature will be renamed accordingly on the bridge and in HS. If you rename the features only, there will be no renaming on the bridge.
        Wim
        Thanks. It's tempting to rename the device, but hopefully it wouldn't break some Lutron or Philips naming assumptions. Maybe feature rename is safer.

        Comment


          #19
          Don't worry to much on that. You can always name the device back through the Philips Hue app if the result is not what you expect... it will not break anything as control of devices is not through the name, but the ID's under the hood.
          -- Wim

          Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

          1210 devices/features ---- 392 events ----- 40 scripts

          Comment

          Working...
          X