node-red-contrib-ccu 4.5.2

v4.5.2

on Node.js NPM

Fixed

• No HmIP-RF events for up to 10 minutes after hmipserver restarted
  (B-37). hmipserver keeps its subscribers over a restart: it calls
  listDevices and newDevices on them and answers their pings, but
  delivers no event to such a kept subscription until it is subscribed
  afresh. The liveness ping saw its PONG and was content, so the
  subscription came back only with the 600 s silence timeout. A
  listDevices or newDevices call that does not follow the connection's
  own init now makes it subscribe again at once, and events are back
  within seconds. A device paired while Node-RED runs costs one such init
  as well.

Commits since v4.5.1

• 4.5.2 - HmIP-RF events come back at once after hmipserver restarted (06bc647)
• HmIP-RF: subscribe afresh when hmipserver restarted and kept the subscription (B-37) (8eed6a4)