@Ronwell yes that was an issue in the previous version as well. That’s why I did a rollback
For the time being I would not recommend the test version if you have many variables
how do i send it to you via DM
@Ronwell you could share here as well if the JSON is too long: https://sharetext.io/
thanks,
try this
@Ronwell Thanks will check tonight/tomorrow
Martijn, I get two false errors. My flows “Picnic” and “Luchtkwaliteit” are flagged. My guess is that this is the case because the app is the trigger and not a device.
Not a big issue for me, but I just want to inform you.
Thanks for the great app!
New app update (
LIVE: 1.35.2.):
Changelog:
NEW:
1. NoneFIXES:
1. FIX: false positives for app variables
2. FIX: false-positives for unused logic
New app update (
TEST: 1.36.0.):
Changelog:
NEW:
1. NEW: prevent cached data during check to prevent memory build upFIXES:
1. FIX: decrease memory usage when checking variables.
If you find any issues, send a diagnostic report
Note: Before sending a report make sure to reproduce the issue so the issue will be visible in the report
Via Homey Mobile app:
More - apps - Flow Checker - settings wheel right top - send diagnostic report (add your email to the description)
Via Homey Webapp:
Settings wheel bottom left - Select Flow Checker - Click on send diagnostic report (add your email to the description)
You can install this version by clicking the link (version number) above and press install
Don’t want to be part of a test version? Install the live version → Flow Checker | Homey
@Ronwell @Victor_Bicknese see update above ![]()
@Victor_Bicknese if you want can you also try out the test version? I think i made a fix which shouldn’t crash on the variable check on your Homey. Would be nice to know before I push it LIVE again ![]()
Downloaded, test is running….
Martijn, it crashed a couple of seconds after restart (version 1.36.0), but I cannot send the diagnostics, button stays disabled.
New app update (
TEST: 1.36.1.):
Changelog:
NEW:
1. NEW: prevent cached data during check to prevent memory build upFIXES:
1. FIX: decrease memory usage when checking variables.
2. FIX: crash with many variables
If you find any issues, send a diagnostic report
Note: Before sending a report make sure to reproduce the issue so the issue will be visible in the report
Via Homey Mobile app:
More - apps - Flow Checker - settings wheel right top - send diagnostic report (add your email to the description)
Via Homey Webapp:
Settings wheel bottom left - Select Flow Checker - Click on send diagnostic report (add your email to the description)
You can install this version by clicking the link (version number) above and press install
Don’t want to be part of a test version? Install the live version → Flow Checker | Homey
@Victor_Bicknese thanks for testing, I made a new version which should fix that
It crashes again. And I’m not able to send the diagnosis again, sorry.
It seems to use a lot of CPU.
@Vincent_Dessy ok thx. Then I think only thing I can do is disable that check if people have a large amount of variables. ![]()
Thanks!
I agree! Thanks!
@Victor_Bicknese LIVE version of the app should give you no issues though
thank you
135.2 seems to be working well, didnt fined dind any flows with broken variables.
i did notice in the app settings, the overview doesn’t see the flows my variables are in
Hi,
with last version v1.35.2 I am facing a continuous issue regarding “There are disabled flows” flowcard. It rises always the error: “Flow Card not registered (type: condition, id: condition_DISABLED)”. I’ve tried to restart the APP and Homey too but it persists.
I have an HPE2023 running v12.8.2. The diagnostic report produced just now is: 6B4C3717
Created also the diagnostic report directly from the Flow Checker APP: bf1133fa-8c81-4bf0-af2e-14000a7386aa
Pls let me know, also in case you need other info
Thanks
@Ronwell nice that it works
Yes correct that is temporarily disabled because of performance. If you install the test version you can see it
@Domenico_Etere I didn’t receive a flow checker report
Can you send it again?
Edit: I did receive it but don’t see any issue. Can you restart the app and send it again