I would like to use the LaMetric device in an internal network without internet access, i.e. independent from the cloud server. I would like to display data on the device that comes from an internal server of mine. This data is completely private, it's not accessible from the internet.
I'm a programmer myself (Python, C, and others, whatever is needed) and have programmed TCP/IP based client/server software in the past. So, I would like to write my own server software to control my LaMetric device. In order to do that, however, I need to have documentation about the network protocols (i.e. low-level network API) that the LaMetric device is using. I could try to reverse-engineer it, but that would probably be somewhat tedious.
So, I would like to ask for the "official" documentation of the LaMetric's network protocols. During the Kickstarter campaign it was promised that such documentation will be made available.
Oliver, you can do this now...(I've done it) but be aware that accessing the application via the web dashboard causes the LaMetric PHP webpage to crash out (it can't find the host). See my other post. Vote it up so that this error can be trapped more cleanly.
How can this be done? I don't see a way to use my local RPi to push a frame directly to my LaMetric (e.g. at 192.168.0.64).
im getting a bit tired, no answers form la metric? what is the plan???
It's already relegated to a paperweight for me. Hopefully you all read the EULA for the app before creating a developer login right? How they can eventually charge you for apps or that they don't have to allow you to download your own app? Not very encouraging. Take a look at the firmware (squashfs) and you'll see enough alarming things that I won't put this thing on my network.
Very easy, just like many router and other embedded device firmwares.
Grab the 1.0.24 (lm_ota_1.0.24_20151016_112_sa1.bin) firmware from lametric.com/firmware
In linux, install squashfs-tools which will give you unsquashfs and mksquashfs.
Then, just run "unsquashfs lm_ota_1.0.24_20151016_112_sa1.bin"
That will create a squasfs-root directory with six files in it: 2 signature files, 2 md5 checksums, and 2 regular files. The rootfs.squash file is the one you want. Run "unsqashfs rootfs.squash" for that guy. You may want to do that as root as it tries to create character devices that you'll want to recreate when you rebuild the filesystem.
You will now have another squashfs-root directory and that has the entire directory structure of your Lametric pre-configuration. From there you'll be interested in looking at the /etc/shadow file, sshd config, how it handles networking, lighttpd config, etc.
Wanted to inform you that we just released new firmware 1.5.0 and we have local push feature there. More details here. Local API mimics the one that you use to push data to cloud. Comments are appreciated.
Thank you for the tip; I had no idea it was accessible online!
It's odd that when dropbear is running, openssh is also installed. Isn't it likely that it utilizes less RAM?
Meanwhile, I'm trying to see if john can do anything with the md5crypt, and I'll let you know if I discover anything, despite the fact that I only have 8 threads, not a cluster... tiny fishing
However, I agree that this should be more python-based and have a true local API; I'm hoping they implement this right after IFTTT, which they said was their first priority...:|