This was no easy feat for my HASS version 0.77.3 on Debian jessie in a virtual environment on a Pi Zero W. I kept running into
“Compile failed: command ‘gcc’ failed with exit status 1” for multiple reasons, including running out of memory. The tricks were to make sure you’re installing the libraries in the virtual environment [rooky mistake, I know] and create a swap file to avoid the memory problem. Here’s the step by step of what worked for me, starting as pi user
I am using fritzbox component tracker for tracking with the following configuration. My problem is that the away mode is delayed for around 10 minutes. This is not always the case, since sometimes the away is correctly interpreted. Just for the sake of discussion I have a fritzbox 7490 modem and two 1750 fritz wifi repeaters. Any help.
device_tracker:
- platform: fritz
password: xxxxxxxxxxxxx
interval_seconds: 15
consider_home: 60
new_device_defaults:
track_new_devices: False
hide_if_away: False
I think that Fritz keeps the devices in its table even if the devices are not connected . In order for fritz to remove the device from the table and set the device as disconnected it needs 10min.
The fritz component scans this table. So, if the device is there it thinks that the device is connected but this is not always the case.
Hi, please, can you help me?
I would like to include a remote fritz tracker in my home assistant. I would like to make an entry like -host_dns - also so that every 3 days I delete the list of tracked devices
Thank’s in advance!!!
The device_tracker for “platform: fritz” is not at all useless.
Fritz!Box remembers the devices but does not cache their states.
The states correctly switch from “home” to “not_home” and vice versa.
The configuration is extremely simple. As the network devices data is exposed anonymously by Fritz you do not even need to provide login credentials. Simply add these two lines to configuration.yaml and all devices in your LAN will be tracked automatically: