Skip to content

Device faking of sensors/switches is now first class
Compare
Choose a tag to compare
@zxdavb zxdavb released this 04 Jan 23:40
· 137 commits to master since this release
0.31.7
4a701ff

This is version 0.31.7, which has been tested on HA version 2024.2.x. It is considered stable.

It is a stable release, but please backup your HA installation before installing this version.

You should be able to upgrade/downgrade between 0.31.x and 0.2x.. Whilst doing so, there should be no need to (temporarily):

  • stop enforcing your known list
  • disable your state (packet) cache

Note, however some breaking changes, below, and:

  • RFC2217 no longer supported (see #143)

Overview

This is the first release of ramses_cc that exposes version 2 of device faking. Please see the new guide (WIP) in the wiki for:

It is extensively refactored and includes many fixes over the 0.30.x track, and many, many since 0.2x.x.

These uncorrected bugs have been identified:

  • some OTB sensors (dhw_setpoint, and ch_max_setpoint) are often unavailable when they shouldn't be
  • fetching controller logbook entries (system faults) is currently broken

Changes in 0.31.7

These bugs have been fixed:

Changes in 0.31.6

These bugs have been fixed:

Changes in 0.31.5

The OTC (outside temperature compensation) sensor has had its friendly name changed to 'OTC active'.

These bugs have been fixed:

Changes in 0.31.4

These bugs have been fixed:

  • CO2 sensors were missing from the ramses_cc.put_co2_level service call
  • The material design icons used for relay state (open/closed) were swapped (fixed in commit 8673169).
  • The user wasn't warned that hold_secs isn't supported for the remote.send_command service call (#146)
  • The binary_sensor.18_xxxxxx_gateway_status sensor had the opposite value (e.g. Problem when is OK) (18109e5)
  • The ramses_cc.send_packet service call has a shorted max payload length (#145)
  • Backoff (of polling interval) has been disabled for now (39f0a2d0)
  • Deprecation (of non-responsive devices) has been disabled for now (88bb9d7)
  • Several other binary sensor icons have been improved (78f4f55)
  • Fix bug with updating entity state via async_write_ha_state_delayed (1cb73b8)
  • Most FAN sensors are exposed by default, as before (2772979)
  • Refactoring of OTB._handle_msg() and associated code (e.g. e8ca4c24)
  • Lots of unavailable OTB sensors (792e90ab)

Changes in 0.31.3

The default entity_id for the DHW has changed from water_heater.stored_hw to water_heater.01_123456_hw. This will be an issue if you e.g. reset your entity registry, but keep your automations (this is for people with multiple controllers, with at least 2 having DHW)..

The schema sensor, sensor:01_123456_status is now called sensor:01_123456_status.

Retrieving zone schedules has been fixed (status of DHW schedules?).

Retrieving fault logs is currently out of action, pending a re-write; this means binary_sensor.01_123456_active_fault is unavailable.

Changes in/before 0.31.2

Service call names have added/changed. See the wiki for the new service calls.

In particular, these service calls have been removed:

ramses_cc.fake_device      # is now ramses_cc.bind_device
ramses_cc.put_zone_temp    # is now ramses_cc.fake_zone_temp
ramses_cc.put_dhw_temp     # is now ramses_cc.fake_dhw_temp

Note: the new ramses_cc.put_dhw_temp is different to the old put_dhw_temp service call.

Restored many missing / unavailable / entities. These entities, if extant, can be removed:

binary_sensor.10_xxxxxx_actuator_state
binary_sensor.13_xxxxxx_actuator_state

Extraneous sensors, created in error, have been deprecated. They contained oem_code in their entity_id. They can be safely removed in Settings > Devices & Services > Entities.

Note that the following is a real sensor, and so should not be removed:

sensor.10_048122_oem_code
Assets 2
Loading