Oh, thanks chytrak-house for the tip that the manual activation fails. I spent a few hours yesterday trying to fix this problem as well. I will wait and see if the data are sent over to loxone now and will report here.
Update: Seems to work now. Thank you all for the information provided here.
(In the beginning I had a 301 error in the logs, which was due to a typo in the password. W*F.)
Hi, this is exactly what I was looking for, however, I have a question, where should I put the sensors I want to exchange?
following -domain: sensor ?
Hi, thanks for this work Gigatexel, I had it working but somehow it stopped after I did some updates (can’t remember which). Couple of questions:
- should I put the portnumber with which I normally communicate with loxone in the adress ate the restcommand? ie:
“http://<LoxoneUser>:<LoxonePassword>@192.168.2.110:port/dev/sps/io/{{ parameter }}” - should I configure something on the loxone side that I am not seeing?
- in the timeline of traceroute there is a start and a finish, no errors
- any idea where to look? please find some info from the traceroute below:
domain: rest_command
service: update_loxone
service_data:
parameter: pet_feeder_last_amount/6
target: {}
running_script: false
- it says running_script: false, is there a script that I have not installed? I have only 1 rest command in the configuraion.yaml file. Spend hours on it and re-installed bit can’t figure it out.
thanks for the help!
- Do you use a different port-number for the Miniserver? I think the default config is port 80.
- You need to configure the VI offcourse.
Cab you try to trigger the update in your browser?
Should be something like:
http://<LoxoneUser>:<LoxonePassword>@192.168.2.110:port/dev/sps/io/pet_feeder_last_amount/6
3 Likes
Thanks for your help, feel a bit silly now, in the end just typo / wrong config in the URL (yes, port is needed). Triggering update in browser helped solve it and helped testing workings of other sensors.
1 Like
Hi, first of all thanks for the blueprint! I’m struggling to get the data to Loxone, I’ve followed all the steps, but the value in Loxone remains 0.
Attached a picture of all the settings and stuff I’ve configured. Hope someone can point me in the right direction as to where to find the solution.
In the developer tab, I can find the Loxone rest command in the services tab, but when I trigger this, nothing changes in Loxone.
The call is missing the data itself.
Can you post the trace for the service all in the automation?
I see two different entities: the sensor in HA is called sensor.pv_estimate_1000 and the trigger for the blueprint is pv_estimate_today_1000?
Are you kidding me? Did I overlook that… Really sorry for wasting your time on this…
Hi, may i have the same problem. My sensor is a binary sensor, too.
Do i have to edit the loxone.inputs.yaml for binary sensors?
Yes.
I have also edited the blueprint in the first post to support binary sensors.
Would you pleas let me know , how you edited it?
just remove and import the blueprint
Hello,
I am unable to get the script to work.
Here is the error message in the logs:
“Home Assistant to Loxone: Error executing script. Error for call_service at pos 1: Error rendering data template: UndefinedError: ‘dict object’ has no attribute ‘entity_id’”
I’ve checked, and I can’t find the reason for this error.
Can you help me?
Fix found :
My WRONG config in coniguration.yaml
update_loxone:
url: "http://<toto>:<fifi>@192.168.2.49/dev/sps/io/{{ parameter }}"
method: GET
The GOOD config in configuration.yaml
rest_command:
update_loxone:
url: "http://toto:[email protected]/dev/sps/io/{{ parameter }}"
method: GET
I can’t get any data to loxone. the value always remains on 0.0. I think the problem is because the parameter is missing ‘sensor.’ (see screen)
Your Loxone configuration is most certainly wrong.
they are exactly named as you described. without the domain and the dot separator:
What happens when you call the URL in your rest-config manually from your browser?
So for example: http://<LoxoneUser>:<LoxonePassword>@192.168.2.110/dev/sps/io/mein_pool_orp/852.0