johnnyt

Polisy not new but move to PG3 is new. It is (was) up to date prior to move as far as I know. Below is what I have installed running (on PG3) along with PG3 and ISY version numbers (am still on 994i, not using IoP yet). I have no other ST NS's and nothing running under PG2. I did have ISY inventory installed on PG2 and it wasn't working properly. Would work for about a day than stop working. Would that have any relevance here?

Ok i'll report to UD support but all I did was "purchase" and "install" NS on same day. I didn't think I had to do an update on the same day I installed it. Let's see what UD support says.

I did some packet sniffing on port 50222 (default "listen" port) and the "Destination IP" for the traffic from the hub is 255.255.255.255, which can't really be pushed to another VLAN or translated to the Polisy's IP address. Or at least I don't think it can because what I've tried that's worked in other situations (e.g. NAT'ing 192.168.100.1:50222 to 192.168.200.1:50222, or subnet to subnet) didn't work for this. Unless someone reading this knows more about networking than I do, I think I may have to stick ISY & Polisy on the VLAN with all the insecure IoT devices. I guess they are kind of IoT devices anyway.

I moved to PG3 a couple weeks ago and installed ST-Inventory. My ISY crashed 3 times in 2 days so I decided to stop 1 NS at a time starting with ST-Inventory. Not only did ISY not crash again for the few days I tested but when I restarted it, it crashed again within hours. Attached is ST-Inventory log. Here are the restarts in first round of testing (from ISY log) Time User Log Type Thu 2022/07/07 05:05:03 PM System Start Fri 2022/07/08 02:40:52 AM System Start Fri 2022/07/08 07:14:10 PM System Start And here's the restart time related to the ST-Inventory flood of errors in the attached log file Sun 2022/07/10 01:25:01 PM System Start ST-Inventory_7-10-2022_25135_PM.zip

Oh, I see. I think it's a VLAN issue. I have all my wireless IoT devices (a.k.a Internet of insecure things) on a separate VLAN (100) from ISY - and ISY is on separate (more trusted) VLAN (200) than my regular computers (VLAN 0). I do have firewall rules that allow all VLANs to connect to VLAN 100, but block VLAN 100 from connecting to other VLANs. How does the Node Server connect to the Tempest Hub? I'm wondering about the mechanism the NS uses because I noticed I didn't have to put in an IP address for the hub. I wonder if being able to put in the hub's IP address would solve the problem, and, if so, if you would consider adding that option? As you know, there are many horror stories of IoT devices not getting patched when critical vulnerabilities are discovered so I would think it's important to allow for segregation of those onto their own separate subnet or vlan.

I set log level to debug, restarted NS, and waited at least long poll (600) seconds (I assume). Attached is log. WeatherFlow_7-13-2022_54818_PM.zip

Ignore the question, There is a value field for VOC. I was distracted by the assessment field that's actually labeled "VOC Level" Instead, can you explain what the time value is - and if there's a way to convert it to something meaningful?

Thanks for doing this Node server. I have 7 Wave Plus devices. Does 1 API call return all info about all devices, or does it take one call per reading or per device? All I've done is set things up and one device has no data and the log reports "WARNING Controller:api_get: API Rate limit exceeded, waiting until 2022-07-09 16:45:23.514700 query the Airthings service." I set short poll to 120 secs, for what that's worth. Maybe this is just because of the rush of calls due to set up but for future reference how calls will it "cost" to update my 7 devices? Also, I'm not seeing the VOC level, just a "Clean" report. Can the level be provided instead, or is that all Airthings returns?

So not getting the error anymore (after upgrade) but am also not getting station data, and top node will go from "Hub Seconds Since Seem" of 0 right to 1657295307 and move up from there (since screenshot I took the number has gone up to 1657295727). See screenshots below

I did enter the same id for both and got the error. i also heard back from tempest tech support and there isn't a separate station ID for forecast. only the one associated with the weather station. In an urban setting one generally only needs one station. certainly I don't need 2 stations. will you be fixing things for those of us with only one station or is this NS only for people with more than one station?

I'm new to the tempest so i may be missing some key info but I can say I'm getting both the data from my station and forecast info on my app and when pointing to the web page for my station and this is with having bought only one station. I'll email tempest support to see if maybe I have two separate stations ID to provide - one for spot data and one for forecast info

