MMM-OpenhabFloorplan

[paphko]

@schummi84 Please open http://192.168.2.122:8080/rest/items to get a (huge) list of all items that are available via the REST API. I realized that items that are automatically created via the Paper UI get an auto-generated name. However, you should be able to find them in the huge list of all items by searching the item labels.

For example, the Paper UI created yahoo weather item ‘Luftfeuchtigkeit’ has item name ‘yahooweather_weather_berlin_humidity’ on my setup. Then the item URL for such an item would be: http://192.168.2.122:8080/rest/items/yahooweather_weather_berlin_humidity

[schummi84]

@paphko thanks for the hint. I will try it this afternoon and come back with the result.

[schummi84]

@paphko I tried you hint with the following result:

[{"link":"http://192.168.2.122:8080/rest/items/ExtendedColorLight_Color","state":"ON","type":"Switch","name":"ExtendedColorLight_Color","label":"Color","category":"ColorLight","tags":[],"groupNames":[]},{"link":"http://192.168.2.122:8080/rest/items/SOFA_Switch","state":"ON","type":"Switch","name":"SOFA_Switch","label":"Color","category":"ColorLight","tags":[],"groupNames":[]},{"link":"http://192.168.2.122:8080/rest/items/SOFA_Color","state":"274,87,24","type":"Color","name":"SOFA_Color","label":"Color","category":"ColorLight","tags":[],"groupNames":[]},{"link":"http://192.168.2.122:8080/rest/items/SOFA_ColorTemperature","state":"0","type":"Dimmer","name":"SOFA_ColorTemperature","label":"Color Temperature","category":"ColorLight","tags":[],"groupNames":[]}]

Basically it shows two items at the moment, both created with PaperUI. I still don’t undertsand why the file based setup/configuration is not working. I wouldn’t mind if th efloorplan integration would work but still doesn’t. I added the two items to the config.js but without success. I checked the pm2 logs to see the follwoing error:

0|mm       | TypeError: Cannot read property 'statusCode' of undefined
0|mm       |     at Request._callback (/home/pi/MagicMirror/modules/mmm-openhabfloorplan/node_helper.js:38:65)
0|mm       |     at self.callback (/home/pi/MagicMirror/node_modules/request/request.js:186:22)
0|mm       |     at emitOne (events.js:96:13)
0|mm       |     at Request.emit (events.js:188:7)
0|mm       |     at Request.onRequestError (/home/pi/MagicMirror/node_modules/request/request.js:845:8)
0|mm       |     at emitOne (events.js:96:13)
0|mm       |     at ClientRequest.emit (events.js:188:7)
0|mm       |     at Socket.socketErrorListener (_http_client.js:308:9)
0|mm       |     at emitOne (events.js:96:13)
0|mm       |     at Socket.emit (events.js:188:7)

Note: I already modified the mmm-openhabfloorplan.js according to your other thread. Unfortunatelly I cannot attach the files here - If required I can post the sourcecode.

Any idea ?

Cheers
Schummi

[paphko]

@schummi84 I’ll test that as soon as I find some time - maybe tomorrow, maybe next week.

[paphko]

@schummi84 @YourhighnessLeender : OH2 has a slightly different JSON format in items response which I had to deal with. Please pull latest changes, set new ‘version’ option is your config, and try again.

[schummi84]

@paphko Thank you very much for your effort. I’ll give it a try and report on the outcome!

[schummi84]

@paphko With you Update everything works as expected!!!

Again, thank you very much for your help and the effort you put in your module!
:grinning:
Best regards
Schummi

[teddy]

Hi, I have problems and need help. What am I doing wrong?

[zdenek]

Hi all
sorry for stupid question - do I need to have another RPi to run OpenHAB, or it can by on the same?

thanks Zdeněk

[paphko]

@teddy Sorry for the late reply, I didn’t check the forum for quite a while. But from your post, I don’t know how to help. It’s as if you say “my car is not working, what am I doing wrong?”
If you want some help, please check logs for errors and post them here.

@zdenek It should be possible to run openhab on the same RPi. I didn’t try it but I don’t see any reason why it should not work. You only have to change the port of one of them because both use 8080 by default.