Z-Wave Door / Window Sensor | Project Home Alone

Manufacturer supplied manual: Inovelli Z-Wave 700 Bypass DW Sensor User Guide.pdf (390.5 KB)

Ours will come later.

We have a unique opportunity in that a major alarm company wants to purchase some door/window sensors from our manufacturer and they do not have a house brand, so they’ve chosen us to be their brand of choice.

This is an honor as we don’t make door/window sensors, but their track record with us and our switches and bulbs really made them push us to carry a couple of different sensors.

The project is a bit different in that we don’t have the flexibility to change much outside of some firmware changes as this is a, “white-label” product (already produced by the manufacturer, we’re just putting our name on it) so we’re just putting this out there for visibility.

At the very least, we can build on the white-label and if this project takes off, we can ask for hardware changes and possibly come out with our own version.

As per our tradition of working with you amazing people, here’s what this thread allows us to do as a community.

  1. Allows us to keep everyone updated on the project status (either good or bad)
  2. Allows you to participate and help us develop amazing products together
  3. Enjoy each other’s company and have fun talking home automation

How this initial post will be laid out is in five sections:

  1. Project Overview
  2. Timeline (edited to remain up-to-date)
  3. Hardware & Software Specs
  4. Pinned Ideas & Shout-outs (edited to remain up-to-date)
  5. Weekly Recap


  • DATES & FUNCTIONS ARE NOT SET IN STONE: Just a reminder that all dates and functions are sometimes fluid. We have to make choices based on feasibility, opportunity costs, and overall timeline. I will be as transparent as possible on these decisions, but just a heads up, they may not always be exciting.
  • NO IDEA IS A BAD IDEA: Ok, some are, but honestly throw out anything that you can think of. If we use your idea, we’ll credit you and send you a free device, so take that shot!
  • WHITE-LABEL PRODUCT: As mentioned above, this is a white-label product (ie: manufacturer has already designed this to resell and we are just putting our name on it), so we do not have the capability to change the hardware or design of the product and some firmware ideas may be limited to how the hardware was designed. However, this is a good thread to capture ideas that may allow some influence over a V2 design.

Ok, let’s get this party started!

Project Overview
The purpose of this project initially was to provide one of the (if not the largest) alarm companies with a solid door/window sensor. We were approached by them to put our brand name on a sensor for them to resell as they do not have their own, “house-brand”. In addition, we thought, “you know, who wouldn’t want a door/window sensor?” so we decided to carry this ourselves.

Project Name - Home Alone

There’s a classic scene in Home Alone where one of the burglars comes in through the window. While Kevin does a great job putting ornaments down, he would’ve also known the window was open with one of our door/window sensors!

Home Alone - Hardware
As mentioned, this is a white-label product, so we don’t have any influence over the current version of the door/window sensor.

Hardware - Door/Window Sensor (Look / Feel)


I’ll get a better picture, this is all I could find online.


Detective Range: 20mm (this is the gap between magnets)
Communication Protocol: Z-Wave, S2 Encryption & SmartStart
Chipset: 700 Series
Power Source: Battery - 3V-CR2 (1x)
Battery Life: 3yrs (under normal usage)
Mounting: Screws or 3M Tape
Operating Temperature: 32-104°F (0-40°C)
Operating Humidity: Up to 85%, non-condensing

  • Inches: Main Body = 2.7"(L) x 1.0"(W) x 0.8"(H) // Magnet Part = 1.7"(L) x 0.6"(W) x 0.5"(H)
  • Millimeters: Main Body = 68.4(L) x 24.4(W) x 21.5(H) // Magnet Part = 44.4(L) x 15(W) x 13(H)

Hardware - Features & Capabilities

The sensor will have the ability to detect open/close, temperature, and has a bypass button on it (the big button in the middle) that will temporarily disable open/close reports until it’s pressed again. This is good for if you have to let the dog outside, but your house is armed.

Home Alone - Software
We do have a bit of wiggle room here to improve the firmware, but depending on the timeline of when the alarm company wants these, we may not be able to implement them all at once.

Firmware is pretty simple and includes:

  • Magnetic field range calibration
  • Battery Level indication
  • Bypass feature (ie: press the button and the sensor will not send commands to the hub)
  • Temperature Reporting
  • Anti-tamper

