For some reason, I have it in my head that the newer INSTEON Motion Sensor (2844-222) is not compatible with the ISY994i. Is that right?  Or maybe it's not compatible with V4.7.3 that I'm running?  Or am I just imagining things. 

4 minutes ago, Kentinada said:

Or maybe it's not compatible with V4.7.3 that I'm running?

Bingo.  Another reason to upgrade... ?

It can be added as the older motion sensor you just won't be able to configure the settings

What firmware version do we need to be able to use it fully?  Is there a firmware that isn't in beta that works with it?

1 hour ago, remotesanitizer said:

What firmware version do we need to be able to use it fully?  Is there a firmware that isn't in beta that works with it?

No, it was reverse engineered and finally supported in the 5.x.x series, and UDI has indicated that it won't be back ported to the older firmware.  It'll install in the 4.x.x series as an 2842-222, but it can't be configured.  There might be two ways to get past that:

1. Use an Insteon Hub to configure the sensor
2. Upgrade to the latest ISY firmware (5.0.15), configure the sensor, then downgrade back to the 4.x.x series, and install the configured sensor as a 2842-222 (I haven't tried this)

Or, install the 5.0.15 beta...

I've been hesitant to install a beta firmware.  Is there a projected date it will become released? 

No projected date. To be honest there will always be beta firmware. A new device gets released UDI will push a beta out to support it. 

Personally you're better off upgrading now then later. The more they add and change the harder it may become too upgrade later. This is especially so as you add more devices and programs. It's easier to grow with the system than have a fully matured system and adapt.

Currently, v5 is very stable. I wouldn't get hung up on "beta" at this point. 

Can I upgrade directly from 4.7.3 to 5.0.15?  

1 hour ago, Kentinada said:

Can I upgrade directly from 4.7.3 to 5.0.15?  

Yes.

Edit: Added suggestions...

A couple things to note before you upgrade:

• After the upgrade the username/password to access the Admin Console will be reset to admin/admin
• If you have disabled any programs in v4, they may not be disabled in v5.  So you should make a note of any programs that you have disabled before upgrading
• The same thing may be true of programs you have set to "run at startup" so make note of those before upgrading
• Some people like to save a text version of all of their programs before upgrading.  This gives them an easy reference to use after the upgrade.  Simply go to the top of the program hierarchy in the Admin Console (in my case it's "My Programs"), right-click and choose "Copy to Clipboard".  Then open Notepad and paste the results and save the text document.  If you do this, it will also give you a record of programs that are "disabled" and "run at startup" since "[Not Enabled]" and "[Run At Startup]" appear to the right of the program name (or at least it does when I do this in v5).
• You might also want to review the 5.0.14 upgrade thread to see what other people have said about upgrading.  Comments like the following are spread throughout the thread and provide insight about things that might not be as clear as they should when you begin:

Edited April 4, 20196 yr by kclenden

Thanks for the details on the upgrade.  I assume I should be looking at 5.0.15 since that is now available.  I'll post my installation questions on the 5.0.15 thread.

11 hours ago, Kentinada said:

I assume I should be looking at 5.0.15 since that is now available.

Definitely go directly to 5.0.15.  You'll want to look at the 5.0.15 thread, but after monitoring the threads for the last few versions it seems like the key things look out for have coalesced around just a few things.

So my old 2420M died and I have to use a new 2844 MS.  I am running 5.0.15 in my ISY994i.  But I see no INSTEON address on this new MS so I don't know how to add it to my ISY devices.   Any help would be appreciated! 

I found the address behind the battery.  I went to Link Management/Link to Sensor/Motion Sensor II and put in the address.  I then get the attached error shortly there after.   Suggestions?

 

Factory reset motion sensor and re-try. Also, make sure it's in linking mode while you're adding

Dang. My bad.  I didn't press the Set button on the MS.  Once I pressed the Set button and tried it again, it added to the ISY.  That's the good news.  I have the device in my ISY shown in the attached. But I'm not sure what device name I use in my programs.  And why are the 2nd 2 devices shown with the INSTEON address rather than the name?  I can't tell what device to use to test for motion.  The old MS was much simpler.  Any help or pointers to documentation would be appreciated.  Thanks. 

 

You use the "Kitchen2.1 Motion" device to check for motion.  If you right-click on "Kitchen2.1 Motion" and choose "Group Devices" then the other nodes will appear below, and indented.  It's been a while since I added my motion sensors, but I think when I renamed the main node I chose "Rename all associated devices by replacing the prefix of each name with a new common prefix".

Edited October 3, 20196 yr by kclenden