GTench

Thanks very much for the suggestions. I appreciate it. The ETo value in PG3 is updating each day but does not appear in IoP. As far as I can tell this is the only value that is missing in IoP. Yesterday I deleted and reinstalled the node server. Following that I then noticed that ETo in PG3 was set back to 0 as I believe is correct. This morning I checked in PG3 and ETo had been updated to 2.903759505852784 but was still 0 in IoP. I checked the node server log file but there is no entry at midnight perhaps because it was not in debug mode. I have now set the log file to debug and now I see log entries occurring for the many data value updates. I will leave it in debug mode and check tomorrow for the ETo line around midnight. I am using metric units with tempest. I have now changed to all imperial to see if this has an effect... a long shot I know I had a look in the PG3 log file and these are the entries around midnight that seem to deal with ETo 7/28/2022, 24:00:46 [pg3] info: [00:0d:b9:53:d8:14_6] setup reporting command DOF 7/28/2022, 24:00:46 [pg3] debug: Scheduling http://192.168.2.117:8080/rest/ns/6/nodes/n006_setup/report/cmd/DOF to group commandGroup 7/28/2022, 24:00:46 [pg3] error: ISY Response: [Try: 1] [00:0d:b9:53:d8:14] :: [404 - OK] :: 18.856618ms - http://192.168.2.117:8080/rest/ns/7/nodes/n007_controller/report/status/ETO/2.903759505852784/106 7/28/2022, 24:00:46 [pg3] debug: Scheduling http://192.168.2.117:8080/rest/ns/7/nodes/n007_controller/report/status/GV4/3/57 to group statusGroup 7/28/2022, 24:00:46 [pg3] debug: MQTT Results: [ns/status/00:0d:b9:53:d8:14,7] :: {"set":[{"address":"controller","driver":"ETO","value":"2.903759505852784","uom":106}]} 7/28/2022, 24:00:46 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:0d:b9:53:d8:14_7] {"set":[{"address":"controller","driver":"ETO","value":"2.903759505852784","uom":106}]} 7/28/2022, 24:00:46 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:53:d8:14] :: [200] :: 38.373639ms - http://192.168.2.117:8080/rest/ns/6/nodes/n006_setup/report/cmd/DOF 7/28/2022, 24:00:46 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/frontend/clients/ed35df13-348f-453e-8601-aeee79ef5703 to broker pg3_broker

I believe that I have that set up correctly. I will attach another screen shot. But I see that ETO is being calculated when I look at the nodes but it is not being passed back to my IoP. It is non zero in the nodes display but zero in IoP

screen shots

Just noticed that ETO shows up as 3.17... if I look under the node server nodes but shows up as 0 in IoP?

Thanks, I am using the same version but I still see 0 in the weatherflow node in IoP

I just set up a tempest weather station a couple of days ago and added the weatherflow node server to my polisy. I added the weather station ID under forecast and added the new key for the station ID and set its value to local. Everything seems to be fine except that the yesterday's ETO is always zero. Am I missing something in the node server setup? thanks, Gary

Thanks again. I got a Yolink hub and speaker and gave it a try. I have a camera that looks at my front porch. It is connected to a blue iris system and blue iris node server that detects people when they are at the porch. I set up a program such that when blue iris detects people there the yolink node server announces it over the yolink speaker. Works quite well.

Thanks. Just a couple of questions if you don't mind. Can the speaker be set up to speak different phrases depending upon what triggers it and have you tried using the node server to trigger a phrase from the speaker

I don't have Yolink but I see that they have a speaker that can be used for making user defined announcements. Just wondering if the Yolink node server would allow me to trigger various announcements via IoP programs if I get a Yolink system and the node server thanks, Gary

OK thanks guys. This caused me much confusion when I installed the weather node servers. I originally entered the latitude and longitude values for Toronto as taken from the IoP configuration into the node server's location field. The weather data that I was getting back from the node servers did not match very well with what was occurring locally here. When I entered the values from the google search, the node server weather data matched much better to what I was seeing locally. When I tried to correct the IoP longitude coordinate to be negative, I got an IoP error saying that it was illegal.

If I look up Latitude and longitude coordinates for say New York in google I would get 40.730610, -73.935242. But in IoP under Configuration I see 40.7167, 74.0167. Not questioning the small absolute value differences but why is the longitude negative in one case and not the other? thanks, Gary

I only have 1 legacy X10 device - a baseboard heater thermostat. It still responds to 0n/Off commands from IoP and shows up in my list of devices. It has been I/S for many years now and was just carried over from the ISY944 to IoP port. Interestingly enough, I do not see where you would set its address in IoP if I wanted to change it. Gary

Thanks for the clarification. Everything is now working great for me now on Polisy with IoP and PG3

