[Minor Bug]: NR server 3.0.1 requires a NR deploy for the NRCHKB to become active in Home Kit again after reboot

[houser42]

NRCHKB Plugin Version

1.4.3

Node JS Version

16.16.0

NPM Version

8.11.0

Node-RED Version

3.0.1

Operating System

Ubuntu 20.04

What happened?

Hello,

Just noticed that at least on my two systems, both Ubuntu 20.04, NR 3.0.1 installed with the Pi-script the NR servers requires a NR deploy for the NRCHKB to become active in Home Kit again. No biggie once you are aware of it, but maybe have a look if it can be fixed at some point or is a new NR bug? Many thanks

How to reproduce?

reboot NR server

Expected behavior:

NRCHKB should become active automatically

Additional comments?

Additional comments here, if any.

Relevant log output

No response

[Shaquu]

Hi, thanks for report. We need to check how the flow looks like before and after deploy on 3. Also, any logs before deploy? Could be error printed.

[houser42]

Hi, thanks for report. We need to check how the flow looks like before and after deploy on 3. Also, any logs before deploy? Could be error printed.

I see no difference before and after deploy in NR. No errors in the log and all flows appear to work in NR, they are just not published from NRCHKB to Home Kit but are published instantly after redeploy.

[Supergiovane]

Hi I’ve also this issue but… mine works after reboot, but stops working after about 10 minutes and i need to full deploy. Nodered 3.0.2

[Shaquu]

I just tested and it works for me.

Can you please try on latest node-red and using our dev package?

[houser42]

Upgraded to NR 3.2 here now on 3 installs. It seems the issue is gone now with latest main NRCHKB 1.4.3. NRCHKB nodes now deploy after reboot without issues. Not sure if that means closing this thread just yet, but all seems fine here now.

[caitken-com]

@houser42 is this resolved?

[houser42]

Hello. Yes. I am still on NR 3.0.2 and this issue is gone.

[caitken-com]

Glad it’s sorted. Feel free to ask more questions on our Discord.