Everything posted by ISY4Me
-
Ecobee not communicating
@Jimbo.Automates When I read this… are you referring to adding our own APi to the current Ecobee poly or the new Ecobee? I added my own APi to the current PG3 Ecobee and was able to get it to recover from “disconnected” to “connected”, but no node data populated into IoX. Another confusion I would like to ask about. In some of the read.me and config.md files for the new HomeKit poly and the new Ecobee poly I get the impression that there is a path to still use the backend=cloud while data moves through HomeKit (if the user has their own API). Can you elaborate on if this will be possible with the new polys? Thank you in advance.
-
Ecobee not communicating
@Jimbo.Automates Thank you for the update. I am temporarily using IoX married with an Ecobee HA Integration w/API (no version of HomeKit ever installed). The HA Ecobee Integration is doing all the hardware control and all the logic is being done in IoX… so those delays are still being experienced, as would be expected. Hopefully just a temporary fix, but it allowed everything to continue to function. Bringing HomeKit into PG3 while still using a version of the Ecobee PlugIn sounds like a cool solution. I look forward to the updates. Thank you for all the work and support.
-
Ecobee not communicating
@Jimbo.Automates I don’t know if this is a valid concern or not, but I wanted to put it out there. With the old plugin there are changes to the thermostat settings made in IoX that take minutes for them to traverse from the plugin-> Ecobee via API -> back to my thermostat. With what you are working on… will reducing polling result in increasing the delays that I already see?
-
Ecobee not communicating
@Jimbo.Automates Is the removal of Ecobee from the Plug-In Store and the Plug-In Purchases a sign that Ecobee PG3 fix is not possible?
-
Ecobee not communicating
I was not sure the Ecobee forecasting is superior to others, so I use OpenWeather for forecasts... current and future. The user controls the polling by setting the number of times per day the polling occurs and then you have to multiply that by the number of days out you want to forecast. In their current setup you do have post a credit card, but if the polling is low there is no charge... I think it was free below 1000 per day. This is just an example of options, I am sure there are others that will work for forecasting. So if giving that up helps get re-enabled, it is workable.
-
RCS TZ45 Thermostat (z-wave) on EISY
I am evaluating using a TZ45 thermostat on my EISY setup, but I can’t find documentation listing the parameters that will be added when the z-wave device is added to my network. RCS is the original manufacturer of the thermostat, but they were also sold as Trane TZ45. If there is a member that uses one of these devices I would appreciate a photo/screenshot of the main device screen on the IoX Admin Console so I can see what parameters I will be able to work with. Of course, if anyone has a pdf reviewing all the parameters and their options, that would be even better. I appreciate the help.
-
Ecobee not communicating
@Jimbo.Automates Have you been able to see if there will be a path forward? Any encouraging signs would be a positive thing and I suspect all Ecobee PG3 user would be thankful.
-
Ecobee not communicating
As with others, this is broken for me as well. I had communicated with Ecobee today and they confirmed that new APIs are not being released, but that the old API that was issued should still work and that all I had to do was to re-link or re-authenticate the API. The agent that helped me, kept thinking I was on Home Assistant where apparently this re-authentication is documented, so I do not know if this is a real fix for a UDI PG3 node. However, I can't see how to do that and I am hoping someone knows if that is possible. Is there a configuration key that can be added for the Ecobee PG3 that will achieve this re-authentication?
-
New UD Mobile install on Android… spinning blue icon
Thank you @Javi... This problem was fixed with the Android UDM 1.5.4 update that was available today.
-
Variables not syncing name
@apostolakisl I was examining this “Variable Names Showing as Number” issue and when I went to my monitor attached to the EISY box and looked at the Variables List to get the Variable ID for the parameter I was looking for to add a panel to my favorites. I noticed that in some cases the Android UDM did not pull the same variable data that showed when I looked at the variable list directly on the EISY box. Did you observe the same thing? Variable ID comparing UDM Android to EISY Variable ID, some data agreed and some did not. ... Update. I noticed the next day that some of the variables which were not consistent with the actual data on the EISY box were now updated and were showing the same value as the EISY. This was not an issue of waiting a few hours, but roughly 24 hours. Not sure about this... is there some sync or data update on a timer? No idea, but as of today, all the variables I have added to the favorites tab are the same as the raw data on the EISY Box.
-
New UD Mobile install on Android… spinning blue icon
Since I updated this morning, I am running: udx-4.4.0 Name : udx Version : 4.4.0 Installed on : Mon Dec 29 08:57:49 2025 EST I will submit a ticket.
-
New UD Mobile install on Android… spinning blue icon
When I was writing the last post, I realized that I had not updated the EISY for a while. So, I did that this morning. I had been getting some error relating to nodes when I was syncing... considering other issues I was trying to resolve it didn't seem high enough priority to mention. However, after updating the EISY, those errors related to nodes that showed on sync, stopped. However, when I go to bring up the User Preferences in Settings -> App Settings -> I still get the spinning blue icon in the center of the screen and I am unable to change any of the settings within the User Preferences. Same thing happens if I bring up User Preferences from the Home Tab. Also, still only seeing numbers for all the variables in the Automations Tab.
-
New UD Mobile install on Android… spinning blue icon
@DennisC Let me see if I can answer your questions clearly. First off, I have UD Mobile running on iOS and that configuration works on WiFi in the house and on Cell when out side the house. When I go to Safari on the iPhone or my desktop I can log into the Portal without issues and the EISY shows connected to the Portal and online. License is current and active. When I go to the Android device and go to Settings -> App Settings -> Controller -> EISY, I can see the portal setup fully populated with the EISY UUID populated, the remote connection settings populated with my portal account and the remote url also correct. All the local connections are populated and the System Network Relations populated with my WiFi credentials. The local connection works. I have gone through the UD Mobile guide multiple times and if there is something that I am missing for the setup, I have not discovered it yet for this Android installation With the current state of the Android setup… all of the devices have populated on Home Tab; I can enter favorites (so far just a few, as they all need to be redone as iOS backup can not be used); Automations all populated except for variable which are only showing numbers not the variable names (others are reporting this too). But, when I click on User Preferences on the Settings Tab, I see the actual form, but you can not touch as it is locked with this spinning blue icon in the center screen. I will go through the UD Mobile document again tomorrow, but if any thoughts come to mind let me know and I will give it a try.
-
New UD Mobile install on Android… spinning blue icon
I am setting up UD Mobile on a new Android install and have noticed some issues. The first Issue is the EISY Controller did not set up properly. It did not recognize the proper portal name and local settings were all blank. I think I resolved this by deleting that automatically installed controller and then went through and installed it manually to essentially match all the setup to be consistent with my UD Mobile setup on my iPhone. With that issue resolved I went to setup the User Preferences and the app is not allowing me to access any of the fields as it is starting with a spinning blue icon in the middle of the screen and it just keeps spinning. I have not tried to do much else, as I would like to resolve this first. Suggestions?
-
Variables not syncing name
I just discovered the same issue on trying to setup new UD Mobile install on the Android OS. Everything claimed to sync, but discovered this on setting up the first favorite. If I discover any reasons for this I will post or eagerly wait experts response.
-
eisy.ui home page
@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..
-
eisy.ui home page
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.
-
eisy.ui home page
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?
-
eisy.ui home page
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.
-
eisy.ui home page
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.
-
Writing variable data to a file for long term analysis
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.
-
Writing variable data to a file for long term analysis
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.
-
Writing variable data to a file for long term analysis
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?
-
Viewing Programs in UD Mobile
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?
-
UD Mobile - New beta charting
@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.