Typically, inverters and power supplies are only visible on the Wi-Fi network while they are generating energy. At night, they don’t even respond to pings.
Great to see this is happening now!! I tried to install my DTU-Pro-S, but I only get “Homey object has no attribute” error message. I’ve tried to scan the network, as well as inputting the IP address and the Serial Number, but still the same.
What was wrong: The app was calling the Node.js translation function (homey.__()) in Python code, which crashes instead of showing the proper error message. This masked a second issue: your DTU-Pro-S likely requires an encrypted connection (common on newer firmware), and the error about that never reached you.
I’ve published a test build that fixes both. Could you try it here: https://homey.app/en-br/app/gpm.hoymiles.solarpanel/Hoymiles-Wi-Fi-Solar-Panel/test/
I deleted the old version of the app, then installed your updated version. First I tried to find the DTU by scanning the network, but no success. Then tried to add it by the IP address. Then it only says that it is not able to reach it on the IP address (see screenshot). I have double-confirmed the IP address (which is also set as static address).
BTW: The DTU is connected to my Mesh router through cabled ethernet. Would it be better if I only connected it through wifi instead?
Hi Espen,
Thanks for the screenshot — the error message is now displaying correctly, which is good.
The IP 192.168.68.x looks like a TP-Link Deco network. A couple of things to check:
1. Is Homey on the same subnet?
Go to Homey → Settings → General → and check your Homey’s IP address. If it starts with 192.168.68.x as well, you’re on the same network. If it’s a different range (e.g. 192.168.1.x), that’s the problem — Homey and the DTU can’t see each other.
2. Run a quick port check (from any PC on the same network):
nmap -Pn -p 10081 192.168.68.101
If it shows closed, the DTU firmware may not support the protocol this app uses (some firmware versions use Modbus on port 502 instead). If it shows open, it’s a network routing issue.
Wired vs Wi-Fi: switching the DTU to Wi-Fi may help if the mesh router is isolating wired and wireless clients — but only if both end up on the same 192.168.68.x subnet.
Yes, the Mesh network is based on TP Link Deco M4 units. Confirmed that the DTU and Homey is on the same subnet.
I did the nmap, and the results is 10081/tcp closed famdc 
The hardware version of the DTU is H09.06.01, and firmware is V00.02.13.
So does this mean I will not be able to integrate it to my Homey?
Hi Espen,
Thanks for running the nmap scan — that’s very helpful.
Port 10081 closed on your DTU-Pro is likely because it’s connected via Ethernet. There are strong indications that port 10081 is only available on the Wi-Fi interface, while Modbus TCP (port 502) is Ethernet-only.
Could you temporarily connect your DTU-Pro via Wi-Fi and run the scan again?
nmap -Pn -p 10081 <dtu-wifi-ip>
If port 10081 shows as open, switching to Wi-Fi permanently would solve the issue.
