Everything posted by GTench
-
IOP not showing up in the Launcher
I had to shut down my network including polisy to rearrange things to a rack. Now that I have everything back up I cannot get the launcher to show IOP anymore. I can log into polisy (polygot3) ok and IOP seems to be running since it responds to various triggers ok but cannot see it in the launcher or log into it. I tried clearing java cash but that did not solve the problem. Any help would be appreciated. The IP address of polisy is the same as it has always been thanks, Gary
-
PG3 (and 2) Nodes won't run
but... it does seem to be working ok
-
PG3 (and 2) Nodes won't run
I have this problem just now with one of my node servers (Yolink). After I did a restart it says connected but not running. Tried this 3 or 4 times with the same result
-
Reboot Node Server
Thanks. I know the Yolink developer is working on the issue and has just posted an update. Just thought it might be useful in perhaps some other situations
-
Reboot Node Server
I find the Yolink node server stops responding randomly over a few days; so, I thought I would just issue a restart command to it once a day
-
Reboot Node Server
Is there a command in IoP to restart a specified node server?
-
Insteon acquired and servers coming back up
Not sure if anyone has posted this yet https://staceyoniot.com/podcast-meet-insteons-new-ceo/
-
Rainfall Totals fields are empty
Yes works perfectly...thanks
-
Rainfall Totals fields are empty
I noticed that the IoP rainfall totals fields were empty this morning. I think that they have been populated in the past. I believe these correspond to the tempest fields GV6, GV7, GV8. Just wondering if this is the same decimal point issue that you corrected for ETO. Regards, Gary
-
ETO always zero
Works great now. ETO now shows up in my IOP. Thanks again!
-
ETO always zero
Ahhh that makes sense. I will do as you suggest. Many thanks for looking into this for me
-
ETO always zero
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
-
ETO always zero
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
- ETO always zero
-
ETO always zero
Just noticed that ETO shows up as 3.17... if I look under the node server nodes but shows up as 0 in IoP?
-
ETO always zero
Thanks, I am using the same version but I still see 0 in the weatherflow node in IoP
-
ETO always zero
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
-
Announcements with Yolink and speaker
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.
-
Announcements with Yolink and speaker
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
-
Announcements with Yolink and 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
-
Latitude and longitude coordinates
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.
-
Latitude and longitude coordinates
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
-
Polisy and X-10
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
-
PG3 on Polisy
Thanks for the clarification. Everything is now working great for me now on Polisy with IoP and PG3
-
My Positive Experience moving EnvisaLink-DSC from PG2 to 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