Teken

@markv58 Looking really great here too! Once this gets locked down where more generic things can be incorporated with custom names like energy to display watts, amps, volts, KWH, liters / gallons. it would be nice to see a heart beat state in that last empty box for the Virtual Node Server! ? ? ? A simple 1 / 0 flip flop, True / False, or better yet Active - Not Active state?!? ?

[emoji1787][emoji1785][emoji2357] Older - Wiser - Faster! [emoji869] Sent from my iPhone using Tapatalk

I’m having a brain **** here. There was a specific reason a switch needed to be outside of a folder?!? It was some kind of setting that wasn’t visible unless outside of the folder?? I don’t recall what it was I’m thinking Replace With?? [emoji848] Sent from my iPhone using Tapatalk

Rock On . . . ?

@markv58 What is the secret sauce you're using to calculate the average temperature? I know this is from the highest vs lowest but is that over what time frame / period? An hour, minute, day?

Is this device in a folder? If so, remove it and try to right mouse click and write updates. Bring it close to the 2413S PLM while in linking mode.

Some things to note depending upon the age of the 2413S PLM. There was a period where the manufacture used leaded solder vs the more common lead free! If you don't have a quality solder sucker or solder wick. Some have used their compressor to blow off the solder once it reaches its liquid state to avoid damage to the PCB. Insure you have a high temperature soldering iron or air station because its easy to damage the cheap multi layer PCB. Even with professional tools on hand its sometimes a challenge to desolder high temperature lead free medium.

You’ll only know by removing them and watching the level 3 error logs in the AC. While activating locally, remotely, and through a scene test. If your hops remain as before with the AP in place - Good to Go! [emoji106] If hops increase than you need to keep them there or replace them with a dual use item like On-Off, Dimmer, Outlet LINC. [emoji3516] Sent from my iPhone using Tapatalk

Yes, I thought it was just a label too! But, after I realized it was a button the fact scrolling down the list to see the exact same options I chose in the previous one threw me off! I must have sat there for three minute scratching my head wondering WTF??? It didn't help that the AC was slow to update the values or completing my requested action . . . Regardless, as noted up above insure both fields for push / pull mirror one another for State Variables and press on each left button to force save that option.

@markv58 Just some quick feedback with respect to how the system converts the raw to precision values. I'm not sure where the lag is happening but if its possible for the Virtual Node Server to see the new value, wait X seconds, and than convert - maybe double convert?? As I often see the system will miss the conversion and the net result is that raw value than becomes the high limit value as seen here. When programs were in use I simply inserted a 1~2 second wait prior to the raw to prec conversion and this allowed the two system to breath and complete the operation.

@tmorse305 I have appended what I meant up above so others could benefit from my trial and error. Next to each of the drop down is a button that needs to be pressed to save the option. What threw me off was as I scrolled down the AC would display the same values and settings from the previous node. Now that I know its safe to ignore all I did was change the State Variable to reflect each node.

@markv58 The specifications for the controller say 1024 devices / scenes and 1000 programs. Perhaps @Michel Kohanim can offer some insight as to the maximum state / integer variables can be created within the controller. I think going up to 800 would be near the limit for most of us . . . Using your Virtual Node Server the bulk of the programs in place could be reduced so maybe in the overall grand scheme of things it would even out?!? Have a fantastic day and know I'll be toasting you a few cold one's in this incredible mile stone! ? ??

Scratch everything I just said above everything is working as expected. I think once both Polyglot & ISY Series Controller gets all of the back end processes hammered out all of this will just operate as expected. There must have been some kind of lag or processing error happening and just took some time to complete in the back ground. So for the benefit of others here are the steps to get this up and running. - Virtual Node Server: Update to 1.0.11 and restart the virtual node server within the Polisy Dashboard. - ISY Series Controller: Go to the Virtual Node Server parent tree and select *Update Profile* and close the Administration Console (AC). - Device Tree: Go to each node and define what it is you need from Pull / Push, Variable Action, Variable ID, Raw to Prec, F to C, if required. The key thing is to press on the side button so that selection is saved. When you scroll down to the next node what may throw you off like it did for me is that the previous settings and value follow / mirror. You need only click on each button assuming the primary settings are the same and only change the Variable ID and press the side button. You'll know that action has taken because the system will indicate a *System Busy* message at the lower left side of the screen. @markv58 You have truly outdone yourself in this latest iteration of the Virtual Node Server! ? ??? The only suggestion I can offer at this time is to increase the variable count to 800 plus. As of this writing I have more than 400+ variables so the drop down option of 400 is my limit. Thank You ~ Sir!

