Skip to content

Atome#26044

Closed
BaQs wants to merge 219 commits into
home-assistant:devfrom
BaQs:atome
Closed

Atome#26044
BaQs wants to merge 219 commits into
home-assistant:devfrom
BaQs:atome

Conversation

@BaQs
Copy link
Copy Markdown
Contributor

@BaQs BaQs commented Aug 18, 2019

Breaking Change:

Description:

The atome sensor platform is retrieving the consumption of your home from the Direct Energy Atome electric meter.
This special little device is connected to a Linky Electric Meter, and sends live data to a cloud platform.

Related issue (if applicable): fixes #

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
10172: home-assistant/home-assistant.io#10172

Example entry for configuration.yaml (if applicable):

sensor:
  - platform: atome
    username: YOUR_ATOME_USERNAME
    password: YOUR_ATOME_PASSWORD

Checklist:

  • The code change is tested and works locally.
  • Local tests pass with tox. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
  • Untested files have been added to .coveragerc.

If the code does not interact with devices:

  • Tests have been added to verify that the new code works.

balloob and others added 30 commits July 31, 2019 16:19
* Expose comfort presets as HA presets

* Fix bugs

* Handle unavailable

* log level debug on update

* Lint
* Improve handling of empty results from Rejseplanen (Fixes #25566)

* Exclude attributes with null value

* Add period back into docstring

* Fix formatting
* Improve log error messages

* remove unique_id not ready yet
* Initial commit

* Add some more code

* Local tests passing

* Remove unnecessary line

* Add preset attributes to __init__

* Remove some more debugger lines

* Add some tests

* Fix comparision to None

* Improve test coverage

* Use unknown modes as presets

* Bugfixes and test improvements

* Add tests for unknown preset modes

* linting

* Improve mappings

* Move PRESET_MANUFACTURER_SPECIFIC to zwave

* Replace isinstance with cast

* Add test for hvac_action

* hvac_mode is never None

* Improved mapping of current mode to hvac/preset modes

* Fix bugs where hvac_mode is None

* Add default hvac mode

* Fixed default hvac mode

* Fix linting

* Make flake happy

* Another linting

* Make black happy

* Complete list of default hvac modes

* Add mapping to heat/cool eco

* Fixed another bug where mapping goes wrong
* enable climate away_mode and home.refresh

* Add Party eco modes
* Allow configuration to not track clients or devices
* Revert Black

* Revert "Introduce support for color temperature (#25503)"

This reverts commit e1d884a.

* Revert "Fix flux_led only-white controllers (#22210)"

This reverts commit 4813818.

* Revert "Fix MagicHome LEDs with flux_led component (#20733)"

This reverts commit 1444a68.

* Re-Black

* Use mode detection for scanned bulbs
* Fix issue with incorrect Notion bridge IDs

* Less aggressive

* Member comments
* Make connectivity control in line with other implementations
* Add HmIP-SCI to Homematic IP Cloud

* Bump upstream dependency

* Fix HmIP-SWDM
* Bump envoy_reader to 0.8.6, fix missing dependency

* Bump envoy_reader to 0.8.6, fix missing dependency
* Allow reloading scenes

* Update requirements

* address comments

* fix typing

* fix tests

* Update homeassistant/components/homeassistant/scene.py

Co-Authored-By: Martin Hjelmare <marhje52@kth.se>

* Address comments
* Update HTTP defaults

* Fix tests
* Handle device not having a name
@MartinHjelmare
Copy link
Copy Markdown
Member

You can do an interactive git rebase. If you're not comfortable with git it might be easier to start over in a new branch and PR.

@BaQs BaQs requested review from bachya and robbiet480 as code owners August 25, 2019 11:14
@BaQs
Copy link
Copy Markdown
Contributor Author

BaQs commented Aug 25, 2019

You can do an interactive git rebase. If you're not comfortable with git it might be easier to start over in a new branch and PR.

I just tried rebasing, I don't think this is better, right ?
( if it's the case I'll do a new PR indeed, sorry for that)

@MartinHjelmare
Copy link
Copy Markdown
Member

Just git rebase won't do the trick. You need to specify the commits to remove or keep somehow. One way of doing this is with the -i switch, to enter interactive mode. But please read up on git rebase before doing this.

@BaQs BaQs closed this Aug 25, 2019
@BaQs
Copy link
Copy Markdown
Contributor Author

BaQs commented Aug 25, 2019

Ok here is the clean PR:
#26197

@BaQs BaQs deleted the atome branch August 25, 2019 12:07
@lock lock Bot locked and limited conversation to collaborators Aug 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.