I have to fix:
the power and energy values are output.
I’m going to put a capability on it to see the soil temperature
I don’t know why, it says that it does not support the 0x0000, occupancy attribute when the manual does include it for the Away mod.
The logs are missing when you select AWAY mode on the thermostat to see what it sends to the driver.
I will write to you privately and you will answer me there.
Hi…I’m intermediate level with Smartthings and just a beginner with Edge Drivers. I just installed the latest beta temp sensor with child thermostat and paired my aqara temp sensor.
Everything was good with my new routines to turn on an electric heater based on temp. Out of nowhere the temp sensor goes from reporting 69.6⁰ f to 30⁰f. Which of course turned on my heater. Needless to say, it was not 30⁰f on my room.
I did have an offset of -1. After the drop to 30⁰, I set the order back to 0…not sure if that would have caused this though.
Any ideas what caused? 20 min later it did update to 72.1⁰f and my heater turned off.
It would be awesome if we could just install a virtual thermostat and choose an existing temp sensor. Current I have an ecobee thermostat downstairs and remote sensors in other rooms. I would love to just be able to use my ecobee remote sensor to measure and feed temp to the vThermostat. Right now, I have to use my aqara sensors with this driver as I don’t want to unpair my ecobee sensors from the ecobee app.
I know there are some virtual thermostat drivers now but I don’t believe they allow setting a temp sensor.
If the remote Ecobee sensors show up in ST you could use the API Rules. The rule would transfer the room temperature from your remote Ecobee device to the virtual thermostat. You can copy some ones rule, edit the devise IDs and upload the revised rule using @TAustin API Browser+.
I can accomplish that with Sharptools, which I just tested. Thanks for getting my mind on that track. I just think it would be really clean to have a vThermostat with a setting to choose the temp sensor of your choice.
In my case it’s never 0⁰. It’s around 30. I just checked the history of my other aqara sensors that’s not using your driver and occasionally drop from 67 to 32F.
So just ignoring 0⁰ like the other developer did won’t fix mine. What it tells me though is that the aqara sensor is just too unreliable for a heater automation. Kinda dangerous even.
I’ve since stopped using aqara for this case and I’m using my ecobee sensor. I’m using a vEdge driver with a vThermostat. I’m sending values of my sensor to the thermostat with Sharptools. I could not use your thermostat because it doesn’t let me set the temp value.
I’m an italian user and in Italy we use Vimar as Thermostat.
there are a lot of pepole that can’t find a way to use their thermostats, because nobody use Vimar out of Italy.
We ask for your help, please.
A thermostat is a more complex device than a switch or a temperature sensor.
It is not enough to add your fingerprints to an existing driver.
Need to know all its characteristics, modes used, if it is used for heat, cold or both…, it is necessary to know the manual and the cluster and attributes it uses to see if it is possible to add it or have to write a specific subdriver and the most It is important to do debugging tests, viewing logs with the CLI
If you are willing to provide the manual and send logs with the CLI to debug the driver, then I could try doing that
Dear Mariano, thank you.
i don’t know how it works, because i’ve never used it: for use vimar devices in classic way you need a gateway. in my home i haven’t install it, because i work only with smartthings and zigbee protocol.
I don’t know if this can help, anyway this is the link of the product: Termostato rotella connesso IoT2M grigio - 02973
of course i’m willing to share with you the logs, but i have to know how