Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Videonisse

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    V
    • Profile
    • Following 1
    • Followers 0
    • Topics 3
    • Posts 100
    • Best 5
    • Groups 1

    Videonisse

    @Videonisse

    5
    Reputation
    36
    Profile views
    100
    Posts
    0
    Followers
    1
    Following
    Joined Last Online
    Location Stockholm, Schweden

    Videonisse Follow
    Starter

    Best posts made by Videonisse

    • RE: Fragen an die Entwickler zu Matters

      Jetzt ist es ja so weit, Matter v1.0 ist am 4 Oktober veröffentlicht 😊: https://csa-iot.org/newsroom/matter-arrives/

      Wie denkt eigentlich Ihr core Entwickler über die Zukunft für Matter und ioBroker?

      Home Assistant has schon Entwicklung unterwegs und wird den Funktion als Controller anbieten. Ob auch als Bridge ist mir aber unklar. https://www.home-assistant.io/blog/2022/05/29/matter-in-home-assistant-workshop-announcement/

      Die Standard Dokumente für Matter Version 1.0 ist hier vorhanden:

      Matter 1.0 Core Specification
      Matter 1.0 Application Cluster Specification
      Matter 1.0 Device Library Specification

      Ich hoffe ioBroker wenigstens als Matter Bridge funktionieren kann aber warum nicht auch als Thread Border Router, und noch besser, als Matter Controller.

      posted in ioBroker Allgemein
      V
      Videonisse
    • RE: Devices, Alias, Assistenten + Visualisierungen + die Zukunft

      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.

      2020-10-19 00_10_41-Smart home APIs Google Alexa Homekit.xlsx - Taxonomy mapping.png

      Many thanks for the impressive work with ioBroker and all of the adapters!

      posted in Entwicklung
      V
      Videonisse
    • RE: Test Adapter KNX v1.0.x

      @killroy2 It's better to use 1.1.250 (or a similarly high number) for your IP Gateway.

      As @frankthegreat writes, else you need to manually stop Devices from using the Tunnel addresses and as new devices usually get the first free lowest address automatically, you need to remember to change them or stop this to happen. Then it's easier to use the upper area to avoid those conflicts.

      posted in Tester
      V
      Videonisse
    • RE: Devices, Alias, Assistenten + Visualisierungen + die Zukunft

      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.dots
      

      And 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
      
      posted in Entwicklung
      V
      Videonisse
    • RE: Devices, Alias, Assistenten + Visualisierungen + die Zukunft

      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:

      2020-10-20 12_53_12-OCF Device Type overview - Example Required Resources.png
      Source: https://openconnectivityfoundation.github.io/devicemodels/docs/index.html

      2020-10-20 13_11_27-OCF_Resource_Type_Specification_v2.2.0.pdf - Example Light Dimming.png
      Source: OCF Spec v.2.2.0 Resource Types

      posted in Entwicklung
      V
      Videonisse

    Latest posts made by Videonisse

    • RE: Fragen an die Entwickler zu Matters

      Jetzt ist es ja so weit, Matter v1.0 ist am 4 Oktober veröffentlicht 😊: https://csa-iot.org/newsroom/matter-arrives/

      Wie denkt eigentlich Ihr core Entwickler über die Zukunft für Matter und ioBroker?

      Home Assistant has schon Entwicklung unterwegs und wird den Funktion als Controller anbieten. Ob auch als Bridge ist mir aber unklar. https://www.home-assistant.io/blog/2022/05/29/matter-in-home-assistant-workshop-announcement/

      Die Standard Dokumente für Matter Version 1.0 ist hier vorhanden:

      Matter 1.0 Core Specification
      Matter 1.0 Application Cluster Specification
      Matter 1.0 Device Library Specification

      Ich hoffe ioBroker wenigstens als Matter Bridge funktionieren kann aber warum nicht auch als Thread Border Router, und noch besser, als Matter Controller.

      posted in ioBroker Allgemein
      V
      Videonisse
    • RE: Test Adapter tibber v0.1.x

      @magnus-1 sagte in Test Adapter tibber v0.1.x:

      @michaelnorge na dann schau ich mir das doch mal als erstes an und sehe zu, dass ich das schon mal einbau. komme dann ggf. nochmal zum testen auf dich zurück weil ich selbst hier in DE noch kein pulse habe, sondern über discovergy daten bekomme.

      Ich teste auch gern mit Pulse, ich habe den (Schwedishen?) mit P1 schnittstelle.

      Wegen die sehr hohe stunden-preisen habe ich jetzt gerade nicht Tibber aber benutze immer noch Pulse mit live data. Hätte es gern in ioBroker 🙂

      posted in Tester
      V
      Videonisse
    • RE: Test Adapter KNX v2.x

      @chefkoch009 sagte in Test Adapter KNX v2.x:

      @videonisse Have you seen this object?

      javascript.0.variables.dayTime
      

      Mayby this is, what you're searching for.

      Leider funktioniert es nicht. Ich have mit GA DPT10.001 (Time 3 Byte) und DPT11.001 (Date 3 Byte) probiert.

      b4971018-a939-4a78-92b6-56445616d83e-image.png

      @tontechniker sagte in Test Adapter KNX v2.x:

      @chefkoch009/@videonisse I have a Blockly that sends every minute the Date and Time to a KNX-Object "date" and a KNX-Object "Time".
      The two ojects have also a KNX-Object-Adress (x/x/x), and so the Date and Time are available by the KNX-Bus.

      Ich verstehe dass es mit Blockly funktioniert aber ich möchte nicht das die Werte alle 60 Sekunden Broadcastet werden, sondern nur gesendet wird als Respons zur eine GroupValueRead Anfrage.

      Ist es nicht möglisch mit dem KNX Adapter?

      posted in Tester
      V
      Videonisse
    • RE: Test Adapter KNX v2.x

      How can I create an Object where Direct Link is connected with the current Time/Date? Or has ioBroker such Object in the Object Tree already available?

      It should be used to send the actual Time/date to the KNX bus as a response to a GroupValueRead.

      posted in Tester
      V
      Videonisse
    • RE: Test Adapter KNX v2.x

      @chefkoch009 sagte in Test Adapter KNX v2.x:

      iobroker u knx

      It actually works. The issue was that the button "ADD" for Direct Links was not visible on my screen. I'm using Full HD resolution and the GA-TOOLS GUI lacks a scroll bar so I didn't understand there was another button below "Add new relation".

      8887b934-1d3a-440b-93b8-5f70f67a0347-image.png

      posted in Tester
      V
      Videonisse
    • RE: Test Adapter KNX v2.x

      @chefkoch009 sagte in Test Adapter KNX v2.x:

      Ich gebe einfach mal folgendes Szenaren:

      1. Es gibt einen Sonosplayer und einen KNX-Tastsensor. Nun soll die Taste 1 vom Tastsensor "play" machen und im Display vom Tastsensor soll der Interpret und die Lautstärke angezeigt werden.
        Dazu lege ich eine GA Bsp 5/0/1 "Sonos-play-stopp", eine GA 5/0/2 "Interpret" und eine GA 5/0/3 "Lautstärke" an.

      Nun verknüpfe ich über directLink die 5/0/1 mit Sonos-simpleState, die 5/0/2 mit Sonos-Interpret und die 5/0/3 mit Sonos-Volume.

      Somit werden diese Sachen im KNX abgebildet und umgekehrt, das heisst, wenn ich die Lautstärke über meine Sonos-HandyApp ändere, wird sofort die 5/0/3 aktualisiert und umkehrt, wenn ich einen Wert für Volume in die 5/0/3 schreibe, dann werden die Sonos-States aktualisiert.

      Ich kann nun auch über ein GroupValueRead den verknüpften State abfragen.

      1. mein iobroker soll als Zeitserver für KNX dienen. Dann verknüpfe ich das iobroker object, welches mir die Zeit liefert direkt mit der KNX GA. Wenn sich nun das Object aktualisiert, dann tut es das auch auf dem KNX Bus.

      Ich hoffe das bringt etwas Licht ins Dunkel 😉

      VG
      chefkoch009

      Ich versuche den "DirectLink" funktion zu konfigurieren aber kann nicht die ioBroker Objekte wählen beim Verlinken. Warum kann ich nur andere KNX GAs wählen?

      Adapter version ist 2.0.8

      2022-01-09 16_45_48-instances - iobrokerv3 och 17 sidor till - Privat – Microsoft​ Edge.png

      posted in Tester
      V
      Videonisse
    • RE: Test Adapter KNX v2.x

      @iccube sagte in Test Adapter KNX v2.x:

      @chefkoch009 habe ich gesetzt KNX Musikzimmer.png

      Wenn ich den Wert über die ets abfrage ändere auch den Wert beim dp nur bei einem Neustart des Adapters aktualisiert ert den Wert nicht.

      Ist es die gleiche problem als Issue #162 "GroupValueResponse is ignored"?

      posted in Tester
      V
      Videonisse
    • RE: Test Adapter KNX v2.x

      @klamm-0 sagte in Test Adapter KNX v2.x:

      Wäre natürlich schön, wenn es mit dem V2 funktioniert aber meine eigentliches Problem war ja dass der Wert vom DPT 7.012 nicht angezeigt wird.
      Wäre das denn mit der V2 behoben oder ist das ein anderes Problem?

      Funktioniert bei mir (mit v2.0.3) einwandfrei.

      posted in Tester
      V
      Videonisse
    • 30 Zeitreihendaten mit Line History Chart

      Für mein Heizsystem benötige ich ein Zeitablaufdiagramm (Line History/Time Series Diagram), das Daten von bis etwa 30 verschiedenen Datenpunkten anzeigt.

      Gibt es eine Visualisierung in ioBroker, die damit umgehen kann? Sehen Sie unten den Screenshot, wie meine aktuelle Lösung aussieht.

      Die Daten werden alle 60 Sekunden gespeichert. Heute in MySQL aber in Zukunft in InfluxDB.

      ThermIQ_low.gif

      posted in Visualisierung
      V
      Videonisse
    • RE: Aus JSON 136 Datenpunkte erzeugen

      @homoran Ja, ich habe normale weise 60% frei von 2GB ram. Aber mit die letzte Code Änderung von @paul53 bleibt javascript.js auf ~245MB

      Alles ist jetzt stabil und keine Fehler in log.

      posted in Blockly
      V
      Videonisse
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo