garybixler

@dbwarner5 I was wondering which MCA you are using. MCA-C3 or the MCA-C5 or the MCA 88.

Just updated to V 3.5.2 and all looks good. Thanks so much. Gary

I think all is OK. After bringing up the admin console from being down for awhile I see the zone is now reading the temp ok. I did restart the admin console after upgrading the Elk NS to 3.5.0 but am now on version 3.5.1. It must have upgraded when I did a restart to see if that would fix the problem. So right now it is all working on V 3.5.1. Thanks so much for the temps. Thanks Gary Note: 3.5.2 isn't available yet but will upgrade when available.

Just install ELK version 3.5.0 and discovered that it is reading temperatures. One zone reads the temp fine but another zone always shows -40 until I do a query and then it reads correctly but reverts back to -40 about 2 seconds later. I made sure poll voltage is set to true and did a restart but still reads -40. I also see -40 in the NS CLITEMP for that node. Also checked ElkRP2 and they are defined the same. Zone 8 and 9 on the main board. Thanks for the temp. Will gladly provide additional info. Thanks Gary

Thanks, it looks like WirelessTag is now working but the bad news is that TeslaEV won't start up. I included the log. Correction Tesla Ev my fault.

I don't believe I had a trial license. Can't be 100% sure however. I did find this in the log. 9/18/2022, 12:35:07 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3frontend_zEVyq has published message on udi/pg3/frontend/ns/admin to broker pg3_broker 9/18/2022, 12:35:07 [pg3] info: startNs:: WirelessTag 9/18/2022, 12:35:07 [pg3] info: startNs:: WirelessTag is valid 9/18/2022, 12:35:07 [pg3] debug: checkLicense:: WirelessTag Getting node server store entry 9/18/2022, 12:35:07 [pg3] debug: checkLicense:: WirelessTag Getting node server purchase record 9/18/2022, 12:35:07 [pg3] debug: Getting status for WirelessTag 00:0d:b9:52:bf:38 7ad25b20-1c13-45ca-9a94-85bd5063815d 9/18/2022, 12:35:07 [pg3] info: checkLicense:: WirelessTag Valid license found. 9/18/2022, 12:35:07 [pg3] info: startNs:: WirelessTag finished update check 9/18/2022, 12:35:07 [pg3] info: [WirelessTag(3)] :: Starting Node server - Version 3.1.6 9/18/2022, 12:35:07 [pg3] info: startNs:: WirelessTag updating database (enabled, timestarted) 9/18/2022, 12:35:07 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/frontend/clients/def85f13-bf7c-43f3-8055-aa7dfcb35d85 to broker pg3_broker 9/18/2022, 12:35:07 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/frontend/clients/def85f13-bf7c-43f3-8055-aa7dfcb35d85 to broker pg3_broker 9/18/2022, 12:35:08 [pg3] info: startNs:: WirelessTag starting polls 9/18/2022, 12:35:08 [pg3] info: Starting Node server Info timer 0 9/18/2022, 12:35:08 [pg3] debug: MQTT Results: [frontend/ns/admin] :: {"startNs":{"success":true}} 9/18/2022, 12:35:08 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/frontend/clients/def85f13-bf7c-43f3-8055-aa7dfcb35d85 to broker pg3_broker 9/18/2022, 12:35:08 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3frontend_zEVyq has published message on udi/pg3/frontend/ns/admin to broker pg3_broker 9/18/2022, 12:35:08 [pg3] info: startNs:: WirelessTag 9/18/2022, 12:35:08 [pg3] warn: WirelessTag validation checks returned :: Already running. 9/18/2022, 12:35:08 [pg3] debug: MQTT Results: [frontend/ns/admin] :: {"startNs":{"success":false,"error":"Already running."}} 9/18/2022, 12:35:08 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/frontend/clients/def85f13-bf7c-43f3-8055-aa7dfcb35d85 to broker pg3_broker 9/18/2022, 12:35:11 [pg3] debug: Client pg3frontend_zEVyq unsubscribed from udi/pg3/frontend/clients/def85f13-bf7c-43f3-8055-aa7dfcb35d85/log/00:0d:b9:52:bf:38_3 9/18/2022, 12:35:11 [pg3] debug: Stopping log stream for pg3frontend_zEVyq 9/18/2022, 12:35:11 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3frontend_zEVyq has published message on udi/pg3/frontend/isy/admin to broker pg3_broker 9/18/2022, 12:35:11 [pg3] debug: MQTT Results: [frontend/isy/admin] :: {"getNodeServers":[{"id":"ffedd022-28c5-4867-8452-3129f5b27eb8","uuid":"00:0d:b9:52:bf:38","token":"elyDV3+95aO%

Hi, just updated to PG3 v3.1.6 and all went well except for wireless tags. I keep getting the error ' The subscription for this node server has expired' and disconnects although it shows up fine in purchased nodes. Also including the log. Thanks Gary 2022-09-18 14:46:17,694 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-09-18 14:46:17,696 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-09-18 14:46:17,698 Thread-34 udi_interface ERROR udi_interface:write: Exception in thread 2022-09-18 14:46:17,700 Thread-34 udi_interface ERROR udi_interface:write: Thread-34 2022-09-18 14:46:17,700 Thread-34 udi_interface ERROR udi_interface:write: : 2022-09-18 14:46:17,701 Thread-34 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-09-18 14:46:17,702 Thread-34 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2022-09-18 14:46:17,706 Thread-34 udi_interface ERROR udi_interface:write: self.run() 2022-09-18 14:46:17,707 Thread-34 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2022-09-18 14:46:17,711 Thread-34 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-09-18 14:46:17,712 Thread-34 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db952bf38_3/nodes/Controller.py", line 185, in handler_poll 2022-09-18 14:46:17,714 Thread-34 udi_interface ERROR udi_interface:write: self.shortPoll() 2022-09-18 14:46:17,715 Thread-34 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db952bf38_3/nodes/Controller.py", line 197, in shortPoll 2022-09-18 14:46:17,717 Thread-34 udi_interface ERROR udi_interface:write: node.shortPoll() 2022-09-18 14:46:17,718 Thread-34 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db952bf38_3/nodes/TagManager.py", line 90, in shortPoll 2022-09-18 14:46:17,720 Thread-34 udi_interface ERROR udi_interface:write: if self.set_url_thread.isAlive(): 2022-09-18 14:46:17,721 Thread-34 udi_interface ERROR udi_interface:write: AttributeError 2022-09-18 14:46:17,722 Thread-34 udi_interface ERROR udi_interface:write: : 2022-09-18 14:46:17,722 Thread-34 udi_interface ERROR udi_interface:write: 'Thread' object has no attribute 'isAlive' 2022-09-18 14:46:17,952 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message stop 2022-09-18 14:46:17,954 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING stop 2022-09-18 14:46:17,955 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2022-09-18 14:46:17,957 Thread-35 udi_interface DEBUG Controller:handler_stop: Node server stopping 2022-09-18 14:46:18,010 Thread-35 udi_interface DEBUG Controller:handler_stop: Node server stopped 2022-09-18 14:46:18,011 Thread-35 udi_interface.interface INFO interface:stop: Disconnecting from MQTT... localhost:1888 2022-09-18 14:46:18,012 Thread-35 udi_interface.interface INFO interface:_disconnect: MQTT Graceful disconnection. 2022-09-18 14:46:18,014 MQTT udi_interface.interface DEBUG interface:_startMqtt: MQTT: Done

Hi, would appreciate any suggestions on wireless vertical blinds for a 6' sliding door that will work with Bond or Zwave. Thanks in advance. Gary

That's right. The estimated range in miles left on the battery. I relate better to miles rather then battery % remaining. Although I see many just go by percent. On another note I was just wondering if the API could receive a push from the Tesla cloud without polling. For example if a new software version is pushed down to the car. I do receive a notification on my phone. Something must be running in the background to receive that. The app is not active. Thanks Gary

Hi, would like to also see mileage available displayed on the Charging Info page or where appropriate maybe some time in the future. Thanks Gary

@GQuack The russound MCA types require the RussoundRIO NS which isn't available on the PG3 platform at this time. I also have been waiting to move to the PG3 version from the PG2 version when it becomes available for my MCA-C5s.

Just thought I would pass this error along. Doesn't seem to affect the operation. Thanks Gary 2022-08-25 08:37:33,515 Thread-2163 udi_interface DEBUG Controller:shortPoll: done 2022-08-25 08:37:36,713 ELK-21607 udi_interface INFO Controller:callback: ELK Controller: cs={'real_time_clock': '3537085250822110'} 2022-08-25 08:37:36,714 ELK-21607 udi_interface INFO Controller:callback: real_time_clock=3537085250822110 2022-08-25 08:37:38,524 ELK-21607 udi_interface ERROR Controller:timeout: ELK Controller: Timeout sending message ZV!!! 2022-08-25 08:37:38,526 ELK-21607 udi_interface.node DEBUG node:setDriver: controller:ELK Controller Reporting set ERR to 1 to Polyglot 2022-08-25 08:37:38,527 ELK-21607 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2022-08-25 08:37:38,527 ELK-21607 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'ERR', 'value': '1', 'uom': 56}]} 2022-08-25 08:37:38,529 ELK-21607 udi_interface.custom DEBUG custom:__setitem__: CUSTOM: ns_error = ERROR: 08/25/2022 08:37:38 See log for: ELK Controller: Timeout sending message ZV!!! ...saving 2022-08-25 08:37:38,530 ELK-21607 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2022-08-25 08:37:38,531 ELK-21607 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'notices', 'value': {'ns_error': 'ERROR: 08/25/2022 08:37:38 See log for: ELK Controller: Timeout sending message ZV!!!'}}]} 2022-08-25 08:37:38,533 ELK-21607 udi_interface DEBUG Controller:set_st: ELK Controller: elk_st=1 st=6 2022-08-25 08:37:38,534 ELK-21607 udi_interface.node DEBUG node:setDriver: controller:ELK Controller Reporting set GV1 to 6 to Polyglot 2022-08-25 08:37:38,535 ELK-21607 udi_interface.node DEBUG node:reportDriver: Updating value to 6 2022-08-25 08:37:38,535 ELK-21607 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV1', 'value': '6', 'uom': 25}]} 2022-08-25 08:37:38,685 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2022-08-25 08:37:38,687 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2022-08-25 08:37:38,688 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {'ns_error': 'ERROR: 08/25/2022 08:37:38 See log for: ELK Controller: Timeout sending message ZV!!!'} 2022-08-25 08:37:38,689 Command udi_interface.custom DEBUG custom:load: CUSTOM: -- checking ns_error / ERROR: 08/25/2022 08:37:38 See log for: ELK Controller: Timeout sending message ZV!!! 2022-08-25 08:37:38,728 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: ERR to 1 UOM 56 2022-08-25 08:37:38,730 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2022-08-25 08:37:38,810 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV1 to 6 UOM 25 2022-08-25 08:37:40,203 ELK-21607 udi_interface INFO Zone:callback: zone_8:Outside Temp: changeset={'voltage': 0.7} 2022-08-25 08:37:40,204 ELK-21607 udi_interface DEBUG Zone:_set_voltage: zone_8:Outside Temp: val=0.7 2022-08-25 08:37:40,204 ELK-21607 udi_interface DEBUG BaseNode:set_driver: zone_8:Outside Temp: CV,0.7 default=None force=False,report=True

