@luma You are amazing, thank you for typing this out, because it is not spelled out this well anywhere else.
My config bit is also the default ff05. I would love to stop the logs being spammed (I just cleared 2.5M log entries) with this, however I'm unclear as to WHY it is being logged.
Also, not sure whether the bitmask affects logging only, or if the alarmdecoder functionality evolves (ie. by masking out things that it would otherwise be looking at.
Have you noticed any difference in behavior? Do you run Home Assistant or Homebridge (not sure if they would be impacted somehow)...
Again, thank you so much for taking the time to write this up. Absolutely wasn't expecting to see this when I came here given the state of AD over the last 2-3 years.
luma wrote:I just went through this myself so I figured I'd write up the process for the next guy.
1. Telnet to the device on port 10000
2. Hit "C" (note caps) and press enter
3. You should get a string back something like: MODE=A&CONFIGBITS=ff05&ADDRESS=18&LRR=N&COM=Y&EXP=NNNNN&REL=NNNN&MASK=ffffffff&DEDUPLICATE=N
4. You want the part after CONFIGBITS=, in my case that's ff05
5. Open Windows calculator, switch to programmer mode, then click on HEX.
6. To disable AUI reporting, enter your CONFIGBITS code, click AND, then enter FFFE, then =. The answer is your new CONFIGBITS, in my case that's FF04.
7. If you also want to disable RFX reporting, take your new value, click AND, then FEFF, then =. The answer is your new CONFIGBITS, in my case that's FE04.
8. Enter the following then press enter, note the double leading "C": CCONFIGBITS=fe04