Your reporting interval says NULL. Please change that from 1 to 2 and then go back and change it to 1 again. Watch live logging to make sure errors go away.
Yep… the problem appears to be the connectors on the FMI, if I keep pressure on them, all works perfectly…
That’s kinda what I suspected. You can try Fortrezz support, and if they can’t help, try a cell phone repair shop that can solder connectors that small if you don’t want to try yourself. Sorry you had to go through all that!
Excellent work John!!
Thank You so much for your support and efforts!!
I am now using the other two Smart Apps you have updated as well… Job well done!!
I’ll continue to use by keeping pressure on the connectors… Once they stop working, I’ll bring to a cell phone location for repairs…
Sadly, my FMI has not been used or handled that much… so I suspect maybe they have deteriorated from environment exposure… as it is in my garage and not a air conditioned space…
No problem at all!
Your water flow meter app looks amazing! I was hoping there would be a way to integrate it with my system. I am using a Fortrezz Mimolite wired to the terminals of my water softener pulse flow meter using a pull up resistor. Is there a way to get that pulse data into the app even though it is coming from a different source? I would be grateful for any help you could offer.
Thanks @BlueWater , FortrezZ’s FMI for the meter sends an actual value (current and a previous meter values in gallons) which is used to determine flow, total gallon used, etc. Subtracting previous from current gives the rate of flow, depending on the rate set in the DTH (10 seconds to 60 seconds).
You could use the logic in the DTH, but there may be some heavy lifting to covert those pulses into values, as well as using state variables to store the previous value because I believe the Mimolite doesn’t store/send anything like that (It’s been a while since I’ve had those devices).
I wanted to find out if anyone is still utilizing the graphs/data feature of iot.swiftlet.technology. That’s the server that receives data pushes and creates these graphs upon request:
I have been providing that software as a service to Ezlo since they purchased FortrezZ but my contract there is ending in November.
Would the service be missed if it disappeared altogether? Is anyone interested in purchasing a copy of the source code? Would folks chip in to keep it running (It’s not very expensive)?
Just wanted to test the waters. @ me if you reply, I’m not very active on this forum any more. Thanks!
Thanks for the offer. Before I discovered Home Assistant, I used these graphs in a Magic Mirror. @johnconstantelo took it out of the latest version, however, and Home Assistant has multiple ways to prepare graphs.
I’m anxious about losing the FortrezZ Water Flow Meter. Does anybody have any suggestions for how to keep it going in the new Smart Things or else port it over to Home Assistant or Hubitat?
Hi @FortranFour , it was removed because when the new app was released a while ago it did not support those graphs.
Thank you enormously for creating the Edge driver for the FortrezZ water meter–very much appreciated!
My meter is installed at a remote location that I likely won’t be able to visit and manually exclude and then re-include on the Z-wave network (using the buttons on the device) prior to the Groovy phase-out. So, the only way for me to replace the driver is to install it on my hub now and wait for “option 4”* to take place, is that correct?
- from https://support.smartthings.com/hc/en-us/articles/9339624925204 - Option 4:
“Install a replacement custom Lua Edge Driver from the SmartThings community here into your SmartThings hub and SmartThings will migrate your device. If the custom Edge driver is already on the hub, we will attempt to migrate the device to that specific driver. This option is to move a custom Zigbee/Z-Wave Groovy DTH to a custom Lua Edge driver without needing to delete the device in SmartThings.”
No problem @FortranFour , this was one device I was most worried about as well.
Yes, option 4 is your best bet. I would still reset the meter after conversion. You can do that by having a simple routine that when a light comes on to then reset the meter. I did that so I could have a clean transition, but it wasn’t too pressing for me since I perform a reset every month. Once I reset using a routine, I deleted the routine so that is wouldn’t accidentally run the next time that light switch turned on.
Thanks, again. That meter was expensive and took a lot of effort to install and has proved itself quite useful to me, so I truly appreciate your efforts to keep it working.
Hope you don’t mind one more question. I now have your edge driver installed on my hub. This is how my flow meter is currently configured in the IDE (using the old Groovy FortrezZ DTH):
Should I change the type (or do anything else), in order to allow it to be automatically converted to your Edge driver when the IDE shuts down? Thanks once more.
You can’t change Type to make the conversion. You can either exclude and rejoin the device (remove the custom DTH), which will pick up the new driver and it will show up as “placeholder”, or wait for ST to migrate you, which should technically automatically pick up the edge driver.
Thanks, but just to be absolutely clear, I was under the impression that I had to be using a “stock” DTH for the conversion to edge, even a custom edge driver already installed on the hub, to be automatic (without manually excluding and rejoining). For that reason, I was worried that the meter would somehow be passed over and that ST would not migrate it unless I change the DTH to a stock ST DTH. (It’s located far from where I am now and, for various reasons, I won’t be able to travel there before the transition occurs, so exclusion and rejoining is not an option for me prior to the transition.) It sounds like your saying that if I keep the FortrezZ custom Groovy DTH, then it will still automatically pick up your Edge driver at the time of the migration, correct?
From what we’re hearing in the community, that is correct.
@andresg can you confirm or provide a link to an FAQ about the transition for devices that have a community developed Edge driver and it being picked up when that happens?
Sorry for the late response. I am not sure if I fully understand your concer, but you don’t have to ‘manually’ change the driver if that is what you are asking for. You can just wait till the migration changes it for you.
I was just checking to see if someone installed a custom driver like mine that when the migration comes it will pick up that driver.
Ah, I already understand your concern @johnconstantelo. If your device is already handled by an Edge Driver (custom or not, it doesn’t matter) then the migration won’t affect your device at all. Migration will only affect devices handled by DTHs.