ok stbemu

[Dynas]

What is the latest (ok2 stb emu) Can the okstb be updated right on the Buzz xpl3000?

[nobodyspecial]

https://www.satfix.to/showthread.php?211250-stb-emulator-pro-1-2-1-0

[Emporium]

What is the latest (ok2 stb emu) Can the okstb be updated right on the Buzz xpl3000?

Just curious... Why would you waste a buzz xpl3000 by installing stbemu ? Kind of defeats the purpose.
The xpl3000 can do it better than stbemu and a lot nicer interface. And with 10 server slots available on an xpl3000, you can have as many services as you need/want.

The only downside I can see at the moment is with ok3 (don't know about ok2) and an xpl3000, is you can't use same sub on another device using stbemu. I just tested it again recently on a new ok3 sub. If you use stbemu only with ok3, you can use it on any device as long as it is only one being used at a time (obviously). Use it once on an xpl3000, and you can't use it again on stbemu (without resetting account). The server seems to marry to something of on an xpl3000 (I suspect it is s token exchange witch ministra supports and the buzz gladly handshakes), but I could be wrong. I've tried using same serial, device ids, etc.., but that makes no difference.

But so far, no matter how many other services I've tried, I always keep going back to ok3.

[dishuser]

Just curious... Why would you waste a buzz xpl3000 by installing stbemu ? Kind of defeats the purpose.
The xpl3000 can do it better than stbemu and a lot nicer interface. And with 10 server slots available on an xpl3000, you can have as many services as you need/want.

The only downside I can see at the moment is with ok3 (don't know about ok2) and an xpl3000, is you can't use same sub on another device using stbemu. I just tested it again recently on a new ok3 sub. If you use stbemu only with ok3, you can use it on any device as long as it is only one being used at a time (obviously). Use it once on an xpl3000, and you can't use it again on stbemu (without resetting account). The server seems to marry to something of on an xpl3000 (I suspect it is s token exchange witch ministra supports and the buzz gladly handshakes), but I could be wrong. I've tried using same serial, device ids, etc.., but that makes no difference.

But so far, no matter how many other services I've tried, I always keep going back to ok3.

my 3000 and 3900 share mac on ok3 and both work

[Emporium]

my 3000 and 3900 share mac on ok3 and both work

Thanks for sharing.. So that means that the token theory is out of the question. I don't have another buzz box, so I couldn't check that variation.

Have you tried using an android box with STBEmu and configured with same MAC ? just curious.

With a new recent sub, I tried the exact same as before. Tried it on 3 different android boxes first using stbemu (1.2.2.0) and it worked flawlessly. I configured it on a buzz box and it worked.. But then going back to any of the 3 android STBEmu boxes, I would get the "Call your provider to register this device" message.

I do the same with other providers, and don't have this issue. Only with OK3. And this only happened after the xc incidents (sometime after, so can't confirm which event exactly caused it - since a lot of things changed since then).

I hope one day we figure out what it locks onto so it can be fixed (if it is not intentional). But this does not mean I wont use ok3. It is the most stable one I have right now, and one of the best for montreal locals. I don't have to "settle" for toronto locals or others.

[7leaves]

my 3000 and 3900 share mac on ok3 and both work

at the same time, or one at a time?

[herk]

at the same time, or one at a time?

of course not at the same time

[dishuser]

Thanks for sharing.. So that means that the token theory is out of the question. I don't have another buzz box, so I couldn't check that variation.

Have you tried using an android box with STBEmu and configured with same MAC ? just curious.

With a new recent sub, I tried the exact same as before. Tried it on 3 different android boxes first using stbemu (1.2.2.0) and it worked flawlessly. I configured it on a buzz box and it worked.. But then going back to any of the 3 android STBEmu boxes, I would get the "Call your provider to register this device" message.

I do the same with other providers, and don't have this issue. Only with OK3. And this only happened after the xc incidents (sometime after, so can't confirm which event exactly caused it - since a lot of things changed since then).

