I have successfully changed my Max! system to a Max! Cube CUL and I am running Homegear. I have paired my valves successfully some of which are linked to wall thermostats through a channel 1 (wall Thermostat source) - channel 3 (Valve target) link.
Everything works perfctly with the valves linked to wall thermostats. I get regular actual temperature and valve state updates through MQTT.
BUT I get nothing from the stand-alone valves. They are communicating with homegear OK. I can get and put paramsets and I can change the set temperature and if I do, I get an MQTT message of the new variable values including the new valve state and the actual temperature.
But when the valves are running their own schedule and the set temperature changes or the actual temperature causes the valves to move, I get nothing, no MQTT notification and no notification of the valve setting when it changes.
This is a major problem as a vital part of my setup is to control my boiler depending on how many radiatiors are calling for heat. Currently I cannot tell when the radiator valves close either when the schedule changes to a lower set temperature or because the room is warm enough and so I don’t know to turn off the boiler.
I understood that the valves reported their new state (and the current temperature) every time the valves moved (and only then). They certainly did when I was running the Max! software and they don’t need to be linked to a wall thermostat to do that. I don’t have wall thermostats in every room.
Is Homegear missing something or am I?
I have the same problem with both BC-RT-TRX-CyN and BC-RT-TRX-CyG-3 valves
I’d be very grateful for some help here.