I need some Zigbee info to tell… but unless you have not yet, please try the test version of the app first.
If I remember correctly those will not pair with Homey, if you are able to pair them as generic Zigbee units please let me know. As FKey says there is an alternative way to use those.
Thanks I’ll check it out today, it is possible to use them to control hue lights, I just thought it would be great if I could use them to control other devices in the house. They are really good remotes, far better then the newer hue remotes.
thank you, I was looking to make it simpler, only with a luminance value, possible?
Dev-version works with plug. Thanks for your support
1 Like
Sure, that works but if the lum shifts between a value above/below the threshold your lights will trigger multiple times… perhaps not an issue.
in fact, I want the detector to activate the light when it is dark and each time it detects a presence, thanks
Good to read this, and thanks for your great apps Johan. Just wondering. When we use the Philips hue with bridge app from athom, only the buttons work and the dimmer button doesn’t do anything. Do you expect that to work once you add it? It d be great to have that to work.
New test version out.
I’m about to push the test version to Live. So if anyone notice any issues with the test version I’d love to hear from you asap.
// Johan
3 Likes
I know you asked for if it doesn’t work, but still wanted to say it all works fine here on 2019 and 2023 homey’s.
Does it include the explanation for the double and triple spots that all lights need to be included individually?
1 Like
Good to hear! 
Hmm, no it does not… good one… I’ll add it NOW!
2 Likes
I’m having issues with SML004 being unavailable in the app. However sensor data is still updated as I can see values changing in the insights. It’s only the motion part that’s not triggering.
When I re-add the device it works for about a week or so.
Dunno if this is a general problem or only a problem for me 
Thanks for the info, can you please send a diagnostic report when this happens, add a comment so I know it’s your report.
Will do 
New test version out, made a few fixes to mitigate potential memory leaks, added more info to pairing instructions and added support for the Hue Tap Dial Switch.
// Johan
4 Likes
I noticed that the “blink” and “warn mode” flow cards are in a different spot for Homey Pro (early 2019) and Homey Pro (early 2023), app v2.0.46.
for Homey Pro (early 2019) it is under the device itself;
for Homey Pro (early 2023) it is under the app (with additional device selector);
Was this already the case before? didn’t use these custom flow cards yet for HP2023, so it won’t affect me much, but hope it won’t kill the already existing cards for other people if it was under the device itself before.
Or was it already in my PR, but didn’t notice it being weird for HP2023.
Hi there @Caseda, this is actually something that differs between the new Pro and older models. It’s been like this since I introduced the alert and blink functionality (not your PR doing this). I have not tested to migrate an old homey with flows using these cards to the new Pro so I really have no idea if this works or nor… no complains so far…
1 Like
@johan_bendz I noticed that my recently new bought Philips Hue A60 light bulbs are added as a generic zigbee device. Cause the device ID changed: LWA021
I also have older A60 light bulbs and they have another device ID: LWA004
Any chance you can add the LWA021 to the A60 light bulb device, so it would be seen by your app?
I also made a Github issue
It could be related to this old post, although that one is LWA011:
When I interview the light bulb, the light goes off/on for a while, then it remains very bright and the light is unreachable. Have to reset it, to get it to work again.
Edit: interview code added
"ids": {
"modelId": "LWA021",
"manufacturerName": "Signify Netherlands B.V."
},
"endpoints": {
"ieeeAddress": "00:17:88:01:0d:31:2b:1b",
"networkAddress": 36332,
"modelId": "LWA021",
"manufacturerName": "Signify Netherlands B.V.",
"swBuildId": "1.104.2",
"capabilities": {
"type": "Buffer",
"data": [
142
]
},
"endpointDescriptors": [
{
"status": "SUCCESS",
"nwkAddrOfInterest": 36332,
"_reserved": 30,
"endpointId": 11,
"applicationProfileId": 260,
"applicationDeviceId": 257,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
0,
3,
4,
5,
6,
8,
4096,
64515,
64514,
64516
],
"outputClusters": [
25
]
},
{
"status": "SUCCESS",
"nwkAddrOfInterest": 36332,
"_reserved": 10,
"endpointId": 242,
"applicationProfileId": 41440,
"applicationDeviceId": 97,
"applicationDeviceVersion": 0,
"_reserved1": 0,
"inputClusters": [],
"outputClusters": [
33
]
}
],
"touchlinkGroupIds": [],
"extendedEndpointDescriptors": {
"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": 1
},
{
"id": 4,
"name": "manufacturerName",
"value": "Signify Netherlands B.V."
},
{
"id": 5,
"name": "modelId",
"value": "LWA021"
},
{
"id": 6,
"name": "dateCode",
"value": "20230403"
},
{
"id": 7,
"name": "powerSource",
"value": "mains"
},
{
"id": 8,
"name": "appProfileVersion",
"value": 0
},
{
"id": 9
},
{
"id": 10
},
{
"id": 11
},
{
"id": 16384,
"name": "swBuildId",
"value": "1.104.2"
},
{
"id": 65533,
"name": "clusterRevision",
"value": 3
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"identify": {
"attributes": [
{
"id": 0,
"name": "identifyTime",
"value": 0
},
{
"id": 65533,
"name": "clusterRevision",
"value": 2
}
]
},
"groups": {},
"scenes": {},
"onOff": {},
"levelControl": {},
"touchlink": {}
},
"bindings": {
"ota": {}
}
},
"242": {
"clusters": {},
"bindings": {}
}
}
}
hi @johan_bendz here’s the diagnostic report of the Hue Outdoor Motion Sensor (SML004) becoming unavailable in the app:
939c5e84-c820-4c6d-a820-73eb1d4866c2
Could you have a look at that?
I have to motion sensors… the SML002 and the SML004. The motion sensor with id SML004 is constantly triggering motion even if I set the sensitivity to Low. Any one an idea how to prevent this?
