Can someone help me?
After a restart of homey my hue outdoor sensor doesn’t come back up. The device is unavailable but any flows with it do work. I’ve pressed the setup button once, but it is still unavailable.
What is the way to fix this?
I’ve got a Philips Hue Ensis that is not working due to a missing product number. While I can include them as an unknown zigbee device with limited functionality, I miss the extra features. I’ll include the information below:
Model number Philips hue ensis upper light → 929003052501_01
Model number Philips hue ensis lower light → 929003052501_02
Could you add them to the next test version? I can test it and provide feedback.
Please interview them and add output here… thank you.
upper light ensis
"ids": {
"modelId": "929003052501_01",
"manufacturerName": "Philips"
},
"endpoints": {
"endpointDescriptors": [
{
"endpointId": 11,
"applicationProfileId": 260,
"applicationDeviceId": 269,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
0,
3,
4,
5,
6,
8,
4096,
64515,
768,
64513
],
"outputClusters": [
25
]
},
{
"endpointId": 242,
"applicationProfileId": 41440,
"applicationDeviceId": 97,
"applicationDeviceVersion": 0,
"_reserved1": 0,
"inputClusters": [],
"outputClusters": [
33
]
}
],
"endpoints": {
"11": {
"clusters": {
"basic": {
"attributes": [
{
"id": 0,
"name": "zclVersion",
"value": 8
},
{
"id": 1,
"name": "appVersion",
"value": 2
},
{
"id": 2,
"name": "stackVersion",
"value": 1
},
{
"id": 3,
"name": "hwVersion",
"value": 0
},
{
"id": 4,
"name": "manufacturerName",
"value": "Philips"
},
{
"id": 5,
"name": "modelId",
"value": "929003052501_01"
},
{
"id": 6,
"name": "dateCode",
"value": "20221031"
},
{
"id": 7,
"name": "powerSource",
"value": "mains"
},
{
"id": 8,
"name": "appProfileVersion",
"value": 0
},
{
"id": 9
},
{
"id": 10
},
{
"id": 11
},
{
"id": 16384,
"name": "swBuildId",
"value": "1.101.5"
},
{
"id": 65533,
"name": "clusterRevision",
"value": 3
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"identify": {
"attributes": [
{
"id": 0
},
{
"id": 65533,
"name": "clusterRevision",
"value": 2
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"groups": {
"attributes": [
{
"id": 0,
"name": "nameSupport",
"value": {
"type": "Buffer",
"data": [
0
]
}
},
{
"id": 65533,
"name": "clusterRevision",
"value": 3
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"scenes": {
"attributes": [
{
"id": 0
},
{
"id": 1
},
{
"id": 2
},
{
"id": 3
},
{
"id": 4
},
{
"id": 65533,
"name": "clusterRevision",
"value": 3
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"onOff": {
"attributes": [
{
"id": 0,
"name": "onOff",
"value": true
},
{
"id": 16384
},
{
"id": 16385,
"name": "onTime",
"value": 0
},
{
"id": 16386,
"name": "offWaitTime",
"value": 0
},
{
"id": 16387
},
{
"id": 65533,
"name": "clusterRevision",
"value": 2
}
],
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"levelControl": {
"attributes": [
{
"id": 0,
"name": "currentLevel",
"value": 254
},
{
"id": 1,
"name": "remainingTime",
"value": 0
},
{
"id": 15
},
{
"id": 16384
},
{
"id": 65533,
"name": "clusterRevision",
"value": 2
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"touchlink": {
"attributes": [
{
"id": 65533,
"name": "clusterRevision",
"value": 3,
"reportingConfiguration": {
"status": "UNREPORTABLE_ATTRIBUTE",
"direction": "reported"
}
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"colorControl": {
"attributes": [
{
"id": 0,
"name": "currentHue",
"value": 32
},
{
"id": 1,
"name": "currentSaturation",
"value": 140
},
{
"id": 2
},
{
"id": 3,
"name": "currentX",
"value": 29973
},
{
"id": 4,
"name": "currentY",
"value": 26870
},
{
"id": 7,
"name": "colorTemperatureMireds",
"value": 366
},
{
"id": 8,
"name": "colorMode",
"value": "currentXAndCurrentY"
},
{
"id": 15
},
{
"id": 16
},
{
"id": 17
},
{
"id": 18
},
{
"id": 19
},
{
"id": 21
},
{
"id": 22
},
{
"id": 23
},
{
"id": 25
},
{
"id": 26
},
{
"id": 27
},
{
"id": 48
},
{
"id": 49
},
{
"id": 50
},
{
"id": 51
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
}
},
"bindings": {
"ota": {
"attributes": [],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
}
}
},
"242": {
"clusters": {},
"bindings": {}
}
}
}
lower light ensis
"ids": {
"modelId": "929003052501_02",
"manufacturerName": "Philips"
},
"endpoints": {
"endpointDescriptors": [
{
"endpointId": 11,
"applicationProfileId": 260,
"applicationDeviceId": 269,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
0,
3,
4,
5,
6,
8,
4096,
64515,
768,
64513
],
"outputClusters": [
25
]
},
{
"endpointId": 242,
"applicationProfileId": 41440,
"applicationDeviceId": 97,
"applicationDeviceVersion": 0,
"_reserved1": 0,
"inputClusters": [],
"outputClusters": [
33
]
}
],
"endpoints": {
"11": {
"clusters": {
"basic": {
"attributes": [
{
"id": 0,
"name": "zclVersion",
"value": 8
},
{
"id": 1,
"name": "appVersion",
"value": 2
},
{
"id": 2,
"name": "stackVersion",
"value": 1
},
{
"id": 3,
"name": "hwVersion",
"value": 0
},
{
"id": 4,
"name": "manufacturerName",
"value": "Philips"
},
{
"id": 5,
"name": "modelId",
"value": "929003052501_01"
},
{
"id": 6,
"name": "dateCode",
"value": "20221031"
},
{
"id": 7,
"name": "powerSource",
"value": "mains"
},
{
"id": 8,
"name": "appProfileVersion",
"value": 0
},
{
"id": 9
},
{
"id": 10
},
{
"id": 11
},
{
"id": 16384,
"name": "swBuildId",
"value": "1.101.5"
},
{
"id": 65533,
"name": "clusterRevision",
"value": 3
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"identify": {
"attributes": [
{
"id": 0
},
{
"id": 65533,
"name": "clusterRevision",
"value": 2
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"groups": {
"attributes": [
{
"id": 0,
"name": "nameSupport",
"value": {
"type": "Buffer",
"data": [
0
]
}
},
{
"id": 65533,
"name": "clusterRevision",
"value": 3
}
]
},
"scenes": {},
"onOff": {},
"levelControl": {},
"touchlink": {},
"colorControl": {}
},
"bindings": {
"ota": {}
}
},
"242": {
"clusters": {},
"bindings": {}
}
}
}
1 Like
Hi!
I’m having issues with all of my SML003 motion sensors. I added them with the occupancy sensor drivers and they all show a red alert icon in the device card:
I don’t have this issue with older Hue motion sensors where I use the Motion Sensor driver.
The strange thing is; the SML003 sensors still track motion and work in my flows.
Here you can see a temperature graph. That means the sensor is still reporting to the Homey:
What is the problem here?
Thank you!
Jannick
I’m going back to the Hue Bridge. Adding my Philips Hue accessoires and some bulbs to make the network a bit stronger. It should be more reliable than this integration.
The only major downside of doing this is latency. It takes 1/2 seconds before the HP 2023 responds to actions from devices paired to the Hue Bridge.
Anyone knows how to reduce this latency to the maximum?
Devices added to the Hue Bridge do nothing for Homey’s Zigbee network.
That’s a shortcoming of the Hue bridge app, which uses (periodic) polling.
I understand and know both networks are different. I ment that I’m purposely adding lights to the Hue Bridge so that it’s network would become more stable.
I really hope Athom updates the official Hue app so that it will use the real-time API (I thought I red there was one) instead of the polling.
Sadly the ‘without bridge’ app is just not good enough at the current moment with the devices that give errors and the lack of support for the Wall Switch Module.
My guess is that this is a HP2023 issue so hopefully will be ironed out soon(-ish).
i have the same issue after migrating to the HP23, I have also installed a SML001 as occupancy sensor. it migrates fine and HP sees it but after that it does nothing, after a while the red alert is showing again.
I posted a message on github
1 Like
Answered on github.
// Johan
1 Like
This is related to Homey not supporting a feature the device is using when communicating with the Hue hub making it impossible for me to finish the driver. 
(when paired to Hue hub one gets the option to decide how the buttons are to behave and based on this settings are written to the device and the device is then added with the specific functionality, this feature is not part of the Homey pairing logic).
I can’t seem to repair a device since migrating to HP2023, have tried with several bulbs but no luck so far. Is my only option a Hue remote or bridge as it says on the repair screen?
Download the Hue-app and connect bulb with Bluetooth. Then factory reset the bulb in the hue-app. After this you can repair from the Homey app. 
I send an email to Athom about this problem and asked them if they could implement this. This is the answer i got.
Thanks for reaching out to our support and thinking along with us! I’m not sure if this way of adding a Zigbee device is only used by the Hue wall switch. If this is the case and it’s purely one device needing this functionality I doubt development will prioritize this. But if this is something that is used by multiple different Zigbee devices the chances of it getting implemented are a bit higher.
I have taken the liberty to add your request to our internal list for feature requests.
Please keep in mind that we cannot give any guarantees on if and when we will implement your suggestions, as there is already quite the development roadmap laid out. That being said, your request is definitely noted and will be discussed.
Thanks again for your input, we appreciate it!
I wish you a great day and lots of fun with Homey!
Best Regards,
If we want this to get more attention, more people have to make a support request for this issue 
1 Like
A new card for the lights is on its way, making the light, and ambiance if supported by the lamp, follow the sun based on Homey’s geolocation.
8 Likes
Hi has anyone also a problem that after Reboot some motion sensor (hue) have a red triangle? They are still working (flows with motion trigger) and after some restart of the app (2.0.42) they are available again. Also in the developer portal they are available and ping is working when the red triangle is shown. I use a Home Pro 2023 with 10.0.0rc94
Same here!
Me too
Which RED triangle? Can you post screenshot?
