The specs listed on Indiegogo are simply what Inovelli would like them to be. They may or may not be the specs of the chip that will ultimately wind up in the switch.
1 Like
Yeah I totally understand the apprehension. At this time, itâs hard to know exactly now this will work as we were looking for funding to kick of the R&D phase and could only promise what we envision it to look like. Weâve done our own R&D based off of other products in market and based our technical docs off of them (as well as asked for some new things).
To answer your question though, it should (itâs what we asked for) be presented as a sensor as well so you can base automations off of not just bound to the switch.
2 Likes
I can confirm we wouldnât let YOU get away without presenting the presence as a sensor. We need to be able to group in rooms to keep area lights on.
Itâd be DOA for itâs purpose if we didnât make it exposed to hubs!
2 Likes
I donât want to rain on the parade, but I think this switch may end up DOA if it doesnât have some of the advanced features of the Aqara FP2.
The Aquara device looks interesting, but it doesnât seem as useful to me for North American homes. Not sure why you view it as a direct competitor to the inovelli switch.
1 Like
Feature parity to a $60 presence sensor (only) vs. a dimmer switch with so much more going on is an aspirational goal for a switch selling for $71.
I think we will probably see about 1/2 to 3/4 of the range/zones/distance, and IMO that is great for most applications, and if not the FP2 is available to throw wherever a dedicated sensor might need to be!
DOA in my phrasing was a complete joke. We hold Inovelli to a high standard as their community.
I didnât say it was a direct competitor. I was suggesting that users will be expecting more from a product using mmWave technology. These sensors can do so much more than what is planned for this switch. If all you want is a better solution than a PIR, then this will suffice.
Are you trying to encourage Inovelli to broaden the scope for this product in development, or are you trying to discourage people from buying the Inovelli product because you favor the other one?
It seems to me that the thereâs room to discuss the first topic. If your intent is the second then it seems unlikely that weâll find any value in continuing this discussion.
From your comment upthread itâs unclear if youâre here to discuss or disrupt.
1 Like
I was just making an observation. No ulterior motives either way.
Will this switch get false positives from a ceiling fan?
From Ericâs comments on the Indiegogo site, there will be a way to exclude some regions from motion detection - specifically to resolve ceiling fans. Iâm envisioning this as selecting cells in a view from the detector (as you typically configure the motion detection for security cameras) - but thatâs just me!
But it would be rather nice if this concept could be expanded slightly - so that different regions to be assigned to a few different motion triggers. The âmainâ purpose of the motion detection is to control a single lighting circuit, so 32 detection zones seems a bit excessive. But I can see a use case for a bathroom where motion in the shower vs. the sink vs. the toilet could be used to cause different actions. For a big room, Iâd expect multiple lighting circuits, so multiple switches, each potentially with their own (few) motion zones.
Eric mentioned in the Indiegogo discussion that it should have several different zones that it detects presence in and turning off the ones that have the ceiling fan in them will prevent it from detecting them.
That is a really cool product! I wouldnât say itâs out of the question on what we can/canât add to the switch.
I think weâll have to do some R&D on it to see whatâs on the inside and how itâs being accomplished.
Have you found any specs anywhere on it? I wonder what sensor theyâre using (24, 60, etc).
Thanks for bringing this up though, thatâs the beauty of this being a concept right now. Still plenty of time to tweak things!
1 Like
Iâve been excited about this product since it was announced at CES 2023 for the same reasons we are all excited about Project Linus.
According to FCC filings they are using 60GHz sensors.
https://fccid.io/2AKIT-PS-S02
On a side note⌠now that we know the campaign was a success (maybe bigger than expected), can we create campaigns for additional switches to complement the blue series so we can match the whole house: double switches and 4 (or 5) button switches (like the Ra3 ones). Pleeease 
1 Like
While some of those advanced features are useful, I wouldnât say theyâre all necessary.
Ultimately, we need presence sensing in a room with minimal motion. Primarily for things like keeping the lights on, the room heated/cooled, etcâŚ
There is a very small subset of users who will want to run automations based on if there are 1, 2, or 3 people in the room. The only use I can think of for this is for slight adjustments to a roomâs temp based on the theory that 3 people would put out more body heat than 1 person. But I also donât think that would make any measurable difference until you get up into 10+ people which the fp2 canât do.
Also, 32 zones with 320 squares is excessive. Iâm not sure if youâve played with the regions on the fp1 (See here), but even creating and managing 10 zones is a pain and from my testing has been all but useless so far. With Aqaraâs implementation, if there is any motion in any of those zones, the main occupancy sensor will still show as occupied. So you canât use the occupancy sensor for your automations. Instead you need to rely on action messages for either entering or leaving the individual zones. Iâve tried separating these into individual sensors using templating but Iâve found the actions arenât always accurate. For example, the occupancy sensor will show not_occupied while zone 3âs state will be entered but never detected anybody leaving. Another thing to note here is that Aqaraâs zones only work horizontally and not vertically. So to exclude a ceiling fan, you end up with a big occupancy dead zone below that ceiling fan. In a bedroom with a ceiling fan above the bed, you lose the ability to detect occupancy in the bed.
In place of detection zones, Iâd much rather see vertical exclusion zones. The ability to block out that ceiling fan or the cat walking along the floor.
8 Likes
There are some pretty cool features on the FP2 linked above. This video came out today, would be awesome to have some of these features
2 Likes
I was excited until he said it was WiFi only and not Zigbee. Boo. 
3 Likes
I have to also say that if we can do multi-person & multi-zone like the FP2 is able to, that would be killer (even if this was something that got pushed to a software update later on if itâs too complicated for v1). Making sure the hardware is there for later would be really nice.
If a home has 50 switches in it, with many being in the same rooms, it would be nice to have them all share a single âmapâ that can be configured; creating rooms and zones within rooms.
Rather than embed the sensor in the switch plate, why not have the switch include a plug for custom Inovelli wall plates that include the appropriate sensor? Iâd rather have a slightly beefier wall plate with the appropriate sensor. Even having a âfakeâ extra gang on the wall plate that houses sensor(s) to the right or left and integrates with the switch plug would make it easier to customize in the long term. Embedding a mmwave sensor in the switch and having to maintain the different switch models is a support/sales cost issue. A single switch model with an inexpensive GPIO plug to support Inovelli supplied wall plate sensors would allow for multiple different sensors and less expensive upgrades.