macjeff

Sorry I did try that. It worked but then it failed again about a min later. After a reboot its working fine now for a while.

Today I installed the new version of Pg3. It came backup fine. The last version broke backup so I wanted to do a backup I ran a backup of PG3 and it worked but all of my node servers went to fail status (I reported) I rebooted PG3 and it came back up fine and still running but I checked each Node server. Your logs started over today with the reboot of Pg3. I downloaded the complete package also if you want it but it only goes back to this AM (EDT). But it seems to be working. I even had a sensor offline so I changed the battery and it came online inside ISY Jeff

Just ran the new update. Backup took a while but worked. And I tried it twice. When I do a backup ALL the node servers go to fail. I did grab a log. I rebooted PG3 after that finished and they all came back online.

Do I need to worry about these? 2022-03-16 07:40:53,794 Thread-7358 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 07:40:53,794 Thread-7358 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 07:43:54,448 Thread-7362 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 07:43:54,449 Thread-7362 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 07:43:54,450 Thread-7362 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 07:43:54,451 Thread-7362 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 07:46:53,876 Thread-7367 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 07:46:53,877 Thread-7367 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 07:46:53,878 Thread-7367 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 07:46:53,879 Thread-7367 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 07:49:53,930 Thread-7371 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 07:49:53,932 Thread-7371 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 07:49:53,933 Thread-7371 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 07:49:53,933 Thread-7371 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 07:52:54,002 Thread-7375 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 07:52:54,003 Thread-7375 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 07:52:54,004 Thread-7375 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 07:52:54,005 Thread-7375 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 07:55:53,900 Thread-7379 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 07:55:53,902 Thread-7379 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 07:55:53,902 Thread-7379 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 07:55:53,903 Thread-7379 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 07:58:53,908 Thread-7383 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 07:58:53,909 Thread-7383 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 07:58:53,910 Thread-7383 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 07:58:53,911 Thread-7383 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:01:54,313 Thread-7387 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:01:54,315 Thread-7387 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:01:54,316 Thread-7387 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:01:54,316 Thread-7387 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:04:53,991 Thread-7391 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:04:53,992 Thread-7391 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:04:53,993 Thread-7391 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:04:53,994 Thread-7391 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:07:54,014 Thread-7395 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:07:54,015 Thread-7395 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:07:54,015 Thread-7395 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:07:54,016 Thread-7395 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:10:53,999 Thread-7399 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:10:54,001 Thread-7399 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:10:54,001 Thread-7399 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:10:54,002 Thread-7399 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:13:54,876 Thread-7403 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:13:54,877 Thread-7403 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:13:54,878 Thread-7403 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:13:54,879 Thread-7403 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:16:53,930 Thread-7408 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:16:53,932 Thread-7408 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:16:53,933 Thread-7408 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:16:53,933 Thread-7408 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:19:54,004 Thread-7412 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:19:54,006 Thread-7412 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:19:54,007 Thread-7412 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:19:54,007 Thread-7412 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:22:54,078 Thread-7416 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:22:54,079 Thread-7416 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:22:54,080 Thread-7416 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:22:54,081 Thread-7416 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:25:54,073 Thread-7420 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:25:54,074 Thread-7420 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:25:54,075 Thread-7420 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:25:54,075 Thread-7420 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:28:54,064 Thread-7424 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:28:54,065 Thread-7424 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:28:54,066 Thread-7424 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:28:54,067 Thread-7424 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:31:54,023 Thread-7428 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:31:54,024 Thread-7428 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:31:54,025 Thread-7428 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:31:54,026 Thread-7428 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:34:54,109 Thread-7432 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:34:54,111 Thread-7432 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:34:54,111 Thread-7432 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:34:54,112 Thread-7432 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:37:54,041 Thread-7436 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:37:54,042 Thread-7436 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:37:54,043 Thread-7436 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:37:54,044 Thread-7436 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:40:54,007 Thread-7440 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:40:54,008 Thread-7440 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:40:54,009 Thread-7440 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:40:54,010 Thread-7440 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:43:54,879 Thread-7444 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:43:54,880 Thread-7444 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:43:54,881 Thread-7444 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:43:54,881 Thread-7444 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:46:53,999 Thread-7449 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:46:54,004 Thread-7449 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:46:54,005 Thread-7449 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:46:54,006 Thread-7449 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:49:54,392 Thread-7453 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:49:54,394 Thread-7453 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:49:54,394 Thread-7453 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:49:54,395 Thread-7453 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:52:54,195 Thread-7457 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:52:54,196 Thread-7457 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:52:54,197 Thread-7457 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:52:54,198 Thread-7457 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:55:54,041 Thread-7461 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:55:54,042 Thread-7461 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:55:54,043 Thread-7461 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:55:54,044 Thread-7461 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 08:58:54,026 Thread-7465 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 08:58:54,027 Thread-7465 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 08:58:54,028 Thread-7465 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 08:58:54,029 Thread-7465 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:01:54,076 Thread-7469 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:01:54,078 Thread-7469 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:01:54,078 Thread-7469 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:01:54,079 Thread-7469 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:04:54,182 Thread-7473 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:04:54,183 Thread-7473 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:04:54,184 Thread-7473 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:04:54,185 Thread-7473 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:07:54,198 Thread-7477 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:07:54,200 Thread-7477 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:07:54,200 Thread-7477 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:07:54,201 Thread-7477 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:10:54,251 Thread-7481 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:10:54,252 Thread-7481 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:10:54,253 Thread-7481 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:10:54,254 Thread-7481 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:13:54,783 Thread-7485 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:13:54,785 Thread-7485 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:13:54,786 Thread-7485 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:13:54,787 Thread-7485 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:16:54,049 Thread-7490 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:16:54,050 Thread-7490 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:16:54,051 Thread-7490 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:16:54,051 Thread-7490 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:19:54,359 Thread-7494 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:19:54,360 Thread-7494 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:19:54,361 Thread-7494 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:19:54,362 Thread-7494 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:22:54,867 Thread-7498 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:22:54,869 Thread-7498 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:22:54,870 Thread-7498 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:22:54,871 Thread-7498 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:25:54,346 Thread-7502 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:25:54,348 Thread-7502 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:25:54,349 Thread-7502 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:25:54,350 Thread-7502 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:28:54,143 Thread-7506 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:28:54,144 Thread-7506 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:28:54,145 Thread-7506 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:28:54,145 Thread-7506 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:31:54,201 Thread-7510 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:31:54,202 Thread-7510 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:31:54,203 Thread-7510 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:31:54,204 Thread-7510 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:34:54,293 Thread-7514 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:34:54,295 Thread-7514 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:34:54,296 Thread-7514 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:34:54,297 Thread-7514 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:37:54,281 Thread-7518 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:37:54,282 Thread-7518 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:37:54,283 Thread-7518 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:37:54,284 Thread-7518 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:40:54,124 Thread-7522 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:40:54,126 Thread-7522 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:40:54,127 Thread-7522 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:40:54,128 Thread-7522 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:43:54,977 Thread-7526 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:43:54,978 Thread-7526 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:43:54,979 Thread-7526 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:43:54,979 Thread-7526 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:46:54,170 Thread-7531 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:46:54,172 Thread-7531 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:46:54,173 Thread-7531 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:46:54,173 Thread-7531 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:49:54,293 Thread-7535 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV1 2022-03-16 09:49:54,294 Thread-7535 udi_interface.node ERROR node:setDriver: ei_0_1:Ecobee - Invalid driver: GV3 2022-03-16 09:49:54,295 Thread-7535 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV1 2022-03-16 09:49:54,295 Thread-7535 udi_interface.node ERROR node:setDriver: ei_0_2:Ecobee - Invalid driver: GV3 2022-03-16 09:52:03,527 MainThread udi_interface INFO polylogger:se

