-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
web api not returning entity details for second mixer (heating circuit 2) #865
Comments
yup, a stinky bug. Thanks for reporting. |
I think same as #826, the |
thanks. I've added a test, |
@tglynx Please check https://github.com/MichaelDvP/EMS-ESP32/releases if it solves the issue. |
Thanks, i tested that prerelease but something seems to be still broken ... http://192.168.123.146/api/boiler/wwsettemp return just in the log: |
Yes, this needs a different approach. Please try new build. |
This is working in the latest build... Great work! |
nice, thanks Michael |
Hi, this issue may be related to #857. When using the web API, details of an entity can be queried using the full path of an entity in the web API.
As an example http://ems-esp/api/boiler/wwsettemp returns details of the entity wwsettemp.
This does not work with the mixer entities for the second mixer in the system.
Scenario:
http://ems-esp/api/mixer returns
http://ems-esp/api/mixer/hc1/flowtemphc returns
Now the problem:
http://ems-esp/api/mixer/hc2/flowtemphc returns
EMS-ESP logs the following errors when using the ioBroker Adapter to enumerate the hc2 entities:
I would expect that the details of hc2 entities can be queried the same way as the details of the hc1 entities.
http://ems-esp/api/system returns
The text was updated successfully, but these errors were encountered: