When I add either 192.168.68.1 or http://tplinkdeco.net/ and the password, it seems to work, I get to the “New units found” screen, but no units are showing up in the list.
Sorry to hear.I have a small program that can be executed on Windows and macOS. you can download it from my github; go-deco/bin at main · mathiastornblom/go-deco · GitHub
I downloaded it to my other mac computer in the download folder and open terminal;
mathiast@Mathiass-MacBook-Pro ~ % cd ~/Downloads
mathiast@Mathiass-MacBook-Pro Downloads % ./decotest --host “192.168.68.1” --password “MySecurePassword”
See if this throws you a output. You can DM me the output
Getting
zsh: permission denied: ./decotest
You might need to follow this if you have high privacy settings to allow the execution from a unknown developer; Open a Mac app from an unknown developer - Apple Support
Is it to be possible to create a trigger card, which comes on every device that comes online/offline. And have the labels attached to it that are now attached to the trigger card from client_state_changed? Without choosing from the list of devices.
I tried so many times but i still getting an error when trying to login in Homey.
Wrong login information it says.
But i can still login at the Deco app and browser… 
I got Deco M4R
Sorry to hear. As you can login via the web browser to the router and if you use that IP or tplinkdeco.net with the same password as the host and password it should work. Have you segmented you network?
If you read above in this channel you can download a small test program from my github. Does this work?
after day 18h from restart, can see that load (assuming polling) around every 1min, so assuming this keeps getting more often resulting “interesting profiling” …
As said not an issue big for me, but better (stay) safe than sorry…
What I’ve done now is downloaded the source code from github. And in the file driver.settings.compose.json, the IP address changed to 192.168.1.1
Then via CLI I installed it on my homey. Now I just get all the data. Can’t add my deco’s 2 and 3 yet because that gives problems.
So I found out that it doesn’t automatically take over the IP address of the Deco, but automatically grabs the IP address that is in the file.
Hopefully you can do something with this information?
So here, in the driver.ts when you create/add your devices to the Homey, the hostname is set to the fetched device(s);
const devices = deviceList.result.device_list.map((device) => ({
name:
device.device_model +
’ - ’ +
this.cleanString(this.decodeBase64(device.nickname)),
data: {
id: device.mac,
},
settings: {
name:
device.device_model +
’ - ’ +
this.cleanString(this.decodeBase64(device.nickname)),
mac: device.mac,
hostname: device.device_ip,
password: password,
model: device.device_model,
ip: device.device_ip,
role: device.role,
hardware_ver: device.hardware_ver,
software_ver: device.software_ver,
hw_id: device.hw_id,
timeoutSeconds: 10,
},
}));
in the device.ts (one instance per device)
if (changedKeys.includes(‘hostname’) || changedKeys.includes(‘password’)) {
try {
this.api = new decoapiwrapper(newSettings.hostname);
this.connected = await this.api.authenticate(newSettings.password);
this.log(‘API reinitialized with updated settings’);
} catch (error) {
this.error(‘Failed to reinitialize API’, error);
}
}
this code create a new instance with the new credentials if you change them in the device advanced setting.
So if you delete the device it and re-add it it fails?
When I do indeed remove it and add it again, I see the following:
The best thing would be if I could change the ip address there
I changed it to be a text box instead of a label. You can install this version: TP-Link Deco | Homey
Still, something is wrong with the driver’s init() when you add the devices, as it should give you the device’s IP.
Thank you so much for taking a look and making an adjustment.
I have installed your version. I can now indeed change the ip address there and that works.
I was even able to connect the deco’s 2 and 3, but unfortunately the data is not correct. Download and upload remain at 0 and the client count of Deco 2 and 3 are the same and the clients that are displayed are not associated with these decos.
After 10 min, the master also starts acting strange, see printscreen:
I have now restarted the app and that helps for now, Only data Deco’s 2 and 3 are not correct yet.
Perhaps this also has to do with the driver init?
If it happens again, I’ll remove deco 2 and 3
Changed also to test-verion
1st 
good news (did not check in between):
- both X20 (slave) and X50-4G (master) reboot working (at least on UI)
wish list:
- X50-4G still thinks WAN down, while X20 (slave) OK:
- restart flow card for X50-4G still not working (if you fix only this, would be very happy )
— add ----
One more to wish-list (if even possible, as I have other locations with DECOs (100+s of km with own IPs), e.g. periodical reboot by remote-Homey (not yet build in in TP-Link router…
- would be great to connect all devices seen on same account in TP-link App (e.g. via free DDNS xxx.tplinkdns.com)
I have found the missing code, my bad. I Will let you know when i have tested it. Out on Travel rest of today.
After that reboot I didn’t have any more problems ;). So Deco 2 and 3 haven’t been removed yet. Only the data is not yet correct, as indicated earlier.
I’m now trying to make a trigger card so that it always triggers when a client comes online/offline and can use the labels with logic cards. But unfortunately, that doesn’t work yet
Sorry, believe it or not but i don’t have a computer 
I have not done anything what i know about with my network
I can login with the password thru the link, ip and deco app… just not thru Homey
Something keeps taking more and more CPU-time, not more often as I assumed before), visible in last hour (10% takes bigger share…):
Såhär blir det, riktigt frustrerande!
Går som sagt att logga in på tplinkdeco.net samt appen och genom ip i browsern men fungerar ej genom Homey…! 
When I re-installed my DECOs to test-version (to be on safe side even if might not have been done), I used master IP as default did not work for me… psw had no issue…
