Skip to content

Releases: planbnet/livisi_unofficial

1.12.0

29 Nov 10:55
4de9843
Compare
Choose a tag to compare

Fixed reconnection problems.

If you still have issues with frequent disconnections or the system not responding:
Please disable all Plugins in your SHC (such as Philips Hue) - I suspect they never have been properly tested with local SHCs and may cause all kinds of issues (a memory leak I guess) unrelated to this extension (but maybe related to the websocket connection that this extension uses so the problem is triggered by it).

1.11.3

22 Nov 12:52
Compare
Choose a tag to compare
1.11.3 Pre-release
Pre-release

Maybe fix issue #130

1.11.2

21 Jun 15:40
Compare
Choose a tag to compare
1.11.2 Pre-release
Pre-release
  • Improved error handling again

1.11.1

28 May 17:35
fa0e707
Compare
Choose a tag to compare
  • Add debug logging for failed logins (no access token)

1.11.0

15 Apr 10:55
f5a6842
Compare
Choose a tag to compare
1.11.0 Pre-release
Pre-release

1.10.0

20 Mar 08:47
8239ccb
Compare
Choose a tag to compare
  • Adds a binary motion sensor that automatically resets state (thanks @DanielHabenicht)
  • Fix: Reestablish reachability after reconnect to SHC, e.g. after restarts (thanks @DanielHabenicht)
  • Under the hood code improvements and bug fixes

1.9.3

23 Feb 09:16
Compare
Choose a tag to compare
  • This release just adds a list of all devices to the debug log (if activated) on initial connect. This will be useful for implementing addtional sensors I don't have.

from 1.9.2

  • Diagnostics support for SHC V1 (thanks @DanielHabenicht )
  • Improved error handling

from 1.9

  • Add diagnostics data to SHC (cpu, ram, disk)
  • Change brightness unit to lx (Lux) because that's the only unit Home Assistant accepts. This means this integration now approximates lux values from the percentage values that livisi provides. Max brightness of the sensor is 400 lux.
  • Devices that have been removed from livisi are now automatically deleted when reloading the integration, but only after all entities have been manually removed by the user
  • A few other bugfixes around not correctly closing sessions on setup or reload of the integration

1.9.2

22 Feb 19:25
f8286b8
Compare
Choose a tag to compare
  • Diagnostics support for SHC V1 (thanks @DanielHabenicht )
  • Improved error handling

from 1.9

  • Add diagnostics data to SHC (cpu, ram, disk)
  • Change brightness unit to lx (Lux) because that's the only unit Home Assistant accepts. This means this integration now approximates lux values from the percentage values that livisi provides. Max brightness of the sensor is 400 lux.
  • Devices that have been removed from livisi are now automatically deleted when reloading the integration, but only after all entities have been manually removed by the user
  • A few other bugfixes around not correctly closing sessions on setup or reload of the integration

1.9.1

21 Feb 07:32
Compare
Choose a tag to compare
  • Add diagnostics data to SHC (cpu, ram, disk)
  • Change brightness unit to lx (Lux) because that's the only unit Home Assistant accepts. This means this integration now approximates lux values from the percentage values that livisi provides. Max brightness of the sensor is 400 lux.
  • Devices that have been removed from livisi are now automatically deleted when reloading the integration, but only after all entities have been manually removed by the user
  • A few other bugfixes around not correctly closing sessions on setup or reload of the integration
  • 1.9.0 was burned by a stupid bug... Sorry.

1.9.0

20 Feb 18:37
d60bca3
Compare
Choose a tag to compare
1.9.0 Pre-release
Pre-release
  • Add diagnostics data to SHC (cpu, ram, disk)
  • Change brightness unit to lx (Lux) because that's the only unit Home Assistant accepts. This means this integration now approximates lux values from the percentage values that livisi provides. Max brightness of the sensor is 400 lux.
  • Devices that have been removed from livisi are now automatically deleted when reloading the integration, but only after all entities have been manually removed by the user
  • A few other bugfixes around not correctly closing sessions on setup or reload of the integration