Skip to content

Ditmar Rose

My feedback

3 results found

  1. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Ditmar Rose commented  · 

    Aus deviceList.cgi
    <device name="Sen_Wasserstand_Regentonne" address="001FDD89B72162" ise_id="65819" interface="HmIP-RF" device_type="HmIP-FCI1" ready_config="true">
    <channel name="Sen_Wasserstand_Regentonne:0" type="30" address="001FDD89B72162:0" ise_id="65820" direction="UNKNOWN" parent_device="65819" index="0" group_partner="" aes_available="false" transmission_mode="AES" visible="true" ready_config="true" operate="true"/>
    <channel name="Sen_Wasserstand_Regentonne:1" type="28" address="001FDD89B72162:1" ise_id="65843" direction="SENDER" parent_device="65819" index="1" group_partner="" aes_available="false" transmission_mode="AES" visible="true" ready_config="true" operate="true"/>
    </device>

    Aus deviceTypeList.cgi
    <deviceType name="HmIP-FCI1" description="HmIP-FCI1" thumbnailPath="/config/img/devices/50/182_hmip-fci1_thumb.png" imagePath="/config/img/devices/250/182_hmip-fci1.png"/>

    Aus stateList.cgi:
    <device name="Sen_Wasserstand_Regentonne" ise_id="65819" unreach="false" config_pending="false">
    <channel name="Sen_Wasserstand_Regentonne:0" ise_id="65820" index="0" visible="true" operate="true">
    <datapoint name="HmIP-RF.001FDD89B72162:0.CONFIG_PENDING" type="CONFIG_PENDING" ise_id="65821" value="false" valuetype="2" valueunit="" timestamp="1700851090" operations="5"/>
    <datapoint name="HmIP-RF.001FDD89B72162:0.DUTY_CYCLE" type="DUTY_CYCLE" ise_id="65825" value="false" valuetype="2" valueunit="" timestamp="0" operations="5"/>
    <datapoint name="HmIP-RF.001FDD89B72162:0.LOW_BAT" type="LOW_BAT" ise_id="65827" value="false" valuetype="2" valueunit="" timestamp="0" operations="5"/>
    <datapoint name="HmIP-RF.001FDD89B72162:0.OPERATING_VOLTAGE" type="OPERATING_VOLTAGE" ise_id="65831" value="0.000000" valuetype="4" valueunit="" timestamp="0" operations="5"/>
    <datapoint name="HmIP-RF.001FDD89B72162:0.OPERATING_VOLTAGE_STATUS" type="OPERATING_VOLTAGE_STATUS" ise_id="65832" value="0" valuetype="16" valueunit="" timestamp="0" operations="5"/>
    <datapoint name="HmIP-RF.001FDD89B72162:0.RSSI_DEVICE" type="RSSI_DEVICE" ise_id="65833" value="0" valuetype="16" valueunit="" timestamp="0" operations="5"/>
    <datapoint name="HmIP-RF.001FDD89B72162:0.RSSI_PEER" type="RSSI_PEER" ise_id="65834" value="0" valuetype="16" valueunit="" timestamp="0" operations="5"/>
    <datapoint name="HmIP-RF.001FDD89B72162:0.UNREACH" type="UNREACH" ise_id="65835" value="false" valuetype="2" valueunit="" timestamp="0" operations="5"/>
    <datapoint name="HmIP-RF.001FDD89B72162:0.UPDATE_PENDING" type="UPDATE_PENDING" ise_id="65839" value="false" valuetype="2" valueunit="" timestamp="1700851090" operations="5"/>
    </channel>
    <channel name="Sen_Wasserstand_Regentonne:1" ise_id="65843" index="1" visible="true" operate="true">
    <datapoint name="HmIP-RF.001FDD89B72162:1.PRESS_LONG" type="PRESS_LONG" ise_id="65844" value="" valuetype="2" valueunit="" timestamp="0" operations="4"/>
    <datapoint name="HmIP-RF.001FDD89B72162:1.PRESS_LONG_RELEASE" type="PRESS_LONG_RELEASE" ise_id="65845" value="" valuetype="2" valueunit="" timestamp="0" operations="4"/>
    <datapoint name="HmIP-RF.001FDD89B72162:1.PRESS_LONG_START" type="PRESS_LONG_START" ise_id="65846" value="" valuetype="2" valueunit="" timestamp="0" operations="4"/>
    <datapoint name="HmIP-RF.001FDD89B72162:1.PRESS_SHORT" type="PRESS_SHORT" ise_id="65847" value="" valuetype="2" valueunit="" timestamp="0" operations="4"/>
    <datapoint name="HmIP-RF.001FDD89B72162:1.STATE" type="STATE" ise_id="65848" value="false" valuetype="2" valueunit="" timestamp="0" operations="5"/>
    </channel>
    </device>

    Ditmar Rose shared this idea  · 
  2. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Ditmar Rose supported this idea  · 
  3. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Ditmar Rose supported this idea  · 
    An error occurred while saving the comment
    Ditmar Rose commented  · 

    Hier das XML zum fraglichen Bewegungsmelder Kanal 3:
    Der UI-Wert ist "value="23.800000" ".

    <channel name="BewM_Küche:3" ise_id="63939" index="3" visible="true" operate="true">
    <datapoint name="HmIP-RF.00319F298AB44C:3.CURRENT_ILLUMINATION" type="CURRENT_ILLUMINATION" ise_id="63940" value="0.000000" valuetype="4" valueunit="" timestamp="0" operations="5"/>
    <datapoint name="HmIP-RF.00319F298AB44C:3.CURRENT_ILLUMINATION_STATUS" type="CURRENT_ILLUMINATION_STATUS" ise_id="63941" value="0" valuetype="16" valueunit="" timestamp="0" operations="5"/>
    <datapoint name="HmIP-RF.00319F298AB44C:3.ILLUMINATION" type="ILLUMINATION" ise_id="63942" value="23.800000" valuetype="4" valueunit="" timestamp="1699608755" operations="5"/>

    An error occurred while saving the comment
    Ditmar Rose commented  · 

    Nach einer Analyse von Jens Maus Hier sein Kommentar:
    Das "Problem" wird sein: Die WebUI zeigt den Wert des ILLUMINATION und nicht CURRENT_ILLUMINATION Datenpunktes an, da der ILLUMINATION Datenpunkt den Wert beinhaltet der über einen gewissen Zeitraum gemittelt wird. Diese Mittelung kann man in den Geräteeinstellungen des jeweiligen Gerätes einstellen/modifizieren und dann erhält ILLUMINATION eben den entsprechenden gemittelten Wert.

    Problem ist/wird sein das TinyMatic einfach immer nur den Wert des CURRENT_ILLUMINATION Datenpunkten nutzt/anzeigt. Es sollte aber stattdessen ILLUMINATION nutzen damit die Geräteeinstellungen entsprechend mit berücksichtig werden.

    Ditmar Rose shared this idea  · 

Feedback and Knowledge Base