Help with HTTP Request to Ezlo hub to get temp
-
I have a temp sensor on my Elzo Plus hub and I wanted to try and send a HTTP Request from MSR to capture that temp data.
I have tested my API HTTP URL in postman and it works in there OK.
I then created a new rules in MSR which I think is correct?
When I run the Action with the Play button I then see this message.
Side Note: We can no longer copy and paste the text from these MSR alerts, since the panel layout changes.
Thanks
-
-
@cw-kid is there a reason you are not just taking the value from the Reactor entity?
-
@cw-kid is there a reason you are not just taking the value from the Reactor entity?
@toggledbits said in Help with HTTP Request to Ezlo hub to get temp:
is there a reason you are not just taking the value from the Reactor entity?
Very good question and I should of done it that way LOL.
For some reason I just had using their HTTP API in my mind.
OK let me try it that way instead using the Entity.
I am just struggling at the moment trying to create a virtual temperature sensor on my Vera Plus.
Doing this as Home Remote does not support Ezlo hubs and I wanted this temp sensor in my dashboard app, so it has to be a device coming from the Vera Plus hub, but its actually paired to the Ezlo Plus hub as its a Zigbee device etc.
Its a shame Rene's Vera -> Ezlo bridge plugin didn't work both ways Ezlo -> Vera also.
-
OK I am stuck, I assume I need some expression code? to look at the "Bathroom Temperature" Entity / Device on the Ezlo Plus to extract the current temp value in to the local expression data.
Once I have that I can then have an Action to Set Variable and send that value to the virtual temp sensor on the Vera Plus.
Maybe something like:
getEntity( 'ezlo_plus>device_61f0bbc0123e4312a1900a1b' ).attributes.temperature_sensor.value
EDIT:
That seems to work but its a long number
EDIT2:
Running the rules action it has sent data to the virtual device on Vera
However on the main device view I see no value shown.
Maybe something wrong with my virtual device on the Vera hub or it didn't like to display the long number.
EDIT3:
I was using the wrong service on the Set Variable Action it should of been:
urn:upnp-org:serviceId:TemperatureSensor1
I now see the data on the device in Vera, however I still need to round down the long number in the local expression some how.
Also looks bad in Home Remote:
-
-
-
Hi Crille
I was just looking in to that
Not sure how to round however so it would show something like 16.5 rather than just 16.
-
@cw-kid Yes, but you don't need to create a new one, just do it like round(getEntity...sensor.value, 1) in your first expression.