Caseta NS not running after migration to eisy

[Jimbo.Automates]

I migrated to eisy and noticed Caseta NS wasn't running, in PG3 UI it says "press the black button", I changed log mode to debug that message went away and now it just keeps printing:

2023-03-14 08:35:22,212 MainThread udi_interface      DEBUG    controller:start: Waiting for configuration False
2023-03-14 08:35:27,219 MainThread udi_interface      DEBUG    controller:start: Waiting for configuration False
2023-03-14 08:35:32,221 MainThread udi_interface      DEBUG    controller:start: Waiting for configuration False
2023-03-14 08:35:37,321 MainThread udi_interface      DEBUG    controller:start: Waiting for configuration False
2023-03-14 08:35:42,322 MainThread udi_interface      DEBUG    controller:start: Waiting for configuration False
2023-03-14 08:35:47,347 MainThread udi_interface      DEBUG    controller:start: Waiting for configuration False
2023-03-14 08:35:52,359 MainThread udi_interface      DEBUG    controller:start: Waiting for configuration False
2023-03-14 08:35:57,360 MainThread udi_interface      DEBUG    controller:start: Waiting for configuration False
2023-03-14 08:36:02,364 MainThread udi_interface      DEBUG    controller:start: Waiting for configuration False
2023-03-14 08:36:04,301 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message shortPoll
2023-03-14 08:36:04,302 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING shortPoll
2023-03-14 08:36:07,369 MainThread udi_interface      DEBUG    controller:start: Waiting for configuration False

Restarting and it shows press the black button again.  Is that necessary after migration?

Also, is there any way to monitor this NS on the IoP to send notifications if it's not running?

Edited March 14, 2023 by Jimbo.Automates

[bpwwer]

1 hour ago, Jimbo.Automates said:

Restarting and it shows press the black button again.  Is that necessary after migration?

Also, is there any way to monitor this NS on the IoP to send notifications if it's not running?

Yes, after migration the node server has to re-create the certificates for the new machine it's running on and then sync those with the smart bridge.

Having the IoX monitor node servers was something I asked for years ago, but it would be something that needs to be added to the IoX firmware.  Currently, the IoX can monitor node server status for node servers that report that if they use the PG3 node server status reporting feature.  You can have a program that sends notifications if the status is disconnected or failed.

[Jimbo.Automates]

Yes, after migration the node server has to re-create the certificates for the new machine it's running on and then sync those with the smart bridge.
Having the IoX monitor node servers was something I asked for years ago, but it would be something that needs to be added to the IoX firmware.  Currently, the IoX can monitor node server status for node servers that report that if they use the PG3 node server status reporting feature.  You can have a program that sends notifications if the status is disconnected or failed.

Thanks, had to restart then push the black button. All good now.

But, this NS doesn't report any connection state or heartbeat that I could see?


Sent from my Pixel 6 Pro using Tapatalk

[bpwwer]

No it doesn't.  I don't think that creating a node just to report the node server's status is a good way to accomplish that.