Jump to content

CManson

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

CManson's Achievements

New

New (2/6)

0

Reputation

  1. So, overnight, it just started working! Thank you!
  2. Reinstalling did the trick in getting the latest version downloaded and starting the node server. For a minute or two the car appeared as a node but then disappeared? Any thoughts from the attached log? Log.rtf
  3. Here is the main log: 6/18/2022, 16:03:43 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_2] {"shortPoll":{}} 6/18/2022, 16:03:43 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_6 to broker pg3_broker 6/18/2022, 16:03:43 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_2 to broker pg3_broker 6/18/2022, 16:03:45 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3frontend_DF0Q3 has published message on udi/pg3/frontend/ns/admin to broker pg3_broker 6/18/2022, 16:03:45 [pg3] info: [TeslaEV(5)]: Restarting Node server 6/18/2022, 16:03:45 [pg3] warn: [TeslaEV(5)]: Was not running. Starting... 6/18/2022, 16:03:48 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_6] {"shortPoll":{}} 6/18/2022, 16:03:48 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_2] {"shortPoll":{}} 6/18/2022, 16:03:48 [pg3] info: startNs:: TeslaEV 6/18/2022, 16:03:48 [pg3] info: startNs:: TeslaEV is valid 6/18/2022, 16:03:48 [pg3] error: store get requires a nsid 6/18/2022, 16:03:48 [pg3] error: Node server TeslaEV has no store entry. 6/18/2022, 16:03:48 [pg3] error: TeslaEV automatic update failed 6/18/2022, 16:03:48 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_6 to broker pg3_broker 6/18/2022, 16:03:48 [pg3] debug: MQTT Results: [frontend/ns/admin] :: {"restartNs":{"success":false,"error":"automatic update failed"}} 6/18/2022, 16:03:48 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_2 to broker pg3_broker 6/18/2022, 16:03:48 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/frontend/clients/d207e2a7-1484-4ed1-9613-8d2d1e1e88fd to broker pg3_broker 6/18/2022, 16:03:48 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_5] {"longPoll":{}} 6/18/2022, 16:03:48 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_5 to broker pg3_broker 6/18/2022, 16:03:50 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_6] {"longPoll":{}} 6/18/2022, 16:03:50 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_4] {"shortPoll":{}} 6/18/2022, 16:03:50 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_6 to broker pg3_broker 6/18/2022, 16:03:50 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_4 to broker pg3_broker 6/18/2022, 16:03:53 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_6] {"shortPoll":{}} 6/18/2022, 16:03:53 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_2] {"shortPoll":{}} 6/18/2022, 16:03:53 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_6 to broker pg3_broker 6/18/2022, 16:03:53 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_2 to broker pg3_broker 6/18/2022, 16:03:53 [pg3] debug: Client pg3frontend_DF0Q3 unsubscribed from udi/pg3/frontend/clients/d207e2a7-1484-4ed1-9613-8d2d1e1e88fd/log/00:21:b9:02:54:be_5 6/18/2022, 16:03:53 [pg3] debug: Stopping log stream for pg3frontend_DF0Q3 6/18/2022, 16:03:53 [pg3] debug: Sending logfile to frontend :: /var/polyglot/pg3/logs/pg3-current.log 6/18/2022, 16:03:53 [pg3] error: MQTTS: connectionError: null connect did not arrive in time 6/18/2022, 16:03:54 [pg3] debug: Starting log stream for pg3frontend_DF0Q3 :: /var/polyglot/pg3/logs/pg3-current.log 6/18/2022, 16:03:57 [pg3] error: MQTTS: clientError: 00:21:b9:02:54:be_5 Auth Error 6/18/2022, 16:03:58 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_6] {"shortPoll":{}} 6/18/2022, 16:03:58 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_6 to broker pg3_broker 6/18/2022, 16:03:58 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_2] {"shortPoll":{}} 6/18/2022, 16:03:58 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_2 to broker pg3_broker 6/18/2022, 16:04:03 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_6] {"shortPoll":{}} 6/18/2022, 16:04:03 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_2] {"shortPoll":{}} 6/18/2022, 16:04:03 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_6 to broker pg3_broker 6/18/2022, 16:04:03 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_2 to broker pg3_broker 6/18/2022, 16:04:05 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_4] {"shortPoll":{}} 6/18/2022, 16:04:05 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_4 to broker pg3_broker 6/18/2022, 16:04:06 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_5] {"shortPoll":{}} 6/18/2022, 16:04:06 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_5 to broker pg3_broker 6/18/2022, 16:04:08 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_6] {"shortPoll":{}} 6/18/2022, 16:04:08 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:54:be_2] {"shortPoll":{}} 6/18/2022, 16:04:08 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_6 to broker pg3_broker 6/18/2022, 16:04:08 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:02:54:be_2 to broker pg3_broker
  4. So I can't actually access the log file (see error in attached screenshot) and when I try and start it says "Node Server Start: automatic update failed"
  5. Thanks. I have no issue generating the token, my question is where to put it. This is what I see on the configuration page of the node server. I don't see a help section.
  6. I just paid for the node server and am trying to get it up and running but its not clear where to insert the refresh token? Do I create a custom parameter? If so, what goes in the "key" field? I'm assuming that the token goes in "value"?
×
×
  • Create New...