Jon00 Remote Computer Control & Network Monitor (HS2, HS3 & HS4)

[JimBob]

Just simply turning the charger on/off from HS.

It's a tablet that I want to mount on a wall, so looking at options for power. I don't want to leave the charger plugged in and on all the time, but would rather turn it on when necessary.

[jon00]

Let me have a think.....

[JazzmanJohn]

Turn Remote Monitor ON fails - Windows 8.1 Client

This is an excellent piece of software. Thanks Jon!

I primarily want to be able to turn my monitors on and off via HS3 events. I have several PC's, both Windows 7 and Windows 8.1. Using RCCNM I can turn all of the monitors off. And I can turn ON the Windows 7 monitors. But, it seems there may be something different with Windows 8.1. These monitors do not respond to the Mon On command.

Any advice? Has anyone else figured out how to do this?

Thanks,

JazzmanJohn

[jon00]

Yes, send a keystroke such as escape.

[JazzmanJohn]

Solved!

Thanks Jon. Very speedy reply.

It turns out, with Windows 8.1, sending the SSaverOff command does the job of turning on the monitors. This is nice because I can simply use the preset in the event structure you have provided. Quick and easy!

This now allows me to ensure all monitors are off in the evening, and then back on again first thing in the morning.

Terrific.

Thanks a bunch.

JazzmanJohn

[jon00]

Hi Jon,

I would like to monitor the battery level of a remote Jon00RCCNM client (and control the charging of it when it drops to a certain level).

Is there anyway to do this currently with this package? Is this a feature that could be added?

Cheers,
John

Just simply turning the charger on/off from HS.

It's a tablet that I want to mount on a wall, so looking at options for power. I don't want to leave the charger plugged in and on all the time, but would rather turn it on when necessary.

I would prefer to do this with a small client. I've written something which gives the following info to HS3....

[JimBob]

That's exactly the kind of thing I'm after - looks good!

[S-F]

The network intrusion feature kills my voip box. I had the script set to run once a minute and within at most a few minutes after powering the device on it drops from the network. I replaced the device and every associated cable. The only things I didn't try to replace were my switch and router. As soon as I stopped running the network intrusion script both devices run fine. Any idea why this is happening? I Really like the feature, but I like having a phone more.

[jon00]

Do you monitor the voip box with the normal network monitoring capability?

[S-F]

Nope. Until I started using the network intrusion script I only monitored a few devices. Once using that feature I had to tell the NM that the voip box was trustworthy.

[jon00]

I suggest you add an exclusion IP entry for your VOIP box (and any other device you have on the network not monitored). Check the docs.

[S-F]

Yes that seems to have done it. Thanks.

Just out of curiosity though, how could this have happened? Does the script do anything more than send a ping? Does it scan ports or make any blocking attempts? I have a dialog running on the forum for the manufacturer of the device and they are saying that a ping alone shouldn't do this.

[jon00]

It's just a ping but I do send multiple pings out at the same time (to different IP addresses) rather than sequentially.

[jon00]

That's exactly the kind of thing I'm after - looks good!

Would you send me an email and I'll send you a link for something to try.

[Mario23]

I'm sure I'm missing something silly but maybe someone can help me.
My client doesn't seem to connect and the control buttons aren't working.
Here are some screenshots. It should be noted that the client settings are default with client #1 and port 8001.