I noticed that in the log I see the temperature value for one of my temp zones but only the voltage is displayed in Admin Console. Just wondering if that is still a future enhancement. Thanks Gary 2022-08-21 12:44:28,726 ELK-21607 udi_interface INFO Controller:callback: ELK Controller: cs={'real_time_clock': '2644121210822110'} 2022-08-21 12:44:28,728 ELK-21607 udi_interface INFO Controller:callback: real_time_clock=2644121210822110 2022-08-21 12:44:56,746 ELK-21607 udi_interface INFO Zone:callback: zone_8:Outside Temp: changeset={'temperature': 76} 2022-08-21 12:44:56,747 ELK-21607 udi_interface WARNING Zone:callback: zone_8:Outside Temp: Unknown callback temperature=76 2022-08-21 12:44:58,745 ELK-21607 udi_interface INFO Controller:callback: ELK Controller: cs={'real_time_clock': '5644121210822110'} 2022-08-21 12:44:58,747 ELK-21607 udi_interface INFO Controller:callback: real_time_clock=5644121210822110

Same errors here and the tag updates are iffy.

Hi, I updated to version 3.3.6 and the Set Poll Voltage will not stay true both in the Area and Zone. Thanks Gary

Oddly all the temps except outdoor temp slipped back to C. Can't get them to change back to F. Only short polling should have been active. Also EV Online did change from false to true. UPDATE: Oddly the temps went back to F a couple of hours later. I don't know what is triggering the change.

