[ST Edge] SmartThings MyQ Edge (Obsolete)

Antoine6262 · November 2, 2022, 7:24pm

So, I need to use the CLI to find the port and ip that is being broadcast and add that to the App?

j18hockey · November 2, 2022, 7:40pm

/status works for me and shows both garage doors my account has access to.

ViperTK · November 2, 2022, 7:45pm

the logs indicate that there is communication between the server and the ST hub. but, not able to see any devices in the app yet.

11/2/2022, 12:24:04 PM | HTTP server listening on port 8090
11/2/2022, 12:24:04 PM | SSDP server up and listening for broadcasts: urn:SmartThingsCommunity:device:MyQController
11/2/2022, 12:24:07 PM | Got new username/password from hub. Initializing connection.
myQ API: Successfully connected to the myQ API.
myQ API: Discovered device family garagedoor: Garage Left (serial number: XXX, gateway: XXX).
myQ API: Discovered device family garagedoor: Garage Right (serial number: XXXX, gateway: XXX).
myQ API: Discovered device family gateway: Grey Garage [Chamberlain Smart Garage Hub] (serial number: XXX).
11/2/2022, 12:30:51 PM | Detected SSDP broadcast. Posting details back to server at http://192.168.62.14:33125/ping

UPDATE: CLI Logs Added

