sjenkins

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.

The devlist is what you put in the config screen. The logs you can download from the log tab. both tabs are in the mqtt screen of pg3.

@SSamuels, would you mind sharing a copy of your devlist or devfile and the debug.log file? either here or dm is fine

@maxnorth Pushed version 0.40.1 to non-production store 'mqtt-poly' not 'mqtt' variables are available to programs now

Take a look at the edits at the top of this thread & then install from the beta (non-production) store The one you want is mqtt-poly. ** not mqtt We are using the above beta as the alpha .... if that makes sense to you. Give it a test and respond with feedback so we can move it forward.

for those watching here, potential solves for this are in the beta (non-production) store. mqtt-poly NOT mqtt If @SamM verifies he is satisfied, we will call this solved, or take another run at it.

Just putting out there a feature which you may not be aware of which was added recently. The heartbeat feature is part of the UD Template so I won't take credit for it, but many don't seem to be aware of it. Below is an example of the program you would want to have to take advantage of it or something similar. I use this in all my plugins, as well of course devices which offer heartbeat signalling. Heartbeat MQTT - [ID 00CB][Parent 0028] If 'MQTT' is switched On And 'MQTT' is not switched Off Then Wait 1 hour Repeat Every 24 hours Resource 'Heartbeat MQTT' Else Wait 1 hour Repeat Every 24 hours Resource 'Heartbeat MQTT'

Just putting out there a feature which you may not be aware of. The heartbeat feature is part of the UD Template so I won't take credit for it, but many don't seem to be aware of it. Below is an example of the program you would want to have to take advantage of it or something similar. Heartbeat MQTT - [ID 00CB][Parent 0028] If 'MQTT' is switched On And 'MQTT' is not switched Off Then Wait 1 hour Repeat Every 24 hours Resource 'Heartbeat MQTT' Else Wait 1 hour Repeat Every 24 hours Resource 'Heartbeat MQTT'

@SamM , Your devfile and your whole debug.log which includes a restart would be most helpful. Feel free to DM to me.