rg

Can you at least show the latest. The winter storm warning came out many hours after the advisory. And I checked both and they have issue times and dates.

Video attached. We had a winter weather advisory upgraded to a winter storm warning. So basically there are two warnings at the same time. We also had a wind advisory but that never shows up in the video at all. So two issues- One is what if there are two advisories/warnings at the same time. Second what if one is upgraded. The problem is they dont delete the old one so really the upgraded one overlaps the other and probably only way to know is the other is newer. So I would always display the most serious one unless you can display them all. Ignore the error that pops up. I hit query too many times in a row I think 808604954_ScreenRecording2022-03-12at2_39_51PM.mov

I can confirm the backup button seems to do nothing

See screenshot. I have several of these for aquariums and hot tub. They all are missing two fields. Maybe its not being reported for this device as my regular tags are filled in. But if thats the case can you put N/A or something in the fields. When I see blank fields it makes me think its not querying all the data.

I assume you dont need the log now?

Old version 3.1.3 now installs and starts up. Thats better than nothing!! Will watch for a new upload of 3.1.4 (later timestamp) thanks

Yes. Almost every Node server I own was updated today. They all updated fine EXCEPT wireless tag. Its stuck at 3.1.3 and wont start anymore. As a test I tried to install it again in another slot and after 5 minutes nothing happens and that slot is still available. I had this happen with other nodeservers. ST Inventory, Ecobee, etc. and they had to do something and then it worked about a day later. But for now I am down with Wireless Tags because I cant get back to the 3.1.3 version and yes I did update Pg3 to latest version BEFORE I did the updates today due to the install bugs it said it fixed.

