Teken

Nothing, but it doesn’t blend in with my current decor! [emoji869] [emoji2957] Regardless of what TSTAT I buy won’t allow it to auto update / remote access like it did with NEST! [emoji107][emoji90] Probably the biggest sh^t show in modern history only second to Windows Vista / Windows 8 / Windows 10. Sent from my iPhone using Tapatalk

Appreciate the visuals Larry helps me see what features are available and how it’s presented. I’ll take a few moments to read the user manual from the Doc! [emoji1787] Based solely on looks the Honeywell knocks it out the park. It’s symmetrical, well laid out, and white! [emoji106] The eco bee [emoji219] well it’s a little odd shaped [emoji1785][emoji2957] But does offer some nice features and has integration to the ISY Series Controller. The Honeywell too but would need to go Z-Wave to obtain the same integration. Sent from my iPhone using Tapatalk

Nice! Does it offer any metrics in terms of tracking temp, run time, etc? Also, does it support dual stage furnace / AC?

In the heating range image you have provided what is the lowest set point along with the highest a person can define? Based on the little balls presented here it looks to be the lowest goes down to say 8'C??

Time permitting can you check to see if the range for either hot / cold is defined vs the user can enter whatever value they wish and lock it in. For me that is critical as I don't want the home to ever be say 5'C cold for heating / 26'C for cooling etc.