I hope one day we figure out what it locks onto so it can be fixed (if it is not intentional). But this does not mean I wont use ok3. It is the most stable one I have right now, and one of the best for montreal locals. I don't have to "settle" for toronto locals or others.
last time I tried another box with same mac was my global(same layout as stbemu) and it worked
seeing as the essentials rules changed again and I have tomorrow off I will try my zoomtak with stbemu pro
all I have to do is find power supply cause it already has same mac addy...lol

[Maestro701]

Thanks for sharing.. So that means that the token theory is out of the question. I don't have another buzz box, so I couldn't check that variation.

Have you tried using an android box with STBEmu and configured with same MAC ? just curious.

With a new recent sub, I tried the exact same as before. Tried it on 3 different android boxes first using stbemu (1.2.2.0) and it worked flawlessly. I configured it on a buzz box and it worked.. But then going back to any of the 3 android STBEmu boxes, I would get the "Call your provider to register this device" message.

I do the same with other providers, and don't have this issue. Only with OK3. And this only happened after the xc incidents (sometime after, so can't confirm which event exactly caused it - since a lot of things changed since then).

I hope one day we figure out what it locks onto so it can be fixed (if it is not intentional). But this does not mean I wont use ok3. It is the most stable one I have right now, and one of the best for montreal locals. I don't have to "settle" for toronto locals or others.

Delete whatever serial number is in STB EMU and you would be able to use sub on both buzz and STB EMU. As you already know, not at the same time lol

[Emporium]

Delete whatever serial number is in STB EMU and you would be able to use sub on both buzz and STB EMU. As you already know, not at the same time lol

It should be as simple as that.. And it used to be.
But even with a new account which was just started 3 weeks ago, same issues.

I initially started without setting it up on my buzz (xpl3000). Tried it on a few android and androidTv boxes using stbemu (latest 1.2.2.0). Worked like a charm on all devices. And on all devices, I made sure that there was no serial number (blanked out the default one provided), and ensured that deviceID was disabled.
Then I decided to connect my xpl3000, and configured it, with same MAC, and it worked fine.

Then trying to go back to any stbemu, got the following screen on all of them "please contact your provider to register this device" .
28367

I even just tried, a few minutes ago, doing the same on my galaxy tablet. Installed clean new stbemu pro. Delete default profile, create new profile, edit the MAC, remove the serial number, add the portal (no 8000 with /c/ at end. tried with and without final /, no difference - not that I expected any, but just trying everything obvious or not), and low an behold, same exact result. Even tried checking the tick box for enable/disable ministra support.

This should not be rocket science. It worked perfectly before the whole xc stuff started. Had it set up @ 3 different households (3 different subs obviously) and it worked for all of us. Now it doesn't on any of us.

However, doing the exact same thing with 3 different services, works fine. But I don't want the others as my main services :)

The xpl3000 is doing something to the account on the server that it doesn't seem to like the stbemu device after it connects even once.

I'm really out of ideas.. Only option I can see is to just stick with STBEmu, which means my xpl3000 would become just "another" android box :taz:

[Maestro701]

It has to be something in STB EMU because I used to work that and my 3000..Maybe it's the version of EMU because I have encountered that problem once before.

[Emporium]

It has to be something in STB EMU because I used to work that and my 3000..Maybe it's the version of EMU because I have encountered that problem once before.

It's the latest version 1.2.2.0 I have installed. And it is strange that it works fine all the way up to when I connect my xpl 3000 for the first time. Then stbemu stops working. I even got a new account 3 weeks ago to run the tests, and it did exactly the same and reproduced it again.

Previously when I had tested I had gone back a few versions of stbemu, just in case, and it didn't help. I think I had gone all the way back to 0.7 or something like that (then tried 1.0.5, 1.1.14, and a few after that).

Like I said, this used to work perfectly for me and a few buddies also, up until sometime after the xc incidents late last year. I don't recall which of the various changes to the system caused it (since I don't use my secondary boxes too often), but last summer I know for a fact it worked.

I know I'm not the only one, since I know at least 1 re-seller that lost a few customers (who had xpl3000) because of this. I'm just trying to figure out why it does this with ok3 (and xpl3000), but not with other services.

I still suspect that the xpl3000 does something, but I don't know what. Surely the logs on the system showing why an access was refused [what didn't match in the authentication - other than MAC], would help.

