markv58

@Teken Try this, go to the Virtual folder and delete all .db files in the folder then restart the nodeserver. This shouldn't affect any of the settings in the nodes. Restart the nodeserver.

@Teken Maybe something glitched during the update. Do a git pull in the virtual folder and restart.

I have joy joy at my place.

And set your Raw to Prec

@Teken hit the delete db button. That should clear the problem.

Virtual 1.0.14 - You may need to set Raw to Prec on to correct data. Update Profile and restart AC please.

@tmorse305 That can happen on very rare occasions, I believe that is fixed solid in the next update which will show up shortly. The .db files need to be deleted to clear the error. You can do that manually or use the button in each node to do that after the update. v1.0.14 is pushed.

You can change that in ISY, right click and rename, having random names in custom config params can cause problems with ghost nodes being created and those are a pain to get rid of. Having digits as the key and a preset list of values to direct the node creation is the best way to go on this one. The Temp nodes are not going to change, a twist of a movie line in Back to the Future. With the Energy node, I agree that setting parameters like the Temp nodes is the way to go and you can always use a program if you want or need to. I am giving you a shot at the brass ring on this one @Teken. I learned so much doing the Temp nodes that it is no problem, I just need info about how those things work. I've looked at the Brultech / Dashbox stuff and might just invest in that and the one wire has uses for me as well but I can do most of it without the actual devices. I am going to work on the overall design and capabilities and play with it for a while.

I use that for the Since Update timing but it needs to send the HB to ISY. Devices send a HB and ISY is expecting that to happen but I don't think ISY expects a HB from nodeservers. I thought I saw something a while back but don't recall where, I'll think up something, dig around.

@Teken I took the liberty of having the raw to prec trigger automatically but after some thought I should probably stop that as certain circumstances could cause the false trigger or produce weird results. I'll pull out that code and let you do it manually. There are a few things to tidy up and I'm going to add a delete .db button for the nodes because that needs to be done on rare occasions. It's like starting up a new node, everything is wiped out and the db rebuilds. Reset statistics should take everything to 0 but only if there is a db for the node and it doesn't actually store the reset values until the next update cycle runs. Storing data in that instance, right after the reset, is one of the tidy ups I will do this evening. Now as for the Energy Node, formerly know as the Generic Node, it's going to make the Temperature Nodes look like the Switch Node when that's done. I only have an Aeotec device to monitor whole house so I need to know what it is you want it to do specifically so I can design and code the thing and send it as a single update. I was thinking multiple panels with multiple pulls from state vars to those panels or pushed from programs if you choose. Do you need Volt Amp Watt Kwh calculations? where you could pull a couple of values and determine another?

V1.0.13 has been running for 6 hours with no errors, has survived several AC restarts and finally seems to be functioning correctly. Shouldn't have rushed yesterdays updates! Triggering the update now, which will require a restart, an Update Profile and AC restart. The screens are quite different for feedback verification so don't be shocked. If you get an error shortly after the restart you may need to delete the .db files in the Virtual folder. Also, once you set the Push / Pull parameters, let the node go through and update before doing anything else. The data updates during the node update process, I will work on making that happen whenever any parameters are changed. @Teken Maybe you could post a screen shot after the update as I'm working remotely with an antique laptop, I miss my desk.

Of course it's the high and low, averaging starts after 2 updates after the statistics have been reset. That happens on the very first run and after manually resetting via the button at the bottom. So the time period is between resets, forever if nothing crashes or errors out.

@tmorse305 and all, I have everything fixed, I believe, and have v1.0.13 running with no errors and the non- updating problem gone. I will push that out shortly.

I am working on an update that will rid Virtual of some bugs and hopefully smooth out the operations and populate the nodes properly. Be patient, testing is happening now, I will trigger the update asap.

Virtual v1.0.12 fixes a couple of bugs with the Temperature node and omits login information in logging.

Fixes under way.

I see something is wrong with the Temperature node. I will fix.

@Teken That happens occasionally. I need to re-arrange the module and I will. The data shouldn’t be affected though, I’ll check. There is a lot going on during an update so some waits may need inserting. Bugs will be bugs and they will die.

To all: Don’t post Virtual logs on the forum, send them to me by message. Your login would be exposed, I will pull that logging out next update.

@tmorse305 The node key no longer associates with any variable, you choose that as you did and it can be any variable. The since last update should reset to 0 when the pull is done. Check the log for errors. The pull is on the long poll so check that. Restart the node server and see if there are any errors.

@Teken I will update to the max variables as soon I find out how many that is. Do you know? I just logged into home remotely and started the AC and none of my settings were populated in the panels but the settings are correct and the nodes are operating correctly May be a bug, will look at it when off the road Thanks for the kind words.

Virtual v1.0.11 triggered. Update Profile and restart the AC after the update and restart. @tmorse305 Temperature node is updated. Now for road trip. See ya!

Hey, the temperature thing was just a simple part for @madcodger, all 10 lines of code. I wanted the switch for my custom ISY app that is almost finished. The temperature part has taken over like some kind of monster, somewhere north of 300 lines now, because @Teken kept adding requests. But it's done and the final version is about to push to take care of the Temperature F side of things. Of course there is the Generic node to work on sometime.

I am working on the method migration to the Temperature node to mirror the Temperature C node, testing in progress and a version push is immanent. The paying gig beckons so it is a travel day and I will be away from my desk for a few days. I will monitor this forum to help out when needed.

@mwester Thank you for that detailed answer! I am in fact using the ISY REST API to get around the limitations. I am a fabricator by trade and as such, if something isn't doing what I want it to do, I just grab a bigger hammer out of a drawer and convince it. Doesn't work quite the same in programing.