Skip to content

Releases: custom-components/sensor.avfallsor

0.0.6

27 Dec 19:15
Compare
Choose a tag to compare

Full Changelog: 0.0.5...0.0.6

Fix bug after Avfallsor changed their site.

0.0.5

09 Nov 18:51
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 0.0.4...0.0.5

Fix sync

06 Feb 14:30
Compare
Choose a tag to compare

Full Changelog: 0.0.3...0.0.4

0.0.3

06 Feb 14:25
Compare
Choose a tag to compare

Add extra_state_attributes

Full Changelog: 0.0.2...0.0.3

0.0.2

06 Jun 20:33
Compare
Choose a tag to compare

Added version to the component can be loaded by core.

Bug Fix FeatureNotFound

09 Dec 10:59
6978e27
Compare
Choose a tag to compare

Fix a bug with the integration raising FeatureNotFound because html5lib is missing from the manifest.

Breaking changes in v0.0.1

08 Dec 21:41
dd2129c
Compare
Choose a tag to compare

There are some breaking changes in this version.

Config:

municipality: need to be removed, this isnt used anymore
address: Should be in this format Kongeveien 1 A, Kristiansand however most likely the sensor should stille work with the old way you wrote it.
street_id is changed, see the readme.md on how to update it.

Sensor:

entity_id: This is changed to use the hash as a part of the entity_id

The simplest solution is just to delete the sensor from yaml or the integrations page setup again using the integrations page. If latitude and longitude is set you can just click submit button

The integration tries to make it as simple as possible to setup the sensors, as a result it needs to do couple for extra http calls (depending in the settings that was used to retrieve the street_id). To skip this just use the street_id