Not addable to Redmatic after Update

[Robotar1]

** Describe issue **
Already got the Node on Redmatic running on a CCU3 Rasp, after the update on the latest Version of the node.

Get the Notice:
Installation fehlgeschlagen: node-red-contrib-miio-roborock

Cannot read property 'nodes' of null

Überprüfen Sie das Protokoll auf weitere Informationen.

Viewlog:

2022-10-23T12:41:12.973Z installieren : node-red-contrib-miio-roborock 2.3.4

2022-10-23T12:41:13.031Z npm install --no-package-lock --global-style --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production [email protected]
2022-10-23T12:41:19.662Z [out]
2022-10-23T12:41:19.662Z [out] up to date in 6s
2022-10-23T12:41:19.783Z rc=0

---

2022-10-23T12:47:38.112Z installieren : node-red-contrib-miio-roborock 2.3.4

2022-10-23T12:47:38.130Z npm install --no-package-lock --global-style --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production [email protected]
2022-10-23T12:47:44.044Z [out]
2022-10-23T12:47:44.044Z [out] up to date in 5s
2022-10-23T12:47:44.129Z rc=0

** Hardware / Software **
  - raspberry 4  

• version of deconz gateway: [2.05.66 / 16/06/2019]
    - version of node-red-contrib-deconz: [0.10]

Sorry, i´m a nube, need Some help!

[prometheus247]

Having the same exact issue, also redmatic running on CCU3.
Accessing the Log of RedMatic directly from the CCU helped.

It revealed:
Dec 23 01:23:51 homematic-raspi daemon.warn node-red[2226]: [node-red-contrib-miio-roborock] Node module cannot be loaded on this version. Requires: >=1.3.0
My Node-RED version: v1.2.9

I suppose you are also on a later version, as I, @Robotar1
Maybe its not a bug, rather a compatibility issue.

[andreypopov]

Having the same exact issue, also redmatic running on CCU3. Accessing the Log of RedMatic directly from the CCU helped.

It revealed: Dec 23 01:23:51 homematic-raspi daemon.warn node-red[2226]: [node-red-contrib-miio-roborock] Node module cannot be loaded on this version. Requires: >=1.3.0 My Node-RED version: v1.2.9

I suppose you are also on a later version, as I, @Robotar1 Maybe its not a bug, rather a compatibility issue.

it is time to upgrade node-red from 1.2.9 to 3.1.3