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.
Comments
Is for presence only the status everyone home or away possible? Or can you also identify single users?
Unfortunately, it will again be necessary to remove all tado devices first and add them again, since already added devices are not automatically updated... but that's what beta is about.
It might take some time as the people at Athom are really busy at the moment.
No big changes, but some improvements.
However... again some changes (like the icons) which require to delete and re-add the devices... so still Beta.
Still thinking about some further improvements which might require re-adding the devices again at future updates.
- Like including battery status for the devices. I think (while searching for other info) I noticed some basic battery information in the data, like 'LOW', 'MEDIUM' and 'HIGH'
- Including tado Airco Control is still on my to-do list until I have found all required data.
- Maybe (!!) adding a central Home-device which would include some capabilities that are the same for every device in a home now, like outside temperature and weather state. This Home device might also offer Home/Away status for all individual family members/connected phones, instead of the general home/away that is available now.... but again... maybe!!!
battery status would be a further good Point!
Just a question: do you have an idea How to repair the eyes in your led ringcollection app?
Last week I changed the batteries in one of my devices for new ones... The API now shows: batteryState: 'NORMAL'
So... I'm afraid it might be something like NORMAL and LOW only. I'll see what I can do with it
since that lacks such info <span>
When I control Tado with a flow, it’s like the default mode is “keep this temperature untill ended by user”. I would like the temperature to stay the same ”untill the next automatic change”. Is that possible?
I'll think about this... I could add different flow cards for "Manual until user ends", "Manual for a certain time" or "Manual until next auto change".
* Battery state icon for Thermostats.
* New Flow Triggers:
* New Flow Actions:
What?... How the tado app is doing? ... well...
UNDER DEVELOPMENT:
Shows minimal info (OK or Low) for one or more thermostats in a tado° Zone
And now I'm working on....
* Special 'Home zone' that checks the tado-connected mobile devices.
All the other zones will keep the 'global' Home/Away detection, but this one will also be able to offer information about every individual mobile device/person... Like detecting who is at home, who is coming home and who is going away.
* Flow Triggers for Home zone:
this one triggers when someone switches LBC on or off and offers tokens for 'name' and 'LBC enabled (false/true)'
- Home/Away status changes. Check!
this one triggers when someone enters or leaves the home area and offers tokens for 'name' and 'At home (false/true)'
- Distance status changes. Check!
this one triggers when the relative distance to the home area changes for a mobile device, and offers tokens for 'name' and 'distance' ( value = 0 to 1, several decimals ). 0 = Home area, 0.5 = a few times the home radius away from home, 1 = very far away from home. This number doesn't seem to have a logical relation to any measure of distance. Nevertheless it's very usable to see if someone is almost home or going further away.
In addition, the 'Home zone' will also get some Conditional flow cards.
When the 'Home zone' development is done, I think we can consider the tado app as finished... offering all information. triggers, conditions and actions that you will never need.
So.... I'll need some days to finish the 'Home zone'... then I need some days to do some extensive tests..... maybe some more days to clean things up... maybe even day doing nothing
Let's say that I expect to offer a new beta Pull Request to Athom in about 2 weeks... and that might be the last update for a long time... unless something needs to be fixed of course!
great @OpenMind_NL and happy new year!
I searched the internet if someone found out how the relative distance number ( 0 to 1 ) for tado works.... nothing...
Then I started experimenting myself with a Fake GPS app for Android, Google Earth distance measure tool, and some calculations... and finally found a formula to convert the relative distance to a real distance in kilometers... with a margin of about 1-2%, so fairly usable!
Whoever may be interested... this is what I figured out:
Kilometers = ( 0.023733 * Math.pow( 3.33333333333, RelativeNumber * 10 ) )
and the other way around:
RelativeNumber = ( (1 / ( Math.log(3.33333333333) / Math.log( Kilometers / 0.023733 ) ) ) / 10 )
So... expect a nice tado-presence implementation in the next beta... if Athom likes it to.
Gonna get some sleep now...
PS: After some more checks and measurements, it seems that it's even more accurate
to use 0.025 instead of 0.023733 ... How simple things can be
BTW: The real heroes are the people at Athom. Without them we would not have Homey or a tado-app at all.
The Home and away funtion from Tado works so much better as the Homey presence detection. After your release I can finally have my alarm turn on and off with the Tado info. Thnx.
I use this flow:
I think also that Tado is better than Homey for presence detection, but it is not flawless.
Some times after 15 minutes Homey tells me that the Temperture is set on **. (arriving)
And I use also a flow that everyting that Homey says is send to my telephone bij push.
When I'm leaving the set temperture is lowering every 500 meters from my home, but some times it doesnt send a message and when I open the Tado app. I get also a message from Homey that the temp is set on **.
(with these flows, you know how tado is working)
Then, after some more testing by me and the CLI-people among you, I expect to offer a new Pull Request (Beta version) to Athom next week.
This will be the new readme information... if you think that something is missing...
i am looking forward to the homezone-feature for better presence in homey.
I have a test flow that sends a timestamp with my distance and automatic thermostat changes in a push-message to my watch when I'm away.
First message is coming in almost immediatly when I leave the home-zone (my radius = 200 meter).
After doing a lot of location tests with a FakeGPS app on my phone and Google-Earth measurements, and entering all data in an Excel sheet to calculate the best conversion parameters, I managed to get an accuracy of about 96% to almost 100% for 'tado relative distance' -> 'kilometers' calculation. Nearby it's more accurate (in fact very accurate) than far away. There's an margin of about +/- 10 meters (compared to GPS data) at a distance of 1 kilometer... and at 4000 kilometer distance the margin will be about +/- 170 kilometers.
tado also offers information about the direction of the mobile device. I may be able to use that in combination with the relative distance to calculate a more or less accurate position for a mobile device (instead of a circle around the home), but I wont do that because of privacy reasons. There are other apps that help people spying on relatives
Only one thing is annoying me... When a mobile device turns of all connections (WiFi, mobile data) or when app-access to the phone's location is disabled, it takes about 48 43 hours for tado to report that to their (and our) app. So, you can't use the tado app to report a sudden mobile shut-down or other emergency situations.
Turning on/off Location-based control in the mobile tado-app is reported to Homey within seconds.
but we must test. but why is there so a diffence between rporting to tado with shut down and a simple turn on/off of the location-based control?
I do understand that they don't want to mark a device as offline or location-unknown when it's not communicating for a few minutes, but I agree that 1 or 2 days is a bit long.
The 48 43-hours is not mentioned anywhere by tado... it's also not available as a parameter from their API... I discovered it myself by setting my test-phone to 'flight mode' which disables all communications.
In the tado mobile-app (on another, still connected phone) you can still see the switched-off device online in the 'circle-graph' when you enable 'Flight mode'... and it will be greyed and marked as 'no location' after about 48 43 hours (almost 2 days). It may be a little shorter but I presume it is 48 hours because I still saw it online after 36 hours (when I went to sleep) and noticed the device being offline when I woke up.
I will see if I can add a user setting for that... It shouldn't be a big problem to make Homey notice that the tado-location data did not change a bit for a device within a certain time.
Maybe a minimal setting of 30 minutes, and being able to raise that in 30-minute steps (up to 48 40 hours) would be ok?
30 minutes may be to low because a device me be on the same location for hours without moving enough to make tado notice that, but for now I can not think of anything else that could make a device identify as 'out of reach' or 'did not move'.
EDIT: Latest test with sending no location to tado shows a time-for-noticing of about 43 hours. I made notes of the time when I disabled location on my test-phone: januari 16, 5:55 AM. This time I kept WiFi on, so the phone could normally connect to the tado-server, but without updating the location. On januari 18, 0:53 AM I received a push message that my test phone did not have a valid location anymore.
Do i have to readd the thermostats again to have all new settings?
is the presence option already included? I can‘t read it in the readme
Yes... there is a 1.2.0 beta release... and no, it's not my update yet.
I didn't check it yet, but Emile told me about it.
In addition, I am not completely healthy at the moment, so I think my update will take a few days extra.