Minut Point
The Point hub enables integration with the Minut Pointclient_id
and client_secret
with the callback url
configured as your Home Assistant URL + /api/minut
, e.g., http://homeassistant.local:8123/api/minut
. The client_id
and client_secret
should be used as below.
Once Home Assistant is started, a configurator will pop up asking you to Authenticate your Point account via a link. When you follow the link and click on Accept you will be redirected to the callback url
and the Point integration will be automatically configured and you can go back to the original dialog and press Submit.
There is currently support for the following device types within Home Assistant:
Configuration
To use the Minut Point integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] in your installation, add it to your configuration.yaml
The configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file.
After changing the configuration.yaml
The configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file, restart Home Assistant to apply the changes. The integration is now shown on the integrations page under Settings > Devices & services. Its entities are listed on the integration card itself and on the Entities tab.
# Example configuration.yaml entry
point:
client_id: CLIENT_ID
client_secret: CLIENT_SECRET
Device types
The integration supports the following device types within Home Assistant:
The Point is just active occasionally so the sensors are only updated every hour or so. The binary sensors are however updated via Cloud Push, making the changes close to instant.
Alarm
Each home configured in the Point mobile application will show up as a separate alarm control panel. The panels allow arming and disarming of the Point home alarm system.
The Point only supports a Arm/Disarm action, so it is only Arm Away
that is implemented.
Binary sensor
Each Point exposes the following binary sensors:
-
alarm:
On
means alarm sound was recognized,Off
means normal -
battery:
On
means low,Off
means normal -
button_press:
On
means the button was pressed,Off
means normal -
cold:
On
means cold,Off
means normal -
connectivity:
On
means connected,Off
means disconnected -
dry:
On
means too dry,Off
means normal -
glass:
On
means the sound of glass break was detected,Off
means normal -
heat:
On
means hot,Off
means normal -
light:
On
means light detected,Off
means no light -
moisture:
On
means moisture detected (wet),Off
means no moisture (dry) -
motion:
On
means motion was detected,Off
means no motion -
noise:
On
means noise was detected,Off
means noise levels have gone back to normal -
sound:
On
means sound detected,Off
means no sound (clear) -
tamper:
On
means the point was removed,Off
means normal -
tamper_old:
On
means the point was removed or attached,Off
means normal (this is only supported on some “old” devices)
The binary sensors button_press, sound and tamper are switched On
for a brief moment and are then switched back to Off
.
Automation example
The following example show how to implement an automation for the button_press binary sensor.
# Example configuration.yaml Automation entry
automation:
alias: "Point button press"
trigger:
- platform: state
entity_id: binary_sensor.point_button_press # Change this accordingly
to: "on"
action:
- action: persistent_notification.create
data:
title: Point button press
message: Point button was pressed.
Webhook events
The events shown as binary sensors are sent to Home Assistant as webhooks with the event_type
set to point_webhook_received
. Below is an example of how to use such a webhook do note the trigger.event.data.event.device_id
which translates to the id of the Point device that sent the event.
# Example configuration.yaml Automation entry
automation:
alias: "Point button press (webhook)"
trigger:
- platform: event
event_type: point_webhook_received
event_data: {}
condition:
condition: template
value_template: "{{ trigger.event.data.event.type == 'short_button_press' }}"
action:
- action: persistent_notification.create
data:
title: Point button press (webhook)
message: "Button press on Point {{ trigger.event.data.event.device_id }}"
Sensor
Each Point exposes the following sensors:
- temperature: Temperature in °C.
- humidity: Percentage of humidity in the air.
- sound_level: Sound level in dBA