Yep that pretty much sends it up but I think its the speed of the packets. Either way the refresh does not seem to hold so for now if you have to restart your ISY there is one more step. Good news is if you are away and there is a power outage you can go into Alexa app and disable and reenable from remote

I read it as the last thing you did was install the _03 so I was wondering if that changed anything.

That works also. I sent the command to list all so people could use it to check everything and its simple But you are good!!! Now try the disable and re-enable fast. and hopefully it fixes IFTTT If not then use variables with the Messaging command

Just ssh in and type pkg version It will list all packages. Isy should have the _3 after it. But your right the console does not show the _subversion.

For all fairness, when it first came out the SAY option was the only option. I worked with them to allow messages to all devices. So no one should have to use IFTTT for messaging purposes unless there is some other need.

You dont use SAY. Say is for only the alexa you are talking to so thats why IFTTT can only use one. You have to use MESSAGING. Use messaging. Under that choose send announcement. Type what you want to say Hit next and then it asks you which devices. Choose ALL DEVICES and then it announces in all of them. Screenshots below

Thanks for posting Let me send a better instructions since I was mistaken 5.4.0_2 and 5.4.0_3 fix the issue not 5.4.0 even. I mis-spoke earlier and apologize. sudo service isy stop sudo pkg upgrade isy sudo service isy start pkg version check ISY is now 5.4.0_3 NOW it may work right away or it may not. If not go to Alexa app, skills, search for ISY optimized for Smarthome v3, disable it. IMMEDIATELY reenable it. Now it should work. If you reboot your ISY or your Polisy reboots due to power failure (You should put your Polisy on a battery backup but not the PLM) then you will have to do the alexa step again most likely

I dont use it either. I think it used to be the only way. Now using real motion, contacts, or locks or a variable is the way I think is superior but thats my opinion and I dont want to be attacked for my opinion

No. ISY shows the current x.x.x version not the _version. You would have seen it in the log as it was installing with SSH It would say do you want to install with 5.4.0_3 at the end and you say Y and it installs Sudo and do PKG VERSION and it will show you all the versions. My ISY shows _03

I know that inside alexa the device is being changed but Michel has told me he is 100% sure the devices are being blacklisted when the ISY reboots. They have to write in some throttling so this does not happen. For many of us (and every time for me) all I have to do is disable and re-enable the skill after each ISY reboot. That is a band aid until the permanent fix comes out. If it does not solve IFTTT then I cant help. Maybe someone will find a fix for that. But I literally spent all day Thursday and Friday and even restored my ISY from backup trying to fix this. I can confirm it does not work although Amazon does see the motion sensor or locks change in their app so the data is getting there but at that point the routine wont trigger due to blacklist. btw...I do know how they work. I was on the prototype team for Alexa when all the Echo could do is tell you the weather and play music and tested for UD all the way including routines. I have a master ticket in with Amazon on this and upper level can see the issue but they said its the Skill. Universal Devices said they will work on it but it may not be right away. So I came up with the workaround. I am sorry if it does not work for you, but it has for many.

You are posting in the wrong topic then. The topic is "Routines using ISY variables as motion sensors have stopped working" We are talking about ISY Variables used as motion sensors (and actually real motion and contact sensors too as well as LOCKs) do not trigger routines The IFTTT should be in another topic about IFTTT. That may still be broken but for the topic of this forum the fix we have has worked on several installs. If its not on yours I will try to help but I cant support IFTTT as I dont know it.

I dont even have an IFTTT account and have about 50 different anoucements with routines. You use Variables. A lot faster than IFTTT. Set variable to 1 when an event you want to announce occurs in a program Expose the variable to alexa as a motion sensor with motion value of 1. Create routine (SEE SCREENSHOT) where when the motion sensor (fake variable sensor) detects motion announce. I chose all devices and also send a notification to the phone. IFTTT is slow. I tried it once and killed it.

what verson of the ISY There is a 5.4.0 and a 5.4.0_2 and 5.4.0_3. sudo service isy stop sudo pkg upgrade isy sudo service isy start should bring in 5.4.0_3 which I think is newest. Wonder if 5.4.0 even has issue. I actually just realized I only did this test on _2 and _3. But it worked for others including me several times.