EventGhost

Great, thank you very much! No questions, this one seems to be so easy that even I can understand it!

Quick question: Would it be possible to change the info box "Connection with NetHomeServer TCP interface established" to an event? It would make it easier to reset the warning system for lost contact. And if there's a similar box for establishing contact with the Tellstick on the NHS it would be very nice to have that as an event as well.

Would it be possible to change the info box "Connection with NetHomeServer TCP interface established" to an event? It would make it easier to reset the warning system for lost contact.

I think so, I'll look into this

And if there's a similar box for establishing contact with the Tellstick on the NHS it would be very nice to have that as an event as well.

Well, this is currently not possible since this is not monitored internally by OpenNetHomeServer itself. But I agree, it would be good, see also here
http://forum.opennethome.org/viewtopic.php?f=5&t=35

Would it be possible to change the info box "Connection with NetHomeServer TCP interface established" to an event?

Done. New version uploaded

Thank you very much!

Edit: I'm unable to get to krambriw.net. Maybe your server is down?

The windows box running apache had pending updates...now restarted and fixed it seems

Yessir, Geronimo is back! Thanks!

Btw I suddenly discovered that I'm finally getting the wind in through the NHS interface! I moved the sensor yesterday, I'm guessing that's what changed. But it's wrongly formatted (the interface thinks it's a temperature with humidity), so perhaps you could have a look at it? This is what I get there:
And this is the same through the RFTtrx:

Well, I'm not supporting Oregon wind sensors via OpenNetHomeServer

That is very naughty of you! So does that mean "at the moment" or "I won't support it"?

It is possible but I would need some sample original message structures from OpenNetHomeServer to be able to build the decoding. If you provide them, I can look into it.

(open a telnet session,
type 'o ip of Nethome 8005'
type 'subscribe'
wait for messages
copy & paste wind messages
)

But isn't it good enough as it is provided by the RFXtrx?

I will try to get the sample, thanks! The thing is that the only place where the wind is really correct is the furthest from the RFX, and the Tellstick is much closer, so it picks it up every time.

Wacky summer... I took down the wind sensor to move it, but then my ladder on the cabin broke with me on it (luckily not high up...), so I couldn'put it up where I want it to be without a ladder. Not easy to find one here at the cabin, I'm going to get a new one. But now my parents are taking over the cabin for two weeks. Anyway, I have another problem that I disccovered today when I was checking the "parent proofing" of the system. (They're in ther 70's, very much alive and kicing, and very much hopeless when it comes to anything beyond Facebook and reading news on the pc!) I found out that when I start up EG with the ONH plug-in and then kill the Tellstick, I don't get the message "OpenNetHome.TellstickDuo is Not connected". So automatic restart doesn't work. Do you have any idea what that can be? I have botn timeouts to 180 seconds. It only works if the Tellsticks' off when I start EG.

then my ladder on the cabin broke with me on it

Ooops, no good, be careful, happy you did not hurt yourself badly

I'll refresh my memory a bit on the TellStickDuo monitoring...briefly I remember something that OpenNetHome does not report when it loses the connection with the device...I will anyway check how the code handles this

I have looked into the code and I cannot find anywhere that I ever generate the message "OpenNetHome.TellstickDuo is Not connected".

The scenario that you kill the stick during run time is currently not reported by OpenNetHome. So basically, you will not see if the stick is lost. Only thing you will notice is if you have received any sensor event from the stick before you lost it, then that lost sensor will be reported

This is how I believe it works...