Expounding upon @rohan’s comment, since the published specs thus far indicate a wired load capability is a dimmer, it IS like the Blue dimmer, which cannot have a WIRED fan load. However, the published specs thus far indicate that it has a binding capability, so you should have the same binding ability to bind to the fan canopy as the Blue dimmer does.
Just like with the when the Blue dimmer is wired with no load and bound to the canopy, I expect the same here. Both the Controller and the Canopy are to be powered via a hot and neutral. So a bypass would not come into play here for either.
Just wanted to provide a quick update for you all. The manufacturer is still working on tweaking the light leakage as our B2B partner is still pushing back. Here are the latest pictures on what this leakage looks like:
TBH, I think that light leakage is extremely acceptable. I get that pictures online or viewing monitor resolution can differ but there comes a point in time where realistic tolerances must be established. Again, it’s my opinion only.
The issue is with satisfying the B2B partner’s standards, not if we think it’s good enough. Plus Inovelli doesn’t really do “good enough”. I am willing to wait for it to be great
Very true, but I have dealt with partners/vendors in my line of work too. And, letting them say it’s “not good enough” without defining what that means in a measurable manner can be unproductive, especially if you’re dealing with multiple departments from the same partner. They may be paying the bills, but it doesn’t mean it’s a ticket to an endless cycle of guessing what is “good enough”, unless of course they hire you as a consultant on an on-going basis (I’ve worked as that too)
No further updates at this time. We are still waiting on approval from our B2B partner before we can proceed further with this project. We have made some more tweaks to the light leakage, and it is looking much better. Just waiting to hear back now.
Thank you for your patience, we hope to have more news shortly!
This response makes me wonder if most of the confusion in these chats revolves around the definition of an “update”. The message you just sent is exactly the sort of update I’d have hoped for. A quick message saying that you’ve made a couple revisions and are waiting for the B2B partner to respond.
Based on your comment of “No further updates at this time”, you likely do not consider what you just said to be an update. I think I can speak for most of us by saying that is an update and that is exactly what we wanted to hear
A quick update on a Friday afternoon, like this, would be wonderful!
“Quick update: we spent most of this week going back and forth with our B2B partner. Nothing to show for it yet, but we’ll share photos when we get a final version”
I’ve been excitedly awaiting for updates on the zwave version, didn’t realize the discussion was over here. Looking great so far, quality products take time and effort, keep up the good work!
I would assume the same tooling being discussed in the zwave thread is also aplicable to this model, if That is the case that would mean That The testing Was Done on November 30, and we are expecting an update on if the tooling was successful, and if that is the case that would be one step forward.
(I’ve worked as that too)