There does seem to be a central scene command built in where you can press the button a certain amount of times to activate a scene. The firmware we’ve tested does not have this built in, but their spec sheet does. We’ll make sure it’s in there as I think that’s a pretty cool feature.

Ah, everyone’s favorite part. When is this flippin thing going to be released? Great question – here’s the high-level of what happens leading up to the first release of the timeline:

  1. We receive beta units (on their way) and our beta testers will test them
  2. In addition, the alarm company receives beta units and they test them on their platform (this has been done already)
  3. Initial Timeline Released

Again, just want to throw this out there – I don’t have a crystal ball so I can’t predict things that come up along the way. Trust me when I say we’re trying our best to get things launched on time.

The good news is all the heavy lifting has been done here and this should be a simple project (knock on wood) as the hardware has already been developed, the firmware has been developed and also certified by the alarm company as well as the Z-Wave Alliance. We’re just putting some finishing, “Inovelli” touches on them.

Pre-Initial Timeline Milestones:

  • Receive Beta Units for Alarm Company: Completed
  • Receive Beta Units for Inovelli Beta Team: In Progress
  • Initial Timeline Released: Not Started

Timeline (Estimated)

The initial timeline will be shown below and will be updated bi-weekly (if needed). We’ll update once this project officially launches.

Pinned Ideas & Shout-outs

  1. Support Z-Wave Long Range - thanks @chack & @stu1811!
  2. Various inclusion levels (S2, Non-Secure) - thanks @chack!

Weekly Recap
Every Wednesday evening or Thursday morning, we have a meeting with our manufacturer to go over the various projects (status, issues, timeline, etc) and below I’ll provide a recap as well as edit the sections above so we can all keep track. If you have any specific questions you’d like me to ask, feel free to tag me and let me know so I can ask them as well. The weekly cadence for updates will be Thursday mornings (or afternoons depending on when we have the meeting).

March 25, 2021: We’ve received beta units for the alarm company to test as well as a couple extra for the internal team to test (Eric M, Nathan, Brianna and Courtney). Preliminary feedback to come in a comment.


Does it have a dry contact header for external input? I want to use one in my mailbox with a pressure sensor. The ecolink door sensor doesn’t have the range to reach the street. Will this sensor support long range?


Is there a way to disable this feature? Or you just push the button and it stops working (for a time or until pressed again)?

Edit - also any shot at Zwave LR support?

I agree, hopefully there will be a way to disable that feature.

1 Like

No, it doesn’t. Dangit, I was hoping it would too.

I’ll have to defer to @EricM_Inovelli on this one. Hopefully as it is 700 Series!

Looks like it, yes :slight_smile:


What is up with you guys spending my future money after I keep sending you my present money?

Have any details on this? I have a couple of sensors I’ve waterproofed for exterior gates, and really want to check if they are ajar and not just opened. Placement (or calibration) is super critical for this.


Pretty much how @Courtney_Inovelli answers the phone to place the order with our manufacturer.

Hmmmm… not really. This is all I’m seeing:

I can check with Jason and @EricM_Inovelli to see about more info.


Ive been holding out on zwave door sensors, waiting for a reputable company to produce some that meed my expectations:

  • Replaceable battery
  • multi-year battery life
  • A company that actually releases firmware updates

I will be purchasing a few.

When should I start compiling my list of desired firmware features?

1 Like

You sure do know how to make a grown man cry! Thanks @jtronicus :slight_smile:

You can start right now if you’d like – the sooner the better so we can implement them if possible!


Here is what I would like to see from a firmware perspective:

  • button press (same button press that enables the bypass) sends a Central Scene command
    • scene should still send even if bypass mode is enabled.
    • This would allow us to set up our own “bypass” mode at our hub of choice, yet still receive the door state events from the sensor
  • A feature to send a Panic Alert notification event (on certain number of button presses)
    • Technically, a scene could do the same, but I figured a Panic Alert notification would be more useful to an alarm company
  • Option to re-send status every x seconds/minutes/hours if door state is left open (will probably drain battery faster, but there is no reason for the fridge door to be open that long)
  • Option to send a temperature report whenever an door state event is reported (since the device is already awake, might as well send both reports)
  • Option to send basic-set command to associated devices when sensor is opened/closed (useful for when the light in the fridge has burned out and you cant be bothered to replace it closet doors to trigger the light)
  • A way to force the device to send a battery level report (3x button press or something)

