Ok, that type of device i did not migrated yet from gBridge to this plugin.
I will do the migration and publish to test.
-
I add some blinds -> no errors
I add some temp sensors -> works.
Only one thing does not work. In the gBridge plugin you made a synchronization for the measured temp and the set temp. Do you remember? Would be nice to bring this as well in the assistant plugin.
When I ask GA for the temp of the aquarium I get the response to which temp the thermostat is adjusted to and the current measured temp.
For example the Aquarium has 26°C, but the thermostat ist be default on 20°C so I get the answer: “The temp is set to 20° and currently it is 26°.” -
I ask: “What is the temperature of the aquarium?”.
See hereRegarding the blinds. GA response that it will move the blind, but nothing happens. The
auxiliaryof the blind is a shell script which moves the blinds (sh /home/ortin/Homation/jalousienSteuerung.sh modulEinzel esszimmer). In gBridge you extent the command by the given value like “Move the blind x to 50%”. In that case my auxiliary will be extended by 50
sh /home/ortin/Homation/jalousienSteuerung.sh modulEinzel esszimmer 50.
See here -
@bertreb said in New plugin pimatic-assistant:
Did you try “what is the current temperature of the aquarium?
Yep, I tried exactly this. In German and as well in English. I got always both values. When the values are identical, GA response only the current temp. Therefore you did the trick with the synchronization in gBridge.
-
Okay. seems the temp is sync now. When I change the thermostat, then it gets corrected immediately. But what about users who need the thermostat function, for them the sync is not really nice. What you thing about a additional argument?
With the argument the temps gets synced. Without it works like a normal thermostat.The shutters are still not working. Is the implementation now identical to gBridge?
-
When users need a thermostat they should use a DummyHeatingThermostat class device. That device supports setting a temperature (Setpoint) and a temperature sensor for room temperature. I was thinking on making a more sophisticated thermostat device that can do heat, heat-cool, cool, eco etc. All the functions GA supports, but that’s for later.
In the automated adapter selector I first test if a DummyHeatingThermostat device is used (that will map to a normal GA Thermostat) and after that if in the aux field a ‘temperature’ attribute is used. If so, thats when a temperature sensor is emulated via a GA thermostat.
So the temperature device is just using a GA thermostat device ‘under the hood’ to get Google Assistant cooperate.
In the near future i hope real sensors are implemented. In GA they seems to be available and around Nora the discussion on implementing sensors started.Your idea on make it selectable via the aux field is possible, but using a DummyHeatingThermostat class for GA Thermostats and a temperature device for ‘emulated’ GA temperature sensor seems a good solution to me.
On the shutter; should be identical, but i can’t really test it. Do you have debug info of the shutter?
-
@bertreb said in New plugin pimatic-assistant:
In the automated adapter selector I first test if a DummyHeatingThermostat device is used (that will map to a normal GA Thermostat) and after that if in the aux field a ‘temperature’ attribute is used. If so, thats when a temperature sensor is emulated via a GA thermostat.
Wow, this is much more elegant than my idea
@bertreb said in New plugin pimatic-assistant:
I found an error in the shutter adapter, i fixed that in version 0.2.3
Okay, I will try then. Nevertheless here the debug output:
-
Ok, this error tells that the shell script isn’t returning a valid json. Is the last version there was no position value (or null) in the shell-command. That could have caused this response.
-
Test done! Expect of closing the shutter it works!
Commands for closing: “Shutter x close” and “move shutter x to 0%”. Both gets a positive feedback, but the shutter do not react.
Debug output is:
The previous position was 10%. Seems the output fits not to your needs. What you are expecting?
When I say "move shutter to 1%. It works.
Debug output comming from 10%
Further I get this toast:
-
Ahh, you was faster…
-
The problem could be the start position and/or the meaning of position = 0
I’m assuming that the shutter is closed (openPercent 0). After the first command, the real position comes back and the position is updated.
If you send back position 0 is that fully open or closed? -
0 in my case means fully closed and 100 fully opened. It is due to the shelly devices.
-
@ortin said in New plugin pimatic-assistant:
Test done! Expect of closing the shutter it works!
Commands for closing: “Shutter x close” and “move shutter x to 0%”. Both gets a positive feedback, but the shutter do not react.
Debug output is:
The previous position was 10%. Seems the output fits not to your needs. What you are expecting?
When I say "move shutter to 1%. It works.
Debug output comming from 10%The 1% or 10% shouldn’t matter, i’m using the values GA is sending (0%-100%)
-
But doesn’t this debug output means, that your plugin will do nothing, because the requested position is already reached?
-
Yes, the problem is the position sync at the start of pimatic/device. I assume fully closed at start. Once synced it should be ok.
If your shutter doen’t break i will skip the check, because the first command is always send and the position is in sync afterwards (because you return the real position) -> version 0.2.4
