Hi Florian_Truck,
Thank you very much, I’ll take a look on it and will grab parts of code to integer in Nous App.
If you agree, I won’t forget to mention you in App and Forum.
Regards,
SoPhos
Go for it. 
I am fine with that.
Ah thanks for clarifying; I was not sure 
.
I do understand your rationale though.
Note that:
- I assume the local web app will be updated in one of the next Homey firmware releases (as the gap with the cloud version gets larger);
- The advanced virtual device has a ‘reflect’ option. This means that you only need to indicate once which specific capability of a device you want the virtual device to reflect, and then the virtual device stays in sync. No flows needed.
Anyhow, I know these things remain a matter of personal choice/taste 
.
Hi Florian_Truck,
The best option in your case is to group the 3 devices.
This way, Homey displays only one device. When you open it, you can still access the three devices individually.
It’s a very convenient solution that helps keep your dashboard organized.
Regards,
SoPhos
I was not aware of that! Thanks for the tip! In that case I have no dislike of having three devices.
Hi Florian_Truck,
I tried your code but nothing changes on my side, all 3 plugs goes on and off simultaneously.
As I first picked up parts of code to integer in Nous App, I tried to install and run your full App but the result is still the same !
Did you test it and is it working well ?
Did someone else tried with success ?
Your code seems to be picked up on other sources (because most parts of code are exactly the same I found for Magic Packet), did you grab and adapt it or did you write full code ? (the question is only to try to find where changes could have been made in code).
Regards,
SoPhos
I used ChatGPT to build the app. The magic packet code is an adaption of the herdsman converter from Zigbee2MQTT.
What you need to check is:
- Go to developer console https://tools.developer.homey.app/
- Go to devices section there (Not Zigbee!)
- Find your device there
- See which driver it uses. mine is: homey:app:de.ftedv.nousA11Z:a11z
If there is a different driver than mine this would explain the issue.
The device has to be re-paired with my driver in order to work.
I had the same issue and my solution was to disable the Nous app. Then re-pair the device and then the driver was correct.
Hi Florian_Truck,
No, the point is not here because I use a specific environment for dev as I own a Homey 2023 box reserved for devs.
Btw, I anyway verified in dev console, device section, and my A11Z is really linked with your app.
I took a first look at your code and it can’t work as it is because your don’t even use TUYA_MAGIC_ATTRIBUTE (0xfffe) out of the first init readAttributes (in “configureMagicPacket”).
I don’t understand why this could work for you unless your problem wasn’t the one linked to new firmware on latest devices. But in that case, there is no reason why it wasn’t working with Nous App.
If it works for you, your problem is solved and I’ll take some time to find real solution for the new firmware problem - probably making some reverse engennering.
Regards,
SoPhos
Yes, just read but nothing more with it.
it seems read is the only thing needed. I now see what your problem was.
I added a brand new device with my app and it behaved exactly like you explained. Also all 3 sockets were switching. Then I tried something: I went to dev tools and switched one socket from there and it worked. From that point onwards the socket behaved normal.
I have to correct myself again… (I know this is exhausting). You are right. There must be a lot more to tuya devices than I thought. I apologize for the missleading infos i gave.
Hi all,
I finally managed to debug and fix the Nous Smart Power Strip (A11Z) and the Nous 2-Channel Smart Switch (LZ2).
Both devices are now working as expected in the Homey Nous App.
@Florian_Truck @SunBeech: Thank you for your help.
The issue turned out to be quite simple: I needed to retrieve (only read) all device attributes during the initial setup. This was the case when I first integrated the devices into the app for debugging purposes, but I removed those lines of code a few weeks later while cleaning up the codebase.
A new Nous App version including this fix is now available for testing :
Regards,
Sophos
No problem, I like to help when possible. I tested the new version of your app. Your original A11Z device (3 socket devices after pairing) works well and all is like expected. However I noticed you also added my driver with single device. This one does not work (yet). Suggestion: If possible you can add your init code to the device and rename it to A11Z Single Device and maybe the other driver to “multi device”. This way the user can choose what he likes more. Thanks for your great work!
Hi Florian_Truck,
No, this was just a debugging feature that was accidentally left in the code.
Fortunately, there is no need to create multiple drivers in the Nous App, as Homey already provides several ways for users to organize and manage their devices according to their preferences.
Regards,
SoPhos
There is only one downside of grouping the devices: The power capabilities are not taken over from the first Device. So probably I will have to use Device Capabilities app for that to unify in one device everything together.
Hi all,
A new version of Homey Nou App has just been published in test.
This new version adds compatibility for 3 new Nous devices :
Smart Wireless Switch 4 Gang (Nous C1)
Smart Wireless Button Pusher (Nous C2)
Smart Vibration Sensor (Nous E14)
You can test this new test version on Homey App :
Regards,
SoPhos
Hi Karhadras85,
I’m pleased to announce you the new test version of Homey Nou App adds now compatibility for Smart Wireless Switch 4 Gang (Nous C1)
You can test this new test version on Homey App :
Regards,
SoPhos
