Discovery Update

Support & Troubleshooting
1

Swapped routers, different IP for devices, changed 0 to 1 to keep things separate.

Have 2 tablos, no issues connecting with one the second, fusses about internet connection. No flashing light, responds to pings. Using the discovery URL mentioned in the old days

 https://api.tablotv.com/assocserver/getipinfo/

{
    "cpes": [
        {
            "http": 21080,
            "public_ip": "XXX.XXX.XXX.XXX",
            "ssl": 0,
            "host": "giv",
            "private_ip": "192.168.1.100",
            "slip": 21087,
            "serverid": "SID_XXXXXXXXXXXX",
            "inserted": "2020-12-12 13:50:27.349319+00:00",
            "server_version": "2.2.30rc2017417",
            "name": "tablo0",
            "modified": "2020-12-31 17:25:30.857170+00:00",
            "roku": 0,
            "board": "giv",
            "last_seen": "2020-12-31 17:25:30.838873+00:00"
        },
        {
            "http": 21900,
            "public_ip": "XXX.XXX.XXX.XXX",
            "ssl": 0,
            "host": "gii",
            "private_ip": "192.168.0.21",
            "slip": 21901,
            "serverid": "SID_XXXXXXXXXXXX",
            "inserted": "2019-10-24 22:52:32.579047+00:00",
            "server_version": "2.2.30rc2017417",
            "name": "tablo2",
            "modified": "2020-12-31 14:24:58.002975+00:00",
            "roku": 0,
            "board": "gii",
            "last_seen": "2020-12-31 14:24:57.980200+00:00"
        }
    ],
    "success": true
}

One tablo has 192.168.1.X while the second still shows 0 – what’s up with that? I know, I can go and reboot it and likely it’ll update it’s self. Thing is, I didn’t reboot the first one, so again, why won’t it update it’s self since it lost it’s network connection?

Since a it’s unclear weather a recording is in process, to just randomly reboot my tablo isn’t always the best. If one device knows, both running the exact firmware, why?

Note, with 3rd party app where I enter an IP, I can access just like it has the network connection it has, just tablo server doesn’t have the updated information.

One will / One won’t …seems screwy. One of those “it’s a bug” and should be easy to fix, since the fist one did it. :poop:

Instead of rebooting, and risk a recording, I’m going to wait it out, see if it figures it out… or would someone have to wait until it updates / maintenance mode.

2

DHCP servers have a lease time for any IP address they assign. Typically 24 hours, but you can change it on the DHCP server. Once that time expires the client will request a new lease. So either wait for the time to expire or reboot theTablo.

3

Do devices usually detect that they are unplugged when they issue an I/O or the cable into the unit is disconnected. If you unplugged the cable into the router for hours and the blade server just sits there fat, dumb, abd happy - as long as it isn’t trying to access various virtual circuits. You have to have an open virtual circuit and turn on heartbeat before the client gets a clue.

Doesn’t the DHCP standard indicate that the client (tablo unit) default IP lease renewal doesn’t occur until 50% of the remaining lease time has occurred. Unless the actual DHCP server issues a IP release/renewal message.

So it sounds like your router has a bug if one unit got a renewal request and the other didn’t.

4

The tablo has accepted the new IP. It responds to pings to the IP. Third party apps can access it because I can enter the local IP.

The web app gets the IP from api.tablotv.com one of the tablos knows it has a new IP and updated, the other one hasn’t… so it’s not accessible via the web app.

yup, but why, why can one tablo have the sense to update api.tablotv.com and the other never gets around to it?

It got the new IP! As first posted -

It shows in the client table as having a current IP… just won’t come from api.tablotv.com like the first one does as being changed… maybe that’s the bug you’ve mentioned?

I know the tablo’s blue light flashes. My PC says it’s disconnected… that’s as much as I can tell ya.

…but nothing else had to be wait, just loose it’s network and find it again. Lots of wireless IoT, couple mobile devices, stoopid Amazon things. One tablo figured it out, PCs and printers… just one lone tablo

DHCP request:

Dec 31 09:38:03 rt-c404155ba7da.lan dnsmasq-dhcp[1560]: DHCPREQUEST(br0) 192.168.1.21 50:87:b8:XX.XX.XX
Dec 31 09:38:03 rt-c404155ba7da.lan dnsmasq-dhcp[1560]: DHCPACK(br0) 192.168.1.21 50:87:b8:XX.XX.XX tablo2
Dec 31 09:38:03 rt-c404155ba7da.lan dnsmasq-dhcp[1560]: DHCPREQUEST(br0) 192.168.1.21 50:87:b8:XX.XX.XX 
Dec 31 09:38:03 rt-c404155ba7da.lan dnsmasq-dhcp[1560]: DHCPACK(br0) 192.168.1.21 50:87:b8:XX.XX.XX tablo2

Is that what you’re ask’n about?
I’m still say’n one tablo sent it’s new IP to api.tablotv.com while the other - which got a new IP - never sent it to api.tablotv.com for discover via the web app.

5

Overnight, presumably during maintenance mode and/or guide update, the second tablo updated it’s information with the tablotv server. So no the discovery data sent is accurate, and I can access it via the web app again.

Kind of unusual same firmware on both devices, with different results.

6