HM-CC-RT-DN: set_temperature values not propagated


#1

Since about Christmas I hit an OpenHab bug in setting Homegear temperature.
While trying to find the problem and installing home-assistant, I found that the set_temperature values are not propagated anymore (hence I’m not entirely shure about its name or whether it should be here). Other values like actual_temperature or valve_state are properly communicated. The thermostats still work fine, i.e. adjusting their temperatures according to schedule.

The homegear event log (homegear -r => ev) does not show the set values. Device 3 is the only one of which the set_temperature is actually properly shown.

Any hints?

Some log excerpts for reference:

ID >>3<<, channel >>0<<, variable >>RSSI_DEVICE<<, source >>device-3<<, value >>(Integer64) -61<<
ID >>3<<, channel >>0<<, variable >>LOWBAT<<, source >>device-3<<, value >>(Boolean) 0<<
ID >>3<<, channel >>4<<, variable >>ACTUAL_TEMPERATURE<<, source >>device-3<<, value >>(Float) 22.4<<
ID >>3<<, channel >>4<<, variable >>BATTERY_STATE<<, source >>device-3<<, value >>(Float) 2.7<<
ID >>3<<, channel >>4<<, variable >>BOOST_STATE<<, source >>device-3<<, value >>(Integer64) 0<<
ID >>3<<, channel >>4<<, variable >>CONTROL_MODE<<, source >>device-3<<, value >>(Integer64) 0<<
ID >>3<<, channel >>4<<, variable >>FAULT_REPORTING<<, source >>device-3<<, value >>(Integer64) 0<<
ID >>3<<, channel >>4<<, variable >>PARTY_START_TIME<<, source >>device-3<<, value >>(Integer64) 0<<
ID >>3<<, channel >>4<<, variable >>VALVE_STATE<<, source >>device-3<<, value >>(Integer64) 0<<
ID >>0<<, channel >>-1<<, variable >>PONG<<, source >>rpc-client-::ffff:127.0.0.1:45714<<, value >>(String) 96a2a456<<
ID >>4<<, channel >>0<<, variable >>RSSI_DEVICE<<, source >>device-4<<, value >>(Integer64) -52<<
ID >>4<<, channel >>0<<, variable >>LOWBAT<<, source >>device-4<<, value >>(Boolean) 0<<
ID >>4<<, channel >>4<<, variable >>ACTUAL_TEMPERATURE<<, source >>device-4<<, value >>(Float) 22.4<<
ID >>4<<, channel >>4<<, variable >>BATTERY_STATE<<, source >>device-4<<, value >>(Float) 2.8<<
ID >>4<<, channel >>4<<, variable >>BOOST_STATE<<, source >>device-4<<, value >>(Integer64) 0<<
ID >>4<<, channel >>4<<, variable >>CONTROL_MODE<<, source >>device-4<<, value >>(Integer64) 0<<
ID >>4<<, channel >>4<<, variable >>FAULT_REPORTING<<, source >>device-4<<, value >>(Integer64) 0<<
ID >>4<<, channel >>4<<, variable >>PARTY_START_TIME<<, source >>device-4<<, value >>(Integer64) 0<<
ID >>4<<, channel >>4<<, variable >>VALVE_STATE<<, source >>device-4<<, value >>(Integer64) 0<<
ID >>0<<, channel >>-1<<, variable >>PONG<<, source >>rpc-client-::ffff:127.0.0.1:45714<<, value >>(String) 96a2a456<<
ID >>0<<, channel >>-1<<, variable >>PONG<<, source >>rpc-client-::ffff:127.0.0.1:45714<<, value >>(String) 96a2a456<<
ID >>0<<, channel >>-1<<, variable >>PONG<<, source >>rpc-client-::ffff:127.0.0.1:45714<<, value >>(String) 96a2a456<<
ID >>5<<, channel >>0<<, variable >>RSSI_DEVICE<<, source >>device-5<<, value >>(Integer64) -51<<
ID >>5<<, channel >>0<<, variable >>LOWBAT<<, source >>device-5<<, value >>(Boolean) 0<<
ID >>5<<, channel >>4<<, variable >>ACTUAL_TEMPERATURE<<, source >>device-5<<, value >>(Float) 20.3<<
ID >>5<<, channel >>4<<, variable >>BATTERY_STATE<<, source >>device-5<<, value >>(Float) 2.8<<
ID >>5<<, channel >>4<<, variable >>BOOST_STATE<<, source >>device-5<<, value >>(Integer64) 0<<
ID >>5<<, channel >>4<<, variable >>CONTROL_MODE<<, source >>device-5<<, value >>(Integer64) 0<<
ID >>5<<, channel >>4<<, variable >>FAULT_REPORTING<<, source >>device-5<<, value >>(Integer64) 0<<
ID >>5<<, channel >>4<<, variable >>PARTY_START_TIME<<, source >>device-5<<, value >>(Integer64) 0<<
ID >>5<<, channel >>4<<, variable >>VALVE_STATE<<, source >>device-5<<, value >>(Integer64) 0<<


#2

Apparently a full reinstall of my raspi solved this issue.