search

domogik / domogik

Domogik Free Home Automation software
Other
115 stars 39 forks source link

live device_type in json (0.6 Enchancement) #355

Open tikismoke opened 8 years ago

tikismoke commented 8 years ago

In info.json create a simple device_type empty of sensors/commands

User who do not want to allow commands or monitor somes informations could add/remove a function.

Exemple for xeeplugin, a car could send 56 differents sensors types (22 in normal use + 34 in advanced usage) depending on what the vehicule is able to send (for exemple in my case only 15 of the 22 based signals are available). Handling all sensors/commands combinaison in json is not reasonable and will scared user in device_type lis if all were existing.

cereal2nd commented 8 years ago

hmm,

can we restrict this to non-xpl plugins?

in that case i think this is doable

On Thu, Oct 20, 2016 at 12:21 PM tikismoke notifications@github.com wrote:

In info.json create a simple device_type empty of sensors/commands

-

Allow the plugin to add sensors/commands to an existing device from return of the plugin lib (Via a web API result or other lib like in ozwave).

Add an admin page that allow user to activate/deactivate sensors/commandes from the full available list.

User who do not want to allow commands or monitor somes informations could add/remove a function.

Exemple for xeeplugin, a car could send 56 differents sensors types (22 in normal use + 34 in advanced usage) depending on what the vehicule is able to send (for exemple in my case only 15 of the 22 based signals are available). Handling all sensors/commands combinaison in json is not reasonable and will scared user in device_type lis if all were existing.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/domogik/domogik/issues/355, or mute the thread https://github.com/notifications/unsubscribe-auth/ADiy8a4vc38X9lDyvzHrA5fsgziTnwIrks5q10DBgaJpZM4Kb9Uz .

tikismoke commented 8 years ago

Ho yes of course. For the moment i see only Xeedevice and zwave that could need it, but not know all tech maybe rfxcomm could use it too.

For me it's not a problem to handle only non-xpl plugin for that, as only generic and another(do not remember the one's) really need xpl now that we have MQ.

Le 20 octobre 2016 14:36:21 GMT+02:00, Maikel Punie notifications@github.com a écrit :

hmm,

can we restrict this to non-xpl plugins?

in that case i think this is doable

On Thu, Oct 20, 2016 at 12:21 PM tikismoke notifications@github.com wrote:

In info.json create a simple device_type empty of sensors/commands

-

Allow the plugin to add sensors/commands to an existing device from return of the plugin lib (Via a web API result or other lib like in ozwave).

Add an admin page that allow user to activate/deactivate sensors/commandes from the full available list.

User who do not want to allow commands or monitor somes informations could add/remove a function.

Exemple for xeeplugin, a car could send 56 differents sensors types (22 in normal use + 34 in advanced usage) depending on what the vehicule is able to send (for exemple in my case only 15 of the 22 based signals are available). Handling all sensors/commands combinaison in json is not reasonable and will scared user in device_type lis if all were existing.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/domogik/domogik/issues/355, or mute the thread

https://github.com/notifications/unsubscribe-auth/ADiy8a4vc38X9lDyvzHrA5fsgziTnwIrks5q10DBgaJpZM4Kb9Uz .

You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/domogik/domogik/issues/355#issuecomment-255093507

Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

cereal2nd commented 8 years ago

hmm, what is a xeedevice?

On Thu, Oct 20, 2016 at 2:39 PM tikismoke notifications@github.com wrote:

Ho yes of course. For the moment i see only Xeedevice and zwave that could need it, but not know all tech maybe rfxcomm could use it too.

For me it's not a problem to handle only non-xpl plugin for that, as only generic and another(do not remember the one's) really need xpl now that we have MQ.

Le 20 octobre 2016 14:36:21 GMT+02:00, Maikel Punie < notifications@github.com> a écrit :

hmm,

can we restrict this to non-xpl plugins?

in that case i think this is doable

On Thu, Oct 20, 2016 at 12:21 PM tikismoke notifications@github.com wrote:

In info.json create a simple device_type empty of sensors/commands

Allow the plugin to add sensors/commands to an existing device from return of the plugin lib (Via a web API result or other lib like

in ozwave).

Add an admin page that allow user to activate/deactivate sensors/commandes from the full available list.

User who do not want to allow commands or monitor somes informations could add/remove a function.

Exemple for xeeplugin, a car could send 56 differents sensors types (22 in normal use + 34 in advanced usage) depending on what the vehicule is able to send (for exemple in my case only 15 of the 22 based signals are available). Handling all sensors/commands combinaison in json is not reasonable and will scared user in device_type lis if all were existing.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/domogik/domogik/issues/355, or mute the thread

< https://github.com/notifications/unsubscribe-auth/ADiy8a4vc38X9lDyvzHrA5fsgziTnwIrks5q10DBgaJpZM4Kb9Uz

.

You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/domogik/domogik/issues/355#issuecomment-255093507

Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/domogik/domogik/issues/355#issuecomment-255094136, or mute the thread https://github.com/notifications/unsubscribe-auth/ADiy8cuwBolcWHcsObrLJHTtEDQXjFXtks5q12D_gaJpZM4Kb9Uz .

tikismoke commented 8 years ago

Like nest and withing another cloud solutions managing car via odb port.

Look at XeeConnect on the web.

I got it for 12€ on norauto with it's installation.

Ok it's not really good for private life protection. It allow me to manage my car (position/fuelevel/etc...)

