Devices, Alias, Assistenten + Visualisierungen + die Zukunft
-
@apollon77 hab mich verklickt, es wurde kein Objekt angelegt zumindest seh ich keins.
Wenn ich den Adapter lösch sind alle aliase weg, kann ich die davor sichern? -
@Stephan-Schleich Aliasse sind nicht weg wenn DU Devices löschst. Wie kommst Du darauf?
-
@apollon77 in den Objekten verschwindet doch immer alles was mit dem Adapter zu tun hatte, den man deinstalliert.
Edit: Das Problem lag am Browser, Chache gelöscht und jetzt gehts wieder, so sah es aus
-
@Stephan-Schleich Nur states die unter den Instanzobjekten des Adaters abgelegt sind. deviecs hat da nichts. Was sagt die Browser Konsole?
-
@apollon77 sagte in Devices, Alias, Assistenten + Visualisierungen + die Zukunft:
Browser Konsole
@apollon77 Achso okay - danke, wusste nicht das diese nicht zusammen hängen.
In der Browser Konsole hatte ich nicht nachgesehen als ich das Problem hatte, aber es lag am Browser Cache nun läufts wieder.Eine Frage noch sofern es hier rein gehört:
Ich hab meine Klimaanlage via Alias angebunden nun würde ich im selben Objekt gerne noch die IP mit dazu nehmen ohne extra ein neues Objekt anzulegen, theoretisch müsste es doch mit z.b. working gehen da der typ any ist oder? es kommt aber nur true als value und nicht die IP
-
@Stephan-Schleich Bitte nicht anfangen irgendwelche States zweck-zu-entfremden
WORKIGN hat eine semantische Bedeutung -
@apollon77 okay, könnte man ne Möglichkeit bieten selber weitere Felder mit hinzuzufügen bzw ein paar freie?
-
@Stephan-Schleich Feature Request bitte im Github beim Devices Adapter
-
@apollon77 Wollt ich gerade machen, gibt es bereits
- https://github.com/ioBroker/ioBroker.devices/issues/18closed Allow adding more states to device #18
-
@Stephan-Schleich Dann hinterlass ein "Daumen hoch" im ersten post
-
@apollon77 Es ist hier so still geworden. Geht es hier noch weiter oder ist dieser Weg eine Sackgasse?
-
@mlengen In einem der letzten Dev Meetings wurde betont, dass Alias die Zukunft ist und der momentane Stand nur ein Zwischenstand ist. Was genau erwartest Du denn, was hier passieren soll?
-
@mlengen Tage ... 24h ... Privatleben ... andere Prios ... such Dir nen Grund aus ... ja es ist immer noch der Plan ...
-
Ich habe mal eine Frage zum Adapter Devices, wie kann ich selbst Aliase zusätzlich anlegen ?
-
Sorry for late feedback but I just found this thread. I hope it's okey that I write in english as mein deutch ist leider nicht sehr gut (ich kann aber deutch gut lesen).
I'm thrilled to read about the enhancements in this area! This enables ioBroker to become smart
However, I would not use the Alexa Skills as a great Taxonomy for how to implement the metadata in ioBroker. Alexa is great and very flexible, but it lacks a good structure. For example, it only specifies 15 different Device types (Skill Device Templates). Google Assistant is much better; they have currently 78 Devices types for smart home area. Apple HomeKit has 23 (Accessory types).
Have I understood the proposed structure correctly that the Device top level will be called "Alias" and an alias then has a "Function", and below this, it will have one or more "Roles/Types" and these have different "States"?
Could you share how those different levels map to the Taxonomy used by, for example Alexa and Google?
Something else I would suggest is to not focus too much on Alexa and Google but use as much as possible from the already standardized and open framework from OpenConnectivity Foundation, the OCF Specification. The latest release is from July this year. They have already a huge amount of Devices types specified, 54 types for smart home and another 127 for appliances and other IoT devices. For the next level, they call it "Resource Types", they have specified 169 types. Most of the big players are members of OCF. Have you guys already looked at this spec and if so, what is your opinion about it?
For my own benefit, I have put a table together with how I understand the used Taxonomy and how they map. I also counted all the standardized types they currently have officially documented. Please, let me know if I misunderstood something.
Many thanks for the impressive work with ioBroker and all of the adapters!
-
EDIT: I found an online tool showing all the device and resource types as well as enumerations: https://openconnectivityfoundation.github.io/devicemodels/docs/index.html
Here is the list of OCF Universal Device types (Source: OCF spec Annex A)
Device Category / Device Type / Normative Space Conditioning Air Conditioner oic.d.airconditioner Water Heater oic.d.waterheater Furnace oic.d.furnace Pump oic.d.pump Fan oic.d.fan Condensing Unit oic.d.condensingunit Condenser oic.d.condenser Humidifier oic.d.humidifier Dehumidifier oic.d.dehumidifier Thermostat oic.d.thermostat HVAC oic.d.hvac Air Purifier oic.d.airpurifier Air Quality Monitor oic.d.airqualitymonitor Lighting Lighting Controls oic.d.lightingcontrol Light oic.d.light Appliance Airer oic.d.airer Dryer (Laundry) oic.d.dryer "Washer (Laundry)" oic.d.washer Clothes Washer Dryer oic.d.washerdryer Dishwasher oic.d.dishwasher Freezer oic.d.freezer Ice Machine oic.d.icemachine Indoor Garden oic.d.indoorgarden Mattress oic.d.mattress Oven oic.d.oven Range oic.d.range Refrigerator oic.d.refrigerator Water Heater oic.d.waterheater Water Purifier oic.d.waterpurifier Cooker Hood oic.d.cookerhood Cooktop oic.d.cooktop Steam Closet oic.d.steamcloset Electronics Audio System oic.d.audiosystem AV Player oic.d.avplayer Camera oic.d.camera Desktop PC oic.d.desktoppc Notebook PC oic.d.notebookpc Server oic.d.server Computer oic.d.pc Data Storage Unit oic.d.datastorageunit Display oic.d.display Portable Electronics oic.d.portableelectronics Game Console oic.d.gameconsole 3D Printer oic.d.3dprinter Printer oic.d.printer Printer Multi- Function oic.d.multifunctionprinter Scanner oic.d.scanner Musical Instrument oic.d.musicalinstrument Networking Equipment oic.d.networking Handset oic.d.handset Receiver oic.d.receiver Set Top Box oic.d.stb Telephony oic.d.telephonydevice Television oic.d.tv Active Speaker oic.d.speaker Electronics oic.d.smallelectrical Miscellaneous Air Compressor oic.d.aircompressor Bathroom General oic.d.bathroomdevice Battery Charger oic.d.batterycharger Business Equipment oic.d.businessequipment Robot Cleaner oic.d.robotcleaner Portable Stove oic.d.portablestove Exercise Machine oic.d.exercisemachine Portable HVAC oic.d.hvacportable Optical augmented RFID Reader oic.d.orfid Coffee Machine oic.d.coffeemachine Food Probe oic.d.foodprobe Grinder oic.d.grinder Kettle oic.d.kettle Decorative Lighting oic.d.lightdecorative Emergency Lighting oic.d.lightemergency Microwave Oven oic.d.microwave Vending Machine oic.d.vendingmachine Water Dispenser oic.d.waterdispenser Battery oic.d.battery Infrastructure Water Valve oic.d.watervalve Blind oic.d.blind Door oic.d.door Garage Door oic.d.garagedoor Smart Lock oic.d.smartlock Window oic.d.window Fireplace oic.d.fireplace Pump oic.d.pump Energy Generator oic.d.energygenerator Smart Plug oic.d.smartplug Arc Fault Circuit Interrupter oic.d.afci Circuit Breaker oic.d.circuitbreaker Ground Fault Circuit Interrupter oic.d.gfci Inverter oic.d.inverter PV Array System oic.d.pvarraysystem Switch oic.d.switch Security Panel oic.d.securitypanel Generic Sensor oic.d.sensor Electric Meter oic.d.electricmeter Energy Monitor oic.d.energymonitor Transportation Electric Vehicle Charger oic.d.electricvehiclecharger Fitness Fitness Device oic.d.fitnessdevice Activity Tracker oic.d.activitytracker Blood Pressure Monitor oic.d.bloodpressuremonitor Body Thermometer oic.d.bodythermometer Cycling Power Meter oic.d.cyclingpowermeter Cycling Speed Sensor oic.d.cyclingspeedsensor Cycling Cadence Sensor oic.d.cyclingcadencesensor Heart Rate Monitor oic.d.heartratemonitor Muscle Oxygen Monitor oic.d.muscleoxygenmonitor Medical Blood Pressure Monitor oic.d.bloodpressuremonitor Body Scale oic.d.bodyscale Body Thermometer oic.d.bodythermometer CGM oic.d.cgm Glucose Meter oic.d.glucosemeter Heart Rate Monitor oic.d.heartratemonitor Medical Device oic.d.medicaldevice Pulse Oximeter oic.d.pulseoximeter Sleep Monitor oic.d.sleepmonitor Personal Health Activity Tracker oic.d.activitytracker Blood Pressure Monitor oic.d.bloodpressuremonitor Body Composition Analyser oic.d.bodycompositionanalys er Body Scale oic.d.bodyscale Body Thermometer oic.d.bodythermometer CGM oic.d.cgm Glucose Meter oic.d.glucosemeter Heart Rate Monitor oic.d.heartratemonitor Personal Health Device oic.d.personalhealthdevice Pulse Oximeter oic.d.pulseoximeter Sleep Monitor oic.d.sleepmonitor Other oic.d.unknown Access Management Service oic.d.ams Credential Management Service oic.d.cms Device Ownership Transfer Service oic.d.dotsAnd a list with the 169 Resource Type definitions
Friendly Name (informative) Resource Type (rt) 3D Printer oic.r.printer.3d Acceleration Sensor oic.r.sensor.acceleration Activity oic.r.activity Activity Count oic.r.sensor.activity.count Activity Tracker Atomic Measurement oic.r.activitytracker-am Air Flow oic.r.airflow Air Flow Control oic.r.airflowcontrol Air Quality oic.r.airquality Air Quality Collection oic.r.airqualitycollection Alarm oic.r.alarm Altimeter oic.r.altimeter Atmospheric Pressure oic.r.sensor.atmosphericpressure Audio Controls oic.r.audio Auto Focus oic.r.autofocus Automatic Document Feeder oic.r.automaticdocumentfeeder Auto White Balance oic.r.colour.autowhitebalance Battery oic.r.energy.battery Battery Material oic.r.batterymaterial Body Composition Analyser Atomic Measurement oic.r.bodycompositionanalyser-am Binary switch oic.r.switch.binary Blood Pressure oic.r.blood.pressure Blood Pressure Monitor Atomic Measurement oic.r.bloodpressuremonitor-am BMI oic.r.bmi Body Fat oic.r.body.fat Body Fat Free Mass oic.r.body.ffm Body Location Temperature oic.r.body.location.temperature Body Scale Atomic Measurement oic.r.body.scale-am Body Soft Lean Mass oic.r.body.slm Body Thermometer Atomic Measurement oic.r.bodythermometer-am Body Water oic.r.body.water Brewing oic.r.brewing Brightness oic.r.light.brightness Button Switch oic.r.button Cadence oic.r.cadence Calibrate for Continuous Glucose Meter (CGM) oic.r.cgm.calibrate Calorific Value oic.r.calorificvalue Carbon Dioxide Sensor oic.r.sensor.carbondioxide Carbon Monoxide Sensor oic.r.sensor.carbonmonoxide Circuit Breaker (IEC 61850) oic.r.circuitbreaker Clock oic.r.clock Colour Chroma oic.r.colour.chroma Colour Hue Saturation oic.r.colour.hs Colour RGB oic.r.colour.rgb Colour Saturation oic.r.colour.saturation Colour Space Coordinates oic.r.colour.csc Colour Temperature oic.r.colour.colourtemperature Consumable oic.r.consumable Consumable Collection oic.r.consumablecollection Contact Sensor oic.r.sensor.contact Continuous Glucose Meter (CGM) Atomic Measurement oic.r.cgm-am Conversion Factor oic.r.conversionfactor Cycling Power oic.r.cyclingpower Delay Defrost oic.r.delaydefrost Demand Response Load Control (DRLC) oic.r.energy.drlc Deodorization oic.r.deodorization Device Settings - Accessibility oic.r.settings.accessibility Device Settings - Broadcasting oic.r.settings.broadcasting Device Settings - Picture oic.r.settings.picture Device Settings - Sound oic.r.settings.sound Device Settings - Support oic.r.settings.support Device Settings - System oic.r.settings.system Dimming oic.r.light.dimming Door oic.r.door Ecomode oic.r.ecomode Electric Vehicle Connector oic.r.vehicle.connector Electrical Energy oic.r.energy.electrical Energy Consumption oic.r.energy.consumption Energy Generation oic.r.energy.generation Energy Overload/Circuit Breaker oic.r.energy.overload Energy Usage oic.r.energy.usage Gas Consumption oic.r.gas.consumption Gas Usage oic.r.gas.usage Fault Interrupter Switch oic.r.switch.fault Foaming oic.r.foaming Generic Sensor oic.r.sensor Geolocation Sensor oic.r.sensor.geolocation Glass Break Sensor oic.r.sensor.glassbreak Glucose oic.r.glucose Glucose Meter Complex Carbohydrates oic.r.glucose.carb Glucose Meter Exercise oic.r.glucose.exercise Glucose Meter HbA1c oic.r.glucose.hba1c Glucose Meter Context Health oic.r.glucose.health Glucose Meter Context Meal oic.r.glucose.meal Glucose Meter Context Medication oic.r.glucose.medication Glucose Meter Atomic Measurement oic.r.glucosemeter-am Glucose Meter Context Sample Location oic.r.glucose.samplelocation Glucose Meter Context Tester oic.r.glucose.tester Grinder oic.r.grinder HVAC Capacity Oic.r.hvac.capacity 6.157 Heart Rate oic.r.heartrate Heart Rate Monitor Atomic Measurement Representation oic.r.heartratemonitor-am Heart Rate Zone Sensor oic.r.sensor.heart.zone Heating Zone oic.r.heatingzone Heating Zone Collection oic.r.heatingzonecollection Height oic.r.height Humidity oic.r.humidity IAS Zone Info oic.r.iaszoneinfo IAS Zone Collection oic.r.iaszone Icemaker oic.r.icemaker Illuminance Sensor oic.r.sensor.illuminance Impact Sensor oic.r.impactsensor Inverter (IEC 61850) oic.r.inverter KeyCard Switch oic.r.keycardswitch Keypad Character oic.r.keypadchar Liquid Level oic.r.liquid.level Lock oic.r.lock.status Lock Code oic.r.lock.code Magnetic Field Direction oic.r.sensor.magneticfielddirection Media oic.r.media Media Audio oic.r.media.audio Media Core oic.r.media.core Media Image oic.r.media.image Media Source oic.r.mediasource Media Source List oic.r.mediasourcelist Media Source Input oic.r.media.input Media Source Output oic.r.media.output Media Text oic.r.media.text Media Video oic.r.media.video Mode oic.r.mode Movement oic.r.movement.linear Motion Sensor oic.r.sensor.motion Muscle Oxygen Saturation oic.r.muscleoxygensaturation Night Mode oic.r.nightmode Opaque Data oic.r.opaquedata Open Level oic.r.openlevel Operational State oic.r.operational.state Optical RFID Station oic.r.orfid.station Optical RFID Tag oic.r.orfid.tag Pan Tilt Zoom Movement oic.r.ptz Power Source oic.r.powersource Presence Sensor oic.r.sensor.presence Print Queue oic.r.printer.queue Pulsatile Characteristic for Pulse Oximeter oic.r.pulsatilecharacteristic Pulsatile Occurrence for Pulse Oximeter oic.r.pulsatileoccurrence Pulse Oximeter Atomic Measurement Representation oic.r.pulseoximeter-am Pulse Rate oic.r.pulserate PV array system connection terminal (IEC 61850) oic.r pvconnectionterminal Ramp Time oic.r.light.ramptime Refrigeration oic.r.refrigeration Restricted Switch oic.r.switch.restricted Sampling Interface for Continuous Glucose Meter (CGM) oic.r.cgm.samplinginterval Selectable Levels oic.r.selectablelevels Sensor for Continuous Glucose Meter (CGM) oic.r.cgm.sensor Sensor Properties oic.r.sensor.props Signal Strength oic.r.signalstrength Sleep oic.r.sleep Sleep Monitor Atomic Measurement Batch Representation oic.r.sleepmonitor-am Sleep Sensor oic.r.sensor.sleep Smoke Sensor oic.r.sensor.smoke Speech Synthesis oic.r.speech.tts Speed oic.r.speed SpO2 for Pulse Oximeter oic.r.spo2 Status for Continuous Glucose Meter (CGM) oic.r.cgm.status Temperature oic.r.temperature Three Axis Sensor oic.r.sensor.threeaxis Threshold for Continuous Glucose Meter (CGM) oic.r.cgm.threshold Time Period oic.r.time.period Time Stamp oic.r.time.stamp Torque oic.r.torque Touch Sensor oic.r.sensor.touch UV Radiation oic.r.sensor.radiation.uv User ID oic.r.userid User Info for Application Layer oic.r.userinfo Value Conditional oic.r.value.conditional Water Info oic.r.waterinfo Water Sensor oic.r.sensor.water Weight oic.r.weight Window Covering oic.r.windowcovering -
@kubi said in Devices, Alias, Assistenten + Visualisierungen + die Zukunft:
Ich habe mal eine Frage zum Adapter Devices, wie kann ich selbst Aliase zusätzlich anlegen ?
-
@Videonisse said in Devices, Alias, Assistenten + Visualisierungen + die Zukunft:
Have I understood the proposed structure correctly that the Device top level will be called "Alias" and an alias then has a "Function", and below this, it will have one or more "Roles/Types" and these have different "States"?
That is not how I understood it. It is more flexible and linked to the ioBroker way to do things. Currently all aliases have an ID that starts with alias.0. That probalby will stay that way.
The proposed device templates are a thing of an object of type "device", i.e. it describes one physical / logical device. The devices in ioBroker usually have multiple states (which can be sensor readings or ways to control the device). Currently this is all very loose and very different for different device types / manufacturers. The idea of the device templates is to have, as an attribute of the device itself, a list of possible "functions" that such a device can have and with that create a mapping from function to existing states in ioBroker. So that an adapter that creates a visualisation or device for alexa / google home or similar can determine from the device object which states to use to control the device. -
Isn't "Device templates" and (partly) "Alias" just a technical way how to implement the standardized metadata for a Device into ioBroker? I'm not a developer so I don't fully understand what's the best way forward on the technical level. But what I try to understand is the needs of the standardized data; What data and How will this be structured. I'm not sure what has been decided upon already and if the team still wants some feedback. What is the status?
Currently several of mine Adapters has structured the ioBroker Objects into "Devices" and "Channels". Devices and channels can also be tagged with metadata "Roles" and "Functions". Also, the objects for "States" can/shall be tagged with those. So already, a lot of the technical structure is implemented.
As I understand it, currently both Roles and Functions, however, lack details of which group of states that are mandatory as well as are optional to represent, for example, a Light. If this was standardized on all three levels; Device, Channel and State, it should be much easier to programmatically interact with other adapters for automation and visualisation.
An important question must be how to standardize all of those possible Device types and the required data they must include as well as suggested additional Objects/States they may have and in which formats. To use a common Taxonomy and have agreed on a Semantic model should be very important. A lot of work is already invested in the ecosystems from Amazon Alexa, Apple HomeKit and Google Assistant and of course, it's a good idea to copy as much as possible from them. But as they are not complete, I think it would be even more important to use a more open and standardized data model to achieve Semantic interoperability. So far I can see, the most advanced and promising model for the Smart Home is today what OpenConnectivity Foundation can offer as part of their OCF Specification. Of course, if the Working Group Project Connected Home over IP would publish a Semantic specification it would perhaps be even greater, or? But if and when this will happen is hard to tell.
Regarding Semantic model, here is some example from the OCF spec of Device Types and Resource Types respectively:
Source: https://openconnectivityfoundation.github.io/devicemodels/docs/index.html
Source: OCF Spec v.2.2.0 Resource Types -
@Videonisse said in Devices, Alias, Assistenten + Visualisierungen + die Zukunft:
As I understand it, currently both Roles and Functions, however, lack details of which group of states that are mandatory as well as are optional to represent, for example, a Light. If this was standardized on all three levels; Device, Channel and State, it should be much easier to programmatically interact with other adapters for automation and visualisation.
That is exactly the current situation, we have states in some structure of devices and channels associated with roles and they have types and flags of read/write. From all this the type-detector tries to derive a device type. This is quite brittle.
So I understood the proposal to add a description of the device to the device object meta data where a developer can define a device type for the device in question and which states of the device offer which functionality of the device type. So the device-object would describe which device type it is and how to control it / read data from it.Of course those device templates need to be defined, collected and described somewhere. From what I understood, when there is talk about Alexa devices or Google home, then that is not exclusive but a "base set" of devices that should be somehow supported (because integration of those services currently is an important freature for iobroker). If there are definitions of device templates that are a superset of those, then it might be worth having a look.
From what I understood this still is a proposal and has not been decided upon (but I could be wrong there).