2022-11-02T20:54:45.215391485+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:54:52.792037403+00:00 TRACE MyQ Connector  Received event with handler capability
2022-11-02T20:54:52.802727611+00:00 INFO MyQ Connector  <Device: bXXX-XX-XX-XX-XXX(MyQ-Controller)> received command: {"args":{},"capability":"refresh","command":"refresh","component":"main","positional_args":{}}
2022-11-02T20:54:52.806100778+00:00 TRACE MyQ Connector  Found CapabilityCommandDispatcher handler in myQConnectorDriver
2022-11-02T20:54:53.468057736+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:54:53.773442861+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:55:04.206178446+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:55:14.222546530+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:55:15.606072281+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:55:15.611269989+00:00 INFO MyQ Connector  <Device: bXXX-XX-XX-XX-XXX(MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T20:55:15.615363072+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:55:15.618223947+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T20:55:15.727804406+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:55:15.732920447+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:55:25.022127740+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:55:34.092371491+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:55:34.153854491+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:55:34.158829074+00:00 INFO MyQ Connector  <Device: bXXX-XX-XX-XX-XXX(MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T20:55:34.166717241+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:55:34.169658199+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T20:55:34.237375991+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:55:34.241349324+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:55:44.573613742+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:55:54.638084702+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:56:04.652884453+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:56:14.642874454+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:56:24.615477372+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:56:34.586152743+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled

rumrunner424 · November 2, 2022, 8:17pm

Pulled the new image. http://host:ip/status shows my garage doors but http://host:ip/devices shows “Cannot GET /devices”

brbeaird · November 2, 2022, 9:01pm

This is very strange. If you’re getting that far, I have no idea why the devices are not being created. If you force-kill the ST app and reopen it, can you just verify they’re not in the unassigned room? I would be curious to see the results of your devices at the http://serverip:port/status endpoint as well (just blank out the serial numbers and such - mostly curious what your device types are).

That is expected - the /devices endpoint only accepts POST. If the /status endpoint shows data, I do not know why your hub would not create those as devices. Very strange.

I’ll see about adding more logging. If you want to try downloading the SmartThings CLI and watching logs from that end, it could be helpful.

rtorch · November 2, 2022, 9:10pm

Forget what I said, just looked this afternoon and there they are! That was very delayed, but they are in Google Home now, BUT its not working.

Here is a log of what happens when selecting the garage device from Google Home:

11/2/2022, 9:18:09 PM | Setting Small Garage Door to on
myQ API: https://account-devices-gdo.myq-cloud.com/api/v5.2/Accounts/*{account id removed}*/door_openers/CG083015A813/on Error: 400 Bad Request
myQ API: Unable to send the command to myQ servers. Acquiring a new access token.
myQ API: Successfully connected to the myQ API.

ViperTK · November 2, 2022, 9:24pm

I did that and also removed the controller app, restarted the container and installed and configured the app again. Still don’t see the doors. Logs indicate that the server and hub are able to communicate. Please see below and advise.

CLI Logs

2022-11-02T21:13:56.921914250+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T21:13:56.967961375+00:00 INFO MyQ Connector  <Device: XXX-XX-XX-XX-XXXX (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T21:13:56.991002625+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T21:13:57.008337958+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T21:13:57.049433875+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T21:13:57.088609250+00:00 INFO MyQ Connector  Listening for a response at 192.168.62.14:52175:XXX-XX-XX-XX-XXXX
2022-11-02T21:13:57.198125291+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:13:57.203511958+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:13:57.206705916+00:00 TRACE MyQ Connector  Server:tick
2022-11-02T21:13:57.215904458+00:00 TRACE MyQ Connector  Server:_tick
2022-11-02T21:13:57.222330166+00:00 TRACE MyQ Connector  Server:route
2022-11-02T21:13:57.227455416+00:00 INFO MyQ Connector  Content-Length: 72
Content-Type: application/json
Host: 192.168.62.14:52175
Accept: application/json, text/plain, */*
Connection: close
User-Agent: axios/0.27.2

2022-11-02T21:13:57.233257958+00:00 INFO MyQ Connector  Incoming ping from 192.168.62.75:8090XXX-XX-XX-XX-XXXX
2022-11-02T21:13:57.252170541+00:00 INFO MyQ Connector  Found controller.MyQController
2022-11-02T21:13:57.748713208+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T21:13:57.754936+00:00 INFO MyQ Connector  <Device: XXX-XX-XX-XX-XXXX (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T21:13:57.764059416+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T21:13:57.770037333+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T21:13:59.664438792+00:00 INFO MyQ Connector  <Device: XXX-XX-XX-XX-XXXX (MyQ-Controller)> emitting event: {"attribute_id":"statusText","capability_id":"towertalent27877.myqstatus","component_id":"main","state":{"value":"Connected"}}
2022-11-02T21:13:59.674193917+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:13:59.679603167+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:14:08.193594668+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:14:18.326673794+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:14:28.301355753+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:14:38.359462754+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:14:48.373620506+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:14:58.529132090+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:15:08.367863133+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:15:18.246819759+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:15:27.597176219+00:00 TRACE MyQ Connector  Received event with handler capability
2022-11-02T21:15:27.605940885+00:00 INFO MyQ Connector  <Device: XXX-XX-XX-XX-XXXX (MyQ-Controller)> received command: {"args":{},"capability":"refresh","command":"refresh","component":"main","positional_args":{}}
2022-11-02T21:15:27.609414469+00:00 TRACE MyQ Connector  Found CapabilityCommandDispatcher handler in myQConnectorDriver
2022-11-02T21:15:28.108413385+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:15:28.170616469+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:15:38.446263845+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:15:48.346083554+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T21:15:58.303842972+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled

Docker Logs

11/2/2022, 2:05:31 PM | HTTP server listening on port 8090
11/2/2022, 2:05:32 PM | SSDP server up and listening for broadcasts: urn:SmartThingsCommunity:device:MyQController
11/2/2022, 2:05:36 PM | Got new username/password from hub. Initializing connection.
myQ API: Successfully connected to the myQ API.
myQ API: Discovered device family garagedoor: Garage Left (serial number: XXX, gateway: XXX).
myQ API: Discovered device family garagedoor: Garage Right (serial number: XXX, gateway: XXX).
myQ API: Discovered device family gateway: Grey Garage [Chamberlain Smart Garage Hub] (serial number: XXX).
11/2/2022, 2:13:58 PM | Detected SSDP broadcast. Posting details back to server at http://192.168.62.14:52175/ping
11/2/2022, 2:13:59 PM | Got new username/password from hub. Initializing connection.
myQ API: Successfully connected to the myQ API.
myQ API: Discovered device family garagedoor: Garage Left (serial number: XXX, gateway: XXX).
myQ API: Discovered device family garagedoor: Garage Right (serial number: XXX, gateway: XXX).
myQ API: Discovered device family gateway: Grey Garage [Chamberlain Smart Garage Hub] (serial number: XXX).

Status Page Logs

[{"href":"/accounts/XXX-XX-XX-XX-XXXX/devices/garagedoor/XXX","serial_number":"XXX","device_family":"garagedoor","device_platform":"myq","device_type":"virtualgaragedooropener","device_model":"virtualgaragedooropener","name":"Garage Left","parent_device_id":"XXX","created_date":"0001-01-01T00:00:00","account_id":"XXX-XX-XX-XX-XXXX","state":{"dps_battery_critical":false,"dps_no_communication":false,"dps_low_battery_mode":false,"monitor_only_mode":false,"number_of_learned_dps_devices":1,"sensor_comm_error":false,"is_scheduling_allowed":true,"attached_camera_serial_number":"","door_state":"closed","last_update":"2022-11-02T00:51:38.3269947Z","is_unattended_open_allowed":true,"is_unattended_close_allowed":true,"service_cycle_count":0,"absolute_cycle_count":0,"online":true,"last_status":"2022-11-02T21:22:49.7783876Z"}},{"href":"/accounts/XXX-XX-XX-XX-XXXX/devices/garagedoor/XXX","serial_number":"XXX","device_family":"garagedoor","device_platform":"myq","device_type":"virtualgaragedooropener","device_model":"virtualgaragedooropener","name":"Garage Right","parent_device_id":"XXX","created_date":"0001-01-01T00:00:00","account_id":"XXX-XX-XX-XX-XXXX","state":{"dps_battery_critical":false,"dps_no_communication":false,"dps_low_battery_mode":false,"monitor_only_mode":false,"number_of_learned_dps_devices":1,"sensor_comm_error":false,"is_scheduling_allowed":true,"attached_camera_serial_number":"","door_state":"closed","last_update":"2022-11-02T15:15:11.2320763Z","is_unattended_open_allowed":true,"is_unattended_close_allowed":true,"service_cycle_count":0,"absolute_cycle_count":0,"online":true,"last_status":"2022-11-02T21:22:24.6232511Z"}},{"href":"/accounts/XXX-XX-XX-XX-XXXX/devices/gateway/XXX","serial_number":"XXX","device_family":"gateway","device_platform":"myq","device_type":"hub","device_model":"hub","name":"Grey Garage","created_date":"0001-01-01T00:00:00","account_id":"XXX-XX-XX-XX-XXXX","state":{"allow_bluetooth_lock":false,"firmware_version":"3.10","homekit_capable":false,"homekit_enabled":false,"learn_mode":false,"updated_date":"2022-11-02T18:04:42.3863276Z","physical_devices":["XXX","XXX"],"pending_bootload_abandoned":false,"wifi_rssi_decibel_milliwatts":-60,"wifi_signal_strength":"good","supports_dealer_diagnostics":false,"mandatory_update_required":false,"online":true,"last_status":"2022-11-02T18:04:38.382231Z"}}]

Thanks again for all the work on this.

BartschLabs · November 2, 2022, 9:25pm

Pulled the latest image. Status URL doesn’t work.

rumrunner424 · November 2, 2022, 9:28pm

Part of CLI log from my last run:

2022-11-02T20:20:07.346733498+00:00 TRACE MyQ Connector  Setup driver myQConnectorDriver with lifecycle handlers:
DeviceLifecycleDispatcher: myQConnectorDriver
  default_handlers:
    infoChanged:
    driverSwitched:
    added:
    init:
    removed:
  child_dispatchers:

2022-11-02T20:20:07.350879081+00:00 TRACE MyQ Connector  Setup driver myQConnectorDriver with Capability handlers:
CapabilityCommandDispatcher: myQConnectorDriver
  default_handlers:
    switch:
      on
      off
    refresh:
      refresh
    doorControl:
      close
      open
  child_dispatchers:

2022-11-02T20:20:07.359229414+00:00 TRACE MyQ Connector  Server.new_with
2022-11-02T20:20:07.362213164+00:00 TRACE MyQ Connector  Server:post
2022-11-02T20:20:07.365287623+00:00 TRACE MyQ Connector  Server:listen
2022-11-02T20:20:07.376298039+00:00 TRACE MyQ Connector  Server listening on 192.168.1.240:60035
2022-11-02T20:20:07.412409789+00:00 DEBUG MyQ Connector  driver device thread event handled
2022-11-02T20:20:07.415680873+00:00 TRACE MyQ Connector  Received event with handler environment_info
2022-11-02T20:20:07.427818789+00:00 TRACE MyQ Connector  Received event with handler environment_info
2022-11-02T20:20:07.430829706+00:00 DEBUG MyQ Connector  Z-Wave hub node ID environment changed.
2022-11-02T20:20:07.434763248+00:00 TRACE MyQ Connector  Received event with handler discovery
2022-11-02T20:20:07.441903039+00:00 DEBUG MyQ Connector  Device discovery invoked
2022-11-02T20:20:07.447420248+00:00 INFO MyQ Connector  Creating new controller device
2022-11-02T20:20:07.454887206+00:00 DEBUG MyQ Connector  Exiting discovery
2022-11-02T20:20:07.457863998+00:00 DEBUG MyQ Connector  discovery device thread event handled
2022-11-02T20:20:08.557561831+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:20:08.566179247+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received lifecycle event: added
2022-11-02T20:20:08.574726122+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:20:08.577815081+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received lifecycle event: doConfigure
2022-11-02T20:20:08.582962039+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:20:08.586025956+00:00 INFO MyQ Connector  cdbb61fb-c9fa-4425-9b80-cf0fd0301e32: MyQController> ADDED
2022-11-02T20:20:08.588903372+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:20:08.606759831+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:20:08.609546956+00:00 DEBUG MyQ Connector  MyQ-Controller: MyQController> INITIALIZING
2022-11-02T20:20:08.612671456+00:00 INFO MyQ Connector  No credentials yet. Waiting.unknown
2022-11-02T20:20:08.615857164+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> emitting event: {"attribute_id":"statusText","capability_id":"towertalent27877.myqstatus","component_id":"main","state":{"value":"Awaiting credentials"}}
2022-11-02T20:20:08.650848414+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:20:08.655700039+00:00 TRACE MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received unhandled lifecycle event: doConfigure
2022-11-02T20:20:08.658582664+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:20:08.667137997+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:20:08.672303039+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:20:11.760552496+00:00 TRACE MyQ Connector  Received event with handler capability
2022-11-02T20:20:11.826673705+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received command: {"args":{},"capability":"refresh","command":"refresh","component":"main","positional_args":{}}
2022-11-02T20:20:11.830113038+00:00 TRACE MyQ Connector  Found CapabilityCommandDispatcher handler in myQConnectorDriver
2022-11-02T20:20:11.833058955+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:20:13.938024913+00:00 TRACE MyQ Connector  Received event with handler discovery
2022-11-02T20:20:18.661259037+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:20:28.662719659+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:20:38.670534490+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:20:48.680444363+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:20:52.484816487+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:20:52.491038320+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T20:20:52.509109153+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:20:52.512098862+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T20:20:52.520650612+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:20:52.525520528+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:02.233465575+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:21:02.240501722+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T20:21:02.310743125+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:21:02.314005910+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T20:21:02.323548844+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:02.328086408+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:11.556136365+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:21:11.561470697+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T20:21:11.605823842+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:21:11.608795064+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T20:21:11.617180411+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:21:11.630888679+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:21:13.644648722+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:13.649697347+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:17.412012473+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:21:17.417732348+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T20:21:17.428088264+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:21:17.431117806+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T20:21:17.439713514+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:21:17.453537764+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:21:19.467222265+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:19.472092265+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:23.397695474+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:21:23.409361849+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T20:21:23.415218640+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:21:23.419002724+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T20:21:23.427841724+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:21:23.442313224+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:21:25.455850724+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:25.460909682+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:28.445693349+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:21:28.506966807+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:21:30.520680391+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:30.938439308+00:00 TRACE MyQ Connector  Received event with handler capability
2022-11-02T20:21:30.977046016+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received command: {"args":{},"capability":"refresh","command":"refresh","component":"main","positional_args":{}}
2022-11-02T20:21:31.007382308+00:00 TRACE MyQ Connector  Found CapabilityCommandDispatcher handler in myQConnectorDriver
2022-11-02T20:21:31.010320141+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:21:31.032948266+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:21:33.051237391+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:33.455518266+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:21:33.507246975+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:21:35.521758933+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:38.450644975+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:21:38.509662767+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:21:40.528735809+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:43.459963143+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:21:43.509685643+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:21:45.523647643+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:48.464374393+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:21:48.510052977+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:21:50.535512268+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:53.469587310+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:21:53.483243019+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:21:55.504996561+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:21:58.471143478+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:21:58.484834061+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:22:00.515783020+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:03.480426645+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:22:03.494137020+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:22:05.518059020+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:08.494703479+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:22:08.511020937+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:22:10.614312646+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:10.617940062+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:22:10.622786937+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T20:22:10.630552687+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:22:10.633418271+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T20:22:10.641605271+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:22:10.718058937+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:22:12.731452729+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:12.745836063+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:15.645801396+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:22:15.715470396+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:22:17.729531563+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:20.651376480+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:22:20.721026189+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:22:22.639741356+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:22.643338814+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:22:22.650367064+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T20:22:22.710603231+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:22:22.717130772+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T20:22:22.760579356+00:00 INFO MyQ Connector  Send broadcast looking for bridge server
2022-11-02T20:22:22.804492981+00:00 INFO MyQ Connector  Listening for a response at 192.168.1.240:60035:cdbb61fb-c9fa-4425-9b80-cf0fd0301e32
2022-11-02T20:22:24.096718314+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:24.100425772+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:24.103558064+00:00 TRACE MyQ Connector  Received event with handler device_lifecycle
2022-11-02T20:22:24.108694356+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T20:22:24.114001147+00:00 TRACE MyQ Connector  Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T20:22:24.117018147+00:00 DEBUG MyQ Connector  Info changed handler invoked
2022-11-02T20:22:24.652583772+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> emitting event: {"attribute_id":"statusText","capability_id":"towertalent27877.myqstatus","component_id":"main","state":{"value":"Connected"}}
2022-11-02T20:22:24.662427647+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:24.709084397+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:25.876110814+00:00 TRACE MyQ Connector  Received event with handler capability
2022-11-02T20:22:25.900218314+00:00 INFO MyQ Connector  <Device: cdbb61fb-c9fa-4425-9b80-cf0fd0301e32 (MyQ-Controller)> received command: {"args":{},"capability":"refresh","command":"refresh","component":"main","positional_args":{}}
2022-11-02T20:22:25.903527564+00:00 TRACE MyQ Connector  Found CapabilityCommandDispatcher handler in myQConnectorDriver
2022-11-02T20:22:25.953860231+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:29.993180065+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:34.637208357+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:39.635930608+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled
2022-11-02T20:22:44.603044692+00:00 DEBUG MyQ Connector  MyQ-Controller device thread event handled

brbeaird · November 2, 2022, 10:02pm

Don’t worry about that. If you try again, it should work. The MyQ api just randomly fails like that from time to time.

I pushed an update to the Edge driver. Might take awhile before you get it, but once you do, it should be more descriptive:

Same deal - see what the CLI logs show during refresh when you get the latest driver version. I assume you’re using the IP address of your docker host when hitting the /status endpoint?

brbeaird · November 2, 2022, 10:21pm

Scratch that. There is a bug in the door open command I think. Slipped through when I added switch capability. Will get that fixed.

brbeaird · November 2, 2022, 10:50pm

This is now fixed in the latest edge driver version, so it should get pushed out over time. If you had door devices created previously, you will need to delete them and let them get recreated for the fix to apply.

bthrock · November 2, 2022, 11:13pm

@brbeaird I started over with a clean install, pulled the latest Docker Image and driver and I’m still stuck at Awaiting Credentials.

Docker Logs show the server up and running

11/2/2022, 11:03:53 PM | HTTP server listening on port 8090
11/2/2022, 11:03:53 PM | SSDP server up and listening for broadcasts: urn:SmartThingsCommunity:device:MyQController

CLI Device log recognized username/password entries with

showed “Info Changed handler invoked”

Then, repeatedly …

2022-11-02T23:11:57.978029070+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2022-11-02T23:12:05.960228821+00:00 INFO MyQ Connector Send broadcast looking for bridge server
2022-11-02T23:12:05.974405779+00:00 INFO MyQ Connector Listening for a response at 192.168.1.166:46077:c228492a-xxxx

Reading thru the posts above, I’m at a loss at this point.

j18hockey · November 3, 2022, 12:34am

@ViperTK - Were you able to get the devices installed? Looking at your last post I think we may be having the same issue.

I noticed your garages are showing as “virtualgaragedooropener”. I’m having issues with the garage device being created for my garage that has a type of “wifigaragedooropener”, but my garage door with type “garagedooropener” is created fine.

@brbeaird - In your edge driver are you specifically looking for “garagedooropener” ? I’m wondering if that is why some of our devices are not being created in SmartThings.

ViperTK · November 3, 2022, 12:41am

No, still the same. Communication between the hub and server is good. but devices are not being created. My device type showing up as virtual could be due to the fact that I have the add-on MyQ controller that controls both doors. I don’t have the openers with in-built MyQ in them like some models.
Waiting on @brbeaird to advise on a possible remedy.

jkp · November 3, 2022, 1:10am

To anyone who has an RPI and using SSH or the Terminal window… consider getting Portainer. It will make things so much easier than trying to figure out why all the commands don’t work. Portainer offers a free 5 user license when you sign up. I don’t know if there are other options out there so check around if you don’t want to deal with the commands. It kept failing on me tonight with the new commands so I sought out a program that would manage docker on rpi. Installed it and had the container up in moments.

now trying to figure out why I can’t get the connector to install

BartschLabs · November 3, 2022, 2:24am

Not sure if my driver has updated. Is the latest V2022-11-02T05:08:15.091547917?

Yes, I’m using http://192.168.4.200:8090/status where 192.168.4.200 is my raspberry pi zero w docker host IP.

BartschLabs · November 3, 2022, 2:29am

@bthrock, perhaps you’re having the same broadcast problem I was having when using the Bridge network. I’m starting to think it has something to do with the specific host platform that docker is running on (some platforms forwarding broadcast packets to the container, some not).

If you attach the container to the host network and delete the forwarded ports, that might cause the bridge server to see the ST hub.

brbeaird · November 3, 2022, 2:56am

You may be on to something! I just updated the edge driver to look for device_family = garagedoor instead of device_type. Let’s see if that works.

@BartschLabs @jkp and anyone else running docker on a Raspberry pi - can you kill your container and then run this command to launch a new one?

docker run -d --name='smartthings-myq-edge' --network=host 'brbeaird/smartthings-myq-edge:latest'

You may need to prefix it with sudo if the user you’re running it as does not have docker admin rights.

I am not able to get this working using bridge mode on my pi with docker. This seems to be because certain docker platforms are more restrictive in letting UDP broadcasts come through. The workaround is to just use host mode for now.

jkp · November 3, 2022, 3:10am

that loaded fine for me.

I was able to get UDP configured in Docker using brdige but could not verify it was working.

I was able to get my Connector installed earlier (had to reboot ST hub) and server reports the devices but still waiting on Garage Door to load in the app. Still not found with your latest docker commands but may be too soon.

Topic		Replies	Views
[ST Edge] Sense Energy Monitor [BETA] Community Created Device Types requires_server , energy , aftergroovy , edge_services	24	2164	June 8, 2024
MyQ garage door openers Devices & Integrations	8	1026	September 30, 2023
MyQ Lite for edge, be able to use without having to create a server Devices & Integrations	23	3575	September 8, 2023
Build automations based on device online/offline status Community Created Device Types requires_server , project_power , edge-device , edge_misc	33	3849	August 12, 2023
General question about SmartThings Edge architecture Support	8	338	August 30, 2023

[ST Edge] SmartThings MyQ Edge (Obsolete)

Related topics