Hi Matt,
yesterday I scanned my windows network from my laptop ... all my comfort devices appear at the network, is it secure for my home system ?
bagushandhoko wrote: Quote:Hi Matt,
yesterday I scanned my windows network from my laptop ... all my comfort devices appear at the network, is it secure for my home system ?
That\'s a good question - let me explain what is going on.
UPNP uses a discovery mechanism by broadcasting to the local subnet on port 1900 over UDP. Devices respond to these broadcasts by advertising their capabilities and devices. This is how the vast majority of IoT devices make themselves available to other devices (you may have also seen other devices such as Sonos, WeMo, Philips Hue, etc).
These broadcasts and responses are limited the local network and won\'t route to any outside networks so as long as your home WiFi network is secure there is no issue.
Furthermore there are a couple of additional layers of security layered on top of UPNP.
- the alarm.config file allows you to define the comfort devices (inputs, outputs, flags, counters and responses) which are permitted to be exposed
- A pin is still required to unlock the alarm (i.e. it is possible to set the alarm without a pin, but it is necessary to use the pin to clear it - just as you do with the keypad)
We have an additional security feature on the roadmap which is analogous to WiFi easy setup - which will only enable discovery for a short period following a request on the Web GUI. Combined with a password protected GUI and the concept of pairing Comfort with external devices this should make it even more secure.
Thanks,
Matt
Related with new firmware :
1. I just upgraded to 1.0.0a from 1.0.0 , it happen only few seconds , is it normal ?
2.\" All zone devices now have the capability to act as a contact sensor\" ... please explain more regarding this
[user=5404]bagushandhoko[/user] wrote: Quote:Related with new firmware :
1. I just upgraded to 1.0.0a from 1.0.0 , it happen only few seconds , is it normal ?
2.\" All zone devices now have the capability to act as a contact sensor\" ... please explain more regarding this
1. Yes, it should only take a few moments; if it is successful it will report the new version installed and the upgrade button should be greyed out. If upgrading from a 1.0.0 release (such as 1.0.0a or 1.0.0c) you may need to attempt it a couple of times if the upgrade file isn\'t downloaded quickly enough. This issue is fixed in 1.0.1a.
2. The device will appear as a motion detector in SmartThings (although the icon can be changed to reflect that of a door etc) but it now also has the capability of \'ContactSensor\' so SmartApps which allow you to select devices with that capability can find them.
Quote:[indent]1.For the time being can you limit the number of devices exposed to SmartThings to less that ~ 125?
[/indent] Matt
Hi Matt,
How to limit the number of devices exposed from comfigurator side ?
In the alarm.config only list the Inputs, Outputs, Flags and Counters that you need (and to a maximum of around 125).
I am working on instructions for a workaround which will selectively discover devices in batches to overcome this limitation.
Thanks,
Matt
I see
Total all output + zone + response + etc = max 125 ?
Broadly yes - responses aren\'t included as they are manually added rather than discovered. The total number is limited by the available memory to the discovery process in SmartThings which is 100,000 bytes. Devices which have shorter names use less memory and as a result it isn\'t exactly 125 devices.
If you have a lot more devices you would like to discover, a new version which is in development overcomes this limitation with 2 step discovery but is not backwardly compatible. This version will form the basis of the commercial UCM.
Thanks,
Matt
yeah ... ideally match with maximum capacity of comfort :dude: