Hop til indhold

Leaderboard

Popular Content

Showing content with the highest reputation on 05-07-2018 in all areas

  1. Some reason Google translator translate pretty "bad" english, so it's pretty hard to fully understand what you try to reach on your example. Anyhow, following configuration is read only from openHAB perpective, meaning that only timer value change in IHC is updated to openHAB item. Number U_TimerVand "Timerværdi for vanding [%.0f]" <time> {ihc="<0x1102410"} So if you change the U_TimerVand item value, it will not be updated to IHC. When every timer value is changed in IHC side (timer is running or you change it via service view), value is updated to openHAB item. Timers are in millisecond resolution in IHC, so I guess that, if timer is running, you will get a lot of updates. Maybe not every millisecond, but very often. So most probably it's not wise to sync timer value between openHAB and IHC. If you just want to change the timer value from openHAB to IHC, you could make it write only (>). If you want to know when timer is expired (counted to 0), your most probably should change the IHC code so that when timer is expired some kind of flag is set, which change is then syncronized to openHAB. Syntax explanation: Syncronization in both directions (IHC <-> openHAB): Number U_TimerVand "Timerværdi for vanding [%.0f]" <time> {ihc="0x1102410"} Read only (IHC -> openHAB): Number U_TimerVand "Timerværdi for vanding [%.0f]" <time> {ihc="<0x1102410"} Write only (openHAB -> IHC): Number U_TimerVand "Timerværdi for vanding [%.0f]" <time> {ihc=">0x1102410"}
    1 point
This leaderboard is set to København/GMT+01:00
×
×
  • Tilføj...

Important Information

Privatlivspolitik og We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

1200x630bb.png

ok