Le 20 octobre 2016 14:41:57 GMT+02:00, Maikel Punie notifications@github.com a écrit :

hmm, what is a xeedevice?

On Thu, Oct 20, 2016 at 2:39 PM tikismoke notifications@github.com wrote:

Ho yes of course. For the moment i see only Xeedevice and zwave that could need it, but not know all tech maybe rfxcomm could use it too.

For me it's not a problem to handle only non-xpl plugin for that, as only generic and another(do not remember the one's) really need xpl now that we have MQ.

Le 20 octobre 2016 14:36:21 GMT+02:00, Maikel Punie < notifications@github.com> a écrit :

hmm,

can we restrict this to non-xpl plugins?

in that case i think this is doable

On Thu, Oct 20, 2016 at 12:21 PM tikismoke notifications@github.com wrote:

In info.json create a simple device_type empty of sensors/commands

Allow the plugin to add sensors/commands to an existing device from return of the plugin lib (Via a web API result or other lib like

in ozwave).

Add an admin page that allow user to activate/deactivate sensors/commandes from the full available list.

User who do not want to allow commands or monitor somes informations could add/remove a function.

Exemple for xeeplugin, a car could send 56 differents sensors types (22 in normal use + 34 in advanced usage) depending on what the vehicule is able to send (for exemple in my case only 15 of the 22 based signals are available). Handling all sensors/commands combinaison in json is not reasonable and will scared user in device_type lis if all were existing.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/domogik/domogik/issues/355, or mute the thread

<

https://github.com/notifications/unsubscribe-auth/ADiy8a4vc38X9lDyvzHrA5fsgziTnwIrks5q10DBgaJpZM4Kb9Uz

.

You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/domogik/domogik/issues/355#issuecomment-255093507

Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub

https://github.com/domogik/domogik/issues/355#issuecomment-255094136, or mute the thread

https://github.com/notifications/unsubscribe-auth/ADiy8cuwBolcWHcsObrLJHTtEDQXjFXtks5q12D_gaJpZM4Kb9Uz .

You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/domogik/domogik/issues/355#issuecomment-255094669

Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

fritz-smh commented 8 years ago

I agree to handle this only on non xpl plugins.

On Thu, Oct 20, 2016 at 2:41 PM, Maikel Punie notifications@github.com wrote:

hmm, what is a xeedevice?

On Thu, Oct 20, 2016 at 2:39 PM tikismoke notifications@github.com wrote:

Ho yes of course. For the moment i see only Xeedevice and zwave that could need it, but not know all tech maybe rfxcomm could use it too.

For me it's not a problem to handle only non-xpl plugin for that, as only generic and another(do not remember the one's) really need xpl now that we have MQ.

Le 20 octobre 2016 14:36:21 GMT+02:00, Maikel Punie < notifications@github.com> a écrit :

hmm,

can we restrict this to non-xpl plugins?

in that case i think this is doable

On Thu, Oct 20, 2016 at 12:21 PM tikismoke notifications@github.com wrote:

In info.json create a simple device_type empty of sensors/commands

Allow the plugin to add sensors/commands to an existing device from return of the plugin lib (Via a web API result or other lib like

in ozwave).

Add an admin page that allow user to activate/deactivate sensors/commandes from the full available list.

User who do not want to allow commands or monitor somes informations could add/remove a function.

Exemple for xeeplugin, a car could send 56 differents sensors types (22 in normal use + 34 in advanced usage) depending on what the vehicule is able to send (for exemple in my case only 15 of the 22 based signals are available). Handling all sensors/commands combinaison in json is not reasonable and will scared user in device_type lis if all were existing.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/domogik/domogik/issues/355, or mute the thread

< https://github.com/notifications/unsubscribe-auth/ ADiy8a4vc38X9lDyvzHrA5fsgziTnwIrks5q10DBgaJpZM4Kb9Uz

.

You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/domogik/domogik/issues/355#issuecomment-255093507

Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/domogik/domogik/issues/355#issuecomment-255094136, or mute the thread https://github.com/notifications/unsubscribe-auth/ ADiy8cuwBolcWHcsObrLJHTtEDQXjFXtks5q12D_gaJpZM4Kb9Uz .

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/domogik/domogik/issues/355#issuecomment-255094669, or mute the thread https://github.com/notifications/unsubscribe-auth/AEWKcjrBdqc4JSNl_Q2oNzN4CTyUC_xkks5q12GVgaJpZM4Kb9Uz .

tikismoke commented 8 years ago

Do not know how difficult it is ;) For us (discuss with @Nico0084 it only looks like a db modification (all sensors/commands describe in json but not attach to device).

cereal2nd commented 7 years ago

no not only a db modification

1- json modification to identify the field 2- db api for adding a command/sensor (now this is not split from the create_device) 3- mq commands (handled in dbmgr) to create/delete commands/sensors for a device

so it is possible, but its a lot of work

On Thu, Oct 20, 2016 at 2:48 PM tikismoke notifications@github.com wrote:

Do not know how difficult it is ;) For us (discuss with @Nico0084 https://github.com/Nico0084 it only looks like only a db modification (all sensors/commands describe in json but not attach to device).

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/domogik/domogik/issues/355#issuecomment-255096135, or mute the thread https://github.com/notifications/unsubscribe-auth/ADiy8TI1pMXGncf51uT0836n5bM_ey3xks5q12MwgaJpZM4Kb9Uz .

tikismoke commented 7 years ago

We should wait the 0.6 if it need such modification. Focus on current bugs/features/...

We can wait for next release.