I updated to version 1.1.15 and all temps came up in F immediately including Outdoor Temperature. Will check on wake up later after car is asleep. Thanks so much. Gary

I am at 0.1.14 now and I noticed a couple of differences. After updating to 1.1.14 the temps came up as C and temp unit showed F. After a quick click in the Set Unit Of Temp to F they all changed to F except Outdoor Temperature. Can't get that one to F. A question of polling. After reading on github I saw that the long poll will wake up the car and the short poll only checks for heartbeat. So I now set the long poll to 1440 (24hr) and the short poll to 300 hoping that will keep the NS from waking up the car. Is all of my assumptions correct or is there more to configuring polling. The EV Online always shows false now even if I do a wake up. Does that reflect whether the EV is awake or asleep? I also noticed for example that if I do a Honk Horn it may need to be clicked twice. I think I read earlier that a wakeup is sent before a command. Thanks for any clarifications? Gary

I just sent the log but I think I found the problem. I didn't notice the Set Unit of Temp until I scrolled down. It showed set to F but after clicking on it again it did then change to F readings. Originally the Admin Console did show F as the Temperature Unit. Thanks Gary

The only two things that I have noticed is that it wont display temp in Fahrenheit. It does say that the Temperature Unit is Fahrenheit. The other thing is that it wasn't allowing the car to go to sleep so I set the polling at 20 minutes but that didn't seem to work either. I am now trying 30 minutes and I'll see if that will allow enough time for the car to fall asleep. Thanks for the great NS. Gary.

