Unable to register with mDash

capt.asic · August 1, 2019, 12:14pm

code works fine, tried to tie the device into mdash and get the following errors. I do have a custom MQTT server defined, but i included the mdash library as directed.

Aug  1 14:13:28.728] mg_ssl_if_mbedtls.c:207 0x3fff1534 mbedTLS error: -0x2700
[Aug  1 14:13:28.734] mgos_rpc_channel_ws:205 0x3fff09ec TCP connect failed: -3
[Aug  1 14:13:28.745] mgos_mongoose.c:66      New heap free LWM: 24968
[Aug  1 14:13:33.743] mgos_rpc_channel_ws:261 0x3fff09ec Connecting to wss://mdash.net/api/v2/rpc, SSL? 1
[Aug  1 14:13:34.550] mg_ssl_if_mbedtls.c:35  0x3fff15bc ciphersuite: TLS-RSA-WITH-AES-128-GCM-SHA256
[Aug  1 14:13:34.697] mg_ssl_if_mbedtls.c:35  0x3fff15bc x509_verify_cert returned -9984
[Aug  1 14:13:34.703] mg_ssl_if_mbedtls.c:35  0x3fff15bc   The certificate is not correctly signed by the trusted CA
[Aug  1 14:13:34.710]
[Aug  1 14:13:34.710] mg_ssl_if_mbedtls.c:207 0x3fff15bc mbedTLS error: -0x2700
[Aug  1 14:13:34.715] mgos_rpc_channel_ws:205 0x3fff09ec TCP connect failed: -3

lsm · August 1, 2019, 12:22pm

The mdash.net uses MQTT protocol, thus both of your custom MQTT server and mDash compete for the MQTT settings. Choose one.

You can create multiple MQTT connections to multiple servers “by hands”, but that is not as trivial as setting mqtt config.

capt.asic · August 1, 2019, 12:37pm

according to the library, i can assign a second mqtt for mdash explicitly, is this wrong?

github.com

mongoose-os-libs/dash/blob/master/mos.yml

author: mongoose-os
type: lib
description: Support library for the device management dashboard
version: 1.0

sources:
  - src
includes:
  - include

config_schema:
  - ["dash.enable", "b", false, {"title": "Enable"}]
  - ["dash.token", "s", "", {"title": "Access token"}]
  - ["dash.server", "s", "wss://mdash.net/api/v2/rpc", {"title": "Server address"}]
  - ["dash.ssl_cert", "s", "", {title: "Client certificate to present to the server"}]
  - ["dash.ssl_key", "s", "", {title: "Private key corresponding to the certificate"}]
  - ["dash.ssl_ca_cert", "s", "ca.pem", {"title": "Verify server certificate using this CA bundle"}]
  - ["dash.send_logs", "b", false, {"title": "Send logs"}]

libs:

This file has been truncated. show original

lsm · August 1, 2019, 12:52pm

The library uses Websocket connection, not MQTT. Thus is it possible to use the library together with the custom MQTT server. However, we discourage that since the Websocket support may be deprecated in the future.

capt.asic · August 1, 2019, 12:54pm

i certainly hope not as I am planning on an enterprise solution and have narrowed down my best option to be mDash, i’d hate to have to reconsider

capt.asic · August 1, 2019, 1:17pm

I managed to get it working by adding teh CA-bundle and deleting the lines for the SSL cert and key. seems good to go for now, hopefully you give a fair notice when you plan to deprecate websockets. Also, a side question, why cant I rename “deviceXX”, or am i doing something wrong? i assumed it would update with the actual device ID, but its not.

lsm · August 1, 2019, 2:21pm

Device attributes are immutable except the shadow attribute which you can change.

capt.asic · August 1, 2019, 2:28pm

damn, that kinda sucks, lol. illl have to find a way to auto label devices then

lsm · August 1, 2019, 3:44pm

Set tags.labels string field in the shadow.
You can do it via the API.