[crowbay]

If I recall, Herk said it was due to a token issue...

I had same issue with branded ok3 stb app, if all devices use stb emu pro then no issue.
Something on the backend must have saved a SN or ID of the hardware when connecting through regular MAG/branded app and not STB EMU.

[Imsomebody]

This issue is not new, the server locks to the buzz id. You need a reset by your seller to switch back and forth (stb to buzz) each time. Some other servers do the same thing, you can see it in the panel editor. Buzz shows model 256 and stb emu shows model 250. I do not presently have a buzz to test, try changing the model to 256 on stb emu at top of the mac addy page.

[dishuser]

This issue is not new, the server locks to the buzz id. You need a reset by your seller to switch back and forth (stb to buzz) each time. Some other servers do the same thing, you can see it in the panel editor. Buzz shows model 256 and stb emu shows model 250. I do not presently have a buzz to test, try changing the model to 256 on stb emu at top of the mac addy page.
if it locks to the buzz id then all buzz boxes must have same id

[Imsomebody]

I dont think they do, I will check

[Imsomebody]

Different serials of course, which can be cloned. The only difference between stb and buzz is the 256 buzz 250 stb. And the versions of software stb shows 2.18 version r14 pub 250. Buzz shows version 2.20.03-256 on the two I checked only serials different from buzz to buzz.

[Emporium]

Different serials of course, which can be cloned. The only difference between stb and buzz is the 256 buzz 250 stb. And the versions of software stb shows 2.18 version r14 pub 250. Buzz shows version 2.20.03-256 on the two I checked only serials different from buzz to buzz.

Does the buzz actually send the serial ?
If so, is the serial the same as the one shown in the Android "about" screen ?
I don't see a serial anywhere in the buzztv app.

Serials can be cloned. DeviceIDs can be cloned, and the stb model can be cloned in STBEmu.
One you run a buzz on an account, which one of these variables needs to be set up on stbemu to allow it to work. Even if it means I'd have to ask reseller to give me some info from my box which I may not be able to see.

Funny that you can use stbemu on any device. I even changed the STB model from 250 to 254 to 256 on different machines and it does not lock me out, regardless of which I use.
Only when connecting with a buzz (even a single time), does it lock me out of any stbemu after that.
Yes, a MAC reset on the panel re-establishes connection from stbemu, but that is not very convenient. Resellers would be overwhelmed with requests.

[dishuser]

Different serials of course, which can be cloned. The only difference between stb and buzz is the 256 buzz 250 stb. And the versions of software stb shows 2.18 version r14 pub 250. Buzz shows version 2.20.03-256 on the two I checked only serials different from buzz to buzz.

well I use same mac on my 3000 and 3900 and have no issues with ok3

[Emporium]

well I use same mac on my 3000 and 3900 and have no issues with ok3

Do you have a generic Android box/phone (or even on one of the buzz) install stbemu ? Just to try it...
You can get the latest version (https://www.satfix.to/showthread.php?211250-stb-emulator-pro-1-2-1-0&p=1301459#post1301459) from here if you need.

And I don't think it is an token issue (as mentioned at one point), since on one of my buddies 3000, we did a factory reset, and when it came back up, it still worked like before (his stbemu boxes still didn't obviously), but the buzz worked. So if it was a token, it would have been wiped with the factory reset, and would have required a MAC reset on panel to force it to re-issue a new token.


Thnx

[dishuser]

Do you have a generic Android box/phone (or even on one of the buzz) install stbemu ? Just to try it...
You can get the latest version (https://www.satfix.to/showthread.php?211250-stb-emulator-pro-1-2-1-0&p=1301459#post1301459) from here if you need.

And I don't think it is an token issue (as mentioned at one point), since on one of my buddies 3000, we did a factory reset, and when it came back up, it still worked like before (his stbemu boxes still didn't obviously), but the buzz worked. So if it was a token, it would have been wiped with the factory reset, and would have required a MAC reset on panel to force it to re-issue a new token.


Thnx

I have my zoomtak with stbemu that previously worked with same mac addy
but with going to work more now I haven't had time to look for power supply