The Market Ticker
Commentary on The Capital Markets- Category [Small Business]
Logging in or registering will improve your experience here
Main Navigation
Full-Text Search & Archives

Legal Disclaimer

The content on this site is provided without any warranty, express or implied. All opinions expressed on this site are those of the author and may contain errors or omissions. For investment, legal or other professional advice specific to your situation contact a licensed professional in your jurisdiction.


The author may have a position in any company or security mentioned herein. Actions you undertake as a consequence of any analysis, opinion or advertisement on this site are your sole responsibility.

Market charts, when present, used with permission of TD Ameritrade/ThinkOrSwim Inc. Neither TD Ameritrade or ThinkOrSwim have reviewed, approved or disapproved any content herein.

The Market Ticker content may be sent unmodified to lawmakers via print or electronic means or excerpted online for non-commercial purposes provided full attribution is given and the original article source is linked to. Please contact Karl Denninger for reprint permission in other media, to republish full articles, or for any commercial use (which includes any site where advertising is displayed.)

Submissions or tips on matters of economic or political interest may be sent "over the transom" to The Editor at any time. To be considered for publication your submission must include full and correct contact information and be related to an economic or political matter of the day. All submissions become the property of The Market Ticker.

Considering sending spam? Read this first.

It just keeps coming with HomeDaemon-MCP.

  • Camera code has been re-factored.  Overhead has been massively decreased, the pipelines have been shortened by half (much less O/S overhead per-camera) and multi-user dispatch written into the code.  The result is a more than 50% decrease in CPU requirement per-camera, per-consumer.

  • Near-instant detection of failed or offline cameras (and return to service for them if they do fail); detection time has been massively improved from a few minutes to a few seconds.

  • The Pi3 should be able to support at least eight (8) cameras, assuming adequate network bandwidth.  Note that WiFi is never anywhere near advertised speeds due to its CSMA/CD nature (that is, multiple users must contend for bandwidth) and its half-duplex nature (only one direction sending at one time) .vs. wired connections which typically go to a switch and are full duplex (both directions at once, at full wire speed.)  Reasonable frame and bitrate selections go a long way toward good results (e.g. 10fps, 1Mbps VBR, full-frames set to 15); with these settings the data requirement is about ~500 Megabytes per day, per camera.  When the Pi4 becomes widely available it is likely that this capability will wildly expand as the "4" is both much faster, has more RAM available and has a Gigabit-capable Ethernet port.  

  • Audio is now fully supported; if you have it turned on in the camera you'll get it in the stream.

  • Retrospective lookback is automatic.  If you trigger a stream on an event (e.g. motion, noise, door opening, etc) the system will automatically replay the last few minutes into the stream file before the event occurred.  You always want to see and hear what the jackwad was doing before he did the evil thing, right?  Well, now you can -- without recording all the time and having to search through it manually.

  • Speaking of which, full-time archiving is now also supported -- with automatic overlap between files so there is no "gap" when file rollover occurs.  Default is 10 minutes per segment but that can be set as you wish.  Storage can be local (plug in a USB disk) or remote (ssh recommended to keep the data encrypted in transport.)  Yes, it will work over the Internet, provided you have the bandwidth to keep up with it.  The archiving function is a command in the HomeDaemon-MCP software so you can also turn it on and off as you wish unlike "stand-alone" systems (e.g. only record when the house is in "Away" or "Night" modes, for example, not when someone is home during the daytime.)  There is a tiny little shell script that conveniently files the received streams under CameraName/Year/Month/Day, making an automated cleanup process for old, no-longer-wanted files trivial.

  • Streams stored, output and sent are standard .MP4 files and will play on cellphones, desktop and laptop computers.  Nothing fancy -- or any special software -- is required.  It "just works"; Windows 10 is perfectly happy to "eat" and display them, as are Android devices, along with most other mobile and desktop devices made within the last 10 years.

