@eoren1 You can put a friendly name on the track_devices parameter line. Example:
‘GaryC’ will be associated with ‘gary_iphone’ in the Event Log
‘garyc_’ will be used as the sensor name prefix instead of ‘gary_iphone_’
See more info in the iCloud3 docs here.
Thanks for the quick reply.
I put that into configuration.yaml and restarted HA. When I click the badges, I see the correct name but the name under the badges is still the incorrect one.
I ended up adding the device_tracker info into customization.yaml and that fixed the names under the badges.
@eoren1 Post the full track_devices parameters and let me try them out to see what is going on. I try to build a name from the device_name if there is no custom name but may have missed something.
From the configuration.yaml portion? or from somewhere in the iCloud3 event log/debug??
@eoren1 Configuration.yaml iCloud3 parameters. For example:
track_devices:
- gary_iphone > [email protected], gary.png, GaryC
- lillian_iphone > [email protected], lillian.png
track_devices:
- eyal_orens_iphone > eyal.png, Eyal
- heather_s_iphone > heather.png, Heather
- fbi_survailence_van > asher.png, Asher
- leilas_iphone > leila.png, Leila
And badges show:
Eyalorens
Heathers
Fbi_Surva…
Leilas
But if I click on the badge, it shows the correct name (below battery and above zone)
For the HA device trackers, I had to use add the following to customizations.yaml
device_tracker.heather_s_iphone_2:
entity_picture: /local/heather.png
friendly_name: Heather
device_tracker.eyal_orens_iphone_2:
entity_picture: /local/eyal.png
friendly_name: Eyal
device_tracker.fbi_survailence_van_1:
entity_picture: /local/asher.png
friendly_name: Asher
device_tracker.leilas_iphone_2:
entity_picture: /local/leila.png
friendly_name: Leila
Edit: And the top of the iCloud3 event log shows the correct names.
Not sure if the badges are pulling names from iCloud3 or somewhere else…
@gcobb321 I just installed the latest 2.2.0 RC and it looks good… the last issue I had with device detection failing on startup and needed a icloud3 restart seems solved.
One thing I’ve generally noticed w/ icloud3 is the “stationary” state. This seems very different than what your current location is.
To me, it seems like there are 2 relevant attributes: Where are you? vs are you moving? (or similarly direction of travel)
So I’d think it’d be more useful to have the device tracker state always be say “home” vs “not_home” and not ever be “stationary” since that’s not a location.
@tmchow When the iOS App, iCloud & iCloud3 enter a zone, the state (device_tracker entity for both the iOS App & iCloud3) is changed to the zone name to indicate that it is in a fixed location and not moving. This sets a longer polling interval to preserve battery life and, when the zone is exited, the polling will change based on the movement and distance from home. The not_home state typically indicates that the device is not in a zone and is moving.
There are many times when you are not moving but do not have an HA zone set up for the location you are in. This might include a friends house, shopping area, store, doctor’s office, etc. These are places you go but not on a regular basis. iCloud3 creates a stationary zone for each device being tracked and moves the zone to the devices location when the device has not moved for a specific period of time. This way, the device can be put into a zone status to change the polling to, again, preserve battery life. You can control how the stationary zone is set up and used by various configuration parameters. You can even turn off using the stationary zone by making the stationary_still_time a very large number (e.g., ‘24 hours’). The iCloud3 state and zone is changed to stationary to indicate that the device is not moving and has entered a zone in the same manner as other zones (Home, Work, Gym, Cosco, etc) are used.
When iCloud3 sets up the Stationary zone, a check is made to make sure the zone is not overlapping another zone or at another zone’s location. If it does, it will not create the Stationary zone and will put an entry in the Event Log (this was added in rc7). I also added some info to the Event Log regarding Stationary Zones (1) the ‘Results’ item now also indicated when the device will be put into a stationary zone if there is no movement (InStatZoneAt-hh:mm:ss) and (2) the ‘Set Stationary Zone’ entry now contains ‘StationarySince-hh:mm:ss’ .
I’m doing some small tweaks to the stationary zone now to take care of some issues related to entering it’s initial location and hope I have nailed them down. Thanks for the suggestion and I hoe this explanation clarifies any questions on how it is used.
I have just uploaded v2.2.0-rc7a with the Stationary Zone updates and to remove debug code. You can get it here.
ICloud3 v2.2.0 Release Candidate 8 is now available.
It addresses some issues with the with entering and exiting the Stationary Zone. Go to the iCloud3 GitHub repository here to download it.
@eoren1 On my system, the name above the picture on the badges is defined on the Lovelace card configuration in the ui_lovelace,yaml file (name statement).
Hi All,
I can’t figure it out … I’ve been working on the installation configuration for a few days now. I follow the installation steps by this guide:. I do the installation via HACS, that’s fine. I don’t use ui-lovelace.yaml so I add the resources through: Configuration - Lovelace Dashbord - Resource. I think this works.
Then I have to add the custom card (so not via the ui-lovelace.yaml), so create it via manual card. the following code I add but then I get all error messages that I do not get out, no matter how many spaces I use for line 4, error message remains…
and
I already search the web , this topic , other topics but I can’t find a solution , maybe my search is not good
(Asked te same question in " Configuration" I don’t know what is the right place to post this question. I home someone can help me with this, getting desperate 
Love the Icloud3 addon. Having a a peculiar issue. Using the FmF method and the HA app. I get periodic changes to ‘away’ when my phone is at home:
My wife’s phone does not seem to do this. She is not currently use the HA app. Any thoughts?
Thanks.
@Buckeyes1995 What entity goes to ‘away’. State? Sensor.devicename_zone? Sounds like GPS wandering where the IOS App issues state changes to exit a zone. iCloud3 detects that and may change device_tracker state but will not change sensor.devicename_zone.
This is described in the iCloud3 docs Here
@olraccus Try lining up card under title and see if that works
- title ...
icon ...
cards:
- type: ...
entity ...
Still having problems installing, please help with this … I am using Google translate so I hope it is clear what I am trying to tell 
If more information is needed then I’d love to hear it, would like this addon to work
I’ll put here exactly what I did according to the manual
I am not using ui-lovelace.yaml file.
1: HACS:
The installation with HACS is going well
2: Install the iCloud3 Event Log
Add repository:
I add the repository via: Configuration - Lovelace Dashboard - Resources.
Location :
/custom_components/icloud3/icloud3-event-log-card.js?v=1,000
Type: Javascript module
Add card:
Since I am not using the ui-lovelace.yaml I follow this link according to the instruction:
"Hit the three dots button twice (once to edit UI, next to open raw editor) Paste the required configuration at the top of this file (above everything else)"
When I paste the configuration above it and save it I get the following message:
"Unable to parse YAML: YAMLException: bad indentation of a mapping entry at line 2, column 9: icon: mdi: information-outline ^"
Then I will align everything but the following:
"Unable to parse YAML: YAMLException: end of the stream or a document separator is expected at line 7, column 1: title: Home ^"
This is my configuration which I change with the raw editor
- title: iCloud Event Log
icon: mdi:information-outline
cards:
- type: custom:icloud3-event-log-card
entity: sensor.icloud3_event_log
title: Home
views:
- badges: []
cards:
- entity: climate.toon_thermostat
icon: 'mdi:home-thermometer'
name: Thermostaat
step_layout: row
type: 'custom:simple-thermostat'
- entity: media_player.marantz_nr_1604
type: media-control
icon: 'mdi:home'
path: default_view
title: Home
- badges: []
cards:
- entities:
- entity: light.woonkamer_alle_lampen
- entity: light.eetkamertafel_links
- entity: light.eetkamertafel_rechts
- entity: light.staande_lamp
- entity: light.tafellamp_woonkamer
- entity: sensor.woonkamer_schakelaar_battery_level
show_header_toggle: false
title: Woonkamer
type: entities
- entities:
- entity: light.hue_lightstrip_plus_keuken
show_header_toggle: false
title: Keuken
type: entities
- entities:
- entity: light.buiten_alle_lampen
- entity: light.lamp_garage_links
- entity: light.lamp_garage_rechts
- entity: light.overkapping_links
- entity: light.overkapping_rechts
- entity: light.voordeur
show_header_toggle: false
title: Buiten
type: entities
- entities:
- entity: light.brandgang_schuur
- entity: light.hue_lightstrip_plus
show_header_toggle: false
title: Overkapping
type: entities
- entities:
- entity: light.bartafel_links
- entity: light.bartafel_rechts
- entity: light.hue_iris
show_header_toggle: false
title: Mancave
type: entities
- entities:
- entity: sensor.hue_motion_sensor_temperature
- entity: sensor.hue_motion_sensor_light_level
- entity: binary_sensor.hue_motion_sensor_motion
title: Hue Motion Sensor
type: entities
icon: 'mdi:lightbulb'
path: verlichting
title: Verlichting
- badges: []
cards:
- entities:
- entity: switch.hs110
- entity: sensor.wasmachine_watts
- entity: sensor.wasmachine_kw_today
title: Wasmachine
type: entities
- entities:
- entity: sensor.toon_afgelopen_uur
- entity: sensor.toon_totaal
show_header_toggle: false
title: Gas
type: entities
- entities:
- entity: sensor.toon_actueel_laag
- entity: sensor.toon_teruggave_laag
- entity: sensor.toon_totaal_laag
title: Stroom laag
type: entities
- entities:
- entity: sensor.toon_actueel_hoog
- entity: sensor.toon_teruggave_hoog
- entity: sensor.toon_totaal_hoog
show_header_toggle: false
title: Stroom hoog
type: entities
- entities:
- entity: sensor.solaredge_current_power_template
- entity: sensor.solaredge_energy_today_template
- entity: sensor.solaredge_energy_this_month_template
- entity: sensor.solaredge_energy_this_year_template
- entity: sensor.solaredge_lifetime_energy_template
show_header_toggle: false
title: Zonnepanelen
type: entities
- entities:
- entity: sensor.toon_p1_heat
- entity: sensor.toon_p1_power_prod_high
- entity: sensor.toon_p1_power_prod_low
- entity: sensor.toon_p1_power_solar
- entity: sensor.toon_p1_power_solar_cnt
- entity: sensor.toon_power_use
- entity: sensor.toon_power_use_cnt
title: My Title
type: entities
icon: 'mdi:solar-power'
path: energie
title: Energie
- badges: []
cards:
- entity: weather.openweathermap
type: weather-forecast
- entities:
- entity: sensor.owm_temperature
- entity: sensor.owm_cloud_coverage
- entity: sensor.owm_rain
- entity: sensor.owm_humidity
- entity: sensor.owm_condition
- entity: sensor.owm_cloud_coverage
- entity: sensor.owm_pressure
- entity: sensor.owm_wind_bearing
- entity: sensor.owm_wind_speed
show_header_toggle: false
type: entities
icon: 'mdi:weather-sunny'
path: weer
title: Weer
- badges: []
cards:
- entity: media_player.marantz_nr_1604
type: media-control
- entity: media_player.achtertuin
type: media-control
icon: 'mdi:play-network'
path: media
Try moving the title, icon, and card left so it looks like the other lines do. Worth yaml, everything is about spaces and getting things lined up. Frustrating at times but look at the other code and how those statements are lined up.
I already tried every possible combination , nothing seems to work.
Removed everything, manual reinstall (Without HACS)
Copied 5 files to config/custom_components/icloud3
and the icloud3-event-log-card.js file to this location :
local/custom_cards/
I am not using ui-lovelace.yaml.
Adding resource via
Configuration -> Lovelace Dashboards -> Resources , hit the + sign and adding this :
/local/custom_cards/icloud3-event-log-card.js?v=1.000
Resource type : Javascript Module
And after that
Hit the 3 dots In the upper right corner of my dashboard -> configure UI -> hit de + sign -> choose custom and adding the following l
title: iCloud Event Log
icon: mdi:information-outline
cards:
type: custom:icloud3-event-log-card
entity: sensor.icloud3_event_log
There is no error but also no visible card… (Tried every possible line-up)
In your first post, you had:
- title: iCloud Event Log
icon: mdi:information-outline
cards:
- type: custom:icloud3-event-log-card
entity: sensor.icloud3_event_log
title: Home
views:
- badges: []
cards:
These statements define the dashboard:
title: Home
views:
Move your code so it is under the ‘views:’ line so it is included in the Home dashboard with your other entities.
title: Home
views:
- title: iCloud Event Log
icon: mdi:information-outline
cards:
- type: custom:icloud3-event-log-card
- title: Home
badges: []
cards:
- entity: climate.toon_thermostat
icon: 'mdi:home-thermometer'
name: Thermostaat
step_layout: row
type: 'custom:simple-thermostat'
- entity: media_player.marantz_nr_1604
type: media-control
icon: 'mdi:home'
path: default_view
(And the rest of your code)
Unfortunately I can’t get it done yet, too bad because I really want to use this plugin.
I appreciate that you make time for me and want to help with this!
When i do what you told (removed all my other code to be sure it has nothing to do with that) I get a blank page.
When I go back to the “Configure UI” I see this:
I choose edit and then only this code is visible:
type: 'custom:icloud3-event-log-card'
I am going to reinstall the whole system, now not on VirtualBox but on Vmware Fusion.
I have several things that are not going well now, so I really want to exclude everything.
Installation will not take that long I think, have a good backup of the config files.
I’ll be back 