johnnyt

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?

What search are you doing because I'm not finding much info. Searches for "zwave NWE/NWI" and variations of that brings up this thread and the UDI wiki, which doesn't explain it - or at least not the page I found. What does it do? Should I just leave it on (it defaults to off) or could it cause grief to do that?

I see people mentioning they're on zwave firmware 6.82 and 6.88 (ISY 500-series dongle) I'm only at 6.81. Could that be explanation for some problems and annoyances I've not been able to solve? Is there a way to update the firmware? Not finding must by searching forum.

I'm planning my move from 994iZW to IoP. Is the above saying that I won't need to exclude zwave devices from 994i and that IoP will just see them as they were on 994i when I restore the ISY backup (with the embedded zwave backup)? I didn't get that from reading other posts about migrating to IoP. Rather I was under the impression I needed to re-include my zwave devices one by one and manually realign all my 994i device name/numbers to use their inevitably new 'out of the box' device names and the new ZWxxx numbers starting at 001 when doing inclusion. This would change a lot.

There's a new firmware that "Fixed reporting behavior after power outage: if parameters 2 or 3 are set to any value, and parameters 10 or11 are set to disabled" this is the setting that unlinks the sensor from the relay https://www.support.getzooz.com/kb/article/727-zen17-universal-relay-change-log/

So I'm currently working on my 2nd ZEN17 that's not reliably reporting the sensor changes when they happen. Querying it is fine but I need it to trigger properly every time and it sometimes doesn't. The first one Zooz support agreed with me it was defective. It's on-going discussion right now for second one. I just sent ZooZ the attached list of some of the multiple errors from ISY logs - the worst kind: intermittent ones. Did I just get 2 bad units? (bought at same time from amazon - thankfully I don't have to fight to return them) What are other people's experiences with ZEN17 sensors? ZEN17-Errors-summary.xlsx

Just query the sensor node, no? I have to say I'm currently working on my 2nd ZEN17 that's not reliably reporting the sensor changes when they happen. Querying it is fine but I need it to trigger properly every time and it sometimes doesn't. One of my less frequent use cases (I have 3) is when utility power goes out and my UPS kicks in and closes a dry contact. The ZEN17 needs to tell my ISY (which is on the UPS) that power is out. I have my furnace and zwave Tstat on UPS so (in winter) ISY turns it down right away then again a bit more 30 minutes later in case it's going to be a long outage. I'm looking for others' experiences with ZEN17 sensors because I'm getting worried they're unreliable. It could be just 2 bad units from the same batch given I ordered them at same time. I don't know yet. I'm getting two other ones from different supplier so will see how those do. In the meantime would love to hear from others.

After a few exchanges with Zooz support, the answer regarding setting params 2/3/ to 4, 7, and 10 is: " yes, the setting should behave the same way but will have different wording depending on the setting programmed" So they're suggesting I check with ISY support regarding settings 4 and 10 not working like 7. I may do that at some point, although as long as one of the settings works and the only difference is the words used in the nodes and status, it's not critical.

First thing I did with both devices (after getting the latest firmware from Zooz) was include them on my spare zwave stick to do the firmware update. Then i excluded it from 2nd hub and included it on ISY where I changed param 2/3 then did the exclude/include again on ISY then changed the other params (10/11, 19/20). I think when I did the latter param changes at the same time as param 2/3, the values didn't stick for them. I'm not sure - only did that once then just decided to do them after the changes to param 2/3 and the required exclude/include from then on. Something I didn't do between playing with params 2/3 was a factory reset. Didn't seem to need it but then again settings 4 and 10 didn't work as advertised so maybe a factory reset was needed. At this point I'll just wait to see what Zooz support tells me.

I received a 2nd ZEN17 and used it to test a couple different settings to see if there's a setting that works better for my UPS dry contact feature. I left the relays linked to the sensor so I could hear the changes (relays for the 1st unit are being used so I don't want to start messing with them, not to mention exclude/include process.) I found the performance/behavior finicky. Some behavior didn't work the first time and some nodes didn't show up until I went through a couple of cycles closing/opening the sensors. I tried param2/3 at 4, 7 and 10. Only 7 worked properly, and it did work 100% fine when I used the 2nd unit with the UPS. So I did a test again with the unit in "production" and it worked fine today. So I'm thinking these things need to stabilize or something by going though a few cycles. Hopefully this is just an initial stabilization thing but will need to keep and eye and maybe do periodic drills to make sure things do settle and act reliably. I also found that setting 4 doesn't work properly - sensor never changes as one would have expected. (If not the expectation, then why put sensor nodes?) Same with setting 10, as discovered already on in this post. I reached out Zooz support to ask about this and for an explanation of the behavior for all the settings (stressing that I have the advanced settings "manual" so looking for more than that). If they provide something useful, I'll post it here.