Hauppauge IR Blaster won't work in SageTV Service Mode

[Retardical_Sam]

Hey everyone: I've got this wierd problem where my Hauppauge IR blaster won't work with Sage if Sage runs in service mode. It works fine in stand-alone mode, and with the Sage service running, the IR blaster stilll transmits signals to the cable box, it's just whenever Sage wants to change channels or anything, the IR blaster doesn't even send a signal (I can tell 'cause the LED doesn't light up). I have an official support call open on this one, and I just did a full re-install of all the drivers for my PVR-150, including the IR remote and blaster, and then re-installed Sage cleanly to 4.1.3. Any ideas?

[Newt182]

I am having the same exact problem. I have just loaded Sage 4.1.3.67 and have not been able to get my IR Blaster working eiter, i reload all the haupauge drivers and reloaded Sage. I just came across your post so I disabled the sage service and started Sage in stand alone mode, now the IR blaster works perfect. Let me know if you find an answer to this problem. If i Buy Sage I want to use the Server/Client, if this is going to be a problem i will look into an another software package instead.

[that_kid]

Hmm, what version of irblaster are you using. I'm using sage in service mode with the happauge irblaster and the only problem I have is sometimes the box doesn't respond to the digits in a timely fashion and I'll have missed channels.

[Nadim]

I have had the same problem since I switched to version 4.... in version 2.2 I had no problems what so ever. I posted here, but no one seems to have an answer. I am using a USB UIRT. In normal mode it works, but in service mode it doesn´t do anything. I hope some one can fix this.

[Swanson]

Does anyone have any updates on this? I am also experiencing this exact same issue.

[Nadim]

I sent this problem to sage technical support to see if they can help. Maybe it is something simple we are overlooking, but if someone could help it would really be apreciated.

[ben_95sl1]

hmm, that's interesting....I always have the front end running at the same time the service is running so I haven't had problems.

I will have to check to see if it happens with just the service.

[Nadim]

I also have the front running.

What happens is this.

If I run sagetv with service mode off, the server and the front end are the same process and you see the front end. Then the Ir blaster (usbuirt) works I can change channels and everything is dandy.

If I run service mode, then run sage, I get two processes. One for the server (or the service mode) and one for the front end. Still If I run the front end or not, It will not change channels either way so for me this mode is useless. What is strange, is that before version 4.0 it did work. So I don´t know what I am doing wrong, maybe it is just a permision or something dumb like that. But still it doesn´t work. It is driving me nuts.

This is the last bug I have to work out before I have a fully working setup.

I resolved that the best way to have a stable sagetv setup is to use the server just for server, and make clients independant. After having al sort of problems because a PVR350 tvout setup, it drove me crazy of all the random resets, green screens, purple screen, EOF etc. I stop using the PVR350 and all my problems ended. Trade up for a PVR500.

Right now I ordered 2 MVP Sage clients which are on their way and have another one here with me(still waitng for my client to MVP trade in license). Those work great. Stable Stable Stable. Did I mention it was stable? Anyway I´ve been with you guys since almost the begining and it almost becoming a "Set and Forget" experience. Keep up the good work

Ahhh and one more thing never give in to the DRM crap

[ben_95sl1]

maybe something got messed up during the upgrade? I went from 2.2.8 and basically started from scratch with the properties file.

[Nadim]

Well I thought the smae thing.

First I did an upgrade, and that this did didn´t work.

Then I did a clean install, and it didn´t work.

What is curious, is that I have a backup of 2.2.8 before the upgrade. If I restore that, it does work. Go Figure????? I go back to 4.0 and it doesn´t work.

Wierd

[Nadim]

Well folks.. I fixed my problem in the most particular way.

It turns out that I recently bought three media extenders, so I could get rid of my pvr350 as a playback and capture device.

I removed the pvr350 card leaving the pvr500 I also have installed, and guess what, Service mode works again. I would have never expected this to fix my problem, but it did.

Wierd bug.

But that is how I fixed my problem. Not sure if it will help you guys but that is how I fixed my server.

[Swanson]

Unfortunately I am running just a single PVR150 at this time, so that won't work for me.

Thanks for sharing your solution though!!

[Nadim]

Maybe removing the video sorce setup and returning it. That is one extra detail of what happened. When I removed the card the video source got messed up so I removed them and added them again.

Hope this works

[aoehlke]

I too am having this exact issue with a pvr150.

and it was fine prior to upgrade to 4.1.36... waiting on a solution from sage on this. may try one of the beta releases to see if they've looekd into it... i have another thread on this but after reading this one, I realized what my problem is.

I killed the service mode and now channel changing works

[Swanson]

After upgrading to the latest beta version 4.1.6, I tried using service mode again and still find that channel changing does not work. Once back to regular mode, it works like a charm.

Does anyone from the Sage team have any comments on this?

[monkeybounce]

Four years later and still no fix for this? I'm having the exact same problem right now.

[jgontarz]

Anyone??? We could really use some help here.....

[sic0048]

I was told by Sage support that SageTV needed to be installed AFTER the Hauppauge IR software was installed and set up. So the had me uninstall SageTV and then reinstall it since the Hauppauge software had been installed after my SageTV setup. Uninstalling Sage doesn't effect the wiz.bin file or other important files, so you won't loose anything. But it did make it work.

[jgontarz]

Outstanding! Thank you.

[sic0048]

Originally Posted by jgontarz

Outstanding! Thank you.

So does that mean it worked for you, or you are just excited to have something to try?