Mark,
I had a 2420 motion sensor crap the bed, so I used the replace function to put in a new unit. The plugin registered it, and it reports the protocol as i2CS, whereas the previous unit was i2.
I forgot to set jumper 5, which allows for software settings, and when I went to program the timeout, the plugin continued to report that there are setting changes pending, no matter how many times it sent an ON. Realizing the mistake, I put jumper 5 in place.
Unfortunately, despite that, the plugin STILL reports pending changes. I disabled and re-enabled the plugin, then reprogrammed the timeout setting. But alas, despite multiple ONs, it is still not programming the timeout.
Do you know if this is an issue related to the new protocol, or because I left the jumper off, or what? Should I delete and re-link, or should I replace it with another i2 device? Any advice appreciated, as programming settings has always previously worked. Thanks!
Edit: I have v1.7.2.5 of the plugin. For giggles I tested programming settings with another i2 version, and it worked as predicted. So either it has to do with the protocol or the fact that I added the device at first without jumper 5 in place. Will replace it with another i2 and see what happens.
-BD
I had a 2420 motion sensor crap the bed, so I used the replace function to put in a new unit. The plugin registered it, and it reports the protocol as i2CS, whereas the previous unit was i2.
I forgot to set jumper 5, which allows for software settings, and when I went to program the timeout, the plugin continued to report that there are setting changes pending, no matter how many times it sent an ON. Realizing the mistake, I put jumper 5 in place.
Unfortunately, despite that, the plugin STILL reports pending changes. I disabled and re-enabled the plugin, then reprogrammed the timeout setting. But alas, despite multiple ONs, it is still not programming the timeout.
Do you know if this is an issue related to the new protocol, or because I left the jumper off, or what? Should I delete and re-link, or should I replace it with another i2 device? Any advice appreciated, as programming settings has always previously worked. Thanks!
Edit: I have v1.7.2.5 of the plugin. For giggles I tested programming settings with another i2 version, and it worked as predicted. So either it has to do with the protocol or the fact that I added the device at first without jumper 5 in place. Will replace it with another i2 and see what happens.
-BD
Comment