TellStick Duo

[Mastiff]

Doesn't surprise me. Of course that means that we will have to take both the relays! Oh, and I must say it was rather novel to see two ladies from the US on second and third! I don't think anybody saw that one coming!

[Mastiff]

I saw a potential problem yesterday: Because of a problem in the batchfile starting OpenNetHome, EG couldn't connect to it. That was interpreted the same way as if it had been connected and then lost it. So the VM went into a "boot loop", meaning that it rebooted about 20 times before I found out what the problem was! Would it be possible to make the plug-in not send the event "OpenNetHome.Connection with NetHomeServer TCP interface failed" if it doesn't connect on startup of EG, but another event? Then I could tie that one to a mail action and not have the VM rebooting until I was aware of what was happening.

[Mastiff]

Another thing: I have a bunch of "lost contact" with my temp sensors, many more than from the RFXtrx. Is the logic different between them? Is that an event coming from the NetHomeServer or from the plugin, when it detects x minutes without contact?

[krambriw]

Oh, I see, yes that is not good of course. Do you want a one-time event if it happens or do you want it to be repeated in a loop?

[Mastiff]

I think a one time event would be enough, so I can hook that up to a mail action and get a warning, thanks. If not there could be a rather full inbox in the morning if it happens just after I turned off the phone and went to bed!

[Mastiff]

Morning, W-man! Here's what it can look like in the logg with the sensors:

Code: Select all

09:27:05   Tellstick.FineOffset|1185 'Temp|6.6'
09:27:05   OpenNetHome.'Lost contact with sensor: FineOffset|1159'
09:27:06   RFXtrx.Type: THC238/268,THN132,THWR288,THRN122,THN122,AW129/131 id: 50689 ' temperature: +20.0 deg C signal: 5 battery: 9'
09:27:06   OpenNetHome.'Lost contact with sensor: FineOffset|1037'
09:27:07   OpenNetHome.'Lost contact with sensor: FineOffset|1170'
09:27:13   RFXtrx.Type: Viking 02811 id: 16640 ' temperature: +2.2 deg C signal: 7 battery: 9'

I would like a much longer period before those surfaces. Maybe an hour? I'm guessing it's 10 minutes now. Wasn't that what you were using on the RFX plugin?

[krambriw]

I would like a much longer period before those surfaces

Pls explain. You do not want to know that your sensor has been lost already since ten minutes?

[Mastiff]

Yeah, one hour is more than enough. They seem to lose contact a lot for some reason, and I really don't need to kow about sensors on such a short notice. The thing is that it's "loosing contact" with sensors that has never been a part of that setup, sensors that I do with the RFXtrx.

[krambriw]

The thing is that it's "loosing contact" with sensors that has never been a part of that setup, sensors that I do with the RFXtrx.

Yes, but that is expected, right? Sensors are just broadcasting and everybody listening...have you tried to set the protocols in NetHome? I mean if you are only picking up FineOffset with the RFXtrx, you can deselect it in the settings for the TellStickDuo in NetHome and only select Oregon (and UPM if used) . But maybe you have a very mixed population so this is not possible.

I'm guessing it's 10 minutes now. Wasn't that what you were using on the RFX plugin?

Yes, it is currently hard coded as 600 sec. I can look into having this as a setting in the action

[Mastiff]

I have a mix of Oregon and Vikings, so I need to get them all from there. Btw is it possible to set a plugin to only show attached events? So that I only see the events that I have a macro for? That would do the trick as well.

[krambriw]

You can try this one, I think it is handling connections to NetHomeServer (NHS) ok

- Separating connection problems at start up from those happening when connection is established
If you start EG and connection to NHS fails, you wil get a special event with content 'Failed to connect to NetHomeServer at startup'. Once NHS is up, you should get connected automatically


- Time out for lost sensors now configurable (100-7200 seconds)
Most likely, when you restart EG after you replaced the plugin file, you will receive an error message, try then to open configuration for your logger action and set the time out for lost sensors. Eventually save EG and restart again. If it doesn't help, you have to delete the current logger action, save, restart EG and recreate it

__init__.py

(69.64 KiB) Downloaded 106 times

[Mastiff]

Thanks! I had to kill the old action and create a new one, no problem. Set it to 60000 delay for lost contact, so one hour. The non connect on starup warning worked nicely, and when I started NetHomeServer it did connect. But now I'm getting this on startup:

Code: Select all

12:41:19   Error compiling script.
12:41:20   Traceback (most recent call last) (1691):
12:41:20     File "C:\Program Files (x86)\EventGhost\eg\Classes\ActionItem.py", line 121, in SetArguments
12:41:20       self.compiled = self.executable.Compile(*args)
12:41:20     File "C:\Program Files (x86)\EventGhost\plugins\EventGhost\PythonScript.py", line 71, in __init__
12:41:20       self.PrintTraceback()
12:41:20     File "C:\Program Files (x86)\EventGhost\plugins\EventGhost\PythonScript.py", line 97, in PrintTraceback
12:41:20       treeItem.PrintError("Traceback (most recent call last):")
12:41:20   AttributeError: 'NoneType' object has no attribute 'PrintError'

Can that be something in the new version of the plug-in? That's the only thing I have changed.

[Mastiff]

Never mind. It may have been the script with the Yamaha, I forgot that I had changed that too... I corrected that with the : at the end, and now I don't get that error. Sorry.

[Mastiff]

And while I am in spamming mode: Is it possible to choose to get only the attached events in the logger? It would be nice, since my logger is pretty flooded. Every time the RFX sends a command, the Tellstick makes NetHomeServer logs this as a button press from a Nexa button. So everything is doubled.

[krambriw]

Is it possible to choose to get only the attached events in the logger?

Isn't that what the little checkbox down in the left corner is supposed to give?

Skärmklipp.PNG (2.42 KiB) Viewed 4831 times

Set it to 60000 delay for lost contact, so one hour

1 hour is.........3600 seconds, right!?