This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Flows
Comments
All logical issues solved! Asking homey to stop the music stops the music, when there is no music and you want to trigger something else, Homey doesn't start the music.
First of all i'm not a expert in Tasker and managed to get thinks working with some trial and error
What to install:
- Http request App --> Homey
- Tasker --> Android APP
- Autolocation( tasker) --> Android APP(1,19 euro for licence)
After installation I configured Autolocation on the phone:click on place in Map and Accept Geofence and Give it a Name like f.e. Home(thuis)
If you are inside the Geofense then you see " Home - inside" and if not then you see Home - Outside
Now you have to configure Tasker by:
- Open Tasker
- Select Tab Profiles And select + ; select Event; select Plugin; select Autolocation; select Geofence
- select pencil to configure
- Select Geofence Name and select in the pop-up Home(thuis)
- Select Status and select in pop-up Inside and select the V to save
- Select the < to go back
- Select + from New Task and give it an name f.e. Home (thuis) and select V to edit the TASK
- Select the + to Add an action by
ADD the Actions in the following order:- Select Location; Select Get Location
- Select + for new action; select Task; Select If and press the Card for adding a variable in the left field which looks like %algeofence; select the equal and chage it to Matches Regex; select right field type Home(thuis)
- Select the Plus and do the same point 3 but in the left field you have to select %alstatus and right field you type Inside--> don't forget to change the Equal as above.
- Select < to save
- Select + for new Action; select Net; Select HTTP Get; and add https://Athom_Cloud_ID.homey.athom.com/api/app/com.internet/thuis (home)https link at Server:Port; and select < to save
- Select + to add a new action; select Task; select End If
- select < to save Actions :-)
We now have the Geofence Inside configuration and the following steps are for the Outside Geofence configurationSelect Source = GPS and select Timeout 20 sec and go back to save
( My Mobile is not that accurate when it is in sleep mode and then I have an Offset in my location. This way my mobile wakes up when it thinks it is outside the Geo-fence and does check first the real location)
configure Tasker again by:
- Open Tasker
- Select Tab Profiles And select + ; select Event; select Plugin; select Autolocation; select Geofence
- select pencil to configure
- Select Geofence Name and select in the pop-up Home(thuis)
- Select Status and select in pop-up Outside and select the V to save
- Select the < to go back
- Select + from New Task and give it an name f.e. Away(onderweg) and select V to edit the TASK
- Select the + to Add an action by
ADD the Actions in the following order:Select Source = GPS and select Timeout 20 sec and go back to save
( My Mobile is not that accurate when it is in sleep mode and then I have an Offset in my location. This way my mobile wakes up when it thinks it is outside the Geo-fence and does check first the real location)
We now have the configuration Inside- and Outside- geofence ready in Tasker
The last thing we have to do is to make some Cards with Http request App in Homey like:
I'm sure that some steps above can combined but for now, I have for me the best Geo-fence solution.
With this Geo-fence solution you can also add multiply Geo-fence locations , such as WORK, School etc....
Have fun.
you can explore autolocation for free for 1 week.
@dENNtoet I didn't notice any changes from my battery since I use Tasker
When changing the volume of the receiver, I swipe the slider to left or right, and afterwards set it back to the middle position.
The flow to reset the variable to 50 again is just for the next calculation.
Oddly enough when I press the down button it doesn't go down 0.1 exactly ... e.g. when the volume is at 4 and I press down the new volume is 0,30000000000000004. Sonos doesn't understand this number so the actual Sonos volume stays the same. Any idea what's going wrong?
Make a screenshot of ur flows and upload?
After having the better logic number variable u use this card?
Now quit ur Homey desktop app and try Chrome.
At sun set, and the light is out, turn it on and set it to 50% dim level
When its 22:30 set dim level to 20%
When some 1 presses the doorbell and the light is on (so it does not work during day time) start a timer set to 5 minutes
Timer sets the light to 70%
When the timer ends and the time is later then 22:30 set dim level to 20%; else set dim level to 50%
At sunrise it turns the light off.
This is to keep the front door lighted, preventing burglers to get to my door out of sight, and when some 1 presses the doorbell at night it will light up more to give that little extra so we can see who is it the door
Btw, what doorbell and light are you using?
At the moment i got a klik-aan klik-uit plug/dimmer for the light, going to change that later for z-wave.
And i got my regular doorbell connected to my alarm system, so when some one presses it, it switches 2 outputs, 1 for the normal doorbell and 1 for a fibaro binairy sensor that way homey knows the doorbell was used.
if you round it using a mathjs expression before passing it to Sonos it works, it's a workaround but sofar it solves the
issue for me. (below the full syntax in the betterlogic card.
Created this flow to know if someone was ringing my doorbell in my absence. It also gives you the date and time someone rang upon your arrival back home. It uses a boolean(did the bell ring, yes or no) and string (to store date and time)
The variable to tell homey that I'm home is determined in another flow but is irrellevant in this case.
As I mentioned in another thread yesterday (https://forum.athom.com/post/quote/3565/Comment_56596), the problems I had were solved by re-installing apps everywhere - and it works like a charm now.
I think deleting the devices at the "profile" was what did it, but can't promise anything of course :-)