Morris Hansen

I have tried both. I just did a power cycle and here is the log. It seems like it is communicating (sending and receiving) but then seems to stop. While I don't know what a log on a working system looks like, I did notice these log messages: Wrong default trust center key size 0 Error returned from (err = zbee_ef_set_initial_security_state(zbee, NULL, zbeediscover_on_fail, NULL)): Wrong packet from the network or Discovery got bad data (stick communication failed) (-9)

I have a similar but slightly different issue. I have had the dongle for awhile and finally decided to get it installed and operational to start testing some Zigbee switches. I am running 6.0.5. Installed the dongle, have the configuration options enabled for all the technologies and rebooted the EISY. On the main admin UI, the Zigbee menu shows !ZMatter Zigbee not responding I saw that someone went back to 6.0.4 and their's started working again. I don't see where I can go back to 6.0.4 otherwise I would have tested. The Z-Wave and Matter menu shows various options. Here is what I am seeing in the Zigbee log: [2026-05-29 19:36:23.560] [E] [...] Ember status 0x93 - EMBER not joined [2026-05-29 19:36:23.560] [I] [...] Job NetworkInit: Failed status 0x93 - EMBER not joined [2026-05-29 19:36:23.560] [W] [...] Network is not configured. Configuring Network [2026-05-29 19:36:23.560] [I] [...] Adding job: LeaveNetwork [2026-05-29 19:36:23.560] [I] [...] Adding job: ClearKeyTable [2026-05-29 19:36:23.560] [I] [...] Adding job: ClearTransientLinkKeys [2026-05-29 19:36:23.560] [D] [...] Wrong default trust center key size 0 [2026-05-29 19:36:23.560] [E] [...] Error returned from (err = zbee_ef_set_initial_security_state(zbee, NULL, zbeediscover_on_fail, NULL)): Wrong packet from the network or Discovery got bad data (stick communication failed) (-9) [2026-05-29 19:36:23.560] [D] [...] Job (NetworkInit): fail [2026-05-29 19:36:23.560] [I] [...] Job NetworkInit: Success [2026-05-29 19:36:23.571] [D] [...] Sending EZSP LeaveNetwork [2026-05-29 19:36:23.571] [D] [...] SENDING EZSP: ( 22 00 01 20 00 ) [2026-05-29 19:36:23.571] [D] [...] SENDING ASH: ( 22 60 21 A9 74 2A 8A C6 7E ) [2026-05-29 19:36:23.581] [D] [...] Worker thread exit point [2026-05-29 19:36:23.581] [I] [iox] [ZMATTER-ZIGBEE|/dev/cuaU2] Z-Bee stopped [2026-05-29 19:36:23.581] [I] [iox] [ZMATTER-ZIGBEE|/dev/cuaU2] Z-Bee stopped, return [2026-05-29 19:36:23.582] [D] [...] Worker thread successfully finished [2026-05-29 19:36:23.582] [D] [i/o] Closing port [2026-05-29 19:36:23.582] [I] [iox] [ZMATTER-ZIGBEE|/dev/cuaU2] Failed to start Z-Bee Discovery (err=-9) [2026-05-29 19:36:23.582] [I] [iox] [ZMATTER-ZIGBEE|/dev/cuaU2] Z-Bee discovery failed [2026-05-29 19:36:23.582] [I] [iox] ZIGBEE-WORKQ-40 Failed restart Zigbee [2026-05-29 19:36:24.330] [I] [iox] [ZMATTER-ZIGBEE|/dev/cuaU2] Not yet connected [2026-05-29 19:36:24.330] [I] [iox] [ZMATTER-ZIGBEE] Iox Startup() - Initialize port - Complete [2026-05-29 19:36:34.307] [I] [iox] [ZMATTER-ZIGBEE] Iox StartupComplete() - STARTED [2026-05-29 19:36:34.307] [I] [iox] [ZB-INTERVIEW-43 ] Started Zigbee interview thread [2026-05-29 19:36:34.307] [I] [iox] [ZMATTER-ZIGBEE] Iox StartupComplete() - FINISHED [2026-05-29 20:52:21.416] [I] [iox] UDZBee Rest Command : Get NodeDef : 12 : connected=F enabled=T [2026-05-29 20:52:21.416] [I] [iox] UYBProcessCommand.run - Begin - cmdId=12 ec=0 okToRun=T [2026-05-29 20:52:21.416] [I] [iox] UYBProcessCommand.run - End - cmdId=12 ec=0 okToRun=T rc=T

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.