This object is in archive!
Virtual meters are not updating anymore
Not a Problem
I have found that new virtual meters dont work anymore. Old virtual meters are updating and new ones are not.
Steps to reproduce:
Create virtual switch (set to generic On/OFF)
Create virtual meter (set to generic meter)
Make rule like this in picture:
Result: Virtual meter is not updating..
Try to change values in rule - it will not update.
Also
- there is noticable delay.
- new virtual meters are incorectly set up as http device by default.
Reboot does not fix this. I checked API and settings. No clue why some rules work and some not.
I created very basic rules to test this - and I always get this..
Any ideas?
Files:
picture RULE.jpg
The same problem 
No connection
Real-time notifications may not work
I had this problem many times. The solution I found is to delete and recreate the virtual sensor. It works once in two ...
and try to adjust the delay to 4s.
I added this delay to all my rules IFTTT / Google home, otherwise the sensors do not update. For example, in your rule, the sensor will go OFF before it has been set to ON and remains ON. I do not know if I'm very clear
I had this problem many times. The solution I found is to delete and recreate the virtual sensor. It works once in two ...
and try to adjust the delay to 4s.
I added this delay to all my rules IFTTT / Google home, otherwise the sensors do not update. For example, in your rule, the sensor will go OFF before it has been set to ON and remains ON. I do not know if I'm very clear
I stop using the "set" method and use http post to send a value.
No problem after that.
I stop using the "set" method and use http post to send a value.
No problem after that.
HTTP is out of question. It works for simple examples. When combining multiple meters in new one - it is impossible to work with this.
Delay has no impact on this. I noticed problems first when meter is changed once per day. I tried this with 10 virtual meters - and all are not updating.
Can anyone from Zipato look at this?
HTTP is out of question. It works for simple examples. When combining multiple meters in new one - it is impossible to work with this.
Delay has no impact on this. I noticed problems first when meter is changed once per day. I tried this with 10 virtual meters - and all are not updating.
Can anyone from Zipato look at this?
Hello,
I tested your simple rule and it works just fine, the only difference is I didn't use an operator since the "Value1" needs a clean integer value and not an arithmetic value "1+2", which in this case is a 3 but still how you send the value is from the ruleset still different.
Hello,
I tested your simple rule and it works just fine, the only difference is I didn't use an operator since the "Value1" needs a clean integer value and not an arithmetic value "1+2", which in this case is a 3 but still how you send the value is from the ruleset still different.
Hello,
today it is working. I am not sure - what is changed. All tests went ok - and few days ago the very same test/rule were not working.
Maybe there was something about cloud and updates as also mail messages from system had 10-30 min delays in that time window of few days.
We can close this. Thank you for attention.
Metod
Hello,
today it is working. I am not sure - what is changed. All tests went ok - and few days ago the very same test/rule were not working.
Maybe there was something about cloud and updates as also mail messages from system had 10-30 min delays in that time window of few days.
We can close this. Thank you for attention.
Metod
Replies have been locked on this page!