@markv58 Ignore . . .

Ready to test when ready. [emoji106] I can simply update the Virtual Node Server and leave all existing programs in place and everything will just work?!? [emoji848] Looks great and look forward to using this on the Brultech Dash Box as an interim break fix. As an aside for those rocking a Brultech GEM, DB, energy monitor the team is slated to set aside time to develop their very own Energy Node Server. [emoji869] @markv58 Much thanks for helping out bridge this third party energy monitoring / management need! [emoji106][emoji481][emoji481][emoji481][emoji481] Sent from my iPhone using Tapatalk

@markv58 If there was a bow down emoji to be used on the forums!! [emoji106][emoji481][emoji481][emoji481][emoji481][emoji481][emoji481][emoji869][emoji7] Just for clarity will this new release allow those of us with a Brultech Dash Box (DB) be able to see the data now in the AC? As I retasked one of my test boxes to send state variables to the ISY Series Controller and they show up and change. All of the required programs are in place. I selected both generic / dimmer but the AC did not reflect anything in the AC Virtual Node? Hoping this release will see the REST calls from the DB. But am super confused as to why it matters since the data is being referenced from the state variable?!? [emoji848] Sent from my iPhone using Tapatalk

You’ll need to go into each program and update the system to point to whatever resource it was ask to invoke. [emoji3516] Sent from my iPhone using Tapatalk

@markv58 At a high level doing all of the ground work for averaging just makes sense and can be used in the other future virtual nodes. For the temperature the average would apply to the high & low. For the Brultech energy data this would apply to all of them from Watts, Pulse, Temp, Voltage. One thing I haven’t seen anyone do or ask before is having the ability to track how long or off something has been operating in a Node Server. As of this writing I use the ISY Series Controller to track the run time for various appliances and hardware. In the past this was more in part for curiosity and seeing if I could. Later, this novel idea became the cornerstone of many of the safety systems within my home. [emoji3516] As it could tell me if the fridge / freezer was ajar, blocked vent, low Freon, to compressor. During the extreme winters it tracks and alerts me of how long the furnace has been running. Julie U.S. will than verbally call out the increase vs expected runtime. When the girls take endless hot baths and keep topping it up the HWT stays in heating mode for a very long time. Julie U.S. again calls out when that threshold has been exceeded. Various fans are tracked and one thing I haven’t done are lights! Maybe this is a niche idea but if the next Node Server or even this one could count up / count down when say a switch is on - off. That would have great value to me and hopefully to others. Perhaps my goal of off loading as many process heavy items from the ISY is the underlying need I suppose. [emoji848] Thank You! [emoji106][emoji481] Sent from my iPhone using Tapatalk

If we assume the GFCI is from the same period say 80-90’s era as the X10 switch. Replacing the GFCI breaker with a newer one will save you time and hair on your head. [emoji106] Sent from my iPhone using Tapatalk

I'm not sure if this applies but try to set your State Variable to Precision 1 if not already enabled. Also, instead of just restarting Polyglot I would reboot the entire Polisy / RPI.

Will it be possible in later release to reset the individual high / low counters? Love the idea of archiving the old data but if its possible to edit the same in case of an erroneous stored value?

@markv58 Will 1.08 address rebooting the node server and it defaulting to the values you see below? I had a few moments to check the system before starting my day. I was curious to see what the impact was by rebooting the Virtual Node Server. The results are all of the nodes default to -60 / 129'C.

Once the new software has been upgraded the Node Server needs to be restarted. Once done select update profile in the AC for the parent virtual Node. Close the AC and log back in and everything should appear. Sometimes both the Polyglot & ISY Series Controller need to be rebooted one at a time. Sent from my iPhone using Tapatalk

When time permits another feature request is having the ability to reset the low & high counters. Ideally, each counter could be independently reset in case the user really needs to keep track of either. Rebooting the ISY Series Controller / Polisy Node Server isn't ideal to solve this problem.

I believe all of this is working as expected as seen below. I'm not going to lie but this took way longer than it should have! ? ? Regardless, this was a huge undertaking by @markv58 Thank You -Sir! ?