General Category > Ideas/Feature requests

Websocket sensors?

<< < (2/4) > >>

SecureComp:



--- Quote from: bear9rpp on June 01, 2016, 10:18:56 am ---@SecureComp

Yes, a binary device is fine.  Are you saying current websocket APIs already allows for creation of such a device?  Do tell please...

--- End quote ---

No, there is one very important piece missing in the release version of the software to accomplish what I believe folks want to do.

I need to understand exactly what it is the users would want.

It was mentioned that folks want to create a "DIY" device.  Well that device would have to follow the Class rules of an existing device, that or create and entirely new device with all kinds of "settings".  Mimicking an existing device class would be easier. Creating a new device such as a virtual notification device is possible but I question the actual utility of such a device.

The job of something like Homeseer is far different than that of the Almond+ imho.

rpr69:
The stuff I've been doing in Home Assistant isn't even necessarily 'sensors' in the sense that we are talking now, it's more about information and dashboards. I have a page that gives me room status (doors, windows, locks, etc, mostly from A+), server and network stats, one with IP camera views, one with weather/environment data (from Forecast.io, Raspberry Pi sensors, and radar maps), and one with presence status (from A+). I still need to add smoke alarm and water alarm sensors, and then work on the sending to A+ part, but I'm very encouraged so far. I can't do any of this with the A+ now, nor does it look like I could in the future, so I'm taking the good stuff from A+ and adding even more good stuff with H-A.

bear9rpp:
My requirement is really basic, I just need a websocket version of the basic sensors, such as:

binary switch (i.e. on/off state)
sensing device (i.e. temp readings)

SecureComp:

--- Quote from: rpr69 on June 01, 2016, 01:26:37 pm ---The stuff I've been doing in Home Assistant isn't even necessarily 'sensors' in the sense that we are talking now, it's more about information and dashboards. I have a page that gives me room status (doors, windows, locks, etc, mostly from A+), server and network stats, one with IP camera views, one with weather/environment data (from Forecast.io, Raspberry Pi sensors, and radar maps), and one with presence status (from A+). I still need to add smoke alarm and water alarm sensors, and then work on the sending to A+ part, but I'm very encouraged so far. I can't do any of this with the A+ now, nor does it look like I could in the future, so I'm taking the good stuff from A+ and adding even more good stuff with H-A.

--- End quote ---

That's exactly the job of Homeseer, present info of existing systems. It certainly does more than that but it sounds like you are getting what you need.  A comprehensive software platform that allows for a configurable interface is beyond the current scope of the Securifi products.  Not that a configurable app isn't possible down the road but it's far more important to provide robust support of sensors and functionality using the LCD interface and the apps along with providing a quality WiFi router, that's the job of the Almond class of products.

Really sounds like you are doing exactly what you should be. The only thing that would ease the burden in my mind, would be the full blown Almond+, Almond 2015, Almond 3 Plug In for Homeseer.  I'm not sure I'd include that in my business model if I were Securifi but if I were a VAR, I would seriously consider making that a project.

SecureComp:

--- Quote from: bear9rpp on June 01, 2016, 01:55:42 pm ---My requirement is really basic, I just need a websocket version of the basic sensors, such as:

binary switch (i.e. on/off state)
sensing device (i.e. temp readings)

--- End quote ---

When you say " websocket version", what do you mean?

Any 'virtual' device that would be created would need to work as if it were a sensor, meaning it would process input from the websocket , have responses displayed via the websocket interface as well as support the SDK.

As for creating a virtual device that mimics every possible sensor, that's not going to happen. At best I'd be willing to spend some time on a single device, likely something like a binary device.

So I'm not following your train of though, forgive me, but in requesting something like a sensing device, specifically a thermostat for example, what would you be doing that isn't handled by an actual thermostat sensor currently?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version