Can't catch events on hardhat node

[rupansh]

I have the following event in the contract:

event Unfreeze(uint256 action_id, string to, uint256 value);

I am using the websocket provider:

const w3 = new providers.WebSocketProvider(provider_uri, network);
await w3.ready;
const acc = (new Wallet(pkey)).connect(w3);
const mint = new Contract(minter, abi, acc);

Started the listener like this:

mint.on('Unfreeze', async (action_id: ethers.BigNumber, to: string, value: ethers.BigNumber ) => {
  const ev = { action_id, to, value };
  console.log("ev", JSON.stringify(ev));
});

But upon sending a transaction from hardhat console(which does show the event in events array), i don't see any output.
I can also call functions from the contract.

Can confirm this issue isn't present in ropsten (via infura)

[zemse]

Hardhat node and Ropsten have one difference that is blocks on hh node are mined only on tx while Ropsten its continuous. AFAIR, ethers has an exponential delay mechanism which tries pooling block number initially 4 secs, then after 8 secs 16 secs, and similarly waits for more time before quering. So if your node was standby for a while, your provider might have went far in the exponential pooling interval.

Can you try setting auto mine to false (docs), so that the hh node keeps producing blocks even if you don't have any txs.

[rupansh]

Can you try setting auto mine to false (docs), so that the hh node keeps producing blocks even if you don't have any txs.

interval is set to 4000 (tried lower values like 1000 as well)
event appears in hardhat console when calling contract,
no output in the ethers app.

[rupansh]

Hardhat node and Ropsten have one difference that is blocks on hh node are mined only on tx while Ropsten its continuous. AFAIR, ethers has an exponential delay mechanism which tries pooling block number initially 4 secs, then after 8 secs 16 secs, and similarly waits for more time before quering. So if your node was standby for a while, your provider might have went far in the exponential pooling interval.

Is there a way to disable this undesirable implicit behavior (or atleast set a top limit to the polling interval?)
I was facing event misses with HECO Testnet as well (https://docs.hecochain.com/#/en-us/testnet)
I can't control block intervals for this chain.