@hmerk the semanticHomeMenu Part 3 - Security [4.0.0.0;4.9.9.9]
is installed but the actual widget is not available under widgets, please see screenshots.
On openhab 4.2.2
Did you reload the app after installation ? Please try and clear your browser cache.
If it shows up as installed, I donāt have a clue. Anything suspicious in the logs ??
No, this is a brand new VM installation of OpenHAB 4.2.2. I ended up adding the security menu manually via the widget page.
I dont understand, i tried different browsers, rebooted, cleared browser cache, etc.
When i go to Pages, i look for the widget and (besides the manual one i installed), when i click on SemanticHomeMenu, this is what i see and its not configurable either:
can you try to reproduce on a fresh install ?
Will try to reproduce later.
It is not configurable, you need to create the items described in the post!
The aim of the semanticHomeMenu project is to create a complete home with near to zero config. Therefore Items have to be named and tagged like described.
I forgot to mention that it is not configurable in the SemanticHomeMenu that i added (shown in the screenshot above), but since i manually added the widget via github, i was able to find and configure it that way.
i started from scratch now again, and all i installed from marketplace is semanticHomeMenu Part 3 - Security and the widget is not even found when i go to add it under Pages.
The only widget found there is this:
Does both the Main and Security need to be installed just to use Security Alarm? ? This wasnt the case with OpenHAB 4.1.2
I could reproduce your issue even with installed Main widget. As there havenāt been any changes for about a year, there is nothing wrong with the widget or the post. Something must have changed in mainUI causing this.
@florian-h05 Could you imagine, why the security widget cannot be installed through marketplace any more, but can be added via copy and paste from the raw text ??
Thanks. Until that gets fixed i will try what i need to do manually.
Now im having a different issue.
Can you help me with creating a simple rule in pressing one of these buttons?
I created a simple rule with my alarm system and each time i press any of the buttons on the widget, it just sends the NULL Value as a command.
Ive created all the items you specified in the Security Widget and have configured the Widget with the Security Group.
Here is my Rule:
Each time i press any button after this rule the events log says:
[openhab.event.ItemCommandEvent ] - Item 'securitySystem_mode' received command NULL
and the openhab log says:
[e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: undefined
This might be something stupidly obvious but i cannot seem to find the issue? Im unable to create a Rule to press one of those buttons on the security widget, the command i want is not going through.
Just for reference, im just trying to get the Arm Home and the Disarm to work for now, nothing too complicated, yet i cant get it right
I donāt have any of the widgets installed currently and I just tried to install the Security widget. It installed the keypad widget instead. It looks like, in your security widget post because the link to the yaml for the keypad:
comes before the actual link to the security widget, that the add-on store is accessing the keypad code instead.
The semanticHomeMenu_Security Widget needs the semanticHomeMenu_Security_Keypad widget and three items.
- securitySystem [group]
- securitySystem_mode [String Item, member of securitySystem ]
- securitySystem_PIN [String Item, member of securitySystem ]
You need to change the value of securitySystem_PIN through API explorer, as this is the reference to be checked when a PIN is entered.
As the securitySystem_mode Item can have three states (armed-away, armed-home and disarmed)
you will need at least two different rules, one for arming and one for disarming.
Disarming trigger:
triggers:
- id: "1"
configuration:
itemName: securitySystem_mode
state: disarmed
type: core.ItemStateChangeTrigger
Arming trigger:
triggers:
- id: "1"
configuration:
itemName: securitySystem_mode
previousState: disarmed
type: core.ItemStateChangeTrigger
Note the difference here, using previousState instead of state.
Within the rule you can then check if the state i armed-away or armed-home to send different commands to according Items.
Thanks for checking Justin. Thatās strange, as it worked before and nothing has changed.
In general, the Tag āRessourceā should be used. I will try to reorde the post and see if that helpsā¦
Edit: I moved the Keypad part below the Ressources link and will check tomorrw if this solves the issueā¦
I couldnāt get the security widget to work as well and eventually worked out that itās only installing the keypad.
I tried making a widget with the security system yaml code and it sort of worked, but show up 3x times in the UI
I donāt understand the code though so donāt know how to integrate it properly without the installer.
Iām enjoying the UI though thanks.
Well, there is nothing magical installing the widgets through the UI. It is the same like copying the complete code and pasting it into a new widget in the developer tools. Just a bit more user friendly.
Nothing will be configured or set up.
What you really need is to have the Items described in the posts.
Therefore the examples can be copied and used for āimport Items from textā.
For the security widget, you then need to add a default PIN to the according Item, so the keypad can check if the correct PIN was entered.
The real magic then happens within your individual rules, triggered by changes of the mode Item.
Thatās all.
BTW, you should have reported earlier that installation through the UI is not working.
If we donāt know it is not working, we cannot fix it
And it should be fixed by nowā¦.
Yes I didnāt realise it hadnāt installed, I havenāt set up the security system yet.
Iām just adding a room at a time with the correct naming and couldnāt work out why the contact sensors were not showing up in the ui until I came across this post.
Thank you so much, this seems to work now.
Problem still exists, i tried to re-install the addon (after removing all the semantic addons and clearing cache, etc.) its still install the keypad only. Did you try?
Tried just now and the fix was not working. Did another change to the post and will try again later.