sjenkins

@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.

@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!

@jkmcfadden , If you could download something like "MQTTexplorer" or equivalent for your operating system and see health status separate from the plugin, if it updates the offline status immediately when you unplug, or just when you plug back in. I am wondering if the update to the ISY is lagging. If it is logging directly to the mqtt immediately I can look into why the delay. If it is logging at the same time. when you plug in, I could pursue a parameter for last update. MQTT is a middle man which signals when a message comes in & you read it. No ability to get anything beyond that about the device (the health status parameter was supposed to tell if the device was talking to the mqtt). We can do a most recent message timestamp though.

@jkmcfadden , the id can be almost anything, droplet1, stephen, droplet2, it gets turned into the address of the node with a function to make sure its unique and short enough. The type must be "droplet". The name must be < 30 chars and also can be anything, kitchen, livingroom etc. Let me know if you see behaviour different than this.

@jkmcfadden , Ok!! Enjoy and test the crap out of it. Make a few programs but remember when we goto production those programs will require touching up. Has to do with having different id number to the regular plugin. Can’t think of any improvement path but let me know as you use it.

@jkmcfadden , Do an ISY reboot for me. Since eisy-ui came along this is sometimes required on many plugins Actually if you log onto the local AC it will likely all be there. The logs look healthy.

Hi @jkmcfadden , You installed the regular mqtt plugin. Go to the non-production store and scroll right to the bottom and install mqtt-poly It will be version 0.50.0

For the brave ones out there I have spent a bit of time to do a NON-breaking re-write. Mostly for the sake of making it easier to maintain, add devices, add testing files, and improve self documentation of the program. The devices have been made more standardised in their writing ; no changes to their behaviour . There are three new features, one I stole from another plugin, number of nodes in the controller node, just a sanity check. The second, is the ability to have a default status and or control prefix. Not sure who was asking for it, but I found the request in the logs. I updated the config instructions to include some explanation: - status_prefix: "tele/Wemos32" # any status_topic starting with ~ is replaced - cmd_prefix: "cmnd/Wemos32/power" # any cmd_topic starting with ~ is replaced devices: - id: "WemosA1" name: "Wemos A1" type: "analog" sensor_id: "A1" status_topic: "~/SENSOR" cmd_topic: "~/" Finally, the third is a new device, "droplet" which was requested to handle the Droplet water monitoring device, see the config for instructions. Again, all this is meant to be non-breaking but we won't know until more people than me test it. Download and put this non-production version in a DIFFERENT slot than your production, you can point it to the same YAML config file you use or a new test one. Please do some testing and put some feedback here, it won't go into production until we get a few thumbs up as there have been too many changes to risk peoples automation. Thanks! =========== 0.50.0 DONE refactor Controller/Nodes for Pythonic & commenting DONE add user defined default status_prefix & cmd_prefix DONE add numofnodes DONE add MQDroplet device

ok @jkmcfadden , you can download from the non-production store mqtt-poly version 0.50.0 , its right near the bottom due to being all lower case. Your yaml file will need to have something like this: - id: "droplet_kitchen" type: "droplet" status_topic: "droplet-ABCD" cmd_topic: "droplet-ABCD" # don't forget me, even though we don't use it ! I tested it out, without a device but pushing data through the MQTT & it populated on the ISY just fine. Let me know what you see! ps. @tmorse305 - I just searched back in this forum, if you are still interested you may want to give this a try.

@jkmcfadden , So above I updated the drivers & commands in the above post, found a "health" state which is different than the "server status". Health is connection to the MQTT, which server is connection to the Droplet cloud. By doing both of these it changes how you would set up the device in the yaml file a little bit (makes it simpler): MQTT Configuration Example: --------------------------- In your devices configuration, add a Droplet device with the base topic: - id: "droplet_kitchen" type: "droplet" status_topic: "droplet-ABCD" cmd_topic: "droplet-ABCD" Where ABCD is your Droplet's 4-character identifier. The NodeServer will automatically subscribe to: - droplet-ABCD/state - JSON with server, signal, flow, volume data - droplet-ABCD/health - Plain text "online" or "offline" status NOTE: I will push this to the non-production store later this evening after I get a chance to test it. It is called mqtt-poly, all lower case. You will have to put it in a different slot than the production version if you are using it for anything else; as this beta does not play well with the production version. @TriLife and I are working on transferring ownership of this plugin. @xKing wrote it originally, I took it on when I was using the devices a lot, then TriLife took the lead as his whole house used it. He is moving to different technology & so he asked me to take the lead again, which I am happy to do. During all this I want to make sure we stay stable for those users who depend on it. That is very important. I have done a rewrite of the plugin, including adding this device. I have tested it but need the user group to test before it goes into production. You are testing this as a new device so I just want you to know it may not make it into production for a few weeks.

@jkmcfadden , Understand the desire for "one node to rule them all", and that is the easiest to implement. Thanks for the link to the API, that will help a lot. So right now I would have these drivers & commands: """ UOMs: 2 = boolean 25 = index 35 = liter (L) 130 = Liters per hour (L/h) Note: Flow rate from Droplet is in L/min, so we multiply by 60 to convert to L/h Driver controls: ST: Server Connectivity Status (index: 0=Connected, 1=Connecting, 2=Disconnected) GV0: Signal Quality (index: 0=Initializing, 1=No Signal, 2=Weak Signal, 3=Strong Signal) GV1: Health Status (boolean: 0=Offline, 1=Online) - MQTT connection via LWT WVOL: Water Volume (liters) - point-to-point volume since last update WATERF: Water Flow Rate (L/h) """ drivers = [ {"driver": "ST", "value": 2, "uom": 25, "name": "Server Status"}, {"driver": "GV0", "value": 1, "uom": 25, "name": "Signal Quality"}, {"driver": "GV1", "value": 0, "uom": 2, "name": "Health Status"}, {"driver": "WVOL", "value": 0, "uom": 35, "name": "Volume"}, {"driver": "WATERF", "value": 0, "uom": 130, "name": "Flow Rate"}, ] """ Commands that this node can handle. Should match the 'accepts' section of the nodedef file. Below are receiving commands. DON / DOF will be sending commands """ commands = { "QUERY": query, }

@jkmcfadden , You’ve done what you can here. The mqtt plugin is not really set up as a general purpose mqtt interface, it has specific devices which are pointed to topics that device understands. It’s been rattling around in my brain that some kind of general purpose with fields like you are attempting would be fun to make. So currently what we need to do is make another device specifically for this. On first glance I think you have given us all needed to do this. The question a while back from the other Droplet user didn’t have the data you have provided here to go to the next step. I’m doing this on my phone and am pretty full with meetings today but could likely whip something up in the next few days. The json parameter will be simpler as the plugin parses JSON already just fine. So you would call this the Droplet-AE50 , correct? Also, I will need what the ranges or possible values of the fields are, like what is “not connected” “unconnected” or “low battery” “med battery”. I can collect and store unknown ones for now, but will need them eventually. The reason being is I need to parse them and turn them into an index which ISY uses another index to display. We don’t send the whole text to ISY with plugins.

@bmercier Good enough for me. I will offer, if you have scraps of notes on hints or anything you want to puke out of your brain on the subject, to update the hints docs on the wiki and/or the github. Maybe a link from the developer docs. A while ago @Michel Kohanim asked me to do some docs based on my plugin docs. I failed him on that due to my non-use of vscode. Happy to help with this an let you do the more "high value add" stuff.

You mentioned having many Insteon temp and leak sensors. I had my house covered with them and have moved to YoLink for temp, leak, and water valve control. The LoRa protocol is the main reason and local aspects of leak detection (even with the non-local hub, because of the ability to link locally), are a real seller. In addition getting a read on the Insteon batter sensors was a bit hit and miss ; don't get me wrong loved them as an option, but have moved to YoLink for these kind of devices. Also, have moved to the local hub to satisfy my tinfoil hat. I keep Insteon for switches, tried one YoLink switch for a Florida house & would not use everywhere. Things you don't need instant data but want reliable are the sweet spot for these. YMMV but some thoughts with a > 10yr Insteon and few year YoLinker.

@bmercier , sorry to bug on this one, but as I am looking at my hints across my plugins. I have been using the github docs at: GitHubhints/hint.yaml at master · UniversalDevicesInc/hintsNode Server device node hints specification. Contribute to UniversalDevicesInc/hints development by creating an account on GitHub. but digging a bit I see in the wiki there is a less complete, but labelled 0.2 version: https://wiki.universal-devices.com/Node_Hints_Documentation They are a fair bit different in their specifications. Your 4,8,x,x suggestion would give me wildly different answers depending on which one I use. Is there a third place you are getting this from? I do not see anything in the developers docs which are linked from the main UDI site and eisy-ui.