Morris Hansen

I would like to monitor the status of the HVAC fan on a couple different systems. Fan state appears in the dashboard and the EISY, but it never changes. I can see on the thermostat that the fan is running so it would appear the Ecobee knows it, the API seems to support it, it is just not changing in the EISY system. Should this be working? Not sure what I can do from my side. This is a new thermostat and install. Thanks

I started seeing the delayed emails earlier today. Using the default and I am running all the latest firmware.

Ah. I connected ethernet to the EISY and both Sonos and Weatherflow (local mode) work. I figured it was something to do with the wireless.

I guess I should have waited longer. It is on the same subnet. The EISY is on wireless. I was able to get it to work by changing from local to remote. I can pull another log today and share it. Thanks

I have a similar issue. connected but all data is null. weatherunderground seems to be getting the data. WeatherFlow_4-8-2024_114523_AM.zip

The 3 thermostats show up now. Not sure why but they show up now and I can at least see it as a device now. Will continue to test and make sure everything is functional and I can add them to programs, etc.

I see that thermostat support was added in the last few months. Thank you. I just now got to updating everything. In the Polyglot dashboard, the thermostat shows up and has the correct values. It seems to update properly. I am runnnig 3.10.15. Polyglot 3.2.20 and EISY firmware 5.8. My issue is I can't get these thermostats to show up in the EISY admin page. It doesn't show up as a node and I don't see where I can add it. Do I need to delete all the Elk nodes and add it again? I am thinking it must be a simple issue to resolve since the data is showing on the Polyglot dashboard.

Thanks @MrBill, that was what I was missing. I had used the play button before to switch between variables but never clicked it enough to get to the node server. I have it working as I want. I can now send an email with the monthly water usage aligned to my water company billing cycle. Also have email alerts setup on when I am approaching the next tier of usage pricing. Appreciate the support and education. I figured it was possible, just was missing the simple steps.

thanks for the screen shot. I now understand why I was not seeing anything. I see that the Flume values are available as part of the If condition but not part of anything in the Then portion of the program. I could see having a condition to do an alert if an individual value is greater than or less than some predefined value. What I want to do is to actually read the value (Last 24 hours) and add it to another variable every day at midnight. Is it possible to make these values part of Variable action? I know I can add variables to each other, would just like the ability to add a node server value to a variable. for example: Creat a variable monthly_water_usage. If Everyday at midnight Then Last 24 Hours += monthly_water_usage I would also have a program that would send me an email on the day my water meter is read by the water company and then reset the monthly_water_usage value back to zero.

On the device page and for this specific node server, I see all the various values. When I am in a program, I don’t see how to get specific values from the node server. If it is there, can someone help explain how to access the individual values. Thanks.

My monthly water bill is not based on the calendar month. Flume monthly readings are based on the calendar month. As we are charged extra at certain tiers of usage, I would like to keep a more accurate monthly reading based on my bill. One thought to do this is to have the EISY take the Last 24 hour value and add it to a variable. This variable would be aligned to the dates of my water bill and reset at the start of the month. I would then generate an email/alert that would notify me of the monthly total and/or when I am getting close to the next tier. I have seen some node servers that break out each value of the sensor (i.e. Weatherflow) and make these available to programs. I don't see that with the Flume node server. Is it possible to do this? I have not looked into what it takes to create a node server so not sure of the effort involved. I could see the potential of having these specific values available in many other HA scenarios in addition to this one use case. FYI. I have suggested to Flume to allow the user to configure their monthly start and end dates but have not seen it implemented in the few years I have been using Flume. Thanks

I have had my station for several years and never had a bit of problems with it. I would think the corrected values would be the most useful.

That sounds like it may be it. Interesting that there is multiple values in the first place.

I have implemented the Weatherflow and it seems to be working well. I have noticed a discrepancy in the historic rainfall. Yesterday, Weekly, and Monthly are all lower than what the Tempest app and website shows. Yesterday - EISY shows .58, app shows .64 Weekly - EISY shows .93, app shows 1.01 Monthly - EISY shows 3.35, app shows 3.67 Any ideas why? Running the latest of everything.

I see Elk Thermostats is listed on the ToDo list. I just got my Eisy setup and working and I have 3 thermostats still integrated with Elk that I was using the ISY to control throughout the day. Any estimate on timeline for thermostat support? Thanks

While I threw away my first failed PLM, after reading through the success everyone is having I wanted to see if I could repair my IOlinc. After being in a box for a couple years, I plugged it in and it worked for maybe an hour. I opened it up and 4 of the caps were the same as the PLM so I figured it was worth a try to replace. Ordered everything, replaced the caps and the IOlinc is still working after 3 days. Add one repaired IOlinc to the list.

My Aprilaire thermostats are connected to the Elk via RS485. I don't see them listed in the rest/nodes output. Guess that means thermostats behind Elk are not available to the Echo.

What thermostat's does v2 support? I am guessing my thermostats connected via Elk are not supported.

I do pretty much all the same stuff with just an ISY. I tend to have keep my Sonos zones grouped pretty much the same. And if you send a play command to the primary zone of the group, they all respond appropriately. I have not gotten the ability to add/remove zones to work outside of a Sonos controller.

That makes sense. I guess I can use IFTTT to do this for now. Though even having any home automation opens up that security issue. An insteon device could be opening up or unlocking doors today so it probably is a little false sense of comfort to just lump all security system into high risk. I use Elk for everything but security. Don't think I have ever armed the system. I use it for sensing doors, windows and controlling devices such as sprinklers, etc. I had it before Insteon and didn't think it was worth replacing. Would be interesting if for certain commands you could have the Echo prompt for some type of passcode, passphrase, etc. and that enables certain features. Part of the 2way dialog Thanks,

Will all the thermostat skills work with an Elk based thermostat?

Final update for the night. Was able to get things working. I could not run the rc.local on boot. I run the same script after bootup and it seems to be more stable. I am running the habridge in debug mode which seemed to help but it doesn't make sense. I will try tomorrow without debug mode. Running 1.2.3 of habridge and it seems to be working now. Will see what happens in the morning.

Tried habridge version 1.2.1, 1.2.2 and 1.2.3 with no luck. Will try deleting all the databases and see if something is corrupt. Based on the packet capture the bridges are responding to the echo upnp requests. I don't know what the packet flow is when it is working so not easy to tell what is broken right now.

Haven't changed anything with the network. I upgraded to 1.2.3 to see if that helped but no luck. All my Sonos works fine and it uses upnp. I will capture the traffic on the network and see what it shows. If nothing shows up, I will ping Brad.

So today I added a couple devices to the bridges (running 3 different bridges) and went to Alexa, forget all devices which is what I have done countless times and now the Echo will not discover any devices on any of the bridges. I have tried multiple times, reboot the pi, tried multiple times, rebooted the Echo, tried multiple times. Running 1.2.2 of the bridge. Anyone else having issues?