[APP][Pro] Philips Hue Zigbee (Without the bridge)

Apps
,
1049

Unknown Zigbee device. Then i can continue with installing.

GU10-01: b2372703-d10e-4844-92f9-1b2099a47da1
GU10-02: 7fffb6ec-71f0-4300-bfef-28015b9ff732
GU10-03: f65165b7-f073-4864-a7a4-d00be7d1c9f7
Bulb: 29440714-2d67-4f41-952a-b5aa850994d6

1050

Mm, mine says:
Gu10: LCG002
E27: LWA017

1051

Sorry, misread. The correct are:

GU10: zb_product_id: LTG005
E27: zb_product_id: LWA028

Searched for wat you say, but nothing.

1052

They should work as generic Zigbee Lights because this was already with Homey firmware v7.1 implemented (Source). So in general no special app is needed.

If you check the first post of this topic for the ID’s, you will recognize that these (I guess) new ID’s not supported by the app yet. But in the first post it’s also described what has to be done if you want to request a new device to be added to the app. So please follow this instruction.

1 Like
1053

Hi
I have Hue Outdoor Occupancy Sensor (SML004) connected to my Homey Pro (2016-2019). The Outdoor Occupancy Sensor is not connected via hue bridge. It works as I want with flows and detects movement as expected.

When I try to adjust settings, such as “min report interval for lux” of the Outdoor Occupancy Sensor in the Homey Pro i get the error message “invalid_setting_type”.

Can I do anything to fix this? Should I add the sensor to the hue bridge first and after that to the Homey Pro?

1000016549
10000165491080×2400 186 KB

1054

It’s error in the code, you can fix it and do CLI install. Code is available on GitHUB.
Or you can raise new issue for it… Issues · JohanBendz/com.philips.hue.zigbee · GitHub

1055

Hi,

The contact sensor seems defective.
I can add it, but it doesn’t recognize if it make contact or not and can’t find any battery info either.

Is this a known issue, or not?

1056

Have you paired in close distance ? If not, try to re-add it.

1057

I’m experiencing the same issue.
The sensor was paired approximately 2m from working Zigbee devices that function as a router, one of which is a hue GU10 spot connected through the Hue without bridge app,

1058

It seems the Hue contact sensor does not work with Homey. I can install it using the Philips Hue without bridge app , but it does not show any data.

Any idea about the root cause ?

1059

Have you try to restart the app?

1060

Can you repeat the pairing / repair in close distance of Homey, if that will improve anything ?
Even if close distance of Zigbee router, it’s not automatically 100% ensured it’s used by the device, even the probability shall be significant. Also which contact sensor do you mean - please go to Homey Developer Tools and copy Manufacturer and ModelID

1061

Thanks for your response.

This is for the Hue Contact Sensor:

  • Manufacturer: Signify Netherlands B.V.
  • ModelID: SOC001

Tried both a repair as well as a remove + add new device in close proximity of the HP23 (< 1m). Unfortunately no change.

1 Like
1062

Maybe I recommend to update this issue, eventually also do the sensor interview and attach it. Then it’s with Johan to fix it.

1 Like
1063

Thank you. Done.

1064

Restarting the app or restarting homey does not help at all

1065

i had a philips hue bridge with a single wall switch and two hue lamps and the switch controlled one or the other lamp separately using the dual channel of the switch. Now i have migrated everything to the Homey pro (without the philips bridge) but i can’t find how to make the dual channel of the hue switch work! does anyone know how?

1066

Hi @Jaime_Fontes, this is a bug that will be fixed with next update.

1067

Thank you very much for this information

1068

@johan_bendz
I bought some new Philips Hue White GU10 light bulbs, with a new ID that is unkown by your app. I made a github item
This is the product: GU10 White and already known in your app as GU10 PF (White) (LWG001), but mine ID is LWG005

Interview code:


  "ids": {
    "modelId": "LWG005",
    "manufacturerName": "Signify Netherlands B.V."
  },
  "endpoints": {
    "ieeeAddress": "00:17:88:01:0e:46:93:de",
    "networkAddress": 50116,
    "modelId": "LWG005",
    "manufacturerName": "Signify Netherlands B.V.",
    "endpointDescriptors": [
      {
        "status": "SUCCESS",
        "nwkAddrOfInterest": 50116,
        "_reserved": 28,
        "endpointId": 11,
        "applicationProfileId": 260,
        "applicationDeviceId": 257,
        "applicationDeviceVersion": 0,
        "_reserved1": 1,
        "inputClusters": [
          0,
          3,
          4,
          5,
          6,
          8,
          4096,
          64515,
          64516
        ],
        "outputClusters": [
          25
        ]
      },
      {
        "status": "SUCCESS",
        "nwkAddrOfInterest": 50116,
        "_reserved": 10,
        "endpointId": 242,
        "applicationProfileId": 41440,
        "applicationDeviceId": 97,
        "applicationDeviceVersion": 0,
        "_reserved1": 0,
        "inputClusters": [],
        "outputClusters": [
          33
        ]
      }
    ],
    "deviceType": "router",
    "receiveWhenIdle": true,
    "swBuildId": "1.122.2",
    "capabilities": {
      "alternatePANCoordinator": false,
      "deviceType": true,
      "powerSourceMains": true,
      "receiveWhenIdle": true,
      "security": false,
      "allocateAddress": true
    },
    "extendedEndpointDescriptors": {
      "11": {
        "clusters": {
          "basic": {},
          "identify": {},
          "groups": {},
          "scenes": {},
          "onOff": {},
          "levelControl": {},
          "touchlink": {}
        },
        "bindings": {
          "ota": {}
        }
      },
      "242": {
        "clusters": {},
        "bindings": {}
      }
    }
  }