Open KC-inDomus opened 1 year ago
Hey there @milanmeu, mind taking a look at this issue as it has been labeled with an integration (nanoleaf
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
nanoleaf documentation nanoleaf source (message by IssueLinks)
Plus 1 for this one!
Yes please added 4D in the list of effects
I've got the same issue. Please let me know if there's any info or diagnostics you need on this one. Happy to test whatever you need too :)
Please add this feature is a must have in automating between modes with home assistant
+1
It's the only feature missing for me.
+1 here too. I have one and this is the only option missing at the moment.
+1 on this. The only reason I haven't bought one yet is because I found this issue.
Would be really great if someone could look into this. The maintainer @milanmeu appears to be inactive.
For years, Nanoleaf ignored my questions about missing and incorrect information in their API docs, making it impossible for me to further develop the integration for the new devices. Their last major documentation update was from 2019. A lot of people, have been complaining, but they kept ignoring, our questions. Because of this GitHub issue, I just took a look at their documentation and to my surprise they released a new version a few days ago, almost five years after the previous one. I immediately see that there are still errors and missing information that I have been asking for to be resolved for more than two years. Someone from Nanoleaf responded to one of my posts about a month ago with the message that they would like to help with my questions. However due to my personal life, which has become busier since 2021, I have not yet had time to take this opportunity. If the problems I'm still having with the currently supported devices can be resolved, I then may look into supporting the new devices as well. But this all depends on Nanoleaf being able to earn my trust back. For now, I would advise against purchasing another Nanoleaf product. Unless there is someone else who wants to further develop and support this integration, you will unfortunately have to wait a while until I have time to look into these new devices.
I found this forum post in which someone figured out how to control the 4D modes. However, this isn't the official way as described in section 5.9 of the official documentation. I tried that way and couldn't get it to work as I'm assuming that it is probably wrong or maybe isn't implemented yet. I have time this week so I may see if I can work on it in but I don't have too much experience so if anyone else knows more of what they're doing and needs these features too these are some good resources!
Quick update: this integration uses aionanoleaf which I've forked and I am starting to add support for Nanoleaf 4D. Only issue right now is that you can't subscribe to events that report which emersion mode it is in, only that an emersion mode is active. To figure out which mode the only way I've found is to call getScreenMirrorMode as described in the api documentation. I'll be looking into this more today if I can!
I have a working proof of concept right now! I wouldn't say that it is ready for prime time as I threw it together rather quickly and it could for sure have been written better. This is mainly due to how the 4d modes were implemented quite lazily by nanoleaf into their api. Right now when I try testing it as a custom component it will not load due to an import error in the config_flow.py which is strange but it works fine in my dev enviroment as a built in component. But it's getting there!
Ok I just pushed the updated version to my core repo so I still wouldn't recommend using it but it does work for the most part! If anyone wants to look at my core repository and my aionanoleaf repository and has any suggestions or changes you are more than welcome to! I know that the code could be improved and probably wouldn't get merged immediately since its a bit hacky
I created a custom integration in case people want to use it now! You can find it here. It is just a drop in replacement for the default integration. Can be added to hacs or installed manually. It doesn't support the rhythm screen mirroring yet as I don't really use it but I may add it eventually. If anyone encounters any problems just open an issue
Thank you, I'll test it when I'm back next week!
will test it very soon!
tested. 1D-2D-3D-4D effects are on the effects list. not working: effect selection and activation (the new ones as the standard ones).
So when you select 1D-4D nothing happens? Does anything in Nanoleaf the app change at all? I'm not at my apartment this week so it is a bit hard for me to test but I may be trying to activate it incorrectly
yes, nothing changes both ways
Any errors in the HA logs?
It looks like its working for me but then again I can only tell from my camera and the api responses. If I set the colour to red and then select a 4D mode it changes to white so it's changing something for me and when I query the active effect it returns that it is in a 4D mode. Do basic controls and other effects work? Check the HA logs and see if the integration or the python library is spitting out any errors.
Also lets move discussion about that issue to the custom integration repository. I created an issue here.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
This still isn't integrated :)
To all nanoleaf 4D users. How did you pair with HA? I tried holding each of the 4D Controller buttons for 20seconds to get the token, but no dice. I am lost.
To all nanoleaf 4D users. How did you pair with HA? I tried holding each of the 4D Controller buttons for 20seconds to get the token, but no dice. I am lost.
Did you start the config from the ui and put the 4D's IP address in? Or did home assistant discover it? Like how far did you get in the config process? Does home assistant give any errors in the logs at all?
Did you start the config from the ui and put the 4D's IP address in? Or did home assistant discover it? Like how far did you get in the config process? Does home assistant give any errors in the logs at all?
HA Discovered it, if I click next it tells me to hold the "button" for 10 seconds and then press next.
HA Discovered it, if I click next it tells me to hold the "button" for 10 seconds and then press next.
Oohhh ok you have to hold the power button and the lights on the control back should bounce left to right? And then click next and that should complete the set up
oh thats weird i've never seen that before. Looking at issue #87690 have you ever added it to home assistant before? or is this your first time trying to configure it? Is there an existing a nanoleaf config entry at all for any other devices possibly?
if you haven't already, you might want to restart home assistant and/or the nanoleaf 4D and see if that helps at all? Sometimes nanoleaf devices are very finnicky with their connection and a restart can help
HA Discovered it, if I click next it tells me to hold the "button" for 10 seconds and then press next.
Oohhh ok you have to hold the power button and the lights on the control back should bounce left to right? And then click next and that should complete the set up
That worked! I have the controller where its hard to see. I thought that the LED lights would flash, so I didn't clue in that it was the lights on the controller. thanks!
Hi @joostlek, by chance, had the opportunity to read this thread? As you can see, @jonathanrobichaud4 succeeded on integrating Nanoleaf 4D special programs using Nanoleaf APIs (see here); could be great merging those functionality on the official Nanoleaf integration, do you think this is possible?
I'll have to see what I can do. I'm currently away for a week, but I do have some spare time, but I'll have to see when I'm back at nanoleaf things
I'll have to see what I can do. I'm currently away for a week, but I do have some spare time, but I'll have to see when I'm back at nanoleaf things
great. have a good free time. when and if you'll try to develop, on this thread you'll find several guys with 4D available at home to test whatever you need. thanks!
+1
Hi guys, can anyone do something about this? @joostlek, can't @jonathanrobichaud4 bump his working code on the official Nanoleaf integration? It's really a pity having such a brilliant light solution and being unable to fully integrate to HA...
Oh right, I am back from my holiday as you've probably guessed. @jonathanrobichaud4, you can send me a message on discord and we can check how we can integrate this into HA
Hey guys, do you have some news?
Thanks ❤️
The problem
New "Nanoleaf 4D" solution presents the usual configuration (simple color or moving effects) but adds a new mode, called "4D", with 5 different modality (1D, 2D, 3D, 4D, Rythm). This new mode is about mirroring a tv screen, which is the main feature of this new product.
Home Assistant integrations usually shows, on "effect" attribute, the mode currently in use; it works even with "Nanoleaf 4D" (while using simple color or moving effects), but when you set "4D" mode in one of the 5 possible modality, Home Assistant entity's effect attribute disapper, so you don't have any clue of the current mode in use (and you cannot set it by services, too).
What version of Home Assistant Core has the issue?
core-2024.7
What was the last working version of Home Assistant Core?
no one
What type of installation are you running?
Home Assistant Core
Integration causing the issue
Nanoleaf
Link to integration documentation on our website
https://www.home-assistant.io/integrations/nanoleaf/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response