HomeKit Integration

researching

#74

Listen to Apple’s engineers - HLS only provides real advantages from server to client, but HLS encodeing owuld impose too much of a penalty on your small cams, if you wanted to do it within the cam.

Choose H.265 or H.264 instead, from cam to server or to client. H.265 would be preferable if the horsepower of the cam can handle it.


#75

We are listening to them. :slight_smile: And also the fact that HomeKit does not support HLS at all from what we can tell.

H.264 & H.265 is the encoding, not the communication protocol. For the moment we are using H.264 because of the hardware encoder embedded in the camera. Going H.265 would be very CPU costly as we would have to use a software encoder. There is also an issue with licensing fee, which would raise the cost profile of the camera, including existing ones in customers’ hands.

Actually, HLS can be achieved out of the camera, it is not that different from what we are doing and we have a prototype that is not exactly HLS but very close to the behavior of HLS. This is looked into as part of another initiative.


#76

A pile-on for homekit!


#77

This is the part that worries me – all it will take is for some cheap Chinese made camera maker to integrate HomeKit into their product, and WYZE will fall by the wayside. Someone in mainland China will realize the economic promise of HomeKit, and will jump on this.

Once that happens, WYZE will have lost their potential advantage.

This is a serious question - what will it take to make this happen? Do you (WYZE) need more money? Should we start a GoFundMe or KickStarter campaign to show financial support for this?


#78

For those of you who are pretty technical, it is now possible to bring Wyze Cams into HomeKit as motion sensors with the stock firmware. Here is how I did it:

  1. Installed homebridge
  2. Installed homebridge-sqs plugin
  3. Created an FIFO SQS queue in Amazon Web Services
  4. Created an extremely simple AWS Lambda function that is exposed as a HTTP-based webhook using the AWS API Gateway (I use the Zappa framework for this).
  5. Configured each Wyze Cam in my house as a motion sensor in my homebridge configuration file, and also configured the SQS plugin with the appropriate credentials
  6. Created IFTTT automations which ping my webhook when motion is detected on each camera, passing the proper data.

The webhook receives events from IFTTT, pushes messages to the SQS queue, which in turn triggers homebridge via the plugin, and sets the appropriate motion detected state. It works well, but not as quickly as I’d like.

I would love to see Wyze actually make this happen for me! If I can do it in an hour or so with hacks like this, I have faith that your team can do a first-class HomeKit integration!


#79

I like it.


#80

Integration would allow for building a more robust security option without needing to use Honeywell or other high cost solutions. Use of the camera to identify movement in the scene and ideally differentiate between people and animals.


#81

Xiaomi Dafang in mainland China and Europe, NEOS Smartcam in UK and Wize Cam V2 in North America they are all the same. Hopefully the Wyze software will be a differentiator and assure that all our Data stays ours. This is why I use only Homekit compatible devices and stay away from Amazon Alexa and Google Home who are to happy to listen to us and sale our personal data. I also use HomeCam and Homebridge to integrate non Homekit compatible devices and service like IFTTT for at least two homes. It works but I would rather prefer to stay inside only Apple eco-system for security. Considering the you looking into Sense products and others you could make a blast in the market if your products were Apple compatible. Some companies have their product compatible with the 3 eco-systems and some others have different products line for each. Either ways would work for me. I am counting on you Wyze guys!