@johnconstantelo - hope all is well. Something wierd started happening since last evening.
The parent detector app which detects for constant flow (time) is not reporting properly.
Even if i run the water for 2 mins or 3 mins, it hits my threshold of 7 mins (set on app) and the message shows the time counter as an accumulated counter of more than X mins. i.e. the counter is not resetting. See a snapshot of the message.
I then ran a log and attaching a copy of the log as well. Found something interesting. It shows an error line with blacklisted. I also do not see the parent / child apps on the log, just the main fortrezz meter.
Still looking into this. It seems like the blacklist error replaced this error: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure @line 372 (sendDataToCloud)
Iâm not familiar with this integration or that endpoint. I see that the DTH hasnât updated recently, is it possible something changed with http://iot.swiftlet.technology/fortrezz/post.php?
If it helps, the errors started last night around 9:53 PM EDT.
Hi @rcube, their github repo hasnât changed for the DTH since last July, and I looked at their code and didnât see where it sends a push. Do you have any more information on that push message?
Attached is a message that i get when i try to even open the Fortrezz device via the new ST app. It does not allow me to proceed without downloading. I have not downloaded it since i am not sure what kind of an update it will do (messing up everything that we have worked on so far).
This is the first time, i am getting this message, since it had allowed me to open up the device through the new app when i had installed and had it working in May when we both connected and worked through tests.
Also Fyi - i may have mis-stated that i received a push. It was more of a pull. I tried to see what was going on with Fortrezz both via the ST classic and the new apps and the new app gave me this message.
I suspected that was it. Downloading it wonât hurt anything. It doesnât impact the DTH capabilities or anything, including how this device works with SmartApps or automations.
Also, I suspect that FortrezZ may not support charting since this only works in Classic. Iâm keeping my expectations low to be honest.
The âdevice controllerâ is the device plugin the app uses to render the device in the new app. As John said, tapping âDownloadâ will not impact the backend code of the DTH at all. You may see that periodically as updates to device plugins are released or if you add a new device type. It is related to the ocfDeviceType and vid listed in the metadata of the DTH.
@johnconstantelo - just curious. I know you use the new app mostly. But are you also getting the same issue with the classic app (due to the unknown changes / blacklist / server connect issue) that the continuous flow is not resetting ? like i am experiencing ?
Hi @rcube, it doesnât matter which mobile app is used. The blacklist/connect issue to FortrezZâs chart tool doesnât care about the mobile app. The same applies to the SmartApps because those look for device capabilities and states, which are the same for both mobile apps (except for only how they are presented, or not).
All that being said, I am having the blacklist/connect issue, and every so often I have the same issue with continuous flow not resetting. Iâve tried catching live logs, but itâs not predictable and you canât keep live logging on indefinitely hoping to catch it.
Hey, did what you suggested. Powered the flow meter off, pulled that batteries, left it off line over night and reconnected with a new Power supply (in case that could have been an issue). Issue remains and still has a 0.6 GPM continuous flow. Ran some water and it shows an increase in flow reported but always goes back down 0.6 GPM when the flow stops. No clear errors in the Live Logging. It appears from the last few messages that this is not on my side and I assume that this will hopefully clear itself? Let me know if you think something different⊠Oh, and my charts do not work at all nowâŠ
See the posts above regarding the chart issues. The service FortrezZ uses is down (no eta).
Not sure why your meter is reporting flow when itâs not. Iâd go look at the physical meter and make sure the guages are ok as well. The FMI has a âreaderâ on top of one of them if I remember right.
What does your Current State section look like? See post 358 as an example.
Iâll look at the code later today to make sure the issue with charting isnât causing this.
That appears to have fixed the continuous flow measure of 0.6 gpm. Went to zero after the update and jumped to 2.4 gpm when I flushed my toilet and returned to zero a minute later.