
GTench
Members-
Posts
284 -
Joined
-
Last visited
Everything posted by GTench
-
This is what I see in the event log Tue 12/27/2022 03:31:00 PM : ---- Start Adding Devices - S2 Standard --- Tue 12/27/2022 03:31:00 PM : [ZWAVE-INCL-S2STD] Start Include S2 Standard highpower=true Tue 12/27/2022 03:31:00 PM : [ZWAVE-INCL-S2STD] Added 'CommandAdded' callback 0x802beb468 Tue 12/27/2022 03:31:00 PM : Z-Wave Listening for Z-Wave devices to add to the network Tue 12/27/2022 03:31:05 PM : Z-Wave Z-Wave device detected, start adding to network Tue 12/27/2022 03:31:06 PM : Z-Wave Z-Wave device detected, retrieving info Tue 12/27/2022 03:31:06 PM : Z-Wave Z-Wave device added Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x20 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x26 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x33 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x59 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x5A Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x5E Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x70 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x72 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x73 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x7A Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x85 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x86 Tue 12/27/2022 03:31:06 PM : Z-Wave Idle Tue 12/27/2022 03:31:06 PM : Z-Wave Idle Tue 12/27/2022 03:31:06 PM : Z-Wave Idle Tue 12/27/2022 03:31:08 PM : [Device 5] Waiting on interview complete (400 ticks remaining) Tue 12/27/2022 03:31:12 PM : [Device 5] All interviews are done Tue 12/27/2022 03:31:12 PM : ZWAVE-WORKQ-34 Queue sync device 5 Tue 12/27/2022 03:31:12 PM : ZWAVE-WORKQ-34 Start sync device 5 Tue 12/27/2022 03:31:12 PM : [ZWAVE-SYNC 5] Device mismatch, Removing all existing ISY files/objects for Z-Wave device Tue 12/27/2022 03:31:12 PM : [SYNC-DEVICE 5.0] Set commands will now be accepted by the controller Tue 12/27/2022 03:31:12 PM : [ZWAVE-SYNC 5] Not multichannel Tue 12/27/2022 03:31:12 PM : ZWAVE-WORKQ-34 Finished sync device 5
-
I upgraded to 5.5.0 and have the ZMATTER board in my Polisy. I pushed the zwave to matter button, restarted Iox and as expected my Zwave nodes were gone. I then tried to add an anotec zwave repeater. Iox dialogue box says it is interviewing then disappears. The repeater blinks green which should I believe indicate that it is paired but I do not see its node in Iox. I have tried resetting the repeater and retrying pairing without success. Any suggestions? thanks, Gary
-
yes... I ordered and received the ZMATTER board from them a week or 2 ago. I installed it into my Polisy a few days ago Gary
-
Thanks... I used TOP. HTOP was not installed. Looks like I also see the high cpu usage. I am only using 3 message annoucement yolink devices currently
-
Does HTOP need to be installed? If so just wondering how. I would like to check my usage as well. thanks, Gary
-
thanks... I submitted a ticket. I am still getting a large number of entries in the error log file
-
OK thanks. I am using IOP with latest firmware
-
I seem to get a large number of entries like this in the error log file. Just wondered what they are and if I should be concerned thanks, Gary Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(6323)->36895 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(6323)->36895 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(6323)->36895 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(59241)->3689 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(59241)->3689 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(59241)->3689 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(59241)->3689 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(20890)->3689 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(40095)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(40095)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(40095)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(36825)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(36825)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(36825)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(36825)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(16020)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:56 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(10036)->3689 Sun 2022/11/20 01:42:56 PM 0 -10108 Check log Sun 2022/11/20 01:42:56 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(10036)->3689 Sun 2022/11/20 01:42:56 PM 0 -10108 Check log Sun 2022/11/20 01:42:56 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(10036)->3689 Sun 2022/11/20 01:42:56 PM 0 -10108 Check log Sun 2022/11/20 01:42:56 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(42489)->3689 Sun 2022/11/20 01:42:56 PM 0 -10108 Check log
-
oh I did change the ethernet adapter on the computer that I use to access IOP but network/internet works fine through it
-
OK, I got it going by adding it in the finder by entering http://192.168.2.117:8080. Not sure why the finder could not find it by itself though?
-
No its the same router. In fact is was not powered off just disconnected from the switch while I rearranged things thanks
-
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
-
but... it does seem to be working ok
-
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
-
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
-
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
-
Is there a command in IoP to restart a specified node server?
-
Yes works perfectly...thanks
-
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
-
Works great now. ETO now shows up in my IOP. Thanks again!
-
Ahhh that makes sense. I will do as you suggest. Many thanks for looking into this for me
-
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
-
Just noticed that ETO shows up as 3.17... if I look under the node server nodes but shows up as 0 in IoP?