The main feature we needed out of iRidium Server was scheduling and we have not got it in a usable format. This is very disappointing.

Having to use complex JS programming (yes it is complex for most installers) will mean we do not get the take up of iRidium server that we were expecting

I already have a scheduling script (that is much easier to setup than the iRidium Server version in the scenes and macros example). We just run this in one project on a PC on the network that is only used for scheduling and iRidium Gate (ie what iRidium server was going to replace)

All the installer needs to do in my script (and I have done this for them):

delay: driver name: command: hex or text:

"0; Clipsal Gate; ON //JONES/254/56/1; false";

And with the use project tokens in the GUI Editor for if the schedule is enabled, the day of week(not shown), and time and we can much more easily do scheduling:

iRidium server is not solving the scheduling problem - it is making it worse as it is far too complicated.

What we need is a GUI interface to setup scheduling without the need for any JavaScript. 90% of installers are not programmers and this is one of the big preventers of installers using iRidium.

Please re-visit this with urgency as I cannot promote scheduling in the current format as the solution.

In this instance, iRidium server is just replacing a PC. Not a convincing selling point given the increase in complexity for installers :(

Hi,

i think it's good to have an auto-updating feature in iRidium Studio / Server / Windows i3 Pro.

This is absolutely a 'must' when 3.0 will be released; we can not ask installers to manually update all software!!

Please implement auto-updating in the next beta-build, so we can test this functionallity before it will be released.

Thanks

Theo

The logger is a great thing to have. But if you could implement highlighting of messages in it, it would be perfect:

- errors and warnings - RED

- user messages - BLUE

- service messages - BLACK

Can we please look at reducing the time it takes to

1. save and run the emulator (by the way this should not say 'save' as it is not saving)

2. save and send to transfer

3. save the project

Why does it needs to save before running the emulator or sending to transfer?

On a reasonable sized project this can take 30-40 seconds. This is way too long. I use other professional programming IDE's and they do not take this long for similar sized (MB) project

This is a major frustration

Let's vote if we want Homekit support in i3 pro and iridium server or not. It would give us Siri and many new devices compatibility.