It's no big deal about the %, I just changed the password to all digits.
It is weird though that when I use VLC media player the RTSP string works fine and it gives me the video I was looking for.
I like your app for my tablets now once I can get the video tiles working it will be awesome.
Actually, it looks like that "%" isn't a valid character in a URL.. FWIW here's the method (javadocs) I'm calling to check if a URL is valid before letting you add it
Summary
/**
* Constructs a URI by parsing the given string.
*
* <p> This constructor parses the given string exactly as specified by the
* grammar in <a
* href="http://www.ietf.org/rfc/rfc2396.txt">RFC 2396</a>,
* Appendix A, <b><i>except for the following deviations:</i></b> </p>
*
* <ul>
*
* <li><p> An empty authority component is permitted as long as it is
* followed by a non-empty path, a query component, or a fragment
* component. This allows the parsing of URIs such as
* {@code "file:///foo/bar"}, which seems to be the intent of
* RFC 2396 although the grammar does not permit it. If the
* authority component is empty then the user-information, host, and port
* components are undefined. </p></li>
*
* <li><p> Empty relative paths are permitted; this seems to be the
* intent of RFC 2396 although the grammar does not permit it. The
* primary consequence of this deviation is that a standalone fragment
* such as {@code "#foo"} parses as a relative URI with an empty path
* and the given fragment, and can be usefully <a
* href="#resolve-frag">resolved</a> against a base URI.
*
* <li><p> IPv4 addresses in host components are parsed rigorously, as
* specified by <a
* href="http://www.ietf.org/rfc/rfc2732.txt">RFC 2732</a>: Each
* element of a dotted-quad address must contain no more than three
* decimal digits. Each element is further constrained to have a value
* no greater than 255. </p></li>
*
* <li> <p> Hostnames in host components that comprise only a single
* domain label are permitted to start with an <i>alphanum</i>
* character. This seems to be the intent of <a
* href="http://www.ietf.org/rfc/rfc2396.txt">RFC 2396</a>
* section 3.2.2 although the grammar does not permit it. The
* consequence of this deviation is that the authority component of a
* hierarchical URI such as {@code s://123}, will parse as a server-based
* authority. </p></li>
*
* <li><p> IPv6 addresses are permitted for the host component. An IPv6
* address must be enclosed in square brackets ({@code '['} and
* {@code ']'}) as specified by <a
* href="http://www.ietf.org/rfc/rfc2732.txt">RFC 2732</a>. The
* IPv6 address itself must parse according to <a
* href="http://www.ietf.org/rfc/rfc2373.txt">RFC 2373</a>. IPv6
* addresses are further constrained to describe no more than sixteen
* bytes of address information, a constraint implicit in RFC 2373
* but not expressible in the grammar. </p></li>
*
* <li><p> Characters in the <i>other</i> category are permitted wherever
* RFC 2396 permits <i>escaped</i> octets, that is, in the
* user-information, path, query, and fragment components, as well as in
* the authority component if the authority is registry-based. This
* allows URIs to contain Unicode characters beyond those in the US-ASCII
* character set. </p></li>
*
* </ul>
*
* @param str The string to be parsed into a URI
*
* @throws NullPointerException
* If {@code str} is {@code null}
*
* @throws URISyntaxException
* If the given string violates RFC 2396, as augmented
* by the above deviations
*/
Version 1.0.1770 installed without issues and has been running fine on the Relay, thanks for the efficiency and compatibility enhancements!
1 Like
@jpage4500 the flickering seems to be gone from my screen now, well done. I am noticing a different problem now. When trying to enter the rtsp feed on a video tile something in the dashboard is refreshing and closes the tile before I can finish typing in the info.
@jpage4500 my crashes have ceased so far. The motion sensor activation is still not waking the tablet from screensaver though.
I ordered a refurbished Fire HD 10" for $35 from woot and I'll do some testing when it arrives. It'll be hard to resist rooting it and replacing the OS so I can have it fully sleep and wake though 
I'm not sure how this relates to my Samsung Tab4 but what do I know? 
Starting to look at this one and I don't see how to change colorMode from RGB to CT. I'm using a Generic ZigBee RGBW Light device type..
I can change the light color and I can also change the CT on the device - but in both cases I'm not able to tell which one the light is using as the colorMode is always RGB.. maybe I'm missing something
colorMode : RGB
colorName : Green
colorTemperature : 2702
hue : 34
level : 100
saturation : 100
Anyway, I'm assuming the colorMode should change to "CT" when I set the color temp..
update: I asked the question here to try and get some help w/this
lol.. thought you had a Fire Tablet
The motion sensor activation is still not waking the tablet from screensaver though.
I verified wake on motion works on my phone but I can't test on my current Fire Tablet because the OS I'm using (Lineage) doesn't support the camera so I can't test.
Yes, I believe that's how it should work. Here's the attribute changing when I change the color temperature or color. You might have more luck using the "Advanced Zigbee RGBW bulb" (press configure after changing, wait for it to do it's thing and end on blue at 20%) driver and your specific color bulb.
cool - that worked! I actually did find that driver and changed to it but I hadn't hit configure.. that was the key.
version 1.0.1779 (beta)
- don't show color circle when light is in CT mode
- several bug fixes
This is a small update - mostly to get a few bug fixes in and to test out some changes in my automated build script.
done!
2 Likes
I think the motion detector being referred to in this case is an actual external device.
i.e. Wake on device activity.
1 Like
You are correct.
Ok I misunderstood. I have a pretty good idea why this isn't working anymore and will check in a fix shortly
1 Like
version 1.0.1784 (beta)
- fix screensaver not waking up with device activity
- allow changing auto-home timeout
- minor Android TV fixes
This version has a few small changes including fixing the screensaver from being woke-up by device activity.
You can also change the timeout used for the 'auto home' feature. Just long-press on the Auto-Home setting to bring up a dialog with some choices.
UPDATE: I found a bug with the auto home times.. forgot to convert seconds to milliseconds.. oops! I'll get it fixed
should be fixed (but not tested so 
)
fixed!
3 Likes
I confirm, it's fixed!! You impress me so much!! Thank you for all your work and your super app!!
1 Like
just FYI - I'm looking into this one and not sure it really works at least the way I implemented it. I'm able to view 18 tiles on 1 screen with the grid view but displaying as a list (like the battery monitor) I only see 17.. I was thinking the list view would show more
I know you wanted more info on the list view but there's not a lot of extra room once the device name is there.. maybe someone has some other ideas how this could look.. hoping to improve on the normal grid view by enough to make it a good alternative
The list view looks good. Maybe implement a box to click open the color wheel and such, and a way to open the edit.