In that stat how low or high can you set the lowest heating point to? Meaning for a freezing condition can you set it 5~XX or is defined like I saw on whatever TSTAT my friend had which appeared to be say (5-16'C). As I would like to set it to say 17-18'C for the cold and the high (28-XX). By blocked I wanted to know by first hand knowledge do any of these TSTAT's cry by indicating either through the App or on the screen the Internet isn't available. Again, I can't recall the other STAT I saw but it had this annoying pop up message indicating it couldn't this or that because there wasn't connectivity to the mother ship.

I will be in the market in the near future for a TSTAT. Wondering if there is anything new in 2020?? [emoji848] I could really go either way in terms of protocol from Z-Wave, ZigBee, WiFi. One thing I would like to know is how some of TSTATS handle low & high safety limits? A colleague had a TSTAT and for the life of me can’t recall the brand. Regardless, I found it odd the safety low & high were restricted to some odd values. Essentially I want to be able to set my own value and not be locked in by some imbeciles ideas of low vs high. A local API is high on the list along with priority of local first vs cloud first! Lastly, has anyone with a WiFi STAT ever blocked the unit to see how they react? [emoji848] Sent from my iPhone using Tapatalk

Keep in mind as others mentioned if what you have in place works ~ it works! Another benefit of using variables is it gives you the ability to count and do basic math. I use variables to track activity for motion sensors and receive a final report each day / month. This in a round about way allows me to gauge if X battery vs Y battery is offering the run time I expect. The use of variables also enables me to track how long something has been running for. Good to know for things like HWT, Sump, Water Flow . . . Lastly, variables allow me to track the current, low, and high values for a temperature sensor. This allows me to know exactly how hot, cold, just right, that porridge is for those three little bears!

Sadly, I must report the latest Ping v1.07 update has not corrected the false negatives.

You may also consider another method to identify root cause and narrow down the problem by simply replacing the power supply. There was a period of time where the supplied PSU was not very top shelf. The 994 Series Controller can accept a voltage from 5~30 VDC (Center Positive). I would encourage you to not exceed 12 VDC though as you may very well let the magic smoke out. Swap it out and give it a whirl and report back success vs failure . . .

I also believe there have been some basic concepts not fully explained and this is important. Another is proper house cleaning and coming up with a working schema. Doing so will insure over the long term *By Eye* you will know exactly what something is and this should automatically trigger a pause in a person when making a program(s). Variable Schema: Many of us identify the two variables with a (s) vs (i) to denote what you're selecting from the programs tab. This ensures you don't pick the opposite variable that may have the same name which 99% of the time leads to unintended actions in the network. Which leads to the next basics about variables a State variable will execute every time vs a integer variable will not. Using the two when required can offer you untold power and flexibility in crafting unique programs.

There hasn't been a time where you have posed a question in which it hasn't enlighten ten other people in doing so. I very much enjoy watching Larry and others illustrate some of the hardest concepts such as Variable to the masses. His Kung Fu is very powerful . . .

@markv58 Just updated the Ping Node Server now and will report back my experience. May I ask and perhaps make a few enhancement request to get the most out of this fantastic tool? Feature Request: - Long Poll: Please consider implementing this for more flexibility - Multi Poll: I would really like to see this tool have the ability to define each new node with a custom short / long poll. As some network appliance do not need to be pinged as consistently or often as others. - Last Ping: Be able to see when the last successful / failed ping was completed with time stamp - Ping Time: Be able to see and track the average, minimum, maximum ping time as this will give more insight regarding latency and possible congestion / bandwidth issues. - Packet Loss: Be able to see the percentage of packet loss if any. Again this would offer more insight as to factual metrics of that appliance. What Are These Toys: - Many of these network appliances are related to home automation, security, and force protection elements in my home. Items such as 1 wire, water meter, energy monitors, security cameras, HVAC, fire wall, weather monitors, switches, UPS, fire protection, etc.

I didn't see a specific forum for this Ping Node Server or a catch all for general Polyglot. So figured since this is a question why not pose it here! This little Ping tool is very cool and believe given enough development can turn out to be a real killer. Now, having said this I have found the tool doesn't seem to reflect reality as several network appliance which absolutely can be pinged and replies back. Always shows as not reachable from the Ping Node Server?!? Given there isn't any obvious settings besides time between short vs long pings I'm not sure what else could be done. Anyone else using this Ping Node Server please do chime in with your experience and let me know if there is some kind of work around. Also, is it just me but the fact you can't define a custom ping time for individual devices a little odd vs a global setting? Is it somewhere and I missed it?

No worries, moving forward its best to reserve a DHCP address for any network appliance in your home. Going this route vs assigning a static IP address it avoids potential IP conflicts while also ensuring any network related changes are propagated without issues.

Awesome - What's going on with Polyisy? Can't connect to it via the browser? The ISY Series Controller doesn't connect the two together?

Let's start with the Java Console you have two options which is uninstall Java. Or select default all and have the prompts pop up again so pick whatever is easiest to do. Assuming you're referencing Windows Defender. Type firewall in the search field and it will display Windows Defender Firewall -> Allow an app or feature -> Find anything related to the ISY / Java and check mark what is appropriate. Such as Private for whatever service(s) you wish to allow system access.

Hello, Just received the latest news about the EOL of the climate module and have to say it wasn't a great surprise to me. However, would like to know how this will impact those of us who have the module and have it pointed to our own PWS?? Also, there needs to be a recommended and bullet proof way to integrate with Poly Cloud / Polyisy for the alternative weather nodes. My personal experience with all of the weather related node servers has been less than positive. Meaning I have not been able to get any of them to operate or operate correctly. I believe those of us who have *some* technical prowess and fail to get these new services up and running correctly. What is the larger impact to those who have limited knowledge or skills in the same?!? My ask is that there be a concerted effort between UDI and X developers to hammer out all known bugs with respect to one weather service say DarkSky / Whatever. Document in plain English all the requirements with image captures from start to finish to ensure a smooth install and final deployment. This, will reduce incidents and trouble tickets being created for the company and the hundreds of threads asking the same.

Just to be clear do when the finder comes up does it indicate the IP address of that controller? if not the worst case is you can add it to the finder and in later launches it will display it correctly. Lastly, you don't have to use the finder you can always follow the direct method outlined by the firmware release notes where you use the direct IP address to access the controller. http://your.isy.ip.address/admin.jnlp

As always much thanks for the feedback and will give 5.0.16C a try this week end.

Hover over the root of the program tree and right mouse click and select copy to clipboard. There are two copy options for clipboard so pick what ever versions allows you to save the program.

Also the most common reason the short cut may disappear, or not work, is when you upgrade the firmware and follow the process of clearing out the Java cache. That normally deletes the finder from the desktop but in the same vain the last step is to start / invoke the new one so it can pop up and insert it on to the desktop again. Another thing is if you set up both WiFi and Ethernet on the Polyisy this may cause you to not be able to connect to one another. I noticed some odd behavior where the WiFi I defined would not always show up and the system would simply display *Available* networks opposed to the one that was selected. When I tabbed over through the Polyisy system and back to the network tab it would show eventually. If you have both connections active it will cost you nothing to disable the WiFi and see what happens.

Hi Larry, I can't say the heart beat is seeing a off per say as the logs and event view haven't been reviewed. But, do know my daily status emails continue to show leak sensors either staying at 0 meaning the ISY Series Controller was rebooted. Or the expected status number of 1 that heart beat was received within the 25+ hours isn't happening. Many times the status of 2 is seen which means the heart beat has exceeded the 25+ hour threshold whether it be from me rebooting the controller and missed that window. But, in this case the controller has not been rebooted and a value of 2 (missed heart beat) is still being sent in. I'll have to pull all of the sensors from their various places and check if the batteries are still good. It's been a long time since I checked any of them and probably shouldn't expect to see the advertised 10 year run time Smarthome indicates. I'll circle back as to what I find and perhaps might push forward in using that modified leak sensor Rabbit and others have improved upon.

Has anyone seen their leak sensors (monitoring program) constantly reset back to zero along with the heart beat never switching to 1 as being received?!? This seems related to the open / close sensor others are talking about. I haven’t upgraded to the © firmware given the feedback here. Sent from my iPhone using Tapatalk

You may consider trying older versions of office to see if this is compatibility issue. Coming from Office XP, 2007, 2013, 2016 will give you odd problems. You can also use just the viewers to see if there are differences. Sent from my iPhone using Tapatalk