I was looking at the FCC web site for new devices as I got a Developers Notes file today on a 2845-222 Hidden Door Sensor.

It is in the FCC Database. SBP28452.

Internal and external photos. Users Manual. Test results and photos.

http://transition.fcc.gov/oet/ea/fccid/

Grantee SBP

Product Code 28452

 

Details tab.

$29.99 is the guess each, maybe a special at $24.99 (these are totally WAG)

 

I'll take a few, maybe in time for their 20% of black friday add on insteon. Time to update the spreadsheet!

 

Alan

The device has been released and ETA for sale is 11/29/2013. I am looking forward to seeing how this product pans out for others and how they intend to use it.

 

http://www.smarthome.com/2845-222/INSTE ... sor/p.aspx

 

Teken . . .

I will also be waiting for users feedback.

I wounder it its 4" insertion depth is going to be a limit for some potential users.

I will also be waiting for users feedback.

I wounder it its 4" insertion depth is going to be a limit for some potential users.

 

Users should probably be aware that the rated life cycle is 6 months for the battery. Given a high traffic area like the front / garage door I would probably opt to use a lithium battery to extend that time.

 

I can't see myself removing these units so often just for a battery change. I am more interested in how the RF range is for this device given its going to be literally buried deep into a door frame etc.

 

Teken . . .

Has anyone had success linking the 2845-222 to an isy994i controller? I get an unsupported device error message.

It is listed as a supported device under New INSTEON Device on 4.1.0. What ISY level are you running?

I did momentarily see an unsupported message as I added the device, but then it resolved it.

 

On a separate note, I see that it was added as a light and not a switch. Therefore, it can only be a responder. This doesn't seem right.

Support for the 2845-222 was added in firmware 4.1.0

If you have an earlier firmware version. It may not be added correctly or be called Unsupported.

I am, in fact, running 4.1.0.

 

I have removed and re-added it a few times and the behavior is the same each time. The Admin Console pops up the normal progress bar window that you see when adding a device, but the title says unsupported device. The window closes and the device is added anyway. When I press the button on the sensor I can see the state change in the Admin Console, but it is shown as a light and not a switch.

 

One other minor note that I haven't seen before is the name I entered for the device isn't saved when I add it. I have had to manually rename.

 

I wonder if it is a defective sensor?

Click Help | About and verify the UI line indicates 4.1.0.

Click Help | About and verify the UI line indicates 4.1.0.

 

That was it, Lee. Thanks for the tip. I feel like I've looked at that maybe once before, but just figured the firmware update was all I need. Clearly still new to this. Much appreciated!

 

Regards,

Bertram

Glad that helped. Once an ISY update is done and Help | About is correct should not need to look at it any more unless an error comes up unexpected.

It is listed as a supported device under New INSTEON Device on 4.1.0. What ISY level are you running?

 

Updated to 4.1.0 and now it works.

Tx

I got one installed today. Drilling a 3/4" wide 4" deep hole did make me a little nervous. If I use one again I will probably try to put it in the door.

Here is a video of it:

E

My target for these new sensors are interior doors that aren't monitored by the security system.

 

I'm using one for my pantry door. One would never be in there without the door open and when not in there the door should always be closed. Perfect spot for a door sensor without the unsightly contact closures. This application is better suited for a door sensor than a motion sensor.

 

I drilled into the door jam instead of the door. I chose the door because it's more valuable than the door frame. The door costs about $200. The cost to by a 1x6 A-grade pine to replace one side of the door frame would only be about $10, although with more work effort.

 

Another consideration is visibility. If the door open away from you, the sensor is less visible in the door frame. If the door opens towards you, the sensor is less visible in the door.

 

I have dual-band wall switches just 3ft away which obviously provides reliable communications.

 

We'll see how the battery life lasts with a lithium battery. If it makes it 12 months I'd be happy.

My issue with this sensor is after pulling it in and out a few times for battery swaps every 6 months, I doubt the screw would tighten any longer. Seems to me after a couple years it would be very loose. Thoughts? Other than that I like the idea.

I have pulled one out a couple of times. Just don't over tighten the screw and it should be fine. There are simple ways to take care of the potential problem of the loose screw should this occur. First that comes to mind is the toothpick trick. Shove a piece of tooth pick into the screw hole, then replace screw.

My issue with this sensor is after pulling it in and out a few times for battery swaps every 6 months, I doubt the screw would tighten any longer. Seems to me after a couple years it would be very loose. Thoughts? Other than that I like the idea.

 

I expect with the Energizer Advanced Lithium batter to get more than 6 months. However, only time will tell.

 

If you're not cranking down the screw, there's no reason why it wouldn't still seat properly for 20+ removals. There's no reason to crank it down as there's no force required to hold the sensor in. If it does loosen, that can easily be addressed but going up one size in screw thread or by simply inserting a toothpick (or using a utility knife to shave the corner off a piece of wood) into the hole before inserting the screw.

There are posts talking firmware version as well as UI versions required to support this device and so I would like to get clarification if possible...

 

There are references to firmware 4.0.10 required, but I am on the latest supported level of 4.0.5.

There are references to UI 4.0.11 required, and I am at that level.

 

So, if 4.0.10 is required and 4.0.5 is the latest supported level, where do I get it...

 

Also, for those who have successfully paired, does the "Start Linking" and holding the set button for 3 seconds work? The reason I ask is that the ID is hard to read on my device, so auto find would help.

 

Thanks to all...

There are posts talking firmware version as well as UI versions required to support this device and so I would like to get clarification if possible...

 

There are references to firmware 4.0.10 required, but I am on the latest supported level of 4.0.5.

There are references to UI 4.0.11 required, and I am at that level.

 

So, if 4.0.10 is required and 4.0.5 is the latest supported level, where do I get it...

 

Also, for those who have successfully paired, does the "Start Linking" and holding the set button for 3 seconds work? The reason I ask is that the ID is hard to read on my device, so auto find would help.

 

Thanks to all...

 

4.1.2 is the latest build you should be on now. 4.1.3 is right around the corner in a few weeks though. Both firmware and UI should be the same when you view it under *About*

 

If its not you need to ensure you clear the Java Cache once you update the ISY-994 Series controller. Also, what Insteon RF device do you have in your network and where is it located from this new device?

 

Teken . . .

In case anyone else has questions about supported levels being mentioned. The official supported level is 4.0.5 and that is confirmed in the forums and http://isy.universal-devices.com/99i. All the later release are in beta, so if you need them you have to update manually. For more info on getting beta versions: viewforum.php?f=25

I am getting the Cannot Determine Insteon Device Type error. I did update to 4.1.2 and confirmed in the Help in the admin console that both firmware and UI are at 4.1.2. I have one dual band device (keypad device) and the Door Sensor is next to the device. Based on the error message, it sounds like the ISY could talk to it (before updating I got a message about could not determine the Insteon engine). Any thing else required over updating the firmware/UI?

Right click on the node and there is an option to update the insteon engine.

 

 

Encrypted By: Phoenix Security Solutions

Since the sensor is a battery operated device. You did wake it up from its power saving mode before trying to add it?