After update to version 1.2.4 getting such error in logs:

Logger: homeassistant.setup
Source: setup.py:173
First occurred: 1:42:57 PM (1 occurrences)
Last logged: 1:42:57 PM

Setup failed for sleep_as_android: Integration not found.

In Integrations menu:

If delete Integration - new will not presented in Add menu.

Sleep sensor exists, but with state: unavailable.

Revert to v1.2.3 fix the problem.

General information

Home Assistant

2021.12.4: Installation method (according to instructions): [X] Operating System [ ] Container [ ] Supervised [ ] Core

Integration

Installation method: [X] HACS [ ] manual from release [ ] manual from git Integration version:v1.6.0 Root topic:

Application settings

topic: [X] I can see MQTT messages from application at MQTT-server

How it works now?

After installing the SAA Integration and restarting HA, the SAA Integration is not available under Settings / Integrations

What do you expect?

N/A

Steps to reproduce

1. Install Integration through HACS as described
2. Restart HA
3. Go to Settings / Integrations / Add integration
4. Select / Search Slaap As Android

Debug log

No output generated, despite having added the debug setting to my config.yaml

Additional information

General information

Integration

Integration version: v1.2.0 HASS version: 2021.3.4 Root topic: SleepAsAndroid

Application settings

configured Sleep as android to use SleepAsAndroid/roman topic topic:

• [x] I can see MQTT messages from application at MQTT-server

How it works now?

The events are published by Sleep app to the broker and I can read them using mqtt client, However, the HASS integration doesn't create any device nor entity.

What do you expect?

Device and entity that would collect the events and states from the mqtt topic

Steps to reproduce

I followed all the steps as described in readme

Debug log

I can see logs like:

2[[email protected] config]# grep sleep_as_android home-assistant.log | head -12
2021-04-22 13:11:41 WARNING (MainThread) [homeassistant.loader] You are using a custom integration sleep_as_android which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-04-22 13:11:42 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'persistent_notification', 'input_number', 'map', 'input_datetime', 'mqtt', 'media_source', 'script', 'dhcp', 'met', 'default_config', 'alarm_control_panel', 'logbook', 'input_select', 'influxdb', 'cover', 'input_boolean', 'mobile_app', 'blueprint', 'sun', 'group', 'sleep_as_android', 'ssdp', 'updater', 'zeroconf', 'tts', 'counter', 'scene', 'my', 'tag', 'switch', 'zone', 'input_text', 'sensor', 'tasmota', 'kodi', 'binary_sensor', 'zha', 'history', 'system_health', 'automation', 'hacs', 'timer', 'nodered'}
2021-04-22 13:11:42 DEBUG (MainThread) [homeassistant.setup] Dependency sleep_as_android will wait for dependencies ['mqtt']
2021-04-22 13:11:44 INFO (MainThread) [homeassistant.setup] Setting up sleep_as_android
2021-04-22 13:11:44 INFO (MainThread) [homeassistant.setup] Setup of domain sleep_as_android took 0.0 seconds
2021-04-22 13:11:44 INFO (MainThread) [custom_components.sleep_as_android] Setting up ea7971cef4d1354ff40a907b229a869f 
2021-04-22 13:11:44 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=sleep_as_android>
2021-04-22 13:11:44 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.sleep_as_android
2021-04-22 13:11:44 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Subscribing to root topic 'SleepAsAndroid'
2021-04-22 13:11:44 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Subscribing to root topic is done!

Additional information

just wanted to say hi and thank you for the integration

I have done all your passages in documentation: App Configuration: Home assistant Configuration: I restart but i have not entities why????? Id i see logs i can se connected client and After disconnected at the Same back issue??

General information

Could I request an update to the Blueprint to allow entering a value for the the new attributes from Issue 30

(specifically the Label attribute) When using the Blueprint to create an automation, to create a Condition based on the Label. For example, only run if the Label matches, or Run Except if the Label Matches.

General information

Home Assistant

Version: 2022.11.1 Installation method (according to instructions): [x] Linux VM [ ] Operating System [ ] Container [ ] Supervised [ ] Core

Integration

Installation method: [x] HACS [ ] manual from release [ ] manual from git Integration version: 1.9.2 Root topic: nothing? not sure where to check that setting

Application settings

topic: sensor/SleepAsAndroid/%%%device%%% [x] I can see MQTT messages from application at MQTT-server

How it works now?

99.9% as expected, everything works great, except I have old devices that I can not delete from HA that have been changed out for other phones etc.

What do you expect?

The device to be deleteable in the devices screen

Steps to reproduce

Not sure, but I think

1. add phone as a sensor
2. change the device name
3. old device has no delete button in device list

Debug log

N/A

Additional information

Thank you for the great quality of life boost this is giving me!

General information

Include Alarm Name as Part of Trigger Definition

Usage scenario

I use alarms in SleepAsAndroid for both Wake Up Alarms, as well as various reminders throughout the day. Being able to filter by specific Alarm Names would allow setting automations based on specific alarms.

The MQTT call from SleepAsAndroid includes value2 which usually contains the Alarm Name.

General information

Integration

Integration version: I tried the last one and the main branch from github

Last HACS version, last HA-OS version

Application settings

topic:

mqtt:
  broker: core-mosquitto
  port: 1883
  discovery: true

sleep_as_android:
  name: SleepAsAndroid
  topic_template: SleepAsAndroid/fbsleep

[x] I can see MQTT messages from application at MQTT-server

How it works now?

I can use the MQTT integration to send (and receive in MyMQTT on android), and I can subscribe manually to the above topic and send it from the SleepAsAndroid, but the HACS integration doesn't create any device or logs anything on log (I've set the logger to debug).

General information

Integration

Integration version: v1.2.1 Root topic: Integration fails configuration checks

Application settings

topic: Can't check (application won't start) but believe it was default [ ] I can see MQTT messages from application at MQTT-server

How it works now?

Integration fails to load

What do you expect?

Integration should load!

Steps to reproduce

Install the integration

Debug log

Logger: homeassistant.setup
Source: setup.py:311
First occurred: 12:00:55 PM (1 occurrences)
Last logged: 12:00:55 PM

Unable to prepare setup for platform sleep_as_android.sensor: Platform not found (cannot import name 'TRIGGER_BASE_SCHEMA' from 'homeassistant.components.device_automation' (/usr/src/homeassistant/homeassistant/components/device_automation/__init__.py)).

Additional information

Just upgraded to core-2021.7.0

General information

Home Assistant

Version: 2022.3.0b5 Installation method (according to instructions): [X] Operating System [ ] Container [ ] Supervised [ ] Core

Integration

Installation method: [X] HACS [ ] manual from release [ ] manual from git Integration version: v1.8.2 Root topic:

Application settings

topic: [X] I can see MQTT messages from application at MQTT-server

How it works now?

The integration used to work. (MQTT broker settings etc all fine and have not changed.)

Upon startup, the integration errors out with "TypeError: async_subscribe_topics() got an unexpected keyword argument 'new_state'"

Debug log

2022-03-01 14:18:50 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up sleep_as_android platform for sensor
Traceback (most recent call last):
  File "/hass/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
    await asyncio.shield(task)
  File "/hass/.homeassistant/custom_components/sleep_as_android/sensor.py", line 48, in async_setup_entry
    await instance.subscribe_root_topic(async_add_entities)
  File "/hass/.homeassistant/custom_components/sleep_as_android/__init__.py", line 257, in subscribe_root_topic
    self._subscription_state = await subscribe_2021_07(
  File "/hass/.homeassistant/custom_components/sleep_as_android/__init__.py", line 235, in subscribe_2021_07
    return await subscription.async_subscribe_topics(
TypeError: async_subscribe_topics() got an unexpected keyword argument 'new_state'

Additional information

General information

Home Assistant

2021.11.1: Installation method (according to instructions): [X] Operating System [ ] Container [ ] Supervised [ ] Core

Integration

Installation method: [X] HACS [ ] manual from release [ ] manual from git Integration version: v1.4.0 Root topic: SleepAsAndroid

Application settings

topic: bartfp3 [ X] I can see MQTT messages from application at MQTT-server

How it works now?

Configuration changes in name and/or topic are submitted. The integration reports success but values do not change from defaults.

What do you expect?

Values change to strings entered

Steps to reproduce

1. Integration
2. SleepAsAndroid
3. Configure
4. Submit

Debug log

2021-11-08 20:14:59 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration sleep_as_android which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

Additional information

This is part of troubleshooting why the integration does not create a device for the app. MQTT explorer shows events being published to the broker. Home Assistant is able to read another sensor over MQTT.