Yes thank you.I replaced all EVENT_WORK:s with IR.SetInterval but project is still very slow.

Seems like there is still a slow performance problem in my clients iPad with i3 Pro.

I have same project on i2 Control and i3 Pro in same iPad.

i2 Control is running very smoothly and there is no problems at all. Except camera feeds are not working.

i3 Pro is not running smoothly. It is working very slowly and I know our customer will get very upset about that.

I also have i2 Control in that iPad but i do not want to delete it if i3 Pro wont work!

I reinstalled i3 Pro and after that everything seems to work OK again.

Is there any ideas what might cause this?!

I cannot go back to i2 Control because ip cameras won't work with new iOS!

And now i cannot use i3 Pro because projects are working very slow on iPad.

Hi Theo!

If you mean Session Initiation Protocol, then no I don't have that in my project.

I also tried to change renderer but that did not help.

Ok thanks Theo!

Maybe it's time to move to i3 anyway. :)

Yes we must have this property.

Now when trigger button is on for example on Static list, user has to try to find spot where is not any trigger buttons to get to the next page without changing the state of trigger button. And it's even worse when trigger button changes it's state but any command will be send to equipment.

Oh yes. Thank you. :)

Also I have this sonos module in multiple ipads and specific ipad connecting to specific sonos ip adress.

I have disabled Found device listener so it connects only to ip adress i have on SONOS_IP -script but i don't think that is the issue here?

// Found device listener

//IR.AddListener(IR.EVENT_DEVICE_FOUND, 0, FoundDevice);