Hello,
I use RDM Free 2026.2.17.0 with a Xiaomi router Website entry.
Manual Typing Macro with $PASSWORD$ works correctly, including a password containing a special character.
HTML Autofill does not work, and Custom JavaScript gives “Password incorrect”.
I do not see Events / After Open in the Website entry.
Is there any way in the Free version to automatically run the Typing Macro when the Website opens, so login is fully automatic?
Thank you.
Hello,
Good news on the main question: there is no Free edition limitation here. The Events section — with Before opening / After opening — is available in every edition and for every entry type, including Website. It is simply hidden by default.
The entry editor opens in a simplified view that hides the more advanced sections. Open the entry's properties and click Show all properties at the bottom of the left-hand section list — Events then appears under the Connection group, and After opening → Typing macro is what you want for an automatic login on open.
If you would rather not toggle it, you can move Events into the simplified list permanently under File – Options – User interface – Simplified view.
On your other two points:
HTML autofill only works when the entry opens in the embedded browser. If it is set to open in an external browser, RDM has no access to the page, so both element-based autofill and custom JavaScript are unavailable — only Basic/NTLM-style authentication can be passed. Worth checking first. Two other things can silently disable it: the enforce origin check option, which skips autofill when the page origin does not match the entry's URL (routers that redirect to a different host or port often cause this), and login forms built in JavaScript, where the fields may not exist yet when the fill runs — raising the autofill delay sometimes helps. There is also an alternate autofill engine you can try under File – Options – Types – Web.
Custom JavaScript with a special character in the password — this one looks like a genuine bug on our side, and your observation is the giveaway. The typing macro substitutes $PASSWORD$ literally, but the custom JavaScript path escapes the value for XML first, so a password containing &, < or > is turned into &, < or > before it reaches the page — and the site correctly reports a wrong password.
Could you confirm which special character your password contains? If it is one of those three, that is exactly what you are encountering, and we will get it fixed.
Regards
David Hervieux