change_nodes_names was originally set to false on the config. Tried setting to true but same results. Not sure if this would be of any importance.

No, I assume it was something done after the pg3 update. I was getting the message that pg3 needed to be rebooted so I just did the update and pg3 restart through SSH

I am at 3.3.5 and I am getting this error. Tried rebooting. Started after doing pg3 upgrade. 3.0.63. Thanks Gary 2022-07-08 15:15:41,342 ELK-1757 udi_interface INFO Controller:sync_complete: ELK Controller: Adding Area 0 2022-07-08 15:15:41,347 ELK-1757 elkm1_lib.elk ERROR elk:_got_data: Invalid message '19UA000000003030661C41F00CF' Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/elkm1_lib/elk.py", line 139, in _got_data self._message_decode.decode(data) File "/var/polyglot/.local/lib/python3.9/site-packages/elkm1_lib/message.py", line 67, in decode self.call_handlers(cmd, decoder(msg)) File "/var/polyglot/.local/lib/python3.9/site-packages/elkm1_lib/message.py", line 55, in call_handlers handler(**decoded_msg) File "/var/polyglot/.local/lib/python3.9/site-packages/elkm1_lib/elk.py", line 56, in _sync_complete self._message_decode.call_handlers("sync_complete", {}) File "/var/polyglot/.local/lib/python3.9/site-packages/elkm1_lib/message.py", line 55, in call_handlers handler(**decoded_msg) File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:38_14/nodes/Controller.py", line 243, in sync_complete node = self.add_node(address,AreaNode(self, address, self.elk.areas[an])) File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:38_14/nodes/Controller.py", line 205, in add_node cname = self.poly.getNodeNameFromDb(address) AttributeError: 'Interface' object has no attribute 'getNodeNameFromDb' 2022-07-08 15:15:41,472 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV1 to 5 UOM 25 2022-07-08 15:16:00,711 Thread-9 udi_interface WARNING Controller:handler_poll: waiting for sync to complete

Just discovered that one of my NSs that was originally installed from the Production store will no longer update after a restart. Just stops and can't be started. I found that the NS had been moved to the Non-Production store. All I could do was delete it and reinstall from the Non-Production store. I have a couple more NSs that have also been moved. Is there a way to get the version from the Non-Production store without having to delete and reinstall. Would save having to reconfigure the NSs. Thanks Gary

Thanks I will probably do that. Gary