bpwwer

Try re-installing it. the module should get installed as part of the node server install process.

Should be there now, might have to refresh store for it to show up. @photogeek54 you have to change the status to 'active' for it to show up in the store. When status is 'new' it is added to the store, but won't show up in the list.

Go to the "Log" menu item and download the log, then PM it to me. I'll take a look. It should show up just like the OpenWeatherMap node server did.

Yes, you both seem to have the same issue. I just did a migration again on my Polisy and the node servers started without any issues. So I haven't been able to reproduce it. It looks like the node servers are simply crashing when they try to start but nothing in the log files provide any information on why they are crashing.

You may have exceeded the number of API calls your plan allows for in a day. The free plan is quite limited. Or you may have asked for more forecast data than what your plane allows. It looks like they may have reduced the number of days of forecast data you can get with the free plan from 7 to 6. The node server gets stuck if it's looking for 7 days but only sees 6.

When a node server is installed, it places node server configuration information in both PG3 and the IoX (in your case the i994 ISY). To "move" a node server would mean changing PG3's configuration and installing the node server on the new IoX. So that's basically what you have to do to migrate. Once you restore the i994's backup to the IoP, the IoP will have the node server configuration from the i994, but it will be wrong. When you switch PG3 to the IoP ISY, it should detect those node servers, but they'll be unmanaged. I believe you can then select the node server in the node server store and use the "re-install" to same slot option. That will correct the installation without requiring you to re-enter the node server custom parameters so everything should continue to work. It's been a long time since I've done any migrations from i994 to IoP and PG3 has changed a lot since the migration was first documented. Just follow the steps and it should be fine. If you encounter a problem. Stop and post here or open a ticket.

Yeah, that wasn't me that said to restore the PG3 backup, I would have liked to see a PG3x log after you tried starting a node server. I've done the PG3 -> PG3x migration on a Polisy a couple of times to test it, but that's the not same as having it run in the real world.

The status not showing up in programs is a bug. I can fix that. @Jimbo.Automates has nothing to do with this node server. It was written by @simplextech but he's no longer maintaining it, I am. Same for ST-Inventory. As I mentioned, the ST is set to true when the node server starts but there's nothing to ever set it false. Fixing this is a fair amount of work and right now it's not really a priority for me.

@JTsao based on your ticket, I don't think this is useful to you now, but might help someone else later. When PG3x migrates node servers from PG3, it leaves them in the disconnected state. You need to manually start the node servers after migration. You're post says you tried "rebooting, power cycling and restarting PG3x" and none of those steps will attempt to start the node servers when they've been previously stopped. PG3 and PG3x remember the last state of node servers. If you stop a node server, it won't be automatically restarted, you have to start it. In this case it's the migration process that stops all the node servers so they can be migrated, but it still relies on the user to start them back up.

Restart the admin console. You need to do that after installing any node server.

The status not showing up in programs is a bug. I can fix that. However, I don't think it ever changes as it looks to be hard coded to "True" in the node server. You can't use commands in the "if" part of a condition as these are things the IoX sends to the node server. They should be usable in the else/then portion to send the command on some trigger.

Great! Thanks for letting me know. It wasn't hard to add them, but you never know when you can't test.

I'm trying an experiment with this. I added support for both in version 1.0.9. I have no idea if this will work or not since I don't have any Sonos devices. So instead of replacing the existing 1.0.8 version, I added 1.0.9 as a second install option. I think you can simply re-install 1.0.9 over your existing 1.0.8 without having to get a new license, but I'm not sure. If it wants you to purchase it again, DON'T. I'll move it to the beta store. Since this does add new controls, you'll have to restart the admin console after re-installing and starting it to see those new controls.

Yes, you can run multiple copies of any node server. So in theory, you can run two copies each linked to a different smart bridge.

I have no idea what that means. The existing node server doesn't use either of those endpoints.

The node server can only link to one smart bridge.

Thanks @DennisC I meant to imply that I'd look into more, but I probably should have been more clear on that.

It won't automatically try update anymore. Each installed node server checks for updates when it is started and if it sees one available, it will display a notice and add an update button to the node server details page. Clicking the update button is a basically a shortcut to the purchases -> re-install page. It still should be doing global checks for updates every 8 hours same as it was before. It seemed to be working as intended when I tested it, but I only test with a small number of node servers (mostly my own since I can't make updates to other developer's node servers).

I don't see anything wrong. I did an update on my PG3 and it worked fine. I never had a pre 2.0 version installed on PG3x but re-installing seemed fine there. The only reason a re-install could fail is if there's a conflict between the version. That's one of the problems using git repositories to distribute node servers, if the git command fails, there's no way to automatically correct for that. Deleting the node server and then installing it should get the latest version unless something is really messed up in the current installation. Of course you do have to re-authenticate and re-configure if you do that. I have 2.0 installed but I can't get it to authenticate so maybe you don't want to update.

PM me the PG3x log package (Log menu, download log package). Then try going into the node server store, selecting the Holidays Google node server, click install, then click the re-install button and see if that works.

It's not a PG3 problem. It seems like something is really messed up w.r.t. the timezone info on the box. When write a simple program to display the time/date info I get: > console.log(date_ob.toTimeString()); 09:13:51 GMT-0900 (Pacific Standard Time) It should be Pacific Daylight Time which is GMT-0700. However Pacific Standard Time should be GMT-0800, so that's not right either. This appears to be a problem with the /etc/localtime file. It's not currently matching any existing timezone file. I'm guessing the timezone files were updated recently but the /etc/localtime file wasn't also updated to match. If I run sudo tzsetup -r it fixes the /etc/localtime to use one of the valid timezone files and then I get the right time in PG3 after restarting it.

Mine are off by -2 as well, I'm looking into it.

By default, addNode() won't change the name. But you can set the rename=True option to have it rename the node addNode(node, conn_status = None, rename = False) There's no node server differences between PG3x and PG3. You can continue to do your node server development on PG3 and they'll work the same on PG3x.

The changes were all in the server code, not the UI code. It mainly effects all the PG3 log messages.

Yes, It still only checks for the update when the node server is restarted. I'll see if I can make it check more often so you don't have to restart the node server. Thanks for pointing out the incorrect text. I'll get that fixed as well.