We can only guess what is wrong. You need to provide screenshots of your setup for us to help.Right now based off what you have told us there is a 50/50 chance a moose has sat on your other till causing the issue… but I cant be certain…
I made this on my test computer first and it works perfectly (thank you very much for that!!) but when I put it together on my live system the states and reports on my time clock entity screen don’t update unless I leave the screen and go back. I copied and pasted almost everything from the test to the live computers so I can’t see it being a typo but I checked all my automation to be sure and it looks good. Any ideas what may cause this??
Maybe double check the refresh rate/auto update option on entity screen?
Also double check message server settings etc as these are involved in triggering refreshes.
Tried changing the port number for my message server but no change. My kitchen display works fine and updates instantly which makes me think it must be a setting somewhere I’ve missed but I can’t find anything different in setups!! Auto refresh is checked and interval is set to 0 (same as test computer). Only difference between my test computer and my live system is that the test is running on sql 2014 and live is on sql 2012, possible this could be the issue??
Remove Action TC_Login EntityState from the Rule and Save the Rule.
Find the Action TC_Login EntityState in Automation > Actions and change the parameter that contains [:EntityId] so that it uses [:entId] instead, and Save the Action
Open the Rule and add the Action back in to the Rule.