Of course all the Z-wave capabilities, including secure mode and mitigation for the "pick-off key" issues that others have identified (e.g. "Z-shave") remain fully supported.

In short HomeDaemon-MCP is not just a security system with a camera interface any longer.  It is now the equivalent of a full-time, streaming camera storage and archival system that can store archival video footage anywhere and anyhow you wish, for however long you wish, when you wish, either under certain conditions or all the time, along with retrospective "quick looks" when an event occurs (so you can see the previous few minutes before the alarm event happens without sifting through what could be terabytes of video files) and it contains a full home or business environment control system for lighting, HVAC and more -- all integrated into one package.

Finally it does not require "the cloud", nobody gets to spy on you, Amazon does not get your data nor does Google, Apple or anyone else.  Only you get your data.  Only you can get at the streaming connection from cameras and other devices in your home.  Modern, encrypted connections over TLS give you full access, visibility and control from anywhere you have an Internet connection available -- whether mobile on the phone or on your desktop or laptop, and for more-modern systems perfect forward security makes "retrospective" interception nearly impossible.  And, of course, the fully event-driven, english-language-like capability to have the system do what you want, when you want remains at your command -- as it always has.

HomeDaemon-MCP remains for sale "all-in" to the enterprising firm or individual that wants to destroy the existing lines of business that competitors have in this space.

First come gets it, everyone else cries.

Look to the right and email me.

View this entry with comments (opens new window)

2019-05-21 08:09 by Karl Denninger
in Small Business , 246 references
[Comments enabled]  

So 2020 will approach.

And before November of that year gets here, likely well before (like by the beginning of the year) I'm going to be executing on a few things.

I've long maintained that I'm very unlikely to set up or start another entrepreneurial activity.  What I'm seeing both in the political and general context is that the odds have gone from "slim" to "none; Slim ran off with your sister and is banging her in the back of his old pick-up truck."

So here's the deal; Cuda Systems LLC can be yours.  Including the Market Ticker with its registered trademark (which I just reconfirmed as the 10 year anniversary was coming up), and HomeDaemon.  All at once.  Pay once, own forever.

If not, well, with there no longer being a formal structure for all this in another year it'll all go away.  Not all at once, but with certainty. While it's easy to maintain a Florida LLC even if you don't live in Florida (the requirement is only for a registered agent somewhere, which you can pay for cheap) I've no reason to do it, and I'm not going to re-domicile it either.

Let the bidding begin; look to the right for my email.

View this entry with comments (opens new window)

2019-02-01 10:12 by Karl Denninger
in Small Business , 225 references
[Comments enabled]  

Those who sell their souls to the Devil have little to complain about when he shows up without a jar of KY to go with what he intends to do to you.

Arjun Sud was standing outside his son Oliver’s Door Sunday when he heard that voice. He burst in. The voice stopped. He and his wife chalked it up to baby monitor interference. But once downstairs, they heard the voice again.

It was an unseen intruder talking to them through their Nest security camera, using obscenities including the ‘N’ word.

“Asking me, you know, why I’m looking at him because he saw obviously that I was looking back and continuing to taunt me,” he said.

“It was terrifying,” Sud’s wife Jessica said.

Sud says once his shock subsided he composed himself enough to record part of the ominous exchange.

Sud believes the hacker also turned their upstairs thermostat to 90 degrees. He noticed that potential danger to their baby the same night.

“And then they messed with our thermostat,” Jessica said. “Who does that?”

Uh, you are the idiot that connected your house to a "cloud" -- that is, a computer owned by someone else.

It's not like you didn't know in advance that these companies make their money using your data to screw you in one form or another -- even if it's just 'selling advertising.'


Of course the companies always claim it's the customer's fault -- they didn't use a good password, they didn't use 2-factor authentication, etc.  This ignores the reality of the situation, which is both simpler and more-complex.

