Dscalarm initialize at startup

[Zoltan_Varady]

If I see it right dsc binding first initialize item states at startup to off ,then read the real states. Is this normal or I have anything badly ?
When partition is armed , my rule send me notification .
After restart OH the item is first initialized to OFF , then go to real state

From event logs:

2017-02-12 00:25:50.069 [ItemStateChangedEvent ] - PARTITION1_ARMED changed from NULL to OFF.
.
.
2017-02-12 00:25:55.934 [ItemStateChangedEvent ] - PARTITION1_ARMED changed from OFF to ON
.
.

Because this reason my rule is triggered on every startup ,and I get notification needlessly (with OH1 dont have a problem) :

rule “Partition1Armed”

when
Item PARTITION1_ARMED changed from OFF to ON
then
Notify_Warn.postUpdate(“MyHome is armed.”)
end

[Zoltan_Varady]

My rule works as I wanted , with instructions from rlkoshak :

What is the best method to start executing the rules when all bindings are loaded

I really hate polling rules so instead of @bajan’s suggestion, which I don’t think would work in all cases, I would do the following: Create a Switch Item which will act as a flag indicating that the system is starting In all of your rule that you want to prevent from running until your bindings have finished loading add a check to make sure that Item’s state is OFF Create a system started triggered rule that sets the Item to ON, then sets a timer for however long you need to ensure that all t…

rule "System Started"
when
    System started
then
    SystemStarting.sendCommand(ON)
    startedTimer = createTimer(now.plusSeconds(30), [| SystemStarting.sendCommand(OFF)])
end



rule "Partition1Armed"

when
    Item PARTITION1_ARMED changed from OFF to ON 
    
then
    if ( SystemStarting.state == OFF ) {
         Notify_Warn.postUpdate("House Armed.")
    }
end

Thanks