sjenkins

@Panda88 looks like the TSTYolinkLocal is now dead in the water. The "subscription" is out of date & it has shut down. Won't restart or re-install or update. Not sure what is required to give it a jolt, but would appreciate more time on it until the production version makes is out of your shop

sorry I should have been clearer as I knew it would NOT work as a scene controller only in a program as controller (versus status) Scenes prefer DON and DOF. I can add them but there is a design choice here: Insteon uses DON/DOF as 100% / 0% not brighten / dimming. Currently the dimmer / generic device does not have those commands. option 1: add DON/DOF commands as 100% / 0%, this is most consistent with UD scenes which are aligned with insteon scenes. option2: use the current brighten / dim which move the percent by 3% I believe. I would just send the DON / DOF command along with the current command. This might be more useful considering the device but confusing for scene consistency. thoughts?

works ; nothing blew-up ; thanks! Update: the trial period message comes back saying "this node server will expire soon", assuming that 60 days is "soon"

Try it out, I added the commands for tapping up and down on the bright but not for the new value. Also it currently doesn't have DON or DOFF which are the normal on/off commands. Could be added though.

I do think just a new version, same content just bump the version in the development screen & push out the trial time period. Just my opinion, I agree trying to do this in one remote and local version sounds like a nightmare. I at least have never written a program right the first time. You have made this thing really stable ; hate to ruin that. Michel/UDI are really helpful in everything but consider this ; you are truly adding a feature which was not part of the program we originally purchased. I can only speak for myself but I am more than willing to pass you a few bucks for the effort & support involved. My vote is put out a new Yo-link local and call it a separate plugin with a fair one time price. Just one vote but you could put it out to the population.

@Panda88, Would be great if you could "refresh" the beta and kick out the time period until you are more ready to either merge or not-merge the two. I was so excited about local that I DID move my programs over to the beta. No worries I will move to whatever solution you come up with, but would be nice to hang out with the current set-up until then. Thanks again for the efforts, this plugin is now part of the plumbing of my home automation ; literally & figuratively.

As I mentioned to @Diesel not sure why this has not been added before now other than because we all got used to using them as responders. I tested out the switches as control in programs & scenes. Try out the generic, dimmers, garage. I will leave this in beta for a bit to make sure there are not any unintended consequences. I know many of you have this plugin integral to your home automation, please throw me some feedback. 3.1.14 \ DONE commands for switches, generic, dimmer, garage 3.1.13 \ DONE prevent direct poll from re-running \ DONE add notice if comms check fails \ DONE clean-up & debug 3.1.12 \ DONE rewrite sse events collection

@Diesel , sorry for the slow return, been a busy summer. Although the programming doesn't quite work as you have above, this is a feature which should have been added long ago. Not really sure why, I guess we all got used to using it the way we did, as a responder in a scene. Anyway, I have put it up in beta on the non-production store in v3.1.14 I will give people a while to play with it to make sure there are not any unintended consequences.

hi @tmorse305, looks like good work here. Give me some time ; I've got a couple projects backed up & unfortunately I still work. I would look to make a new node in the mqtt plugin framework will start simple & add info & bells & whistles in layers will need you in the test loop, sending me logs as we go. likely will have some clarifying questions too; a snapshot pic of your mqtt explorer screen with some of the above fields populated will colour between some lines I'll update here as I have something ; before then feel free to ping if I go dark too long for a pulse check.

thanks @Guy Lavoie , @DonM there are three different ways to config virtual devices: 1. standard: the way guy shows above, which is the most simple. put a number for the key and type of device, like switch in value 2. json: a json string which describes the devices 3. yaml: a file which describes the devices hit the button for configuration and scroll down, it should describe all of them. (screen shot below) once you do that you should NOT need to do anything in the admin console to add the devices, they will be added automatically

Got around to checking @TJF1960 , can confirm that it does just fine work assuming your router keeps your local network up and going. To explain when I pulled the cable from the modem all was fine ; when I pulled the ethernet from the back to modem (to my router) my router took down the majority of my local network. One to add to my TODO list as I take one off.

I keep meaning to but haven't found the window when I won't get yelled at by the family. I'm off this week so its on the TODO list. I will try to validate @Panda88 's test. I will say that I have been running completely on the Beta plugin with no issues for that last number of weeks. Moved all my programs over will all good.

will need to know for each of those what the number is and the unit. for online status, what are the possibilities: eg, (0,1,99) or (ONLINE, OFFLINE, UNKNOWN) or (online, disconnected, none) need to know these exactly.

@tmorse305 we would need to add a device which creates a node for your flow device. Is flow the only data sent? also, no control? what are the units? knowing the above its not a huge deal to make another node. let me know.

Should only effect VirtualGarage