The simple side is this: These firms make their money off selling data they accumulate on you.  Security is not their first thought or they wouldn't connect such things as your thermostat to the "cloud" at all; they'd design them to be very secure and talk only to your specific devices such as your phone.

But then they wouldn't be able to use that data themselves.

You can bet they intend to -- and are.  Just read this:

We should recognize this pattern: Tech that seems like an obvious good can develop darker dimensions as capabilities improve and data shifts into new hands. A terms-of-service update, a face-recognition upgrade or a hack could turn your doorbell into a privacy invasion you didn’t see coming.

Last month, Ring got caught allowing its team in Ukraine to view and annotate certain user videos; the company says it only looks at publicly shared videos and those from Ring owners who provide consent. Just last week, a California family’s Nest camera let a hacker take over and broadcast fake audio warnings about a missile attack, not to mention peer in on them, when they used a weak password.

Why do you think these folks all design their software and "products" to have a business model that costs them money on an ongoing, perpetual basis?  Computers are not free and neither is storage.  What possible purpose does imposing a cost model on themselves on a perpetual forward basis for said "cloud connections" have unless they are going to use it to screw you in some form or fashion?

It's not necessary for anything more than a licensing check or similar, and that contains nothing of value to a hacker provided the payment information for said license is secured properly (or not even present on that system, which it doesn't have to be.)  There's simply no reason at all to have that data and a back-channel to connect to your house in the "cloud" in terms of access for you; your phone or laptop can simply connect directly back to your house via a secured, SSL-enabled connection and if it was designed that way the only place the data would be is in your house and on your phone.

Instead these "cloud folks" try to sell you "convenience" that isn't really any more convenient at all!

HomeDaemon-MCP provides you remote access to everything in your home that you wish to look at and control along with alarms and similar in real time without any "cloud" involvement.  Yet if you want real-time video from your camera(s), you can see it.  If you want to grab a segment to your phone (directly, not to a cloud computer) you can do that on command.  If you want to adjust your thermostat, you can.  See when someone was last in a room, sure.

But nobody has that data except you, because it's not stored anywhere except on the little credit-card size computer in your house and is only transmitted to your device(s), such as your phone, when they are connected -- and nowhere else.  No cloud, no company mining your data looking for patterns it can sell things to you based on and nobody spying on you either.

I just closed on my late mother's estate (house.)  Her place was built almost-literally on a swamp (along with many others in the neighborhood) and had a full basement, which means a sump pump that had better not, ever, quit working.  Then there's the usual issues when you're not there all the time -- especially in the winter, where loss of heating (e.g. something as simple as a burned-out igniter in the furnace) means frozen pipes and a god-awful amount of damage.

HomeDaemon-MCP took care of all of that, in addition to my home here in Florida.  The sump pump was checked with a plug module that reported power usage.  It thus became trivially simple to know how often it was cycling, for starters.  In addition setting alarm points for the pump being on for too long (a sump pump should never actually run for more than a few seconds per cycle) or excessive power consumption (indicating either a blocked -- like frozen -- outlet or a locked rotor, that is, a failed pump) raised immediate and very loud alarms on my phone.  Finally, a water sensor probe down the volute above the normal level was there -- just in case everything else looked ok but the water wasn't actually being pumped.

Then in the main living space a CO/Fire detector that also talked to the system was put up (battery powered), covering that possibility, and finally a thermostat.  The latter not only made for a big reduction in power consumption when nobody was there but also allowed for trivial monitoring for the situation where it's winter and the furnace breaks, in that too-low temperature would cause an immediate alarm too.

Icing on the cake was the ability to have and look at 24x7 video feeds if desired, and knowing when motion was last detected, so if someone broke a window, well, that was covered too.

I've been living there about half the time since September; the same issue of course arises for anyone else who has a vacation or second home -- or if you just go to work 8 hours a day.  You're not there all the time and it's nice to know that all is well -- and be immediately told if it isn't.

