Securifi Community Forum

Sensors and Home Automation => Home automation => Topic started by: d.kiran on July 10, 2015, 10:26:32 am

Title: UI and Sensor Support - YOUR PREFERENCE
Post by: d.kiran on July 10, 2015, 10:26:32 am
(If you can't see the poll, please login so you can vote)
This should be self explanatory. I am just trying to see if we can give feedback to Securifi about what UIs should be supported.
Title: Re: UI and Sensor Support - YOUR PREFERENCE
Post by: Fire69 on July 10, 2015, 04:15:46 pm
Sorry, I don't understand your question.
All those UI's already have sensor support.  Do you mean what UI should first be updated to support more sensors?
Title: Re: UI and Sensor Support - YOUR PREFERENCE
Post by: d.kiran on July 10, 2015, 09:11:00 pm
That is correct. I realized that I did not word it correctly. The intent is to find out which UI should be prioritized when new sensors are supported.
Title: Re: UI and Sensor Support - YOUR PREFERENCE
Post by: Fire69 on July 11, 2015, 04:26:49 am
That's a hard thing to choose  between :-)

I would say the rules UI,  but I would then also like to control those sensors elsewhere :-)

It's actually a little ridiculous that the rules UI and the local UI are 2 different things. That makes 6 different UI's to maintain and support...  :-\

Title: Re: UI and Sensor Support - YOUR PREFERENCE
Post by: d.kiran on July 11, 2015, 11:56:06 am
It's actually a little ridiculous that the rules UI and the local UI are 2 different things. That makes 6 different UI's to maintain and support...  :-\

To be honest, I don't really know that. I assumed it is based on how each codebase seems to be separate. If they are the same though, then the support for Local WebUI seems to be winning :-)

@Securifi @Ashok - Does adding a sensor to the local webUI ensure that it is immediately available in the Rules as well ?
Title: Re: UI and Sensor Support - YOUR PREFERENCE
Post by: Fire69 on July 11, 2015, 12:02:48 pm
Not unless they changed their way of programing recently.
I had sensors before that could be used in the local UI, but were not available in the rules...