Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration does not work on 2023.8 #53

Closed
W-Floyd opened this issue Jul 31, 2023 · 9 comments
Closed

Integration does not work on 2023.8 #53

W-Floyd opened this issue Jul 31, 2023 · 9 comments
Labels
bug Something isn't working

Comments

@W-Floyd
Copy link

W-Floyd commented Jul 31, 2023

General information

Home Assistant

Version: 2023.8 beta
Installation method (according to instructions):
[X] Operating System
[ ] Linux VM
[ ] Container
[ ] Supervised
[ ] Core

Integration

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

Application settings

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

How it works now?

Integration does not produce any entities

What do you expect?

Integration should produce entities

Steps to reproduce

  1. Install integration
  2. Connect SleepAsAndroid
  3. Note lack of functionality

Debug log

2023-07-30 22:11:39.081 DEBUG (MainThread) [custom_components.sleep_as_android] Got message ReceiveMessage(topic='SleepAsAndroid/William', payload='{"event":"sleep_tracking_started"}', qos=0, retain=0, subscribed_topic='SleepAsAndroid/William', timestamp=datetime.datetime(2023, 7, 31, 3, 11, 39, 81566, tzinfo=datetime.timezone.utc))
2023-07-30 22:11:39.081 DEBUG (MainThread) [custom_components.sleep_as_android] sensor entity_id is SleepAsAndroid_William
2023-07-30 22:11:39.081 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Processing message ReceiveMessage(topic='SleepAsAndroid/William', payload='{"event":"sleep_tracking_started"}', qos=0, retain=0, subscribed_topic='SleepAsAndroid/William', timestamp=datetime.datetime(2023, 7, 31, 3, 11, 39, 81566, tzinfo=datetime.timezone.utc))
2023-07-30 22:11:39.081 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] New attributes is {'timestamp': 'unavailable', 'label': 'unavailable'}

Additional information

@nazar-pc
Copy link

nazar-pc commented Aug 3, 2023

2023.8 is now stable, I wish I knew it doesn't work, I would have not upgraded. HA says entity is no longer provided by integration 😕

@Gibletron
Copy link

Same problem here.
Might have something to do with the MQTT breaking changes:
https://www.home-assistant.io/blog/2023/08/02/release-20238/#breaking-changes

@Gibletron
Copy link

For those looking for a workaround, you can still create your own MQTT sensor:

mqtt:
  sensor:
    - name: "SleepJohn"
      unique_id: sleepjohn_value
      state_topic: "SleepAsAndroid/John"
      icon: mdi:sleep
      force_update: true
      value_template: "{{ value_json.event}}"

For my custom templates and automations this works well enough untill there is an official fix

@theSC
Copy link

theSC commented Aug 4, 2023

Is this being worked on? Should we expect a fix?

@ndrsfr
Copy link

ndrsfr commented Aug 4, 2023

Same issue for me in 2023.8

@W-Floyd W-Floyd changed the title Integration does not work on 2023.8 beta Integration does not work on 2023.8 Aug 4, 2023
@IATkachenko
Copy link
Owner

Will fix it in few days.

Sorry, I have not enough time for the integration support....

@IATkachenko IATkachenko added the bug Something isn't working label Aug 5, 2023
@IATkachenko IATkachenko pinned this issue Aug 5, 2023
@IATkachenko
Copy link
Owner

IATkachenko commented Aug 6, 2023

Done!
Fix release will be available soon.

Right now to fix the issue you may manually edit custom_components/sleep_as_android/sensor.py to just remove line 195 "type": None, from device_info property.

@IATkachenko
Copy link
Owner

Fixed in v2.0.0 (beta now, I hope we will be able to merge #54 today and skip one release / HA restart).

@Gibletron
Copy link

Done! Fix release will be available soon.

Right now to fix issue you may manually edit custom_components/sleep_as_android/sensor.py to just remove line 195 "type": None, from device_info property.

Thank you so much, that's a quick and easy fix!

@IATkachenko IATkachenko unpinned this issue Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants