sjenkins

@maxnorth to answer your question of when, I was waiting for stability & for @TriLifeto return from vacation. We currently have two betas as we both have been developing features and testing them independently. And so with the way polyglot is structured it does not lend well to multiple developers or more accurately more than one releaser of versions. I honestly don’t know if the name change will do it due to the fact that the id used is pushed from one persons developer list who first pushed the app. The id is specific to that app but can be pushed to more than one store. What I normally do when I have caused this issue inside of my login (by creating the listings independently) is go into my developer list, delete one, and push the beta or production from the listing for the other one. This aligns the ids. @bmercier do you know of any way for two developers to push a shared app which then the stores will allow users to install on top of a current install? Is the matching name enough? Or is the id the critical item. You can modify/mimic a name but not mimic an id. Or is the system set for on person to be the pusher of store listings. bottom line our new versioning structure will make this easier. If @TriLife pushes a major version to each store, say 0.45.0 using branch 0.45.x to beta and 0.44.6 using branch 0.45x to the production store. Through the GitHub I can make changes to the branch and they will push. Not perfect as the minor version is currently represented in the push. Again the system is not set up for multiple pushers of development versions.

I had one of those hubs (they were cheep and I was curious). Don’t use it anymore as it added no value to my setup. But while a pita , it’s not as nuclear as resetting all your devices. More of an elephant , one byte at a time. (sic) It’s just a controller like any other. Start adding your devices to it. I think it can just find them if I remember. Scenes were not so easy then, but it may find those now. I was able to use it in parallel to my PLM and 994 at the time. When I dumped the hub I just deleted everything off it (the opposite of what you will do) I didn’t add any automation to it as it could only do schedules then. You could add some simple ones to “sell” your house. Just wipe your PLM and 994 before you leave.

v3.1.2 renaming of nodes based on configuration ISY nodes to be renamed based on config / YAML / JSON changes - rename will happen upon restart or Discover - rename will not happen to default named nodes, where no name was given in the config, so as not to wipe out user renamed nodes in ISY Feedback is welcome, let me know if you have new ideas or devices you would like on the list. I next plan on adding the Garage device, which was my original reason for asking permission to take on this plugin.

See the config instructions for details, Bottom line I added two additional ways to do configuration YAML & JSON, which should make it easier to keep longer lists of devices and back them up. Additionally, this allows more specific naming of your nodes in the configuration. Added the Discover button which in most cases will add/remove nodes based on the configuration. Beware this will delete nodes if they are not in your configuration which was possible to do in the past. I have seen cases where the node is not deleted as it does not show up in the poly node list, just the database. Those you have to delete in the node list. If this is a big deal I can return to it. Finally, some more documentation rework. Let me know if anything is unclear or you find mistakes. Feedback is always welcome! VERSION = '3.1.1' """ 3.1.1 DONE: YAML file option for configuration DONE: JSON option for web based configuration DONE: Discover button to update based on config updates TODO: updates to YAML / JSON based on ISY name changes TODO: new device garage door (update to/from variables option) 3.1.0 DONE: move version history out of README to own file DONE: update docs 3.0.1 DONE fix get value from variable 3.0.0 DONE add control ability to contact device DONE refactored to modern template previous updates: see versionHistory.md

thanks @hart2hart , the electrons must be running slow tonight

Thanks @tazman, Interesting, perhaps the updates are going out slowly?

Thanks guys, I’ll put a ticket in.

odd, like I say I verified on two different devices & downloaded from them I have had issues in the past with updating to the store but that was before they fixed the name change issue. Could someone else out there verify the versions on the production and beta stores for Virtual ?

Thanks for the feedback @hart2hart Beta store should have version 3.1.0 Production store should have version 3.0.1 Are you referring to the blue message that there is an update available or that the store did not update? I did not get the blue update message but the new versions were available in the stores and I was able to upgrade into the existing slots on my EISY and POLSY. I am going to assume the lack of blue update messages is one time as this is my first upload to production. The UID did reset. Can you verify you were able to load them into your current slots?

No functional changes, just refactoring and fixing of the variable write features. see beta Topic for 3.1.x discussion ISY ACCESS IS REQUIRED , tick box is in configuration for those new to this variable write cannot work without this since PG3x changes, see code if you are nervous about this 3.0.1 DONE fix get value from variable 3.0.0 DONE add control ability to contact device DONE refactored to modern template previous updates: see udi-Virtual-pg3.py

@tazman thanks so much for the verification. also, I didn’t mention the need to turn on ISY access for the write to variable to function. I will need to add that to the config instructions And yes you are right on the one digit precision, wasn’t sure if there was any need for more flexibility based on use cases.

I love my OpenSprinkler!! Had the same unit for over 10years now, its plastic is severely yellowing but it’s rock solid. Thanks to @Javi for writing the plugin for the ISY, if I remember right he had to mod it for me because my device is so old & an early version. I am likely the only one still running 2.1 hardware.

per @Goose66 , my multi-device set-up with the homeESP version & HA has been solid for a month now. One day I am going to come back to it and simplify with a plugin, but for now I am pretty happy.

ok I pushed an update to the beta 3.0.1 This fixes the temp and tempc devices as far as the pull and push. So you know, it doesn't pull/push immediately, but on the short poll timeframe. This was a bit of a quick one, so give me feedback; also, I have not been much of a user of these devices until now. opportunities: The average calculation is a bit rudimentary, just high-low / 2 cleaning up the code ; it has some relics hanging around Adding the ability to handle variables with precision other than zero would be good too. Busy week for me so the improvements will not be fast but I should be able to do bug fix. If anyone feels so motivated to update the docs & put up in a thread for peer review, that will speed up the process a bit.

Shouldn’t need to delete to remove those things. Just click the x beside the variable in the configuration tab. save configuration. Restart the plugin.

I would be curious what it looks like after an ac reboot.

I will likely move to a json string holding those variables. btw: : ip, login, and password are holdovers from pg2. They should not be required & looking at the program are not used.

@paulbates , I think the instructions have opportunities, as you have found out. think of the variable name just as a key field. Just needs to be a unique number, has nothing to do with your variables in your ISY. No mapping there. unfortunately the name is just the device type. I would like to add better naming from the plugin. You can rename it to anything you want in the ISY. I keep the number id in the name so I can keep the link. hope this helps.

@tazman , I must apologise, I was testing things out with a number of different starting settings in my local version. It must have been late when I pushed the Beta. Cleaned that up now. As the only changes that I was 'attempting' to make was refactoring, the only testing requested is that it works the same as the old version. Next step will be to start making modifications. Appreciate the feedback & if anyone has any old bugs or new feature requests.

I would say the best is to play around a bit with it. Put a virtual in a scene too. agree you can do it all with programs; this does simplify & make more readable. And we can add more devices if their behaviours are stable.

@paulbates , I do agree, some plugins are obvious ; my other plugin is an interface to HunterDouglas shades, pretty obvious ; this one on the other hand may be at the other end of the scale as I think of it more like a basic tool. So here I my attempt at at a 10k ft description of the Virtual plugin: The Virtual plugin is one way to take data from external sources and in turn use these nodes of data more effectively. The nodes become devices from which status and control are possible in programs & as an included device in scenes. It as well as cleaner display in the AC and Remote tools. I use REST to switch a virtual device from an 8266 device. My Awning controller & heartbeat from Alexa I switch a virtual device. The status of my daughter's goodnight routine. the above devices can be part of scenes or programs both status and control these devices are one way to provide scene status if you make them part of a scene virtual devices can be used to consolidate data. The temp devices, & I am looking to add a garage device. Hopefully this helps. Appreciate the question as it made me think and articulate a few things. I will likely add the above to improve the docs. Remember the above is only from my view of this generic tool plugin. I would appreciate for others to chirp in their thoughts and use cases.

**** Update, I have started to work on v3.1.x adding features. My plan is to push to production v3.0.1 (no new features, just rewrite) and use the beta channel for testing the new features. I am not hearing of any continuing v3.01 issues so we shouldn't break anything with this. Beta now has v3.1.0 with some doc changes, will update as features are added Just be aware for those who continue to follow the beta path! As I do this there may be some one-time disruption to the crowd requiring delete and reinstall rather than update. Has to do with the UID numbers are currently different from production & (beta / my local) due to when I got control of the production. Apologies for this, but I need to rip the bandaid off at some point or it will make switching between them a pain forever. Hi users of Virtual I have been using this plugin for a number of years and appreciated the 'glue' it has provided to some of by automations. A few weeks ago I asked for & received permission to take on stewardship of it from @bpwwer , thanks Bob for all you do! I have done a rewrite, putting it in the 'standard' template ; this will make it easier to maintain, add new devices and features. It is published it in the beta store starting with version 3.0.1 , no new features as of yet. So with this message, I am asking for the brave to test the beta & also to put into this thread any past, or current bugs in the plugin, as well as feature requests. I will fix the quickies & the others can kick around & prioritise development. My current list: bug-list will take priority (I don't have any but looking at the forum there may be some past complaints) In addition to current node method, allow a JSON list and/or YAML files (makes it easier to re-install or back-up) I re-name my nodes in ISY from the way they are defined in the plugin. A name should be able to be defined from the node & updated if changed in the ISY (again easier to maintain) may use Discover button to force re-examination of the above two. Not sure in this plugin if any other 'true' discovery as parameter changes should update on their own unless from file new device for garage door opener (I want this) documentation improvements - Temp device improvements The average calculation is a bit rudimentary, just high-low / 2 not hearing any great demand for change here cleaning up the code ; it has some relics hanging around adding the ability to handle variables with precision other than zero would be good too strike for now based on feedback - HERE IS WHERE YOU ADD IDEAS Stephen

This is solved as of version 0.40 of the MQTT plugin

Hi @EWhite, chugging through the issues list and am digging into them one by one. just played around on my test system with the iFan. it seems to be generating no matter where it is in the devlist as well it is interacting with the mqtt server writing and reading. Wanted to check with you and see if the issue is still happening on your system

Good news; you had me for a moment. Took me a while to unwind that one. The editor profile file was messed up for s31. Anytime the profile files are changed restarting the AC needs to be done.