-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
climate.set_temperature
with multiple zones: not all are updated
#149
Comments
Suggested as a workaround: - service: climate.set_temperature
target:
entity_id:
- climate.margot
data:
temperature: 5
- delay: &delay
seconds: 5
- service: climate.set_temperature
target:
entity_id:
- climate.dressing
data:
temperature: 5
- delay: *delay
- service: climate.set_temperature
target:
entity_id:
- climate.slaapkamer
data:
temperature: 5
- delay: *delay
- service: climate.set_temperature
target:
entity_id:
- climate.febe
data:
temperature: 5 |
climate.set_temperature
with multiple zones: not everything is updated correctly
climate.set_temperature
with multiple zones: not everything is updated correctlyclimate.set_temperature
with multiple zones: not all are updated correctly
climate.set_temperature
with multiple zones: not all are updated correctlyclimate.set_temperature
with multiple zones: not all are updated
climate.set_temperature
with multiple zones: not all are updatedclimate.set_temperature
with multiple zones: not all are updated
This looks like an issue in ramses_rf - After sending the request ( It should look a bit like this:
|
The workaround is effective because of the delay between each |
I have this down as an issue in QoS in ramses_rf. |
Hmmm... For this call: service: climate.set_preset_mode
target:
entity_id: climate.01_145038_00
data:
preset_mode: none ... I get:
|
Now that:
I would expect this service call to work: service: climate.set_temperature
target:
entity_id:
- climate.margot
- climate.dressing
- climate.slaapkamer
- climate.febe
data:
temperature: 5 |
@phdelodder Can you confirm this issue is resolved? |
@zxdavb only 2 of the 4 zones are being changed. |
I think that the cause of this is that |
@phdelodder Would you be able to modify manifest.yaml, restart HA and test this? If there was an issue, you could always restore the manifest to it's original state. |
Where can I fond the file |
sorry - I meant manifest,json - I am about to release a new version of teh client library, ramses_rf that will have |
I'll wait on the new release then |
Installed the new release and now I got this error: |
@zxdavb Any Idea? ^^ |
The 0.x.17 release has been yanked. I have identified the two bugs involved, so new release soon. |
@zxdavb retest wit 0.x.19: |
Can you send me some logs please. HA log and packet log. |
[downloaded & subsequently deleted] |
In the logs, we have a section (I have added blank lines / comments for readability):
The All of the |
There is no corresponding logging in the HA log, so please configure it like so: logger:
default: warning
logs:
ramses_tx.protocol: debug # info for packets rcvd, debug for sent/rcvd
ramses_tx.protocol_fsm: debug # usus. with ramses_tx.transport: info
ramses_tx.transport: info # info for frames Tx/Rx And send me the logs again - just 5 mins either side of the service call, please. |
|
|
When executing the service call
climate.set_temperature
for 4 zones at the same time, not all zones are updated:Here is the corresponding log file:
After adding:
The issue remains:
The text was updated successfully, but these errors were encountered: