Ok Serge , I’ve just restarted the application and it shows the liters of water consumed? Thank you. For Openweather, I’m going to find out how to know if it has rained during the day so that I can trigger the programmer in the evening.
Hello,
I have had the device for 3 weeks and 2 days ago the programming was no longer working. On my homey application the flow was triggered and the application was “ON” but the valve was not triggered and there was no watering. You had to press “stop” and then “on” again on the application (or on the device) for the valve to open. I’ve since restarted the application and everything’s working again. But I have a small doubt about the device, is it normal that when you press “on” (on the application or on the device), the green LED lights up ½ second and then goes out during the entire watering? Or should it remain lit for the duration of the watering? Thank you
Hi Thierry_Sabatier,
Your problem seems related to a battery default or a too long distance beetwen your device and the Zigbee network.
Keep in mind that the Royal Gardineer is a Zigbee device, and the Zigbee network requires a router within then range of the device Zigbee network.
Try replacing the batteries of your device and moving it closer to your Homey box to ensure everything is working properly.
Then, move it to your water source and check again.
This will tell you whether the problem was caused by the batteries or the position.
Regards,
SoPhos
Is it normal that when watering and opening the valve, the green LED lights up for a quarter of a second and then goes out. Common sense would dictate that it should remain lit green throughout the watering process and go out when the watering stops?
Is my valve faulty?
Hi @SergeP I just receive my royal gardineer from Pearl but it seems it is not recognized by your application but only as standard Zigbee device.
Here are the device id:
Manufacturer _TZE284_xuflgcnz
Product TS0601
Is this a new product that is still not registered in the app?
Many thanks for your help! Regards
Hi Galinet_ch,
I’ve just added your device ID to Homey Royal Gardineer App.
Can you try new test App and tell me if it’s Ok with your device ?
Regards,
SoPhos
Hi @SergeP, thanks for the quick reaction ! It does not work. The device is detected by the application while installing but then I receive an error and the installation fails.
I’m surprized because it is a Royal Gardineer engine buyed at Pearl. I made an interview of the device from the developer athom site and I’m a bit surprized that the device does not seem to have any capabilities…. Here the interview of the device:
"ids": {
"modelId": "TS0601",
"manufacturerName": "_TZE284_xuflgcnz"
},
"endpoints": {
"endpointDescriptors": [
{
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 81,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
4,
5,
61184,
0,
60672
],
"outputClusters": [
25,
10
]
}
],
"endpoints": {
"1": {
"clusters": {
"groups": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"name": "nameSupport",
"value": {
"type": "Buffer",
"data": [
0
]
},
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"name": "clusterRevision",
"value": 2,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
}
]
},
"scenes": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 1,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 2,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 3,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 4,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"name": "clusterRevision",
"value": 2,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
}
]
},
"basic": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"name": "zclVersion",
"value": 3
},
{
"acl": [
"readable",
"reportable"
],
"id": 1,
"name": "appVersion",
"value": 77
},
{
"acl": [
"readable",
"reportable"
],
"id": 2,
"name": "stackVersion",
"value": 0
},
{
"acl": [
"readable",
"reportable"
],
"id": 3,
"name": "hwVersion",
"value": 1
},
{
"acl": [
"readable",
"reportable"
],
"id": 4,
"name": "manufacturerName",
"value": "_TZE284_xuflgcnz"
},
{
"acl": [
"readable",
"reportable"
],
"id": 5,
"name": "modelId",
"value": "TS0601"
},
{
"acl": [
"readable",
"reportable"
],
"id": 6,
"name": "dateCode",
"value": ""
},
{
"acl": [
"readable",
"reportable"
],
"id": 7,
"name": "powerSource",
"value": "battery"
},
{
"acl": [
"readable",
"writable",
"reportable"
],
"id": 65502
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"name": "clusterRevision",
"value": 2
},
{
"acl": [
"readable",
"reportable"
],
"id": 65534,
"name": "attributeReportingStatus",
"value": "PENDING"
},
{
"acl": [
"readable",
"reportable"
],
"id": 65506
},
{
"acl": [
"readable",
"reportable"
],
"id": 65507
},
{
"acl": [
"readable",
"writable",
"reportable"
],
"id": 65487
}
]
}
},
"bindings": {
"ota": {
"attributes": [
{
"acl": [
"readable"
],
"id": 0
},
{
"acl": [
"readable"
],
"id": 1
},
{
"acl": [
"readable"
],
"id": 2
},
{
"acl": [
"readable"
],
"id": 3
},
{
"acl": [
"readable"
],
"id": 4
},
{
"acl": [
"readable"
],
"id": 5
},
{
"acl": [
"readable"
],
"id": 6
},
{
"acl": [
"readable"
],
"id": 7
},
{
"acl": [
"readable"
],
"id": 8
},
{
"acl": [
"readable"
],
"id": 9
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 3
}
]
},
"time": {
"attributes": [
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
]
}
}
}
}
}
Do you see something problematic?
Many thanks,
Galinet_ch
Hi Galinet_ch,
Can you give me error message displayed after installation fail ?
Could you also send me a diagnostic log :
- Restart Royal Gardineer App
- Try to add your device
- After about 1 minute, send me an App diagnostic report
Thank you,
SoPhos
Hi Galinet_ch,
There is nothing abnormal in your diagnostic report, no error message.
I don’t know what’s happening but it’s not linked to Royal Gardineer App.
Maybe you should try to remove your device from Homey, restart your Homey box, remove betteries from your device (I don’t know if there is a reset option on it but perharps pressing button for 10-20 seconds could work), put batteries back in device then try to pair again…
Regards,
SoPhos
Thanks for your support. I found what’s wrong: my device does not support the cluster number 6, used basically for onOff features but implements a 61184 cluster known as Tuya cluster.
Thanks to the Tuya Homey app, I succeed to developp a small application to make it works correctly.
As your app supports official Royal Gardineer device, I can give you my sourcecode if you want to integrate it as a new device + driver in your app.
Regards,
Galinet_ch
Hi Galinet_ch,
Happy you could find a solution ! 
Many Tuya devices use cluster 61184, it’s the case for every TS0601 I encountered and the Royal Gardineer App also works with cluster 61184.
There might have been a specific problem with your device when pairing with Royal Gardineer App as there are actually hundred devices already working with it. But we don’t know what…
Regards,
SoPhos
Hi SergeP,
First of all, thanks for creating this app! I am currently trying to connect a Royal Gardineer smart water valve to my Homey Pro using your app, but the pairing process keeps failing at the very end with a generic error message (“Connection not possible / Something went wrong”).
Device details:
-
Brand/Model: Royal Gardineer / Pearl ZX-7155 (Item number: ZX-7155-675)
-
Type: Smart Water Valve (Battery powered, 2x AA)
What I have tried so far:
-
Inserted brand new batteries.
-
Did a full PtP (Pull the Plug) on the Homey Pro.
-
Factory reset the valve.
-
Kept the device awake by pressing the button every 1-2 seconds during the entire pairing process.
Since it still fails, I suspect that the specific Zigbee ID for this model or hardware revision is not yet included in the app. I created a diagnostic report from your app right after a failed pairing attempt so you can hopefully see the signature.
Diagnostic Report ID: e599b2ae-de82-48d1-96e8-6a58e0eaa66a
Could you please take a look at the log and see if it’s possible to add support for this specific model? I can also provide pictures of the device if needed.
Thanks a lot for your help!
Hi Boris_Peters,
I received your diag report but there is nothing else that the App driver initialization.
This means your device didn’t event create on App.
And this is not due to a specific Zigbee ID because if so, your device would be created as “unknown device” and no error would appear.
I d’ont know what’s hapening with your device but, with my own experience on Zigbee in Homey (sometimes instable), I suggest you to :
- Remove previous unknwon device from Homey
- Remove batteries from your device
- Restart your Homey
- Insert batteries in your device
- Try to pair again
Sometimes, Homey Zigbee network become instable and makes pairing hasardous.
Regards,
SoPhos
Thank you very much for your advice! I followed all your steps precisely (removed devices, PtP, waiting, fresh batteries). Unfortunately, it still fails.
To rule out a hardware issue, I bought a second, brand-new device of the exact same model. Furthermore, I went to a friend’s house and tried pairing both devices to his Homey Pro (different network, different setup). The exact same error happens every single time.
It seems the Homey Zigbee Core drops the interview on a hardware level before it even reaches your app (which explains the empty diagnostic report). It looks like Pearl might be using a very non-standard Zigbee implementation in this specific batch (ZX-7155-675). Is there any way to report such core-level interview failures to Athom, or is this device simply a lost cause for Homey?
HI Boris_Peters,
I didn’t mention that but did you try to pair really nearby from the Homey box, to be sure ?
Regards,
SoPhos
Thanks for checking! Yes, I made absolutely sure to pair it right next to the Homey Pro (less than 20 cm distance) during all of my attempts.
Just to give you a quick update: I reached out to the official Athom Support. They confirmed your suspicion that even if there is an app issue, the valve should at least show up as an “unknown device”.
I just provided them with my core diagnostics and a screenshot of my Zigbee developer tools. It really seems like the Homey Zigbee core is dropping the hardware interview completely before your app can even see it.
I will let you know as soon as I hear back from the Athom engineers. Thanks again for your continued support!
Best regards,
Boris
Hi Boris_Peters,
Sorry about your problems, Athom support is reliable and should find quicly what’s happening.
Please give me any feedback as I manage few other Zigbee Apps and it helps me (and so other users) to get issues with Homey Zigbee network problems.
Regards,
SoPhos