Thanks for posting this. My experience was very similar but I had to do the update and save on each program that referenced one of the alarm zones. I use the Envisalink motion zones mostly to trigger lights. I found PG2 to be surprising quick in this regard. PG3 seems to be even quicker. I'm very happy overall. Gary

Here is the process that occurred in a bit more detail I started off with 3 connected node servers in PG2 and showing up properly in IoP and functioning well. The same 3 node servers were also present in PG3 but were unmanaged with no obvious way to remove them. I did a backup of PG2. I deleted all 3 node servers from PG2, checked in IoP and there were no node servers now shown there. I did however still have the 3 phantom node servers in PG3. I tried numerous reboots of PG2, PG3, and polisy. Checked in IoP and PG2 again and there were still no node servers there. Checked in Pg3 and the 3 phantom node servers were still there but there was still no button to delete them. I tried numerous times to update PG3 from the PG2 backup with no success. I then installed a random free node server from the store in slot 4 as slots 1 to 3 were taken up by the phantom node servers. When the slot 4 node server finished installing I watched the PG3 screen as the phantom node servers vanished. I then deleted the slot 4 node server but cannot recall for sure if I tried to load PG3 from my PG2 backup again. PG3 now showed no node servers installed. I then manually installed my 3 node servers. Since I only had 3 of them, this was not a big deal other then renaming all my zones in IoP. I thought a fresh install might be a good thing to do kind of like reinstalling an OS to clean things up I should point out a couple of things that likely impacted my ability to use the PG2 backup based on comments in previous threads. My EnvisaLink-DSC node server is configured differently from the defaults in the store; e,g., I added a parameter to set the number of zones higher than the default - I have 48 vs the default of 8. I also added more parameters that are not present in the default settings. So there is not an exact match between the PG2 nodes in my backup vs the default set from the store. Also I notice that PLEX starts of with 1 node but my PG2 backup has multiple nodes that were dynamically added over time as new devices accessed PLEX. I also believe that some of the PG2 nodes, although named the same, appeared in a different order than some PG3 nodes but I cannot be sure now that I have deleted the PG2 node servers. Gary

I think I tried that and it did not work for me but I cannot remember for sure

Tried that but did nor work for me. After deleting PG2 nodes I was still left with 3 phantom unmanaged nodes in PG3. A restore from PG2 backup did nothing. If I try to install a new node server from the store it wants to go to slot 4 berceuse the phantom node servers are taking up the first 3 slots. So, what I found worked to get rid of the unmanaged 3 PG3 node servers was to just install any node server in the next available slot, 4 in my case. This then removed the unmanaged node servers. I then deleted the slot 4 node server and proceeded to install my 3 node servers into slots 1 to 3 as they were in PG2. Gary

OK thanks. I have 3 node servers: Blue IRIS, PLEX, EnvisaLink-DSC. I purchased the EnvisaLink-DSC. I backed up PG2. PG3 shows the 3 node servers as unmanaged. I deleted the 3 from PG2. I opened IoP and saw that they were gone there. I restored from PG2 backup in PG3. The 3 node servers still show up as unmanaged in PG3. Should I now just install the 3 node servers on PG3 but will this leave me with a managed and unmanaged version of each in PG3? thanks, Gary

Thanks... unfortunately they cannot be changed in the custom parameters. I edited them in ISY.

So if for example, I delete my EnvisaLink-DSC node server in PG2 and restore a PG2 backup to PG3 will my IoP show all of the renamed Zone names from IoP as they were when connected to PG2 or will I have to rename all my zones again as I did when I first installed it on PG2. When EnvisaLink-DSC was first installed on PG2 it used default zone names in IoP (Zone1, Zone2, etc). I am hoping not to go through the renaming process again, thanks, Gary

I bought the one from amazon.ca and is working fine for me with Polisy. Gary

Thanks to both. I have Polisy, Network Resources, and the Portal. I will investigate your suggestions and get back if I have any further questions. What I wanted to do was get a pop up when I get motion triggered on my front porch by Blue Iris. I tried just using email but the cell phone polling for new mail is not as fast as I would like. I get some capability with the blue iris app but I want to tune out some false positives with ISY logic like if the front door is open (using its alarm contact status) then don't send any alerts Gary

Just wondering if there is a way to get the app to open a pop up message and/or play a tune on my cell phone based on an isy event or trigger thanks, Gary

also the transmit loop problem happened sometime in the night and I did not have any indication of electrical disturbances however it is possible that something very brief could have happen that I am not aware of

I should add a bit more info... the 8 button keypad dimmer caught in the transmit loop also caused a few lights to turn on (some on switchlics and some on plug in modules) and some but not all to turn off. One light plugged into a module did this twice. The on/off times were minutes apart. None of the lights that turned on or off were linked to the keypad dimmer. I power cycled the keypad dimmer (did not to a restore) and that solved the problem. The keypad dimmer now flashes green when buttons are pushed and there is no continuous red led indicator on