sjenkins

Couple bits of news: First, as you know @TriLife has had the lead on this plugin for a few years, with me helping out, mostly with the non-Tasmota nodes. As his use case has been changing he has asked me to take the lead. Big thanks for all his time and efforts, both with building the plugin and tireless helping of users. I will still need to call-a-friend with the Tasmota nodes; he has more real world experience than almost anyone. Second, as I now have the "keys", I can put into the non-production store the 0.50.0 update named properly MQTT (as opposed to mqtt-poly). This beta version can be put into your production slot and then revert back to the production version as the NSID is consistent. There are a few out there who have been using the mqtt-poly version due to the new features and Droplet node. The plan is to let you play with it for a week then move it into the production slot. Please let me know if something is amiss or didn't work in the transition. Just to remind, below is the log of this non-production version: 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

A few minor updates, 1.13.2 is back office so I didn't announce it, while 1.13.3 fixes two bugs, one which caused a crash on every batteryLevel event. I will leave it in beta for a few days before moving to production. Let me know if anything seems amiss. sj """ 1.13.3 DONE package updates "dependabot" DONE fix typo, crash on batteryLevel event DONE fix timeout, drop every 300s timeout 1.13.2 DONE requirements.txt changes DONE comments improvements DONE testing additions 1.13.1 DONE refactor controller discovery, put, get, goodip functions DONE refactor controller startup, config, params, naming, logging DONE refactor cmdSetPos 1.13.0 DONE polling rewrite, controller: shortPoll=G2 poll, heartbeat for all, re-start G3 events, longPoll=G3 poll DONE polling rewrite, shade: shortPoll: re-start events if stopped, longPoll: not-used DONE polling rewrite, scene: shortPoll: re-start events if stopped, manually clear G2 scene activate, longPoll: not-used NOTE default & recommend setting shortPoll=60, longPoll=600 DONE major re-write of function and Event routines DONE add number of nodes managed by controller to controller node

If there is value, it wouldn't be hard to make another virtual device which could hold an Integer or maybe a number with pick your number of decimal places (zero being integer). Would you move the number there in a program or like the temperature device. I don't have a need for this, is this something that is required for different use cases? This looks similar to what @tazman was looking for ; am I right?

I haven't yet ; started looking into it then a butterfly flew by. I've put it on the request list now.

sent you a DM with it.

Fixed with update

@Panda88 , Low on the priority list, but for feedback. I am growing my YoLink fleet & added a couple motion sensors to test. they are the YS7806-UC, seems the temperature is showing -67C on the AC no matter the temp showing on the app device screen. EDIT: seems to be well off for the Two button FOB YS3614-UC Again, I don't actually use these, just to add something to your todo list

@Panda88 , All my devices with legacy and non-legacy are the same except for the water valve manipulator. I have the YS5001-UC, see below, Manipulator (legacy) shows open the other shows closed. Legacy is correct.

This update takes production up through 3.1.26, with adding the onOnly device and fixing an old bug in garage which caused intermittent crashing. The rest of the changes are clean-up in nature, let me know of any unintended consequences. VERSION = '3.1.26' """ 3.1.26 DONE add timeout to ratgdo requests and sse client to prevent hanging DONE chg DFOF to DOF for Toggle & onDelay 3.1.25 DONE add onOnly device DONE update generic project files DONE Controller comments, refactor checkParams DONE change hints for temperature devices DONE testing added

@tazman , That mirror is beautiful, very nice job. I get the desire to get the data public for all to see. I need to get around to something like that. If you are good with the workaround, then I will put it on the list but not too high. If we get more interest in #3 I could move it up. Let me know if that changes.

I was having this new device issue ; 6.04_1 fixed it for me. So far it did NOT fix the socket error pop-ups though.

@tazman , sorry for the delay, been on vac with the kids. Was just coming to answer when I see your last message. So, lets me say back to you what I think you want. you want to on some regular interval take a value from a variable put it in a GV value with the KW or (and?) KWH unit does the variable need any other processing? (conversion or multiply/division) you are just using the temperature device as a model, there is no need for temperature functions Let me know if I got it right. If the above is correct and this is of value you could come at this a couple of ways. kluge the temp device to make this work make a specific device for KW or KWH make a generic device which the user in their set-up would set the unit and maybe conversions if required. I'm not doing #1, the temperature device is the ugliest device already. My preference on it is to remove the AC controls and have it set-up with the yaml or json. #2 could be done quickly but may be a user base of one. #3 could be useful to some of the other HA users who are moving values back and forth to variables and want some units attached to them. The #3 device could look like this ST = status of the node, GV0 - GVn could be a list of values with units defined in the set-up json or yaml. UD has added a feature which lets nodes be defined pragmatically rather than being hard coded in profile files. I have not tried it out but this adds significant flexibility to nodes which need this. Interested if anyone else would find value in #3, to make the mountain worth the climb.

Hey there, just saw this thread, I am the curator of the Virtual plugin. The virtual devices do send control or switched signals as well as status & work in the AC or UD Mobile. Thus they will fire scenes or programs. Saying that some of the advice higher up does apply & is the way to do it without Virtual. Think of this plugin as a "macro", doesn't do much impossible without it, just shortcuts things. For this use case I might use a virtualSwitch and have the Fastoff program set it, while a program with the other switches turn it off. In the AC or UD you could change the virtuslSwitch directly. Now your other programs could use the "flag". You could mix and match with scenes and virtualSwitches as well, but as mentioned fastOFF is easy to pick-up in a program and more subtle in a scene. FastOFF immediately turns off the scene which just off uses the ramp ; I have used this feature to make a delayOFF happen, but in the end I created a virtualDevice to do this. hope this helps.

@Guy Lavoie , You have mentioned this before & didn't understand so I think my answer was incorrect. I am able to trigger scenes with a virtual switch both from UD Mobile and the the Admin Console. I am also able to trigger a program using a virtual switch from the AC and have programs turn a light ON or OFF using control. I just verified both again to make sure there were no changes. For example: test dimmer ON - [ID 0068][Parent 01B1] If 'Virtual Device Controller20 / Test Dimmer' is switched On Then Set 'Living / Living Fireplace Lt' On Seeking to understand here ; can you explain more what you are trying to & what isn't working?

Two fixes, one which only effects ratgdo garage node hopefully preventing hanging ; two fixing Toggle and onDelay so they send only DON and DOF. Feel free to test and let me know if everything is acting as expected. VERSION = "3.1.26" """ 3.1.26 DONE add timeout to ratgdo requests and sse client to prevent hanging DONE chg DFOF to DOF for Toggle & onDelay 3.1.25 DONE add onOnly device DONE update generic project files DONE Controller comments, refactor checkParams DONE change hints for temperature devices DONE testing added 3.1.24 DONE configuration based optional overide initial default 3.1.23 DONE add onDelay, offDelay, toggle switch, update documentation DONE magic number scrub 3.1.22 DONE generic/dimmer static/dynamic behaviour

@tmorse305 , Looks like the team has you covered. Anywhere under your home directory. I made a dir for all my local test plugins which I keep these, but anywhere there is good. Thanks @jkmcfadden & @maxnorth !!

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