Finally! It’s about time you added a contact sensor to round out the core device pool.

The bypass button is an awesome touch. A few requests on that front:

  • Ability to toggle modes (on/off, one-time, two-time). Think leaving early to go to work vs walking dog. Just different reset thresholds.
  • Ability to vary this setting based on time of day.
  • Timeout limit for bypass option


Feedback for current design:

  • Allow the button to fully report as a button… so we can react to it (coming from Hubitat) as a button however we want in Rules. It is great to have it as a bypass, but if the overall system knows about it someone can make sure it does not trigger the motion sensors when the dog goes out for example.
  • Double-click, hold, options like that for the button to send.
  • What is the temperature ± for the sensor? ±2 degrees C? 1 degree? Want to have an idea how accurate it is.
  • Configurable rate of reporting what the temperature reading is.
  • Inovelli battery pack sets for devices like these or at least a couple recommended types… so we know we have ones that will work reasonably.

Future version ideas/options:

  • Outdoor weather resistance (including better temperature range, it gets much colder here… but this is usually more due to the battery than the circuit).
  • External contact (this is a HUGE one) an alternative would be to make the internal contacts be headers so that the internal contact could be “disabled” to connect wires for an external contact, but both is always better. I would love to replace my old WADWAZs even if it means I do not get the “fun” of continuing to work on the WADWAZ driver I made for Hubitat. But the external contact is a MUST for me.
  • More standard battery size (AAA or AA for example)
  • Power headers (so it can be WIRED for power), with a hole in the battery compartment (or designated spot to drill a hole) to run wires through.

That is seriously cool that your company received such a cool offer! I was waiting for a good zwave option for door/window sensors for a while while I stuck with battery guzzling zigbee sensors in the interim.

I would seriously love to start phasing my current sensors out in favor of these new options at some point. Does your team have a price point you’re trying to eyeball? I know this project is brand new, but was hoping to have a ballpark number in the back of my head to get an idea what the damage will be once the time comes.

Is there a rough idea on price? I’m actually in the market for three of these and was gonna pull the trigger on some cheap zigbee sensors, but Id love some more secure/reliable ones with much better battery life.

Agreed this is great. I’d love to ditch the crappy Zigbee sensors I have that get a few months out of a CR2032 and move to something with decent battery life.

+1 on the thought that the bypass option should be done hub-side, not on the device. If someone wants to allow bypassing that’s fine, but I don’t want anyone in front of the sensor to have that option.

I am also a bit curious how these will integrate with the z-wave mesh. One one hand it’s nice to think the sensors furthest from my hub will get a boost, but I am a bit worried about switches routing through these and either reducing the battery life, or worse, going unresponsive if a battery dies.

Z-wave spec says battery devices are not repeaters per my understanding.

1 Like

If you get a chance to make your own hardware modifications down the road…

  • Vibration / Tilt sensor - to detect knocking at a door, a garage door opening, or a window being interacted with prior to being opened. Would want sensitivity control on something like this though.
  • Smaller Size - The smaller the better
  • Color options - A darker color would be cool to have or even a surface material that is accepting to being painted
  • External Power source
1 Like

Awesome thanks @jtronicus, @Snell and @amdbuilder for the firmware suggestions. We will for sure pass it on to the manufacturer and see what we can do! Really good ideas :slight_smile:

Out of curiosity, is this a special Z-Wave command or is this just something you’d setup via your hub (ie: via scene control as you suggested)?

Could you expand here a bit? I think I understand, but the one-time/two-time has me a tad confused lol.

Unfortunately, no.

I’ll have to follow up on this one. Mine seems to be a little off (reporting 62°F, when my ecobee is reporting 67°F – however, the sensor is right by the door, so it could be real). The driver does have the ability to calibrate the sensor by +/- 10°F, but I’m not sure if @EricM_Inovelli has activated that yet.

That would be cool – but likely we wouldn’t have the capital to brand our own batteries. However, the sensors that came to us had Duracell in them (I’m not certain that will be what production comes with). We can certainly test a few different types.

Yes, we’re trying to stay competitive with the other sensors out there, so likely around $30 until the tariffs go away. We are also throwing around the idea of 10pks so the price per unit will be lower there.

@kreene1987 is correct

Lastly, I posted the manual from the manufacturer. It’s not your standard Inovelli manual, but it should give you an idea of the features better than me :slight_smile: