garybixler

Michel Hi, I physically relocated a device supported by a node server. After moving I had to restart Polyglot to get it to poll again. I may have restarted Polyglot a second or third time. What I started to see on the logs of all the nodes was tripple events. Example: 2019-11-08 10:18:04,683 [Controller] [DEBUG] Home:1 test:11ce08fb58c09a:wTag12F:set_seconds: 207 2019-11-08 10:18:04,683 [Controller] [DEBUG] Home:1 test:11ce08fb58c09a:wTag12F:set_seconds: 207 2019-11-08 10:18:04,683 [Controller] [DEBUG] Home:1 test:11ce08fb58c09a:wTag12F:set_seconds: 207 2019-11-08 10:18:04,684 [Controller] [INFO ] Updating Driver 11ce08fb58c09a - GV14: 207, uom: 25 2019-11-08 10:18:04,684 [Controller] [INFO ] Updating Driver 11ce08fb58c09a - GV14: 207, uom: 25 2019-11-08 10:18:04,684 [Controller] [INFO ] Updating Driver 11ce08fb58c09a - GV14: 207, uom: 25 2019-11-08 10:18:04,686 [Controller] [DEBUG] Home:0 Tesla:abe9250b593a93:wTag12F:set_seconds: 0 2019-11-08 10:18:04,686 [Controller] [DEBUG] Home:0 Tesla:abe9250b593a93:wTag12F:set_seconds: 0 2019-11-08 10:18:04,686 [Controller] [DEBUG] Home:0 Tesla:abe9250b593a93:wTag12F:set_seconds: 0 2019-11-08 10:18:04,687 [Controller] [DEBUG] Home:Light Sensor 7:6d16a649e2f3e2:wTag26F:set_seconds: 2 2019-11-08 10:18:04,687 [Controller] [DEBUG] Home:Light Sensor 7:6d16a649e2f3e2:wTag26F:set_seconds: 2 2019-11-08 10:18:04,687 [Controller] [DEBUG] Home:Light Sensor 7:6d16a649e2f3e2:wTag26F:set_seconds: 2 2019-11-08 10:18:04,688 [Controller] [INFO ] Updating Driver 6d16a649e2f3e2 - GV14: 2, uom: 25 2019-11-08 10:18:04,688 [Controller] [INFO ] Updating Driver 6d16a649e2f3e2 - GV14: 2, uom: 25 2019-11-08 10:18:04,688 [Controller] [INFO ] Updating Driver 6d16a649e2f3e2 - GV14: 2, uom: 25 I also entered this command requested in an earlier request. [admin@polisy ~]$ ps -aux | grep poly polyglot 27773 8.8 2.8 724668 115152 - S 10:06 0:43.06 /usr/local polyglot 27774 0.2 0.6 44728 26536 - Is 10:06 0:03.45 python3 ./ polyglot 1189 0.0 1.8 306628 72892 - Ss Wed07 1:04.56 node ./nod polyglot 1830 0.0 0.1 10768 2336 - Is Wed09 0:00.01 daemon: /u polyglot 1834 0.0 1.9 312804 78396 - Ss Wed09 2:16.38 node ./nod polyglot 26133 0.0 1.7 303696 69532 - Ss 09:05 0:09.31 node ./nod polyglot 27775 0.0 0.7 50604 30192 - Is 10:06 0:04.29 python3 ./ polyglot 27776 0.0 1.5 295852 63568 - Ss 10:06 0:04.79 node ./nod admin 27801 0.0 0.1 11248 2696 0 S+ 10:12 0:00.01 grep poly [admin@polisy ~]$ I did another Polyglot restart from SSH but still shows triple events. I did a power reset on the Polisy and that cleared the triple logging. Reentered previous command. [admin@polisy ~]$ ps -aux | grep poly polyglot 1062 13.1 3.4 727004 142828 - S 10:29 0:30.85 /usr/local/bin polyglot 1214 0.5 1.5 294736 62908 - Ss 10:29 0:04.78 node ./nodeser polyglot 1212 0.1 0.7 45716 27436 - Is 10:29 0:03.48 python3 ./wll. polyglot 1061 0.0 0.1 10768 2184 - Is 10:29 0:00.00 daemon: /usr/l polyglot 1213 0.0 0.7 51172 30636 - Is 10:29 0:04.03 python3 ./wire admin 1234 0.0 0.1 11248 2696 0 S+ 10:33 0:00.01 grep poly [admin@polisy ~]$ Thanks Gary

I too have started to get the "device not responding" message. Also some slow downs of routines . I notified Amazon about the issue. In the past I was getting sporadic long delays in responses or no responses to routines I had set up. Mostly voice responses. Now like then I told them that their servers for my area are under powered. I see we are all from the same general area. I could be wrong about this but in the past the problem cleared shortly after my issue was escalated up to their engineering staff. Gary

No duplicates after restarting polyglot. It all seems to clear after power resetting the Polisy. If it happens again after an upgrade I will just restart Polyglot again after the initial restart without power resetting the Polisy to see if that alone will clear any duplicates. I was using the restart from the webpage. Thanks Gary

Michel Hi, I just did the latest update and the duplicate events returned on all nodes after restarting Polyglot. Example for wireless tags. 2019-11-06 07:03:34,108 [Controller] [DEBUG] Home:0 Tesla:abe9250b593a93:wTag12F:set_seconds: 193 2019-11-06 07:03:34,108 [Controller] [DEBUG] Home:0 Tesla:abe9250b593a93:wTag12F:set_seconds: 193 2019-11-06 07:03:34,110 [Controller] [INFO ] Updating Driver abe9250b593a93 - GV14: 193, uom: 25 2019-11-06 07:03:34,110 [Controller] [INFO ] Updating Driver abe9250b593a93 - GV14: 193, uom: 25 2019-11-06 07:03:34,112 [Controller] [DEBUG] Home:Light Sensor 7:6d16a649e2f3e2:wTag26F:set_seconds: 193 2019-11-06 07:03:34,112 [Controller] [DEBUG] Home:Light Sensor 7:6d16a649e2f3e2:wTag26F:set_seconds: 193 2019-11-06 07:03:34,112 [Controller] [INFO ] Updating Driver 6d16a649e2f3e2 - GV14: 193, uom: 25 2019-11-06 07:03:34,112 [Controller] [INFO ] Updating Driver 6d16a649e2f3e2 - GV14: 193, uom: 25 I then did a power reset on the Polisy and all was good after that. No duplicates. Thanks Gary

Michel, No duplicate events after reboot. It only seemed to have happened after doing the last upgrade (2.2.5) until I rebooted Polisy after that. Thanks Gary

I did the unplug and just keep getting request failed messages

polyglot 1077 0.6 3.3 731296 138344 - S 10:07 8:11.18 /usr/local/bi polyglot 1076 0.0 0.1 10768 2184 - Is 10:07 0:00.00 daemon: /usr/ polyglot 1202 0.0 0.7 45716 27396 - Is 10:07 0:41.73 python3 ./wll polyglot 1203 0.0 0.7 51520 31084 - Is 10:07 0:38.69 python3 ./wir polyglot 1204 0.0 1.8 308412 74484 - Is 10:07 0:14.75 node ./nodese admin 1740 0.0 0.1 11248 2696 0 S+ 12:47 0:00.01 grep poly

I deleted it there when I setup Polyglot on the local Rpi. That was months ago.

Michel I only have the node server running on Polisy. I have shut down polyglot running on the Rpi awhile ago.

Hi After the latest update and restarting Polisy I noticed that the Tesla node server logged every action twice. Before restarting the Tesla node server the horn button would blow the horn twice for example. After restart of the Tesla node server the horn button would then blow the horn once but still logged as doing it twice. Example 2019-11-03 09:56:04 info: NS: Starting Tesla Node Server 2019-11-03 09:56:04 info: NS: Starting Tesla Node Server 2019-11-03 09:56:04 info: POLY: Interface starting 2019-11-03 09:56:04 info: POLY: Interface starting 2019-11-03 09:56:04 info: POLY: Waiting for stdin 2019-11-03 09:56:04 info: POLY: Waiting for stdin 2019-11-03 09:56:04 debug: POLY: Log file set to: logs/debug-2019-11-03.log 2019-11-03 09:56:04 debug: POLY: Log file set to: logs/debug-2019-11-03.log 2019-11-03 09:56:05 info: POLY: MQTT client connected 2019-11-03 09:56:05 info: POLY: MQTT client connected 2019-11-03 09:56:05 info: NS: MQTT Connection started 2019-11-03 09:56:05 info: NS: MQTT Connection started 2019-11-03 09:56:05 warn: POLY: Message config ignored: Shutting down nodeserver 2019-11-03 09:56:05 warn: POLY: Message config ignored: Shutting down nodeserver 2019-11-03 09:56:06 info: NS: Config received has 2 nodes 2019-11-03 09:56:06 info: NS: Config received has 2 nodes 2019-11-03 09:56:06 info: NS: Running nodeserver on-premises 2019-11-03 09:56:06 info: NS: Running nodeserver on-premises 2019-11-03 09:56:06 warn: POLY: Message config ignored: Shutting down nodeserver 2019-11-03 09:56:06 warn: POLY: Message config ignored: Shutting down nodeserver 2019-11-03 09:56:06 info: NS: Config received has 2 nodes 2019-11-03 09:56:06 info: NS: Config received has 2 nodes 2019-11-03 09:56:27 warn: POLY: Message command ignored: Shutting down nodeserver 2019-11-03 09:56:27 warn: POLY: Message command ignored: Shutting down nodeserver 2019-11-03 09:56:27 info: NS: HORN (226851899) 2019-11-03 09:56:27 info: NS: HORN (226851899) 2019-11-03 09:56:27 info: NS: Tesla API: /api/1/vehicles/7806862550326485/command/honk_horn 2019-11-03 09:56:27 info: NS: Tesla API: /api/1/vehicles/7806862550326485/command/honk_horn 2019-11-03 09:56:27 info: NS: Reusing existing tokens 2019-11-03 09:56:27 info: NS: Reusing existing tokens 2019-11-03 09:56:47 warn: POLY: Message command ignored: Shutting down nodeserver 2019-11-03 09:56:47 warn: POLY: Message command ignored: Shutting down nodeserver 2019-11-03 09:56:47 info: NS: HORN (226851899) 2019-11-03 09:56:47 info: NS: HORN (226851899) 2019-11-03 09:56:47 info: NS: Tesla API: /api/1/vehicles/7806862550326485/command/honk_horn 2019-11-03 09:56:47 info: NS: Tesla API: /api/1/vehicles/7806862550326485/command/honk_horn After power resetting the Polisy all is normal again. Thanks Gary

Ok I didn't uninstall the nodes but still when I install a server I get 8 install messages "nstalled into ISY sucessfully. Profile uploaded, restart Admin console."ll Info between node servers is being shared with each other. Update: I realized that multiple Polyglots were running. All seems good now. Thanks Gary

I need to delete the node servers in the data base. Everything seems to be overlapping. I tried this command but does't seem to work. The normal delete from the poly UI doesn't work. mongo polyglot --eval "db.nodeservers.remove({'name': 'ISY Portal'})" Thanks Gary

I just received my first WEMO device and thought I would give it a try on Polisy. The WEMO node server loaded fine with no errors but it can't find the device when I do Re-Discover. I did find that WEMO node server running in Pi required the python module Pywemo to discover the devices. Not sure if that means anything or not. Anyway not critical for now just thought I would pass it along. Love the Polisy. Thanks Gary

Just a couple of suggestions. Would be nice to have a shutdown button to shutdown Polisy for relocation or other reasons. I hate to just pull the plug. Right now I do it through SSH but I know that won't be available later. The ISY also lacked that ability. Maybe pulling the plug is just fine. The other would be to have the ability to clear the log rather then having it scroll though the entire log each time just to see the latest entries at the end. Thanks Gary

WOW That worked. Thanks for that.

Ok I can give that a quick try.

I ran the fix again just to be sure but still won't install without errors or allow the command ./install.sh However I do have my other nodes running now so I can do without the Tesla node until it can be loaded successfully from the store. Thanks so much for all the assistance with the other nodes. Thanks so much. Gary

I am at the Tesla file in the nodserver directory but the command ./install.sh doesn't seem to be valid. Just get command not found. Thanks Gary

Ok it appears after I reinstall it from the store

Jimbo I am getting no tesla file found.

Sounds like a terminal command. I have that up but don't know how to run install.sh Gary

I just have one more issue with the Tesla Node. I get this while installing. 2019-10-28 20:17:02 [polyglot] info: NSChild cloneRepo: Successfully cloned Tesla into NodeServer directory. 2019-10-28 20:17:03 [polyglot] error: NSChild: Install failed - Non-zero exit code: 127 2019-10-28 20:17:03 [polyglot] error: NSChild: Tesla cloneRepo: Error: runInstallProcess: undefined 2019-10-28 20:17:03 [polyglot] error: Error: runInstallProcess: undefined at runInstallProcess (/snapshot/polyglot-v2/lib/modules/children.js:45:11) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7) 2019-10-28 20:17:03 [polyglot] error: NSResponse: Success: false - cloneRepo: Error: runInstallProcess: undefine Thanks for any thoughts Gary

Thanks MWareman That got my tags working also. Gary

Bumbershoot Thanks that worked for me. Gary

To find out what the mac address was on the Polisy for dhcp reservation I was able to get it from one of my smart switches. Gary