macjeff Posted February 15, 2022 Share Posted February 15, 2022 About to upgrade to PG3. Can I add the nodeserver twice once for Tempest and once for Air/Sky Jeff Link to comment
bpwwer Posted February 16, 2022 Share Posted February 16, 2022 Yes. You should also be able to just enter multiple station ID's in the configuration and you'll get nodes for all the devices associated with those station. The PG3 version is different from the PG2 version in configuration and the nodes that it creates. Link to comment
macjeff Posted February 16, 2022 Author Share Posted February 16, 2022 so will the nodes I have now convert when I do the upgrade? Link to comment
bpwwer Posted February 16, 2022 Share Posted February 16, 2022 No, there's no conversion and no upgrade. The PG3 node server is a different node server. I wasn't happy with the design choices I used in PG2 so I used PG3 as an opportunity to re-write it. Link to comment
macjeff Posted February 16, 2022 Author Share Posted February 16, 2022 8 minutes ago, bpwwer said: No, there's no conversion and no upgrade. The PG3 node server is a different node server. I wasn't happy with the design choices I used in PG2 so I used PG3 as an opportunity to re-write it. I know it’s not in this topic but I hope this is not the case with Climacell. I use the variables there in lots of weather related emails to show temperature today and tomorrow and things like that. I also used them in programs. Link to comment
bpwwer Posted February 16, 2022 Share Posted February 16, 2022 The PG3 version of Climacell should create the same nodes and node values as the PG2 version. Link to comment
macjeff Posted February 16, 2022 Author Share Posted February 16, 2022 Got weatherflow running but my forecast data is Sunday with all zeros I used the NOAA forecast code which may be the reason (KJYO) In my case also once fixed I assume forecast zero is today and 1 is tomorrow and so on Link to comment
bpwwer Posted February 16, 2022 Share Posted February 16, 2022 What do you mean you used the NOAA code? WeatherFlow uses the WeatherFlow station ID to identify the station you want to use for forecast data. Link to comment
macjeff Posted February 16, 2022 Author Share Posted February 16, 2022 also I have programs to monitor nodeservers. It first does a query and weatherflow is not there. I need Weatherflow nodeserver to show up under Your Devices in programs and then Query to be there Link to comment
macjeff Posted February 16, 2022 Author Share Posted February 16, 2022 5 minutes ago, bpwwer said: What do you mean you used the NOAA code? WeatherFlow uses the WeatherFlow station ID to identify the station you want to use for forecast data. Sorry I am doing a lot of pg2 to pg3 conversion and was thinking NOAA station ID. I did put the NOAA one in there but now I changed to my tempest station ID. Restarted several times. Still Sunday and Clear and 0's on every day Link to comment
bpwwer Posted February 16, 2022 Share Posted February 16, 2022 It only updates the forecast data every 5 minutes by default. Did you give it 5 minutes to pull data the first time? Link to comment
macjeff Posted February 16, 2022 Author Share Posted February 16, 2022 1 hour ago, macjeff said: also I have programs to monitor nodeservers. It first does a query and weatherflow is not there. I need Weatherflow nodeserver to show up under Your Devices in programs and then Query to be there I think this is the same for all your weather servers. Need a Query in programs. Its in the pg2 version Link to comment
macjeff Posted February 16, 2022 Author Share Posted February 16, 2022 20 minutes ago, bpwwer said: It only updates the forecast data every 5 minutes by default. Did you give it 5 minutes to pull data the first time? Yes it filled in. New issue- Weatherflow is asking for climacell info? See screenshot Link to comment
bpwwer Posted February 17, 2022 Share Posted February 17, 2022 1 hour ago, macjeff said: I think this is the same for all your weather servers. Need a Query in programs. Its in the pg2 version Most don't support query because the data is being polled at timed intervals, not by a manual query. Link to comment
bpwwer Posted February 17, 2022 Share Posted February 17, 2022 1 hour ago, macjeff said: Yes it filled in. New issue- Weatherflow is asking for climacell info? See screenshot That's a known bug in PG3. The browser gets confused and needs a refresh/reload to show the correct data. Link to comment
macjeff Posted February 17, 2022 Author Share Posted February 17, 2022 1 minute ago, bpwwer said: Most don't support query because the data is being polled at timed intervals, not by a manual query. I need to query the server itself. I have had it where a server goes down and comes back up and the program does not realize it. So I wrote a program that opens another program to query and then runs the first program again. So I just need True or False for online in each one Link to comment
Bumbershoot Posted February 17, 2022 Share Posted February 17, 2022 On 2/15/2022 at 3:58 PM, macjeff said: Can I add the nodeserver twice once for Tempest and once for Air/Sky This may be something entirely different that what you're asking for, but I was able to add an additional SKY unit to the hub that also connects to my TEMPEST unit, and the PG3 nodeserver shows data from both the SKY and the TEMPEST. Only one copy of the nodeserver running. Very handy. The SKY unit is measuring indoor data. Thanks for adding this functionality, @bpwwer! Link to comment
bpwwer Posted February 17, 2022 Share Posted February 17, 2022 17 hours ago, macjeff said: I need to query the server itself. I have had it where a server goes down and comes back up and the program does not realize it. So I wrote a program that opens another program to query and then runs the first program again. So I just need True or False for online in each one Ok, I understand. This is related to a bug in the ISY where the work-around is run a query. BTW, node server status is no longer true or false in PG3. It's connected, disconnected, and failed although I don't think most node server handle this correctly yet. Link to comment
macjeff Posted February 17, 2022 Author Share Posted February 17, 2022 29 minutes ago, bpwwer said: Ok, I understand. This is related to a bug in the ISY where the work-around is run a query. BTW, node server status is no longer true or false in PG3. It's connected, disconnected, and failed although I don't think most node server handle this correctly yet. so I hope you will add that. Meanwhile see the posts I put in Weatherbit. Had to revert to pg2 version. Actually have them both installed with two different API's. Pg2 version keeps on ticking. Pg3 I cant keep up for more than 30 min and only way to get it going again seems to be to delete the nodeserver and reinstall. Restarting it (or stop and start) does not get it working again. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.