Add support for node info received event

[AlCalzone]

https://zwave-js.github.io/zwave-js/#/api/node?id=quotnode-info-receivedquot

This is forwarded by the server starting in v3.5.0

[MartinHjelmare]

Let's add a test similar to this test:

zwave-js-server-python/test/model/test_driver.py

Lines 398 to 408 in 0644630

	async def test_driver_ready_event(driver):
	"""Test that the driver ready event is succesfully validated by pydantic."""
	event_type = "driver ready"
	event_data = {"source": "driver", "event": event_type}
	event = Event(event_type, event_data)
	def callback(data: dict) -> None:
	assert data == event_data
	driver.on(event_type, callback)
	driver.receive_event(event)

[vexofp]

Eagerly awaiting this PR to land, be released, and make its way in to Home Assistant. 🙏

Some of my older GE switches like to generate this event quite often. The missing entry in NODE_EVENT_MODEL_MAP causes Node.receive_event() to throw, causing the Home Assistant integration to disconnect/reload, causing all entities to become temporarily unavailable and generally causing mischief with automations as the states repopulate afterward.

Testing this patch locally, it successfully resolves the issue.

[AlCalzone]

The missing entry in NODE_EVENT_MODEL_MAP causes Node.receive_event() to throw, causing the Home Assistant integration to disconnect/reload

@MartinHjelmare this is concerning. I suppose we should ignore new/unknown events, not crash.

[MartinHjelmare]

Yes, sounds good. A separate PR with that is welcome.

[MartinHjelmare]

Thanks!

[AlCalzone]

Yes, sounds good. A separate PR with that is welcome.

#1348