Mqtt 2.5 updating items

[matt_shepherd]

Hi guys,

I have successfully updated my sonoff switches, temp sensors etc to the new mqtt 2.5 format. Now I would like to update my security system, PIR and contact switches (although there’s nothing wrong with my old mqtt items and config)

Here are my original cytech.items

cytech.items

Contact	Kitchen_PIR	      "Kitchen Motion    <motion>     (SecuritySystem         {mqtt="<[mosquitto:comfort2/input2:state:MAP(openclosed.map)]"}

And this is what I’m trying to update to, but I’m getting a bit confused with the mappings part?

Contact	Kitchen_PIR	      "Kitchen Motion"     <motion>     (SecuritySystem)        {channel="mqtt:topic:comfort2:input2:motion"}

New things file

Bridge mqtt:broker:comfort2 "comfort2" @ "Security System" [ host="xxxxx", port=1883, secure=false, retain=false, username="xxxxx", password="xxxxx", qos=0, keep_alive_time=30000, reconnect_time=60000 ]
{
    // Kitchen PIR
    Thing topic input2 "Kitchen PIR" @ "Security System" {
    Channels:
        Type contact : Motion       "Motion"                [stateTopic="stat/input2/motion", transformationPattern = "MAP:openclosed.map"]
    }

}

Any help will be much appreciated

Cheers

[Thedannymullen (Danny mullen)]

I know I am not answering your question, but I notice this.

@matt_shepherd

Bridge mqtt:broker:comfort2 “comfort2” @ “Security System” [ host=“xxxxx”, port=1883, secure=false, retain=false, username=“xxxxx”, password=“xxxxx”, qos=0, keep_alive_time=30000, reconnect_time=60000 ] {

For your sonoff items do you have this line in their file also? Generally you only want one bridge assuming the broker is the same broker.

I put my bridge connection in one file then you can divide things into separate files.

On your mapping I believe the map goes in the things file as you have it. Is it not working properly?

[H102 (CM6.5 H102)]

Try removing the spaces for the transformation.

Example:

Thing topic input2 "Kitchen PIR" @ "Security System" {
    Channels:
        Type contact : Motion       "Motion"                [stateTopic="stat/input2/motion", transformationPattern="MAP:openclosed.map"]
    }

I have similar devices that are working and the spaces are the only difference I’ve noticed.

[H102 (CM6.5 H102)]

@matt_shepherd: Also it’s recommended to use PaperUI for Things to help with syntax errors but either way will work.

You can migrate your Things to PaperUI via REST API, here is an excellent post, with pictures, that will guide you. The first one took a few minutes but after that it’s a breeze.

Migrating from text files to Paper UI for Things using REST API

The first place to start is to install the REST API Docs. It’s under the Misc tab in PaperUI. They are docs so using it should be pretty self explanatory. If not please ask and we can try to answer. You will scroll down to the Things section, click it and it will open up with all the Things API calls. [image] The two circled end points are the ones you care about. Look at the text to the right, it tells you what the endpoint does. First get the Thing. Click on that row and a form will ope…

[matt_shepherd]

So am i correct in thinking that the rest api doc is a tool for helping you right items files? I was wanting to update my items and things so i can integrate it better with the Alexa skill.

[H102 (CM6.5 H102)]

The link was for migrating your Things file to PaperUI. It’s still recommended to use files for items but the correct syntax for the channel can be retrieved from PaperUI and no having to guess.

In the example item I posted above the channel info was copied straight from PaperUI. All the other info is left to you for however you like…except the item type e.g. Switch, Contact, Dimmer, etc…

I’m not the best at explanations in text so I made a bit of sense. If not let me know and I’ll try again.

EDIT: Forgot I didn’t post an item example.

Item:

Switch CouchLight "Couch Light" <light>  ["Lighting"]  { channel="mqtt:topic:pibroker:sonoff2:power" }

From PaperUI you can see the channel info that I copied.