Some time passed by but I just wanted to thank you @guillermo-schimmel , I've finally managed to connect sensors properly (at least one of them).

I had to do some changes based on official documentation, so what I did is I just installed mqtt binding from paperUI, and then added one mysensors.things file with fallowing

Bridge mqtt:broker:mosqbroker "Work Broker" [ host="192.168.1.ip", port="1883", secure=false, username="myuser", password="mypassword", clientID="OPENHAB", startupCheckEnabled=false  ]

Thing mqtt:topic:mosqbroker:ChargingStation_Switch4h_raw_thing "Charging station button" (mqtt:broker:mosqbroker) @ "Home" {
    Channels:
        Type string : ChargingStation_Switch4h_raw_button "Charging station 4h button" [ stateTopic="mygateway1-out/31/4/1/0/16"]
}

and then in my items file I had this

String ChargingStation_Switch4h_raw_converted       "ChargingStation Switch4h"           { channel="mqtt:topic:mosqbroker:ChargingStation_Switch4h_raw_thing:ChargingStation_Switch4h_raw_button"}

and I get the value of the item properly (note I have string for testing, number might be more appropriate here, but that will be fixed another day)

hey @berkseo these look amazing, any estimate when they might be available again as assembled unit?
Any estimate on how long the battery lasts, with lats say update every 15min?
Could these be updated OTA somehow (or directly perhaps)?
I would like to have option to change layout, or perhaps add some other values to it maybe.
They look amazing, I would like several of these in each room for various things displayed

@apl2017 care to share? :)

@guillermo-schimmel said in 💬 OpenHAB:

The 1.b. route: MQTT using new MQTT 2.x binding
The 1.b route. It also works fine, you define the broker via Paper UI and/or files, and you then define every channel by hand, the easier way is via PaperUI.
This is awful.

It looks that I was using 1.a, as this is how I already have items defined from before, f.eks.
Number Temp_03 "Temperatura [%.1f °C]" {mqtt="<[mosquito:mygateway1-out/3/1/1/0/0:state:default]"}

but I do agree, this is a bit... time consuming to figure out which value should be sent when.

To migrate from this to 1.b, I would have to define every channel in the things file?
I am not a fan of PaperUi , and would like to have a official bindings when possible. It is always annoying to update openhab, and I would like to keep it as less complicated as possible.

Do you have an example (or give some tips) on how to go with 1.b route, either via PaperUi, or things file? What do I write there for one, f.eks. temperature-humidity sensor?

I like having good control over each node, so defining each channel should be fine for me, I am just struggling to get started, then I can copy-paste from there :)

Thanks!

thanks @Guillermo-Schimmel , what I have so far is
MQTT Binding from paperUi
MQTT Broker - added from paperUI where I input my ip adress
Then I should add channels from PaperUi as well?
If I try that, only option I have is Publish Trigger. There should I put topic i guess?
Or should I just add Things as you described and something new appears?

I can wait for tutorial if that is easier for you, I have just a few non-vital devices in mysensors.
Thanks again!

hi @Guillermo-Schimmel thanks for the info, I searched for a while but didn't understod what to do with channels. Do you have an example or perhaps a list of the channels that should be added, and what the values are?
Thanks!

@nca78 I used white decorative self adhesive wallpaper, so not sure which plastic you are planing to use, but you can easily test that before mounting I think. If you go for paper/foil, put some one-peace plastic in front of the displays as they (mine) are not perfectly soldered in line, so they are noticeable sa foil will glue to them. Not a big deal for me, but would love "the perfection". But yeah, plastic or some harder material would work awesome I think.

All in all, not difficult project and a very high wow-factor/time-spent value (and waf)

My wife said "I do not want to see "those things""...
Challenge accepted!

(see the gif in action here https://ibb.co/BCbS2Dc )

Ooops, my bad then :( I was pretty sure I checked readme.md file, but apparently I got confused.
Thanks a million!

Thanks @hek it is certainly helpful. However the most powerful information is actually in the description page, about how to use the board, how to wire it up for different use cases etc. I suppose a previous version of the information tab is not available?
If it could be archived (maybe even linked somewhere) it would be really helpful!

Thank you @hek , I think this might be useful feature
I however do not see any data in there, is it something for project owner to allow?
I tried both as guest and as logged inn, I do see the rows, but no data in fields, screenshot:

@sundberg84 nothing special about now, I figured it out based on older projects. But since I still have about dosen of boards, I will probably need documentation few years from now, so was just hoping to have it somewhere easily available :) Like a downloaded pdf or something

Hey @sundberg84 I just saw the new rev.10, congratulations on the upgrade!
I still have a bunch of rev 9, do you happen to have images/manual for previous version somewhere? link or a pdf?
Thanks!

Saw that all other kids cool kids have one, so I installed one kitchen-pc as well.
It is Flytech K757 15'' POS terminal, windows 10 pro, touch screen, 300gb (soon to be ssd) 8gb ram dual core 2,2ghz. Purchased from local "ebay" for around 140 eur.

Now I can make that awesome dinner, once in a full moon, without having to carry and unlock my phone all the time...

If anyone is trying the same, I did it as @mfalkvidd recommended, with several child IDs
Then I basically reset the message if data comes on on first childId, and only append it if data comes on any other sensor, something like

if (message.sensor == messageCHILD1){
  strcpy(newMessage, "       ");                 // we put some spaces in front
  strcat(newMessage, message.getString());    
}else{
  if(curMessage!=""){
    // append existing message to newMessage
     strcpy(newMessage, curMessage);   
   }
  //append rest
  strcat(newMessage, message.getString());
}
			

Note: the code also works with just two sensors, first for reset, and second that only appends data, but I decided to go with four child IDs, in case there is something I am not seeing at the moment.

Thanks everyone for ideas

Thanks! Btw, does anyone have a example of resending of missed messages from OpenHab via Mqtt?
Or retrieving any data at all, I just never managed to get any data from openhab from the node. F.eks., asking what is the time and such thing, do I need to have a rule for each "question" and then reply in response, or as a new call or what?

Hi,
I am building a LED matrix display for displaying some messages from controller. I searched and found some discussion few years ago about its limitation and possible workarounds in sending few messages from gateway and the nodes. Was there any progress on this, or has anyone come with some workaround?
I am using openhab and node-red over mqtt if that helps.
I was considering making small custom logic in node-red that would split the messages and send them with few seconds delay, and then on the node to combine them in a single text, something like:
Message1: |CS| This is some 24 message th
Message2: at is being split over multipl
Message3: e messages

So if node gets message starting with "|CS|" it will delete message from the screen, if not it will just append the message to it

But what if some message gets lost? Or any better suggestions?

Thanks, I tried running it on old laptop, but it was difficult for non-russian speaker to figure things out. And I remember that the app was constantly using around 30% of CPU which kept the fan running all the time (because php was running in infinitive loop).
I switched to domoticz on raspberry, but have now settled on openhab and am very happy with it.

None of them used more then 1-2% cpu on same laptop, and both are very stable (also easy to find documentation for english-speaking user).

Built case for soldering tools, to easily move them out of the way.

Not really, bought it on banggood and asked wife to assemble it (she likes those type of projects, especially if the office might look a tiny bit cleaner) https://www.banggood.com/DIY-Self-assemble-RC-Model-Tools-Case-Screwdriver-Box-Gripper-Package-Plier-Stand-Retro-Style-p-1257252.html?cur_warehouse=CN

Laser cut plywood(or something), looks quite nice I think. I will order few more when they appear in stock.

thanks @parachutesj , I was thinking of something similar as well, sounds much simpler then my initial thought to have several sensors in a line to determine position of the shade in the room... I also like your temperature sensor solution, as that is actually what we would mostly like to react to, especially on the winter.
I have quickly found one solution on the internet, using luminosity sensor http://www.instructables.com/id/A-solar-tracking-automatic-motorized-window-blind-/

I must also deal with "manual override" but I have seen some design patterns for it already, using the "dead switches" / proxy items. And a door that should prevent blinds to go down if doors are open. Should be possible to program in node-red.

And according to my wife, I must fix it all very soon :)

Thanks again, will look more into it.

@nca78 said in What did you build today (Pictures) ?:

"22" board
Looks great, can we get more info about it/link?