Skip to content
This repository has been archived by the owner on Oct 22, 2022. It is now read-only.

Commit

Permalink
Clarifies in documentation that Lattices will re-connect if the broke…
Browse files Browse the repository at this point in the history
…r goes down
  • Loading branch information
alex-miller-0 committed Feb 3, 2021
1 parent f1959fc commit f49427f
Showing 1 changed file with 1 addition and 5 deletions.
6 changes: 1 addition & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ The [Lattice](https://gridplus.io/lattice) is a next generation, always-online h

By default, communication with all Lattices is routed through GridPlus' centralized cloud infrastructure. Although there is great care that goes into encrypting and securing these communication channels, we at GridPlus want your Lattice to be 100% yours, so we want to offer `lattice-connect` as an alternative to centralized message routing. This module exists to bridge connections between target Lattices and web applications (generally, but not limited to, applications that use the [`gridplus-sdk`](https://github.com/GridPlus/gridplus-sdk)). **If you are an advanced user, you can deploy this module yourself and change your Lattice's config to hook into your deployed instance.**

This module contains both HTTP server and MQTT broker, so it can be used as a singular communication endpoint. *It is important that the process created by this module does not go down, as any lapse in availability can result in severed connections with Lattices subscribed to the MQTT broker.*
This module contains both HTTP server and MQTT broker, so it can be used as a singular communication endpoint.

## 🏃 Installation and Usage

Expand Down Expand Up @@ -171,10 +171,6 @@ If you are not getting messages from your external requester to your Lattice, so

The most generic troubleshooting you can do is unplug your Lattice and plug it back in. Wait a minute or two and make sure that the top right of your screen eventually shows only a single icon: the wifi icon. If it shows any other icons, you probably aren't connected to the internet. Update your wifi on your Lattice by going to `Settings -> Wifi`.

### Make sure your cloud service didn't go offline

If your MQTT broker goes offline, it will probably sever connections with subscribed Lattices. You can repair a connection by simply unplugging your Lattice and plugging it in, assuming your Lattice is connected to the internet. You can also run `service mosquitto restart && service gpd restart` if you are SSHed in.

### Watch trace logs

If you want to get more information about what's going on with your app, update `config.js` to use `LOG_LEVEL: 'trace'` and run:
Expand Down

0 comments on commit f49427f

Please sign in to comment.