I have now waited 18 days without any response. My problem is that the app I created works normally on Homey PRO early 2023, but not on Homey PRO early 2019. One of the errors is that when custom pairing via html page (as described by Homey) you get a message that Homey cannot open the file on Homey PRO early 2019, while it works fine on Homey PRO 2023. The strange thing is that the error only occurs on 4 out of 5 devices in the app, the last one is OK. Has anyone experienced anything similar?
Pls share your repo and clarify what driver works and other developers try to spot the issue.
The source is open on GitHub, it can be found here: GitHub - boeyum/WizLan. The app uses custom pairing where you register the device’s IP address and name. When the app is installed on a Homey PRO early 2023, everything works normal, but if you install the app on a Homey PRO early 2019, you only get the registration screen on 4 of 5 device types. On the other devices, you only get a message about “unknown error opening file”. There is no difference between installing from development or the current version from the official Homey app store.
Hi Jan,
I would say you are missing the whole “/.homeycompose” directory…
Unfortunately, it disappears when you do an automatic download to GitHub. The directory is there on my development platform, however. The only thing in “.homeycompose” is special capabilities, and these are on GitHub in app.json.
Sorry to say, but I guess assisting Development of Community developers isn’t exactly the questions that have the priority for the normal Support channel.
And maybe they should have told you that…
Support is busy (and maybe temporary understaffed due to circumstances) providing user that bought a Homey Pro or a Bridge and with issues supporting their own Apps and stabndard functionality for consumers.
Homey 201x and 2023 have many differences as 2023 is build on other hardware from scratch (and adopted to the Could Platform)
I guess the Socket is working fine? and the others have an issue on the Homey Sphere / 201x platform?
But I guess that’s off-topic as this Topic only about:
Does anyone know how long it normally takes to get a response from Homey support?
Hi, thanks for the answer. I have received a response from Homey support. They cannot help with developer questions, and refer to the Homey community. I am fully aware that there is a difference in hardware between the different versions of Homey, but since they do not differentiate between versions in the Homey store, the software (let’s call it the operating system) should be backwards compatible. At least that was the first thing I learned when I started in the computer industry around 1982. When it comes to my problem, I have tried to dig further. It seems that Homey cannot find, or cannot open the pair html file or something in it. I have tried to remove the icon that is in the file, but this did not help. I also see that it is the simplest device that works, and all those that have more than one on/off function do not work (even the socket where you can read consumption does not work). It therefore seems that there is something around the complexity and definition of this that is wrong, but I am unsure.
Where you building the App with .homeycompose ?
Pls fix the Repo as not everything necessary in your local repo is on git. (as @ChrisG mentioned)
Are you asking me to guess what the simplest device is? (I already did a Guess but that was probably nog good?)
which one is working ?
btw, even AI 
can create better Topic titles,
please choose what you think best fits:
Sorry that I wrote it in a way that could be misunderstood. I just tried to explain the error a little better. You are absolutely right, it is the “socket” that can only be turned on/off that works, and as I said, the error is present on all those that have “multiple functions”. The strange thing is that it seems that Homey cannot find the html file for pairing. I will update the GitHub repository (unfortunately I won’t have time today) with .homeycompose.
And they didn’t have spaces in 8.3 notation in that time…
Try if you remove them from the driver ID if that fixes it.
Not sure if that was accepted by # homey app driver create but I also don’t expect Athom to fix that in fw if Homey 201x …
And 2023 is backwards compatible with all apps updated to SDK3 that run on the 201x, guess you are now asking the other way around 
The spaces that are there today were not there the first time I submitted the app for the homey store. The app was rejected, among other things, because I had used underscore characters, and was told that this had to be replaced with space. I’ll try to test a bit around this.
The app was initially developed for my new Homey Pro 2023, and works great on it. However, I have been contacted by users with 2019 who say that the described error occurs on these. I use SDK3 in developement, and parameters in app.json are: “Compatibility”: “> = 5.0.0” and “SDK”: 3. When I test on my “old” 2019 I can see that the error is there.
I have tested on my 2019 and it seems that the driver init went fine. I have stripped the pair html file of everything related files in /locales and icons etc… I have also added logging in the return from the html file. However, it seems that it is the actual html file for pairing that Homey 2019 cannot find.
I found the problem by building a “shadow app” from the bottom. It turns out that Homey Pro 2023 accepts spaces in the name of driver directory. However, this does not accepted by Homey Pro 2019. So when directory names were changed, the app worked in 2019.
1 Like
