The engineId was correct, but I’ve tried the same config, and it was not working. Then I’ve cut/past again the engineId, and it started working. Then I’ve tried AUTH_PRIV, again not working (with DES). Back to AUTH_NO_PRIV, and … not working
At the end I’ve cut/paste again the engineId, and AUTH_NO_PRIV started working again
reloaded … nothing, AUT_NO_PRIV is not working anymore. Same AUT_PRIV. I’ve found an issue (the password cannot contain special characters). But still not working
on QNAP side, don’t use special characters in the password. It doesn’t work
on OH side, don’t put privPassphrase even if you use as securityModel “AUTH_NO_PRIV”. removed privPassphrase, it became green immediately.
@J-N-K can you please put in the code something that can bypass the privPassphrase configuration if you use the securityModel “AUTH_NO_PRIV”? privProtocol can be in the config, but privPassphrase blocks something.
my feeling is there is something in the relation between QNAP and OH that is not stable. If I change the securityModel, to have AUTH_NO_PRIV working again I need to stop/restart the snmp demon in QNAP, and recreate the thing in OH file. Or cut/paste again the engineId. After some changes, it works.
It seems that the QNAP devices change the engine id every time the configuration changes. I changed the code to auto-discover the engine id, maybe you can try if that works better: org.openhab.binding.snmp-4.2.0-SNAPSHOT.jar.txt (681.3 KB)
Yes, that works for me with QNAP. But I believe there is a limit either to length or allows characters. It works with a privacy passphrase 12345678 but not with foobarfoobar.
but this is not correct. Special characters are not allowed (foobar$ doesn’t work). My password for SHA is 10 characters, and it works. I expect also for DES, but something doesn’t work.
I think this may be related to the 5s timeout for discovery. If the printer sleeps it is probably not responding fast enough and we have to wait for the next round (default 60s later). I’ll increase the timeout to 15s.
@J-N-K hello
just to let you know that the last binding in this thread is working well. Just printer and NAS are sometimes offline, but they come back online without manual intervention. Perhaps a timeout, as you said, that can be improved.
Question: when I’ll be able to switch to the normal distro version? in 4.2.0.M4?