Unfortunately I cannot access VRM anymore. This happened since yesterday now.
Is there a moderator that can assist me with this problem?
Resetting password succeeded, but the result is the same,… I still cannot login with the same error
Do you use any home automation? Any API calls to VRM?
I’ve got Home Assistant running on a mini-PC. But as far as I know there aren’t any API calls to VRM. Furthermore this configuration is running for months without issues on VRM login.
Correction: Home Assistant itself does not appear to make VRM API calls, but Node-RED on my Cerbo GX does.
One flow performs a GET request to /dynamic-ess-settings once daily at 00:05. It only performs a PATCH request when the Dynamic ESS schedule actually needs to change. The SMA monitoring that runs every 10 seconds is local Modbus TCP traffic and does not use the VRM API.
Under normal operation there should therefore be only one daily VRM read and an occasional write. I am checking whether this Node-RED HTTP branch could nevertheless be repeating unexpectedly.
Could you please check whether my block is account-based or IP-based, and whether you can see which endpoint or request rate triggered it? Resetting my password did not remove the “Too many requests” error.
Additional test result: logging in with the same account works immediately on my iPhone when Wi-Fi is disabled and mobile data is used. Through my home internet connection I still receive the “Too many requests” error.
This strongly suggests that my public home IP address is being rate-limited rather than my VRM account. Could you check which endpoint or request source caused the limit, and whether the IP block can be cleared?
I have now inspected the live Node-RED configuration on the Cerbo GX.
The VRM flow is scheduled only once daily at 00:05. “Inject once after startup” is disabled. Each run performs one GET request and only performs one PATCH when the Dynamic ESS schedule has actually changed. There is no retry path, delay loop or feedback connection, and the SMA flow contains no VRM requests. The current Node-RED debug panel also shows no repeating VRM errors.
I did not manually trigger the flow, to avoid generating another API request while the home IP is rate-limited.
Could you please check the VRM server logs to identify the endpoint and source that caused the IP rate limit?
Let me ask if someone can look.
Most common cause for that issue is when multiple devices are accessing VRM/the same dashboard from a common internet-facing IP.
Examples are multiple users on the same network - doesn’t seem to apply to you - or home automation devices/extra dashboard devices.
It is most likely unexpected executions of API calls triggering rate limits.