@jkmcfadden,

Likely the droplet server has a timeout of that length which triggers it to send the health signal.

Let me know how the adding of the next Droplet goes!

@sjenkins So my second droplet arrived and has been successfully added to MQTT. Thank you for all you help!

Once you have moved it into your production MQTT release, I'll re-add everything. But for now, everything looks good with beta.

For anyone looking to add this device, here is what I did.

1) In the Droplet phone app -> Smart Home Integrations -> MQTT, configure:

Host Name : the local IP address of my EISY

Port Number: of my MQTT interface (I used 1884)

User name and password of your EISY

All other fields blank

2) I added my .yaml file name in the MQTT configuration entry

3) I added the below entries in my .yaml file (I have two droplets). The status and cmd topic entries are the unique value displayed in the phone app, type: must be "droplet", id: and name: are what I chose.

devices:

- id: "DropletAE50"

name: "Droplet-AE50"

type: "droplet"

status_topic: "droplet-AE50"

cmd_topic: "droplet-AE50"

- id: "Droplet53B4"

name: "Droplet-53B4"

type: "droplet"

status_topic: "droplet-53B4"

cmd_topic: "droplet-53B4"

Once I restart my MQTT to pick up the entries, this is what I see in the console:

I created a test program to notify on flow and that worked as well.

Kelly

@jkmcfadden ,

Good news!

Small item from your notes above:

The EISY MQTT server at 1884 will work without an id or password, admin / admin is fine or anything else.

Unless you actively change it yourself on the EISY from ssh.

The server at 1883 is the one used by the EISY for conversations with the POLY ; it is behind security for obvious reasons.

I have not received any feedback from the crowd on the beta in the last week or so. Will give it a bit & push to production.

Edited Thursday at 06:43 PM1 day by sjenkins