ISY4Me

@bmercier Thank you... I knew there was something that I was missing. I played with setting the properties a little and sort of got the hang of it... a lot of clicking to get everything set... but I assume that will get easier over time. Many thanks..

OK... I am like a dog with a bone and problems like this just challenge me... until I figure it out. Most of my problems were in PG3x and I did not have the configuration complete and I was missing the proper Custom Configuration for the node. Once this was corrected, everything started to fall into place. The AC started to populate and I was able to write a short program to force it to update automatically, since in this case it is truly a dynamic variable. From here adding the variable (essentially as a node) to the eisy.ui Home Screen was straight forward I guess my one feedback is that in creating tiles for the eisy.ui Home Screen we are not given any options to only add select components of the node and all the data from the node loads into the tile. If we are trying to create a concise Home Screen overview page, this adds a lot of extra data (or clutter). For a eisy.ui home page were we want to be able to control everything about that device, then this is fine. This was my first dive into the eisy.ui home page and it is a great feature. Great work.

The other thing I have just stumbled over is... If I look at the PG3 node, I see that it sees one node for the Virtual Plug0In. On the AC Main Page I see and the Virtual Device Controller shows... Even though I added the Outside Temp node during trying to set this up, the Virtual Device Controller show ) for the Number of Nodes. Does this make sense?

I tried to explore what was obvious. I could see the Plug-in was added to the AC and if I clicked on the AC Menu item I saw I could add a Temperature Node. So, I clicked on Virtual Temperature and added a new n006_0001 node address and it shows in the node list So, then I created a program to update the Current value to my variable I am trying to convert to a node. Even if I force the program to run nothing changes for the new Outside Temp virtual node and all the fields remain empty. When I went back to the eisy.ui nodes page it reports an error saying that the nodedefs are missing for the Virtual Device Controller. I tried all of this from what seemed to be the obvious guess as to what to do to get this working, but it is clear that I am still not getting it. So to say the obvious, a "how to" would be great help, if you have one.

Thank you... I have added the Virtual Device Plug-In However, I can not locate any instructions as to how to use it. I have looked at the GitHub README, but it just shows what you could do... not how to. I can see the Virtual Device Controller in my Node list in the AC. Any guidance would be helpful.

Thank you @mjrush and @Ross. These both sound like they could be just what I am looking for. I will start researching all the suggestions, including @paulbates inputs.

I have seen discussions relating to the Pushover app before. That sounds like it could be a candidate for a receptor for data. I would just have to explore the possibility and educate myself. Thanks for the suggestion. As far as capturing the data I want… I know there will have to be devices out there. Temperature sensing with the ds18b20 I am already using. I may want to attempt airflow rate as well… that might take some digging. I have a few devices that measure current usage and I think they might report voltage as well, but I will have to research as I have not used that mode if it exists. This is a long term project, so focusing a way to save the data comes first. Data collection devices will be the 2nd stage. Thanks for the suggestion.

I have an issue with one of my heat pumps and I want to try to analyze what data I can capture in an attempt to predict the next failure. I did a search on writing data, but the few discussions that I found seem to assume the user knows what they are doing. What I need is a dummy’s guide. My plan is to setup some voltage and temperature sensors that will allow me to monitor a few points in the system, then based on system events I want to write what data I can capture for a longer term analysis. In the depths of the forum there is tons of info, but does anyone have a step by step perspective on how I would send the targeted data to a simple data file?

When something in my home automation appears to not be working correctly, one of the first things I do is go to UD Mobile and try to view the contents of the suspected programs. However, due to the complexity of how many of the programs are written, I often see something like the following. Seeing this warning message means I need to go to the EISY or my desktop to bring up the Java interface to see the details of what I wrote in the program. Even if I can’t edit my more complex programs in UD Mobile it would be informative if I could see the text of the program so my debugging process can begin. Might it be possible to present something like simple text or PDF in something like a view mode from within UD Mobile?

@Javi Thanks for response. I figured the beta status probably implied there was much work in progress. I will continue to watch and test as updates occur.

I have been experimenting with the new UD Mobile Graphical Charting beta option that was discussed in the recent UD News email. All in all, things are working. I realize that this feature is still in beta, but is there a way to constrain the x-axis, as an example… to the last 24 hours? In the example here I bring up the temperature response for the main thermostat and you can see it defaults to the time window just after 1:00 AM, when the time I did this was 11:30 AM on the same day. I am sure there will be further improvements. I think this ability is great. Currently I do this with Home Assistant… here is an example for the same device. Just a suggestion it would be cool to be able to display the graphical history as a separate object on the Dashboard, as opposed to having to select the device, then the device dashboard and then scroll to the graph. I think this is a great feature and I am looking forward to watching it’s evolution.

Thank you @larryllix... that is essentially what I have done for now. It is a simple solution.

@paulbates Thank you. I saw that and having the status in Climate didn't initially make sense, but I just setup a test case using Climate and the Vacation state and it worked perfectly. @dbwarner5 I agree with your approach. Eventually, I hope to go in an integrate my own Vacation controls into my programs so that everything remains explicitly controlled by the EISY. This is will take some time... and with that in mind, detecting the state and letting the thermostat control vacation settings was a quicker solution. Using the detection to disable folders of HVAC control was just a quick solution.

I want to be able to detect when my Ecobee's are in Vacation Mode. The Vacation Mode controlled my the Vacation setting in the app works great, but I have some programs that could possibly override things and I want to be able to detect the Vacation Mode being enabled so the program folders in question can be set to not run. However, when I try to determine how to detect the Vacation Mode state in EISY, I can't see how to do this. Has anyone attempted to do the same?

Thank you @Ross. Your response helped me understand the basics… I was not even close to thinking age/time since last new moon.