Sorry, but for all end-devices (battery operated) this is BS;
They go in sleep mode after sending an update, and therefore not reachable almost all the time. Hence the ?
And the zigbee overview shows the last known status & route.
Overview of all fine functioning devices:
I meant the Route naturally not Online state.
Hi @TedTolboom any chance you can get this to work?
I have got the High Precision Motion sensor, I previously asked if you could add it. I know there are a lot of requests, this one is quite old and wanted to put it under your attention once more!
edit:
"ids": {
"modelId": "lumi.motion.agl04",
"manufacturerName": "LUMI"
},
"endpoints": {
"endpointDescriptors": [
{
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 263,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
0,
1030,
3,
1
],
"outputClusters": [
3,
25
]
}
],
"endpoints": {
"1": {
"clusters": {
"basic": {
"attributes": [
{
"acl": [
"readable"
],
"id": 0,
"name": "zclVersion",
"value": 3
},
{
"acl": [
"readable"
],
"id": 1,
"name": "appVersion",
"value": 25
},
{
"acl": [
"readable"
],
"id": 2,
"name": "stackVersion",
"value": 2
},
{
"acl": [
"readable"
],
"id": 3,
"name": "hwVersion",
"value": 1
},
{
"acl": [
"readable"
],
"id": 4,
"name": "manufacturerName",
"value": "LUMI"
},
{
"acl": [
"readable"
],
"id": 5,
"name": "modelId",
"value": "lumi.motion.agl04"
},
{
"acl": [
"readable"
],
"id": 6,
"name": "dateCode"
},
{
"acl": [
"readable"
],
"id": 7,
"name": "powerSource",
"value": "battery"
},
{
"acl": [
"readable"
],
"id": 8,
"name": "appProfileVersion"
},
{
"acl": [
"readable"
],
"id": 9
},
{
"acl": [
"readable"
],
"id": 10
},
{
"acl": [
"readable"
],
"id": 11
},
{
"acl": [
"readable"
],
"id": 16384,
"name": "swBuildId",
"value": "2019"
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": []
},
"occupancySensing": {
"commandsReceived": []
},
"identify": {
"attributes": [
{
"acl": [
"readable",
"writable"
],
"id": 0
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [
0
],
"commandsReceived": [
0,
1,
64
]
},
"powerConfiguration": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 32,
"name": "batteryVoltage",
"value": 32
},
{
"acl": [
"readable",
"writable"
],
"id": 49,
"name": "batterySize",
"value": "CR2"
},
{
"acl": [
"readable",
"writable"
],
"id": 51,
"name": "batteryQuantity",
"value": 1
},
{
"acl": [
"readable",
"writable"
],
"id": 52,
"name": "batteryRatedVoltage",
"value": 30
},
{
"acl": [
"readable",
"writable"
],
"id": 53
},
{
"acl": [
"readable",
"writable"
],
"id": 54,
"name": "batteryVoltageMinThreshold",
"value": 27
},
{
"acl": [
"readable",
"reportable"
],
"id": 62
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [],
"commandsReceived": []
}
},
"bindings": {
"identify": {
"attributes": [
{
"acl": [
"readable",
"writable"
],
"id": 0
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [
0
],
"commandsReceived": [
0,
1,
64
]
},
"ota": {}
}
}
}
}
This is not a response to the message above this; it is merely a pattern I see in this channel and in many other channels as well.
I cannot help but notice that there are high expectations towards the volunteers that help developing the apps in the community.
Please understand that the app developers are generally not paid professionals. They are working on apps in their time off work, and only if and when they feel up to it.
We as a community should try to not be too pushy about apps not getting updates. Yes I too like it when an app is current, if it works, if it is updated frequently etc. But it does not mean I get to demand updates from the developer.
If I really would like to speed up development I could help the developers by creating pull requests, or if I cannot code, perhaps by suggesting a donation for updates to the app as appreciation.
If that does not work, I could hire a developer for making the update. This way I get my updates when I want them and I support the community in the process.
If I were an app developer, demanding apps to be updated in the community would probably put me offâŚ
So⌠I do hope that @TedTolboom is fine. And I also hope that someone would create updates.
I have paid developers before and I would probably do it again. If the FP1 sensor is added and I could find out who added the support for it to this great app, I will support the person with a donation for coffee, although the last developer I supported did go out and bought a keg of beer instead⌠
In the meantime, I need to be patient and hold off my FP1 purchase for a little while until itâs supported.
Thank you all for being constructive community members.
Please like this post if you support it. Thank you very much!
@TedTolboom I have a question about Zigbee, how you make this Interview with mode 1? com.xiaomi-mi-zigbee/device.interview-mode1.json at master ¡ TedTolboom/com.xiaomi-mi-zigbee ¡ GitHub
I tried different ways to set attribute 9 (mode) to see this missing endpoints in default interview. The first question is why it doesnât work in your application, and the question is why it doesnât work in general?
I would pay to get things integrated, if that would help developers.
Is it possible to disable/enable sensors in the action part of a (simple) flow?
(like you can do with Hue motion sensors, but now with the Aqara vibration sensor)
Hey @Otter and others.
You can donate money directly to TED here : PayPal.Me
To show your appreciation for all the hard work he has done over the last several years, there are over 40 devices alone in this app.
Just please keep in mind that this is a donation thank him, and he doesnât owe you anything if you donate.
Iâm very gratefull for people like @ted making this happen, without all the developers Homey just isnât the same.
Even though a donation is always a nice way to support someone. What I meant with my comment, that I would pay to have a specific device implemented.
The repo is public, and there are other developers on these forums,
We have a thread here, where you could make a request, which any developer could pick up, or if that fails you could go more general.
As a general rule : you are going to want to assume about $150 USD per hour, plus the cost of the device. Timewise I would expect 1 day to understand the code base and adapt to it, 1 day to test and then obviously time to code the device. $3000 - $6000 USD, would a decent incentive for as contractor.
Someone very familiar with zigbee on Homey could do it faster, but they will likely expect a higher rate. Keeping in mind that ted is âthe guruâ, for these devices.
I hope you find this useful and it helps you put a proposal together to find a developer.
Hi Everyone,
Is there or will the be an intergration for the Aqara roller shade?
Thank you in advance!
Hi MaxLeonhardt,
Did you take the time to search/read this topic? Guess not!
Hi! Just a notification to highlight this topic (AQARA E1 Roller Shade). This product is now very popular and I would love to know when this app can support the E1 Roller Shade.
Any update ? Anyone with a workaround? Thanks!
Apologies did not read it thoroughly enough! 
Iâll wait patiently for an update!
Hi i can not add the aqara water senor, its registed as unknow device what can i do
Aubess Zigbee Smart Tuya Water Leakage Sensor Water Leak Alarm Detector Works With Tuyasmart / Smart Life App Easy Installation - Leakage Alarm Detector - AliExpress this is the sensor
Probably nothing as this is not an Aqara/Xiaomi device.
See the supported modelnumbers in the first post of this topic.
This!
Seems like the newer P1 sensor (not FP1) with 5 years battery life etc. is not supported yet.
Would be nice if someone could get it working.
Hey guys (and ladies) I have a question about one of the oldest supported Aqara devices. Light bulb lumi.light.aqcn02 EAN: 6970504211032
Iâm experiencing exactly what was described on github of @TedTolboom Aqara E27 bulb issues #253, essentially Dimming transition is quite long regardless of the settings and light temperature can be set only once and somehow tends to be fixed on warm yellow. Quite confusing. Iâve tested with two of those and both behave the same.
Device was added easily while generally behavior for turn ON/ OFF is like instantly. Also I do not have complicated zigbee network 13 devices in total (out of which 1 is homey) and inside of the 13 there are 4 routers. Any suggestions would be much appreciated.
Last device is the one Iâm referring to.
