Zigbee Button Controller + Dimmer Switch | Project Walt

Crap, I posted this prior to responding to everything – hang on, I’m still typing responses to all!

I go on vacation and this thread turns into a sword fight! Sorry, I should’ve jumped in sooner, but glad to see all the ideas flowing. Let’s remember that everyone is here for the same reason which is to create a great switch :slight_smile:

Yeah I don’t see why this would be a problem.

Yeah good point – I’m still evaluating how difficult this will be and how much time it would consume. LOL what are you guys putting on your switches?!

That’s a great idea!

An interesting thought – I think we’re pretty locked in on the switch having a relay because it’s what we pitched to the B2B company and they made it a requirement. I know they paid for the Z-Wave version and this is the Zigbee version, but it helps us on costs to share tooling.

But, if we end up going down the non-relay path, I’ll keep this in mind. I’ve always liked those switches that have Alexa built into them. This seems like a similar concept with a little more control.

It’s a great idea, but I think @kreene1987 is right in that this should be a hub level automation as most, if not all at this point, have the ability to set automations based on the time of day. The LED Bar will have the ability to adjust brightness levels, so you would set up the automation based on the time of day to change the brightness level.

But, as you mentioned, this is an exchange of ideas and to respect that, I’d like to understand from your point of view why this would be a switch level automation and what the benefits would be?

I can see some benefits in that it’s local and if the hub goes down your switches LED would still change based on the time, but that’s a rare occasion and also the switch would need to be connected to a hub of some sort to account for the change in sunrise and sunset times. The only way I see this being feasible is if it is a strict time of day change.

But maybe I’m missing something and I’d like to hear your thoughts!

Sorry if it’s coming off that way – as someone who is just looking at this thread for the first time since I left for vacation, I read their comments as being more inquisitive, not mocking.

Knowing both of them personally, I don’t think that was their intent either, but I’ll speak for myself in that my response was inquisitive.

Either way, if it is something that’s not too hard to do, and people will see benefit from it, I don’t see why we couldn’t add it to the switch. Heck, we have a parameter that inverts the switch that I think is silly, but someone requested it!

Yes, I’m sure this can be done – let me talk with @EricM_Inovelli our CTO to see the feasibility of it as I’m not sure what all Zigbee can handle or if there’s a way to capture time of day.

EDIT: I see you mentioned there is a UTC time cluster so it may be possible then – @EricM_Inovelli – thoughts?

I agree – I think there’s room for each of these in the portfolio. Based on the success of this initial switch, we can certainly entertain some of the other ones! In fact, there is a vendor who has been asking us to sell their remote version which I think there’s a huge benefit and we’ve tried to get one ourselves for a while, so it would be a great opportunity to grab one without all the associated costs.

Just to give a background on costs as I’m sure there will be a lot of people that read this… it costs about $80-100k to launch a new product (not including the minimum order quantity of products). I realize that there will be some cost savings if we share tooling as well as dev costs, but we’ll still have to incur UL/ETL, FCC/IC, Zigbee fees which are probably in the ballpark of $30-50k altogether. Add that cost to the minimum order quantity that we’d have to order and we’re probably in the $100k range, which is hard for a smaller company.

EDIT: I see you and @rohan talked more about these challenges and I agree, this is good discussion for future strategy and I see your points for each SKU and agree with them!

I think you’re onto something with the three versions – now we just need to convince the masses. I believe we have a strong case for Option #1 and Option #3. Option #2 makes sense if the costs are significantly less per unit. I’ll have to take a look, but my gut tells me that it would be maybe $2-3 less expensive, which at the end of the day would be maybe a $5 reduction in MSRP.

Can I get you to explain this to the Hue team? I’ve tried so many times and they just don’t seem to get it, hence one of the reasons why they don’t see a benefit of becoming Friends of Hue. It frustrates me to no end.

Same at my house – completely agree.

Just wanted to comment on this to say thanks – we do need fresh ideas and I appreciate it!

@PPounce – this is a good point that I forgot to mention in my response. This switches firmware is going to be massive. The largest we’ve ever done because there are so many variables with all the different button combinations, multiple binding options, etc.

I think it’s a fair challenge by @mamber – at the same time as I mentioned above, if we can fit it in, we certainly can. But from my POV as the marketing guy, I need to prioritize what I think is the best features and if we have to pick and choose, I like to hear the arguments for certain features.

Now this will have more memory than our current 2-1 switch and our current 2-1 switch hasn’t maxed out memory, but this is something we ran into an issue with on our Gen 2 Z-Wave switches so I think that’s why you’re seeing some pushback. Again, IMO it’s coming from a positive place and no malice is intended.

I’ll bite here – and @PPounce, @caduck, and anyone else who is looking for a non-relay hardwired version, I’d like to hear your POV too since this was also a suggestion from you guys for removing the relay.

Are you guys just tying the line/load together behind the switch or would you be extending your gang-box from a one-gang to two-gang and keeping the load bearing switch there?

I just can’t think of any situations in my house where there’s a switch that doesn’t have a load connected to it and I’d have to extend the gang-box or tie the line/load together for a non-relay device to work.

I do see the need for a battery powered device and I 100% want to bring that to life, but I must be missing something on the benefit of a hardwired, non-load bearing device other than you wouldn’t have to change batteries with the downside being you have to cut a larger hole in your wall or tie your line/load together behind the switch (which I have never really liked).

Thoughts?

Now this is interesting - so some sort of Qi charger or something?

There are also some devices that do not require a battery and use kinetic energy to send signals to the hub: https://runlesswire.com/

We’ve been talking with them, but the problem is they don’t work with SmartThings, Hubitat or Home Assistant as none of those hubs, to my knowledge, support Zigbee Green Power and the other protocols will not work as the energy produced by clicking isn’t enough to transmit the signals.

Lol, you make it sound so enticing! You mean I could get out of the frozen tundra of Michigan in the winter? Sold.

Yeah, all jokes aside, that’s what my vision is for the company. Now that I’m seeing the light a bit more (pun intended) with logistics, lead times, and inventory being in stock, we have a bit more money to play with to come out with new projects again, which is exciting.

I’m thinking through the same lens as you are – trying to fill the voids so that a sales team or distributors/installers who want to outfit a house can choose us because there’s no gaps.

Yes, this is my next switch after the 5-Button and mmWave. I think this is the last piece of the puzzle. Also, selfishly, I’d like this for my house because it’s all I have left to automate.

I got you: Zigbee Fan Canopy Module | Project Cheryl (named after my mom so it can be a companion to Project Walt, my dad). Just kicked it off with the manufacturer yesterday.

You will be able to use it with this switch or one of our other switches via bindings.

Perfect, you are in the right thread!

You got it :slight_smile:

Definitely want this – we have a white-label option that we’re looking into that I think will work. I’m just not sure how much tweaking we can do to the firmware which is what I’m worried about.

Understood and I may open it up once we are further down the path of development, but thanks for having our back!

1 Like