No cloud, no bullcrap, nobody gets in except me -- and notification is effectively immediate (60 seconds or less) if something happens.  In addition should I want to let someone in (e.g. a Realtor) I can -- remotely, with the push of a button, and know if/when someone does come in, even using a key.

Want to disrupt this space?  The marketing material writes itself with stories like this cited one above, of which there are plenty already and will be more.

Email me -- contact info is to the right.

View this entry with comments (opens new window)

2018-11-29 12:27 by Karl Denninger
in Small Business , 126 references
[Comments enabled]  

Folks, this is why it matters and someone should snap up the entire codebase and app (in source of course) for HomeDaemon-MCP and put it on the market.

Yes, I know, I can.  I have the capital to roll it out.  I have good personal reasons to not want to though, especially given where I live now and what I think is going to happen to the political environment there.  Further, any business that deals in any sort of physical product (even coffee mugs) is ridiculously burdened in Florida.  I knew this when I moved to the State and never intended to start another business that might sell same in the future.  Anyway, that's the short side of the story and there is of course more, but for this coming year it is what it is.

On to the reasons: You now are seeing the media pick up on the business model question -- and especially recommend eschewing cloud anything.  And not just any media -- the GRAY LADY herself.  You want to know why you should do it now?  Because opportunity is best when its hot, and it's hot right now.

Then there's this, which made me spit my coffee:

Hackers ‘can detect your butt plug from outside your house – and turn it on’

They call the new technique screwdriving which seems entirely appropriate... but added massively to the coffee explosion out my nose.  Now I need a new keyboard, which is somewhat of a bummer but definitely worth it.

Look to the right and email me folks -- because I've decided that I just don't want to do it here in Florida, and I'm unsettled on where I'd rather live (in no small part due to the political shifts around the nation) the opportunity is now to buy this out at a quite-polite price all things considered.

View this entry with comments (opens new window)

2018-11-07 06:57 by Karl Denninger
in Small Business , 63 references
[Comments enabled]  

So about those locks.....


One of the challenges I've had with allowing the manipulation of lock state (other than lock/unlock, or setting the keypad on or off) is the risk of someone picking off a code from your phone -- and then being able to break into your house.  For obvious reasons that would be bad.

I've decided to leverage the notification system built into the software for this purpose.  This has several advantages, chief among them being that neither the phone or the base software has to store a code from a lock in any case.

If you select "Get Code in Slot" and enter the slot number when you click Execute HomeDaemon-MCP retrieves the code in real time over the AES-encrypted channel from the lock and sends it back to your device via the encrypted notification system.  It never touches anything else (like the cloud) and is not stored anywhere other than in RAM on the device when displayed in the notification pane, which can be dismissed.  In addition there is no storage off-site, anywhere, of the event itself either so Mr. Subpoena (or "Mr. NSL") can pound sand since nobody can produce what they don't have.

If you set a code it is transmitted to the lock.  Ditto for deleting a code.

Codes on most common locks (they're all using the same basic board) can be 4 to 8 numeric digits.  8 is quite secure; 4, not so much, although after a few (wrong) attempts the lock will raise an alarm exception.  In all cases when the change "takes" an exception is raised back to the phone, so you know it went through, exactly as is the case for an asynchronous event (e.g. someone uses the code to open the lock.)

Disabling the keypad locks out all the codes, instantly (very useful if you're not at home, don't expect to be home, and don't want anyone to be able to open the door.)  The state of the lock in the background is currently set this way ("Prohibited" .vs. "Accessible.")  Oh, and the manual operation of the lock (e.g. with a key or the inside knob) is also instantly reported.

Again -- no cloud, no BeeEss, no stealing.

HomeDaemon-MCP is available to the firm, large or small, that wants to disrupt the model of "smart home" systems.  All rights, source and all, to both the base code running on a $35 piece of hardware and the Android app are included.  Look to the right and email me today!

View this entry with comments (opens new window)