Installed this NS for my new Tempest Wether Station yesterday and am getting the following error: 2022-07-02 08:39:22,072 Thread-730 udi_interface ERROR weatherflow:forecast_query: local variable 'value' referenced before assignment I'm a bit confused about the idea of putting my station ID in twice but if I don't put it in as local I get a message that at least one must be entered. Below are my settings (I deleted token for screenshot but there is one and am not getting any error messages about that). What am I not understanding needs to be done?

just moved to PG3 NS from PG2, which was working fine. It says connected but also has message saying: Hostname or IP address for EnvisaLink device missing in configuration ip address and password are fine and I can browse to the device - see further below.- but none of the devices are seen by ISY (my programs are all messed up)

Hi @JimboAutomates. Just wondering if this is still something you're planning to do?

My question is not about where PG3 is running. it's about what ISY instance it's pointing to.

So if I go explore a PG3 store it links the purchase to the un-configured IoP instance I'm not yet using. This might be because I haven't linked the ISY994i yet (actually I de-linked it so it's not talking to my ISY994i until I need it to.) I can add the ISY994i and link to that, but this display nuance suggests I'm getting a license for a particular ISY instance So can you/someone please confirm I can just change the ISY instance I point to later, e.g. move license from 994i to IoP?

if I buy/install a PG3 NS on my ISY994i then make the move to IoP a couple months from now, will I need to buy the NS again to link it to my IoP or will I be able to transfer the license over?

I'm not seeing a PG3 ISY inventory in either the production or non-production store, so please let me know what I'm doing wrong. Here are the items just before and just after the "I" items in the alphabetical listing that I see for each PG3 store: The PG3 version of OpenWeatherMap is not free. It's not a lot of money but given I may only use it for a couple weeks while I set up my Tempest and WeatherFlow NS (also not free) why pay for both if I don't have to. I'll use the money to buy the ISY inventory NS if you tell where I can get it. So to go back to my 1st question, which wasn't answered: if I don't find (or want) a NS on the PG3 store, will the restore just ignore it?

Can I cherry pick what I move to PG3? Example 1: I use ISY Inventory and there's no PG3 version. If I do a restore of my PG2 backup into PG3, it will have the settings for the non existent ISY Inventory NS - will they just be ignored? Example 2: I use PG2 OpenWeatherMap and my plan it to stop using it and move to PG3 WeatherFlow to support my (soon to arrive) Tempest Weather Station. Can I just delete the OpenWeatherMap node from PG3 once it's been restored from the backup and simply keep using my PG2 OpenWeatherMap NS until I'm ready to move to WeatherFlow NS?

I clicked on PG3 production store link for WeatherPoly and get the following 404 error. Where can I go to get more info? Did I read somewhere it works with Tempest Weather System?

ok this cliches it. Clearly it isn't possible to do the equivalent of taking an image of one Polisy (the whole thing, including settings, config, PG2, PG3, IoP, etc.) and restoring it onto another Polisy in one step (again everything at once, not just IoP, PG2, and PG3 all independently, which I do know how to do) Thanks.

not on the Polisy UI (black screen). where do you see it? I'm not running IoP here - the screenshot with the backup option highlighted in the menu is of my ISY 994i.

not at all. here are screenshots of Polisy and ISY menu.

I'm looking at getting a second Polisy to have a spare (or test unit) on hand. I've learned the hard way that hardware issues can take a while to fix (I live in Canada and every time I've had to get something from UDI, it's 2+ week of waiting/downtime). I do see how to backup/restore Polyglot (PG2 and PG3 separately) but what I'm looking for is akin to the ISY backup and restore, which will duplicate what I have on one ISY to another. Is there such a thing for Polisy? If not in web UI (I didn't find anything) Is there something I can do using SSH, e.g. copy a folder structure from one to the other?

By Default NWI/NWE is OFF in ISY. That suggests to me it can cause problems, otherwise, if it was only goodness, it would be ON. So what's bad or problematic with it? Should I turn it ON and leave ON, or only use it when including known supported NWI devices then turn it OFF right away?