Tried it. No luck. Installed chrome. Same game. Can‘t get the X on a connector. Can‘t select it either
I hopefully fixed almost all of these besides the delete.
Please check if you are running V1.8 for these fixes.
Great! Thank you.
The issues have been fixed indeed.
I do have a question on the tag selection/drop down field. My initial though was that it would show a list of available tags. In my case, no list is shown. But if I start typing something in the field, the space above the virtual keyboard shows the first three hits.
Is the way it should work? Or is the app supposed to show a list of tags?
Its called autocomplete on desktop you type and get a list of items that match your search query. I guess on mobile it takes autocomplete a bit literal? Is it okay or would you like to see a list? The problem I had was the dropdown was huge cause it was device tags + custom tags
I understand your consideration. It’s a bit of a dilemma.
- The current implementations limits the hits displayed. The downside is that you need to know the exact name of the tag/variable, otherwise it will not be included in the three auto-complete suggestions;
- A list with all tags/variables will be long. But it contains all possible items. You do have to combine it with the device name (like you are now also doing in the auto-complete option), as tags with the same name are used for multiple devices.
Personally, I would prefer a list. Like Homey’s own flow builder shows when selecting a tag/variable. I would rather browse through a list knowing the tag/variable is in there, instead of guessing the exact name of the tag/variable in order for it to pop up in the auto-complete section. But again, this is a personal preference 
.
Not sure whether it would be possible to create a searchable drop down list. So that the number of items reduce while typing in the search criteria?
Finally had some time again to work on it V1.9 is available to test.
What’s new:
- Better tag support when editing text arguments
- Tags are now shown as chips, similar to Homey’s own editor
- Backspace removes a full tag chip at once
- You can insert global tags
- You can also insert tags from previous/linked cards, like an Error token
- System cards with arguments should be easier to edit
- Default/placeholder arguments are shown more clearly when they still need attention
- Several mobile/tablet layout improvements
- Better handling when switching flows with unsaved changes
- Tag picker is now a search dropdown rather than auto complete
- Being able to delete flows
- Being able to create regular flows
When you didn’t already, please read the manual in post # 1 of this topic.
I just followed instructions and it works, the generated API key gets accepted.
Note: I copy the generated API key string by “select all” + copy (the copy button on the right doesn’t alway do what I expect it to do)
Thanks guys! If you have any advice or tips or improvement tips for the app please let me know
Hi @Kyle_Michiels: I noted that when I am scrolling though a canvas on my iPad, MAFE sometimes confuses the scroll gesture with moving a flow card, that is in the same spot as where I started the scroll gesture.
Would it be possible to move a flowcard only after e.g. a long press on the card followed by the move action? This would prevent accidental movements of cards.
Hoe can I test a part of an advance flow. For this moment it is not possible to test from selected point.
Second point: In constant in decisions block I do not see decimal point or commas. It will shows as space
A process related advance flow contains many trigger points and many outputs. I see this as a complete process control block.
I am working on iPad Air with mouse and keyboard.
@Kyle_Michiels: I noticed some weird behavior when creating Advanced Flows from scratch via MAFE. See the example below. Just a few flowcards connected to each other. The flow is saved.
If I open the flow in Homey’s own flow editor, the canvas stays empty. If I export the flow in Homey and inspect the JSON-representation of the flow, I noted that all flowcards have either a negative X or Y position or both:
If I manually change the negative X and Y coordinates into 0 or positive values in the JSON and import the edited flow into Homey, it shows the flowcards.
So it seems that MAFE’s canvas is larger than Homey’s own flow editor can display. Homey’s own canvas starts at the position in the top left corner with X and Y coordinates being 0. It does not show flows that are in the negative space (further above or to the left).
I don’t know why MAFE put or allows to put the flowcards in the ‘negative’ area, but I assume that should not be the case.
MAFE v1.9.1 is now available on Test
Hi all, a small maintenance update for MAFE is live in the Test channel.
Why this update?
Athom is tightening how Homey sign-in tokens are issued. From homey-api v3.21.0 on, the short-lived token MAFE uses to sign in to your Homey is bound to that specific Homey, so it can’t be reused on any other Homey. Athom will stop accepting the old, unbound tokens in the future, so MAFE now uses homey-api 3.21.0.
What does this mean for you?
Nothing changes in how MAFE works. You don’t need to re-link your account. Signing in should work exactly as before, just a bit more securely.
If you run into any sign-in problems after updating, please let me know here.
@SunBeech @Gerard_L I’ve seen your latest posts and will get back to them separately.
Update: v1.9.2 now on Test
v1.9.2 makes the app download much smaller (about 2 MB instead of 84 MB) by removing development tooling from the app package. No functional changes.
Update: v1.9.3 now on Test
- Touch devices: cards can now only be moved after a long press, so scrolling the canvas on an iPad no longer drags cards around.
- Flows built from scratch in MAFE now show correctly in Homey’s own editor (no more cards at negative positions). Existing flows are fixed once you save them again in MAFE.
- Number fields accept both comma and dot as decimal separator.
@SunBeech these first two are based on your feedback, I’d love to hear if it works better for you!
@Gerard_L Thanks! Testing from a selected card isn’t possible yet: Homey’s API only lets apps start a whole Advanced Flow, not from a specific card. About the decimals: could you tell me which card it is (e.g. a Logic “number is greater than” condition) and whether the problem is when typing the value or how it’s shown on the card afterwards? A screenshot would help a lot.
Thanks for the update 
!
Dragging the canvas while touching a flowcard does indeed not move the card anymore (just the canvas). And cards on a newly saved flow are now placed indeed in the visible space.
I did came across two other things (not new):
- When launching MAFE, it sets the folder menu somewhere (or exactly?) in the middle of the list. Hence by default, the middle folder is selected and new flows are saved in that folder. I have a lot of folders and sub-folders. The result is that new flows are saved somewhere in a sub-folder that happens to be the one that was in the middle of the list. Could you change this behavior, such that by default upon launching MAFE the top level ‘My Flows’ location is selected?
- Regarding that top level location: I am not able to select the ‘My Flows’ section, as it is not available in the folder list. Note that in Homey you can save flows directly in the ‘My Flows’ section. So not in a folder in that section. The ‘My Flows’ section is actually the default place where Homey stores new flows.
@SunBeech Great to hear the touch and position fixes work for you, thanks for testing! Both folder points are fixed in v1.9.4, now on Test: “My Flows” is always the first entry in the folder list and is selected by default at launch, so new flows are saved at the top level unless you pick another folder. Let me know how it goes.
Thanks for the quick follow-up!
I checked v1.9.4. Indeed MAFE starts in the top level folder (My Flows).
However:
- If the My Flows section does not contain any flows, the canvas shows the contents of the middle flow in the total list of flows.
- If you delete a flow from the My Flows sections and that flow was the only flow in that section, the same behavior as described at the first bullet applies: the canvas shows the middle of the total set of flows.
In both cases I would expect the canvas to remain empty as no flow is selected.
