# \[APP\]\[Pro\]MOES - Unlock full potential of your MOES Zigbee devices

**URL:** <https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967>\
**Category:** Apps\
**Created:** [July 7, 2026, 6:10am UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967 "2026-07-07T06:10:03Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![SergeP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sergep/32/81216_2.png) [@SergeP](https://community.homey.app/u/SergeP)\
**Post date:** [July 29, 2026, 10:13am UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/21 "2026-07-29T10:13:23Z")

</div>

**[SunBeech](https://community.homey.app/u/sunbeech)**,

Are you sure capabilities “Last clic date”, “Lasct action” and “Last button” don’t update ?  
Because I got your logs and everything is going fine with them !

Here are the logs, all reflect prefectly the actions you listed :

```auto
2026-07-29T08:32:28.879Z >> sensor_lastclicdate 29-07-26 10:32:28
2026-07-29T08:32:28.952Z >> sensor_lastaction 1 Click
2026-07-29T08:32:28.953Z >> sensor_lastbutton 1

2026-07-29T08:32:33.910Z >> sensor_lastclicdate 29-07-26 10:32:33
2026-07-29T08:32:33.911Z >> sensor_lastaction 1 Click
2026-07-29T08:32:33.912Z >> sensor_lastbutton 1

2026-07-29T08:32:37.656Z >> sensor_lastclicdate 29-07-26 10:32:37
2026-07-29T08:32:37.657Z >> sensor_lastaction 1 Click
2026-07-29T08:32:37.658Z >> sensor_lastbutton 2

2026-07-29T08:32:41.143Z >> sensor_lastclicdate 29-07-26 10:32:41
2026-07-29T08:32:41.144Z >> sensor_lastaction 1 Click
2026-07-29T08:32:41.145Z >> sensor_lastbutton 2

```

It’s a really strange behavour I can’t explain at this time.  
If you’re on a web browser, did you update your brower (F5) ?

Regards,  
SoPhos

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [July 29, 2026, 10:32am UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/22 "2026-07-29T10:32:48Z")

</div>

Hi SoPhos,

I am sorry that I am causing confusion. I checked it again.

The Sensors tab always shows the last action:

 ![IMG_2846](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/a/aae5a2ae26a4e1742c264068b3efe90a36eee40e.jpeg)

The Last Button insight on the Insights tab, does indeed log the clicks. My bad ☺. Since it averages out the pressed button number over time, I did not see it at first.

 ![IMG_2847](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/e/9e7d7832ea077bcf7dc26d114968c2dad67f2dd6.jpeg)

But the pressed button is logged indeed. Also if I press the buttons again then I see the Insight graph changing. Due to the averaging Homey performs when the data gets older than 1 hour, I am not sure how relevant this Insight is though (but that is another matter).

Finally the log on the Log tab: this one is not updated. It only contains entries from before you changed the app:

 ![IMG_2849](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/3/c3e4cef4d9b5ae686a6e581a7491ad272775e1a1.jpeg)

---

<div class="post-metadata">

**Author:** ![SergeP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sergep/32/81216_2.png) [@SergeP](https://community.homey.app/u/SergeP)\
**Post date:** [July 29, 2026, 10:50am UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/23 "2026-07-29T10:50:06Z")

</div>

> [@SunBeech](#):
>
> Finally the log on the Log tab: this one is not updated. It only contains entries from before you changed the app:

This is what I changed because to get these insights, fake capabilities were created but Homey automaticaly generates flow cards for each capability. Because Homey isn’t designed for that.

So, this is the deal :

- We can get these insights but you’ll have as much flow cards as capabilities (like before)
- If we remove unusefull flow cards, we loose these insights

My position : these insights are unusefull and not standard for Homey as you can create flows linked to buttons actions and add notifications if you want, I will remove them and kepp in line with standard dev. And this is probably what I’m going to do.

Regards,  
SoPhos

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [July 29, 2026, 10:56am UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/24 "2026-07-29T10:56:07Z")

</div>

> [@SergeP](#):
>
> My position : these insights are unusefull and not standard for Homey as you can create flows linked to buttons actions and add notifications if you want, I will remove them and kepp in line with standard dev. And this is probably what I’m going to do.

That’s fine and I agree with you.

---

<div class="post-metadata">

**Author:** ![SergeP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sergep/32/81216_2.png) [@SergeP](https://community.homey.app/u/SergeP)\
**Post date:** [July 29, 2026, 11:05am UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/25 "2026-07-29T11:05:45Z")

</div>

Hi **[SunBeech](https://community.homey.app/u/sunbeech)**,  
Hi all,

Thanks to **[SunBeech](https://community.homey.app/u/sunbeech)** help, I managed to integer **ZT-SY-EU41-\*-MS** (incl. _\_TZ3000\_4upl1fcj_ / _TS0041_) in Homey MOES App.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/f/af30379f219255c8211a29b6daa6629a472412eb.png)

Link to the new MOES App test version :

> **[MOES | Homey](https://homey.app/en-us/app/net.franceweb.moes/MOES/test/)**
>
> Unlock full potential of your MOES Zigbee devices

Please keep in mind to test your devices as I don’t own each one myself and I couldn’t do it.

Regards,  
SoPhos

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [July 29, 2026, 11:47am UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/26 "2026-07-29T11:47:17Z")

</div>

Hi SoPhos,

I am running into some issues when trying to pair the 1-gang Scene Switch:

- Initially it found and added the device, but showed that the device was unavailable.
- I tried to repair it via the Maintenance function in the device tile, but then got a ‘Could not get device by id’ error.  
 ![IMG_2851.PNG](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/2/d2a5a529186fc600eb9aeeb29db502cd7351cf1d.jpeg)
- I removed the device from Homey and paired it again. The device is added, but all capability values are empty  
 ![IMG_2852.PNG](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/0/80b03a4697c7347c800f0405bff37a9f8b044385.jpeg)  
 ![IMG_2853.PNG](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/4/d45d5999f863e623c910bbe52277240f9a0ca0e3.jpeg)
- When I press a button, the last clicked-values are not updated. Also when I create a flow it does not respond to button presses.

I performed an interview of the switch. Not sure whether that gives you any clues.

> **Interview details**
>
> ```json
> 
> "ids": {
> "modelId": "TS0041",
> "manufacturerName": "_TZ3000_4upl1fcj"
> },
> "endpoints": {
> "ieeeAddress": "5c:02:72:ff:fe:0a:60:59",
> "networkAddress": 45515,
> "modelId": "TS0041",
> "manufacturerName": "_TZ3000_4upl1fcj",
> "endpointDescriptors": [
> {
> "status": "SUCCESS",
> "nwkAddrOfInterest": 45515,
> "_reserved": 18,
> "endpointId": 1,
> "applicationProfileId": 260,
> "applicationDeviceId": 0,
> "applicationDeviceVersion": 0,
> "_reserved1": 1,
> "inputClusters": [
> 0,
> 1,
> 6
> ],
> "outputClusters": [
> 25,
> 10
> ]
> }
> ],
> "deviceType": "enddevice",
> "receiveWhenIdle": false,
> "capabilities": {
> "alternatePANCoordinator": false,
> "deviceType": false,
> "powerSourceMains": false,
> "receiveWhenIdle": false,
> "security": false,
> "allocateAddress": true
> },
> "extendedEndpointDescriptors": {
> "1": {
> "clusters": {
> "basic": {
> "attributes": [
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 0,
> "dataTypeId": 32,
> "name": "zclVersion",
> "value": 3,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 1,
> "dataTypeId": 32,
> "name": "appVersion",
> "value": 66,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 2,
> "dataTypeId": 32,
> "name": "stackVersion",
> "value": 0,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 3,
> "dataTypeId": 32,
> "name": "hwVersion",
> "value": 1,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 4,
> "dataTypeId": 66,
> "name": "manufacturerName",
> "value": "_TZ3000_4upl1fcj",
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 5,
> "dataTypeId": 66,
> "name": "modelId",
> "value": "TS0041",
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 6,
> "dataTypeId": 66,
> "name": "dateCode",
> "value": "",
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 7,
> "dataTypeId": 48,
> "name": "powerSource",
> "value": "battery",
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "writable",
> "reportable"
> ],
> "id": 65502,
> "dataTypeId": 32,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 65533,
> "dataTypeId": 33,
> "name": "clusterRevision",
> "value": 2,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 65534,
> "dataTypeId": 48,
> "name": "attributeReportingStatus",
> "value": "PENDING",
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 65504,
> "dataTypeId": 72,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 65505,
> "dataTypeId": 72,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 65506,
> "dataTypeId": 32,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 65507,
> "dataTypeId": 72,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> }
> ],
> "commandsGenerated": "UNSUP_GENERAL_COMMAND",
> "commandsReceived": "UNSUP_GENERAL_COMMAND"
> },
> "powerConfiguration": {
> "attributes": [
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 0,
> "dataTypeId": 33,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 32,
> "dataTypeId": 32,
> "name": "batteryVoltage",
> "value": 30,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 33,
> "dataTypeId": 32,
> "name": "batteryPercentageRemaining",
> "value": 200,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> },
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 65533,
> "dataTypeId": 33,
> "name": "clusterRevision",
> "value": 1,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> }
> ],
> "commandsGenerated": "UNSUP_GENERAL_COMMAND",
> "commandsReceived": "UNSUP_GENERAL_COMMAND"
> },
> "onOff": {
> "attributes": [
> {
> "acl": [
> "readable",
> "reportable"
> ],
> "id": 0,
> "dataTypeId": 16,
> "name": "onOff",
> "value": false,
> "reportingConfiguration": {
> "status": "NOT_FOUND",
> "direction": "reported"
> }
> }
> ],
> "commandsGenerated": "UNSUP_GENERAL_COMMAND",
> "commandsReceived": "UNSUP_GENERAL_COMMAND"
> }
> },
> "bindings": {
> "ota": {
> "attributes": [],
> "commandsGenerated": "UNSUP_GENERAL_COMMAND",
> "commandsReceived": "UNSUP_GENERAL_COMMAND"
> },
> "time": {
> "attributes": [],
> "commandsGenerated": "UNSUP_GENERAL_COMMAND",
> "commandsReceived": "UNSUP_GENERAL_COMMAND"
> }
> }
> }
> }
> }
> 
> ```

---

<div class="post-metadata">

**Author:** ![SergeP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sergep/32/81216_2.png) [@SergeP](https://community.homey.app/u/SergeP)\
**Post date:** [July 29, 2026, 12:08pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/27 "2026-07-29T12:08:32Z")

</div>

I think I know what was happening.  
Sorry, I made a mistake in code, I found it with your feedback.  
It’s very hard to develop without testing purpose…

Please try this new test version :

> **[MOES | Homey](https://homey.app/en-us/app/net.franceweb.moes/MOES/test/)**
>
> Unlock full potential of your MOES Zigbee devices

Regards,  
SoPhos

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [July 29, 2026, 12:17pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/28 "2026-07-29T12:17:33Z")

</div>

Thanks for your quick follow-up. I tried the new version: the switch does get paired (no error) but the capability values remain empty and the flowcard do no trigger when I press a button.

To be sure that it is related to this switch I paired another of the 2-gang model, which worked instantly.

Is there any other information I can provide you with?

---

<div class="post-metadata">

**Author:** ![SergeP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sergep/32/81216_2.png) [@SergeP](https://community.homey.app/u/SergeP)\
**Post date:** [July 29, 2026, 12:19pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/29 "2026-07-29T12:19:05Z")

</div>

Yes, can you send me a log report, please ?

Regards,  
SoPhos

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [July 29, 2026, 12:22pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/30 "2026-07-29T12:22:54Z")

</div>

Yes, sure: 72c69d56-0778-43aa-bbb4-7772a7726734

I created the log after trying to pair the 1-gang switch.

---

<div class="post-metadata">

**Author:** ![SergeP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sergep/32/81216_2.png) [@SergeP](https://community.homey.app/u/SergeP)\
**Post date:** [July 29, 2026, 12:29pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/31 "2026-07-29T12:29:58Z")

</div>

Thank you. Did it pair correctly ?  
Because there is nothing in logs for the Moes 1-Gang,  
Driver for 1 gang starts normaly but there are only 2 and 4 gangs devices.

SoPhos

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [July 29, 2026, 12:33pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/32 "2026-07-29T12:33:29Z")

</div>

The pairing process completes and Homey shows that the device has been added, but it shows no capability values. So I assume pairing may not have fully succeeded, though I did not get any errors.

 ![IMG_2852.PNG](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/0/80b03a4697c7347c800f0405bff37a9f8b044385.jpeg)  
 ![IMG_2853.PNG](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/4/d45d5999f863e623c910bbe52277240f9a0ca0e3.jpeg)

I have only one of these 1-gang devices, so I cannot test with another. I have multiple 2-gang and one 4-gang devices and they pair without issues.

---

<div class="post-metadata">

**Author:** ![SergeP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sergep/32/81216_2.png) [@SergeP](https://community.homey.app/u/SergeP)\
**Post date:** [July 29, 2026, 12:35pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/33 "2026-07-29T12:35:59Z")

</div>

Very strange…  
Please remove it, restart MOES app and pair again your switch.  
Then, send 2 or 3 clics and only after, send me a log report.  
Maybe I’ll get somthing…

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [July 29, 2026, 12:39pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/34 "2026-07-29T12:39:38Z")

</div>

Here you go: 4fa0986b-63c5-4889-9932-78e4e4ef898f

---

<div class="post-metadata">

**Author:** ![SergeP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sergep/32/81216_2.png) [@SergeP](https://community.homey.app/u/SergeP)\
**Post date:** [July 29, 2026, 1:59pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/35 "2026-07-29T13:59:31Z")

</div>

I got it but there is no more trace of your 1 gang button in this log.  
Can you control in **Homey mobile app** that the devices really belongs to MOES App ?

Regards,  
SoPhos

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [July 29, 2026, 2:37pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/36 "2026-07-29T14:37:03Z")

</div>

> [@SergeP](#):
>
> Can you control in **Homey mobile app** that the devices really belongs to MOES App ?

Yes, the device is linked to the MOES app:

- It’s listed in the MOES app’s device overview and the MOES app is mentioned in the device tile as linked app (using the Wall Switch Scene 1 Gang-driver):  

- It part of the MOES app section when selecting flowcards  

- It has the flowcards that I would expect for the 1-gang device. The ‘Button was ’ card does nog contain a button menu, only the action menu. I assume as the device only contains one button. So that makes sense.  

Does it help if I share an interview of the working 2-gang device?

---

<div class="post-metadata">

**Author:** ![SergeP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sergep/32/81216_2.png) [@SergeP](https://community.homey.app/u/SergeP)\
**Post date:** [July 29, 2026, 2:42pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/37 "2026-07-29T14:42:41Z")

</div>

> [@SunBeech](#):
>
> Does it help if I share an interview of the working 2-gang device?

No, no need…  
You’ll just have to be patient for this one, I’ve just bought one just for integration…

Regards,  
SoPhos

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [July 29, 2026, 2:59pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/38 "2026-07-29T14:59:36Z")

</div>

No problem and thank you 👍.

Not sure whether relevant: I am able to pair the device with Johan Benz’s [Tuya Zigbee](https://homey.app/a/com.tuya.zigbee/) app, though that only supports the single and double click action. Not the long press and also does not show the battery level (or any of the other stats you added). I think this device is sold under different labels.

---

<div class="post-metadata">

**Author:** ![SergeP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sergep/32/81216_2.png) [@SergeP](https://community.homey.app/u/SergeP)\
**Post date:** [July 29, 2026, 3:03pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/39 "2026-07-29T15:03:59Z")

</div>

Let’s make a final test today with new test version of MOES App (1.4.3) :

> **[MOES | Homey](https://homey.app/en-us/app/net.franceweb.moes/MOES/test/)**
>
> Unlock full potential of your MOES Zigbee devices

Thank you,  
SoPhos

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [July 29, 2026, 3:08pm UTC](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967/40 "2026-07-29T15:08:30Z")

</div>

Unfortunately no luck. Same result.  
I did sent you a new log: 090fb325-8fcc-4620-80e8-a1a08eccf27b

[Previous page](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967.md?page=1)

[Next page](https://community.homey.app/t/app-pro-moes-unlock-full-potential-of-your-moes-zigbee-devices/156967.md?page=3)