I have an Atlassian account with one workspace, and I can, and always could, create tickets,
and just created this test ticket for you.
I noticed one thing, in the listing on the left, there’s also an entry for ‘Jira issues’, right below ‘Issues’
When I click on 'Jira issues" and then “Create issue” at the right, I get a ‘forbidden’ symbol.
Maybe it confuses some users? Can you hide the ‘Jira issues’ entry from the listing?
(I know your support links open the ‘issues’ page right away, I just noticed the entry in the listing)
Hey, if peter cannot help, please create a ticket.
Now BitBucket is fixed (well, at least with an account) and the adapger should be here “shortly”, it won’t be long before a have an Homey day.
And first think will be goong theough the support tickets.
Thanks for checking, here is the new TEF test flow, now enabled.
I have separately shared the AVD, otherwise you would get tons of flows that are not related to the issue.
You’re welcome. Importing flows doesn’t work anymore here atm → Mistery solved, they were installed on my Homey cloud somehow
I imported your AVD, and replaced a few flowcards in the previous imported basement flow.
I have to say I don’t get your flow (at all), but when I test with updating the status indicator field, there still is nothing getting turned on or triggered with the AVD
Can the flow(s) be the cause of the motion alarm activation?
That’s the only reason I can think of now.
Do you have any other AVD’s which activate a virtual motion state, after updating it’s status indicator field?
Thanks for trying. I have minimized the flow even further in TEF (just in case I did something wrong in the previous one) and screenshot.
The purpose is to log the last virtual motion in a zone and show it in the status of the AVD device.
Virtual motions are generated for example by switching on the lights.
The AVD device is located in the zone “Basement salon”.
When the AVD motion alarm is triggered by setting its Virtual motion field to Yes, then the flow:
A. Triggers activity in the zone “Basement salon”.
B. Sets the time of the last motion in a text field Time last presence
C. Sets the value of Time last presence in the status
When doing C: there is another motion seen, but it is not every time.
There are no other flows/influences on the zone.
Why isn’t the icon of my button changing when I change the icon here and press “save device”?
I have reactivated, restarted and updated the app to newest version.
Because icons are only loaded the first time the are used after a app start.
So you, changing an icon means you need to restart the app. I cannot change or control that (thats why i have it written in the app settings)
Turns out you are right. Bur this is a bug! Please create a ticket?
@Tirrazo button1 is special (its the device tile button and will always be the first button) but it should display custom icons just like any other button.
@Arie_J_Godschalk
I did some more checking on this issue. I want to open a ticket, but cannot get into Bitbucket.
When writing a text into the status field during the time (eg. 3 seconds in my example, but the standard motion duration is more likely 9-10s) that virtual motion equals yes, the motion is interrupted and restarted after the status update. The 2nd motion is then shown which is the bug.
Okay, i have updated the DC App.
There are some bugfixes in the AVD settings, and, there was one mentioned bug:
When a AVD is started (after app restart) or when you create a field, if all Reflected values were older than the ExcludeSeconds, the field value would be empty.
This has now been fixed, the last value will be keept when there are no devices that are not excluded.
This is needed for f.i. lux, since the max is 2000 and that might not be update the whole (sunny) day.
If this generates other issues, please let me know, then we need to find another solution.
But for me this only fixes issues, and i haven’t found any downside to this.
Update to the latest version for those fixes and more translations.
Okay, Chronographs were not correctly updated since my last performance change.
This issue is now resolved, but it was a bug in the Chronograph app, so you need to update Chronograph.
