Some of my custom components for home-assistant. (http://www.home-assistant.io)
You can find them in HACS under 'integrations'
NOTE: API seem to have changed, need new reverse engineering!
Dear Customers,
Omnik old version APP has removed,and no running anymore. Please download new APP version (Omnik Portal) from the App Store.
If you use Android system, please go to Google play download: "Omnik Portal" https://play.google.com/store/apps/details?id=com.jialeinfo.omniksolar&hl=en
If you use iOS system, please go to iOS App store download: "Omnik Portal" https://itunes.apple.com/cn/app/id1246117091
Thank you so much for your notice. Omnik Team
NOTE: Network is shutdown.
As of October 27, 2019 the P-Stats Network has shutdown.
This is not a new component but an example automation config useable together with the fritzbox_callmonitor component. The example below will generate several messages depending on status of the event.
# Example configuration.yaml entry
- platform: fritzbox_callmonitor
# Example automation.yaml entry
- alias: 'Phone Status'
trigger:
platform: state
entity_id: sensor.phone
action:
- service: notify.pushover
data:
title: "Phone"
message: >
{% if is_state( "sensor.phone", "ringing" ) %}
{% if states.sensor.phone.attributes.from %}
Ringing on incoming call from {{ states.sensor.phone.attributes.from }}.
{% else %}
Ringing on incoming call from an Unknown or Hidden number.
{% endif %}
{%-elif is_state( "sensor.phone", "talking" ) %}
Call answered.
{%-elif is_state( "sensor.phone", "dialing" ) %}
Calling {{ states.sensor.phone.attributes.to }} with {{ states.sensor.phone.attributes.device }}.
{%-elif is_state( "sensor.phone", "idle" ) %}
{% if states.sensor.phone.attributes.duration | int > 59 %}
Phone call ended, duration was {{ (float(states.sensor.phone.attributes.duration) / 60) | round }} Minute(s).
{% else %}
Phone call ended, duration was {{ states.sensor.phone.attributes.duration }} Second(s).
{% endif %}
{% endif %}
This component fetches random tags from files to be tweeted. The data files are taken from misterhouse, so al courtesy goes to that project. Currently there are two types of remarks implemented, random daily one taken from file specified in config. And outside temperature based.
remarks.py
to your <config dir>/custom_components
directory.remarks
to your <config dir>
directory.To use this component in your installation, add the following to your configuration.yaml
file:
# Example configuration.yaml entry
remarks:
file: 1100tags.txt
hour: 9
minute: 0
outside_temp_sensor: sensor.pws_temp_c
cold_threshold: 5
freeze_threshold: -5
temp_hour: 6
temp_minute: 30
Configuration variables:
remarks
directory. (default = 1100tags.txt)list_temp_below_20.txt
. (default = 5)list_temp_below_0.txt
. (default = -5)Now for both tags an event will be fired.
You can trigger on this with automation rules.
For example you can send them as tweets, to do so place this in your automation.yaml
# Example automation.yaml entry
- alias: Tweeting Remarks
trigger:
platform: event
event_type: remarks
action:
- service_template: notify.twitter
data_template:
message: "{{ trigger.event.data.text }}"
Cloned from https://github.com/robinostlund/homeassistant-volkswagencarnet
So all credits to Robin Ostlund.
I stripped out non supported stuff to get it to work with my VW T-ROC.
This also needs a modified volkswagencarnet python module!
# Example configuration.yaml entry
volkswagencarnet:
username: your@email.address
password: yourpassword
update_interval:
minutes: 5
resources:
- last_connected
- position
- distance
- fuel_level
- service_inspection
- oil_inspection
- parking_light
- doors_locked
- trunk_locked
- combined_range
Configuration variables: