Does anyone know if @johan_bendz is willing to transfer? I won’t have that much time to maintain all new feature requests. But I will be able to maintain merge requests from other developers and maintain the app that way. I see the current code hasn’t been updated for a while. I have made a version now (for myself) with all open merge requests, but if I read a bit the topic here, it might be that more people might benefit from a little bit updated app.
@Doekse do you know the current state? (maybe we can continue through PM).
You are ofcourse always free to reach out to @johan_bendz about the subject, but I can also connect you via email. Feel free to reach out to partners@athom.com
That would be great!! 90% of the lights I own are Hue, and I understand that @Doekse needs to keep Phillips/Signify happy, but as others have already pointed out, this app is used by many people. The value of this app became clear to me again recently when my router stopped working. No Wi-Fi means no Hue with a bridge. Meanwhile, my Homey just kept running with the lights that are linked to the Hue Without Bridge app.
It also naturally provides a much better Zigbee network on homey, and I agree with what Dirk said: Of the nearly 50 lights I have, the price of a Bridge is a drop in the bucket for Signifiy. Hue could lose many Homey users because of this. In any case, I’ll be looking for an alternative that works directly with Homey if this app really isn’t supported anymore. I’m afraid I’m not the only one.
Do you maybe know when the deadline will expire? To be honest I’m very hesitant to buy anything from Philips Hue due to the status of the app. I’m happy to hear though that there are people like you who are willing to maintain it once you have the ownership.
i have added two philips hue lamps to my homey 2019. They got in the devices list as uniform zigbee lights.
Why can’t i adapt the name and the parameters of the devices? The name is wrong and it is an overig and not a lamp…, but when i try to change it homey says “parameter_not_updatable”
Hmm, should have checked this topic before buying some new Philips Hue stuff . My older wall modules with battery work very well. Now bought some new wired wall modules and a Tap Dial switch but now confronted with the same issues as I read here and in other topics. Only able to connect as “generic zigbee device” or got the message “this device already exists”… hmm too bad.
@MrDutchfighter if you would indeed take over, what do you mean with “But I will be able to maintain merge requests from other developers and maintain the app that way.”? I’m not very familiair with the github way of working of branches, merges, etc., so it’s kind off abracadabra for me.
Would there be a chance that my wall modules and tap dial switch could be added because they are already in the app and this would only require a minimal effort, if we/I would deliver the info required from an interview? Or is that what you call “a new feature request” which you indicate you’re not sure you will have time for?
Curious to hear what your plan would be and what we could expect. Kudo’s anyway that you’re willing to help the community out.
For the short term I’m considering to buy a 2nd hand Hue bridge just to be able to play with my new devices. But it would be a shame, Homey should be The One Ring to rule them all…
With some help of Claude and a lot of testing, I managed to create a driver (ROM002) for the wired wall module with two inputs and created a pull request on the GitHub of Johan Bendz.
It works perfect, now hope someone can integrate the open pull requests into a new version of the app.
I’m currently trying to move back to homey without a hue bridge and/or zigbee2mqtt. I want to stop using external hardware dependencies for my home. I’ve already copied to repo to do some editing myself because the original is practically abandonware now.
Yes, checked again. Should hear something this week, but somehow it is quite difficult (think some internal politics, but that is just guessing). I have my own branch running as well… you can do a MR to it with your changes, then I will merge and can directly publish if they hand it over.
I now have running Homey self hosted server on my Proxmox cluster to try the Homey platform. I have bought a bride to let Homey communicate with my smart stuff. I use the official Homey Hue app and I still have my Hue bridge in use. To be honest I don’t want to use the Hue bridge so then I have to use the community app if I understood correctly. Also it is advised to only use the Hue Homey community app in combination with the Homey Pro. What about updates? What are your experiences by using it this way?
If you already use the Hue bridge, I’d recommend to stay on the Hue bridge. It is so much faster than the Homey app to quickly control a light, way easier to set up Dimmer Switches with your Hue lights and of course updates can be run.
. My older wall modules with battery work very well. Now bought some new wired wall modules and a Tap Dial switch but now confronted with the same issues as I read here and in other topics. Only able to connect as “generic zigbee device” or got the message “this device already exists”… hmm too bad.
