I found an error in the shutter adapter, i fixed that in version 0.2.3
-
@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 -
@bertreb said in New plugin pimatic-assistant:
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.4Okay done, works! Thx for your support!
Just a funny fact: GA response for “Move shutter X to 0%” and “Move shutter X to 100%” >> Shutter will be opened.
-
@bertreb said in New plugin pimatic-assistant:
In GA they seems to be available and around Nora the discussion on implementing sensors started.
Where I can find the discussion around Nora? I found no forum…
-
One thing regarding the sync. Today I asked for the current temp outdoor and I got the “adjusted temp” and the current temp. Then I made a refresh (pull down) in my Google Home app and all sensors get synced. Any idea for this. Next time when I see a gap between the values I will try to recreate the assistent main device. Maybe it will trigger GA to reread the sub devices… I thing this is somehow a problem in NORA.
-
Hi, when an attribute like temperature changes the device will update the state towards Nora. You should see these update as debug info in the log.
When you go into a device in Google Home App, the state is also updated with the latest values. -
I tried it with the sensor in my bedroom where I currently have my office and let the temp increase. I can see the change of the temp in the debug output…
…but the temp in Gome Home is still 23°C as before.
It take maybe a while. But the outdoor temp seems to be not changed since the morning, because the “adjusted” temp was really low compared to the measured temp.
I remember to a previous version (i guess 0.2.2) you published, where I was not really able to change the thermostat temp (just for test), because it was immediately readjusted. Did you changed the behavior somehow in this regard?
-
I will give it a try…
EDIT: Yepp, looks better now. Will observe it the next time… Thx for your update!
BTW. Humidity works with NORA now as well in German
-
Short feedback: Temp sensors works fine now. No more sync problems!
The shutter stuff is working well as well, even I have a error message after each command.