ngy
Junior Member
Posts: 58
|
Post by ngy on Feb 28, 2018 15:41:04 GMT
Hi papa, thanks for the wonderful layout and documentation of all the different threads and organizing them so a beginner like me can get started. I'm a mechanical engineer, but electronics/programming has always been a hobby/interest. I've ordered some parts to start off with and going to try this out in the upcoming months.
Thanks again!
|
|
|
Post by papa on Feb 28, 2018 17:33:23 GMT
Welcome, ngy. I hope you noticed my recommendations of where to start if you are a beginner. I suggest beginners start with an ESP8266 device or an Ethernet Node (they do not require a Gateway to communicate with OpenHAB). Or if you are committed to starting with RFM69 Gateway & Node, I recommend you start with this thread that guides you through the most basic RFM69 Network Building an RFM69 Home Automation Network (Beginners ??)
Also OpenHAB Home Automation Overview - RFM69, ESP8266 & Ethernet is my best introduction to the approaches & the recommendations.
Note: The graphic maps in the introduction thread do not include the Ethernet node. However that node functions similar to the ESP8266 WiFi Node, just with an Ethernet cable connection instead of wireless WiFi connection.
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Feb 28, 2018 20:40:05 GMT
Welcome, ngy. I hope you noticed my recommendations of where to start if you are a beginner. I suggest beginners start with an ESP8266 device or an Ethernet Node (they do not require a Gateway to communicate with OpenHAB). Or if you are committed to starting with RFM69 Gateway & Node, I recommend you start with this thread that guides you through the most basic RFM69 Network Building an RFM69 Home Automation Network (Beginners ??)
Also OpenHAB Home Automation Overview - RFM69, ESP8266 & Ethernet is my best introduction to the approaches & the recommendations.
Note: The graphic maps in the introduction thread do not include the Ethernet node. However that node functions similar to the ESP8266 WiFi Node, just with an Ethernet cable connection instead of wireless WiFi connection.Hi papa, Yes, I noticed the recommendations to start with ESP8266, but given what I am trying to achieve, I have no problems going straight to RFM69 (I found this forum from Eric's instructable). I already have the raspberry pi running openHABian, and just waiting for my buono unos to arrive to get started on the gateway. Thanks for pointing me in the right direction! I will update as I get my components. I did notice a new board out, the Massduino by the same company as the Buono Uno boards. Have you tried any of it for additional cost savings?
|
|
|
Post by papa on Feb 28, 2018 21:16:23 GMT
ngy: "I already have the raspberry pi running openHABian." papa: In order to do this forum's projects,
Give your openhabian Pi a static IP address.
Then be sure you do the following in openhabian:
1) Install Mosquitto (MQTT message broker) 2) Enable Legacy 1.x Bindings 3) In addons, install MQTT Binding (which is a 1.x binding) which will create mqtt.cfg in openhabian's configuration/services folder
4) In services/mqtt.cfg, add these lines, adapting the first line to your situation: mosquitto.url=tcp://[ IP address or name of computer hosting Mosquitto ]:1883 mosquitto.clientId=openhab
^^ The above means ... If Mosquitto's host computer has an IP of 192.168.1.69, your first entry could be mosquitto.url=tcp://192.168.1.69:1883 If Mosquitto's host computer has a name of Dell, your first entry could be mosquitto.url=tcp://Dell:1883========================================== ngy "I did notice a new board out, the Massduino by the same company as the Buono Uno boards. Have you tried any of it for additional cost savings?" papa: I have not tried the Massduino. The Massduino seems to have similar specs as the Buono Uno. Only differences I noticed: microprocessor, 12 bit vs 10 bit ADC resolution, & that Massduino shares 1kb EEPROM with flash memory. So the Massduino may be OK for this forum's projects. If you try Massduino, please report your results on this forum.
|
|
|
Post by papa on Feb 28, 2018 21:34:29 GMT
ngy, I moved our conversation here. I prefer that we continue here & leave the Success thread, which has some outdated information.
|
|
|
Post by greginkansas on Mar 1, 2018 0:36:15 GMT
Also these give a fast start anarduino.com/ I use about 10 of them, good luck
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Mar 1, 2018 5:20:03 GMT
ngy: "I already have the raspberry pi running openHABian." papa: In order to do this forum's projects,
Give your openhabian Pi a static IP address.
Then be sure you do the following in openhabian:
1) Install Mosquitto (MQTT message broker) 2) Enable Legacy 1.x Bindings 3) In addons, install MQTT Binding (which is a 1.x binding) which will create mqtt.cfg in openhabian's configuration/services folder
4) In services/mqtt.cfg, add these lines, adapting the first line to your situation: mosquitto.url=tcp://[ IP address or name of computer hosting Mosquitto ]:1883 mosquitto.clientId=openhab
^^ The above means ... If Mosquitto's host computer has an IP of 192.168.1.69, your first entry could be mosquitto.url=tcp://192.168.1.69:1883 If Mosquitto's host computer has a name of Dell, your first entry could be mosquitto.url=tcp://Dell:1883========================================== ngy "I did notice a new board out, the Massduino by the same company as the Buono Uno boards. Have you tried any of it for additional cost savings?" papa: I have not tried the Massduino. The Massduino seems to have similar specs as the Buono Uno. Only differences I noticed: microprocessor, 12 bit vs 10 bit ADC resolution, & that Massduino shares 1kb EEPROM with flash memory. So the Massduino may be OK for this forum's projects. If you try Massduino, please report your results on this forum. Hi papa, great, i've downloaded the mosquitto binding, enabled the legacy binding, and added the two lines to mosquitto. now it just looks like i'm waiting for my arduino + ethernet shield + RFM69 to come in! I've also ordered a few massduino boards to try out and see how they will work as end nodes.
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Mar 22, 2018 16:26:06 GMT
So my massduino boards came in, and they seem to operate just fine, based on my few basic sketches I uploaded to it. Looks like we have an even cheaper option for creating nodes!
|
|
|
Post by papa on Mar 22, 2018 17:56:37 GMT
Another Possible Arduino Compatible for Nodesngy "I did notice a new board out, the Massduino by the same company as the Buono Uno boards. Have you tried any of them for additional cost savings?" papa: I have not tried the Massduino. The Massduino seems to have similar specs as the Buono Uno. Only differences I noticed: microprocessor, 12 bit vs 10 bit ADC resolution, & that Massduino shares 1kb EEPROM with flash memory. So the Massduino may be OK for this forum's projects.ngy: "my massduino boards came in, and they seem to operate just fine, based on my few basic sketches I uploaded to it. Looks like we have an even cheaper option for creating nodes!" papa: Good to hear, ngy. Keep us posted on how the massduinos perform, especially when you put larger demands on them. I'll post your findings in the Sources for Arduinos, sensors, etc. thread.
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Apr 4, 2018 14:33:12 GMT
ngy: "I already have the raspberry pi running openHABian." papa: In order to do this forum's projects,
Give your openhabian Pi a static IP address.
Then be sure you do the following in openhabian:
1) Install Mosquitto (MQTT message broker) 2) Enable Legacy 1.x Bindings 3) In addons, install MQTT Binding (which is a 1.x binding) which will create mqtt.cfg in openhabian's configuration/services folder
4) In services/mqtt.cfg, add these lines, adapting the first line to your situation: mosquitto.url=tcp://[ IP address or name of computer hosting Mosquitto ]:1883 mosquitto.clientId=openhab
^^ The above means ... If Mosquitto's host computer has an IP of 192.168.1.69, your first entry could be mosquitto.url=tcp://192.168.1.69:1883 If Mosquitto's host computer has a name of Dell, your first entry could be mosquitto.url=tcp://Dell:1883========================================== ngy "I did notice a new board out, the Massduino by the same company as the Buono Uno boards. Have you tried any of it for additional cost savings?" papa: I have not tried the Massduino. The Massduino seems to have similar specs as the Buono Uno. Only differences I noticed: microprocessor, 12 bit vs 10 bit ADC resolution, & that Massduino shares 1kb EEPROM with flash memory. So the Massduino may be OK for this forum's projects. If you try Massduino, please report your results on this forum. hi papa, i noticed that in all the .cfg files, everything has a # in front. does that mean everything is commented out? should I be adding a # to 3, or should I be removing the # for 1 and 2? following your instructions above, is the following correct? 1) in openHAB-conf/services/addon.cfg: #remote = true 2) in openHAB-conf/services/addon.cfg: #binding = mqtt1 3) in openHAB-conf/services/mqtt.cfg: mosquito.url=tcp://10.0.0.10:1883 mosquito.clientId=openhab
thanks!
|
|
brump
Junior Member
Posts: 81
|
Post by brump on Apr 4, 2018 15:18:20 GMT
Hi Ngy, did you install mqtt binding? Accessing http: // localhost: 8080 -> paperUi -> bindings -> mqtt. Note: Remember that you must authorize the installation of bindings 1.x.
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Apr 4, 2018 15:19:51 GMT
Hi Ngy, did you install mqtt binding? Accessing http: // localhost: 8080 -> paperUi -> bindings -> mqtt. Note: Remember that you must authorize the installation of bindings 1.x. hi brump, yes i did. i installed it, and also included legacy 1.x bindings in paper ui->configuration->system->add-on management
|
|
brump
Junior Member
Posts: 81
|
Post by brump on Apr 4, 2018 15:35:08 GMT
Configure mqtt binding on OH2: Find the file and open: mqtt.cfg mosquitto.url=tcp://localhost:1883 mosquitto.clientId=openhab mosquitto.retain=true < edit by papa, see below.mosquitto.async=false Note: : # is used for a comment. If you want to use the configuration, remove #.
papa, update Dec. 10, 2018: brump, ngy & I discovered that mosquitto.retain=true can cause issues. See the discussion starting at the end of this post. Especially see this post including rikoshak's insights.
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Apr 4, 2018 17:42:39 GMT
1) so I have the raspberry pi set up, mqtt binding installed, and made the changes to both the .cfg files. 2) I also have the arduino with ethernet shield hooked up with the gateway ino flashed on (with my IP settings, mac settings, mqtt server settings
but when I hooked it up, I am getting a 'no link' message in the serial monitor. I can verify both my mqtt server (raspberry pi) IP is 10.0.0.10, and my arduino gateway is 10.0.0.11.
What did I miss?
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Apr 4, 2018 18:12:43 GMT
also, both are connected to the same router, both have static IPs set.
|
|
brump
Junior Member
Posts: 81
|
Post by brump on Apr 4, 2018 18:28:36 GMT
Do you use a switch or router?
Is your gateway configured for ip 10.0.0.10 (Ip reserved for your raspberry, mqtt)?
In RFM_MQTT_GW_25.ino Lines 77, 78. byte mqtt_server [] = {10, 0, 0, 10}; // MQTT broker address (Mosquitto) ip byte [] = {10, 0, 0, XXX}; // Gateway address (if DHCP fails)
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Apr 4, 2018 18:32:06 GMT
it's a router, not a switch.
router is 10.0.0.1 raspi is 10.0.0.10 arduino is 10.0.0.11
all IPs are reserved and static.
in the ino, // Ethernet settings byte mac[] = { 0xDE, 0xAD, 0xBE, 0xEF, 0xBA, 0xBE }; // Assigns Gateway's MAC address for Ethernet byte mqtt_server[] = { 10, 0, 0, 10 }; // IP (local network address) of computer hosting MQTT service byte ip[] = { 10, 0, 0, 11 }; // default IP for this Gateway if DHCP does not assign it
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Apr 4, 2018 18:32:55 GMT
wondering in the mqtt.cfg, do i need to put in the username/pwd?
|
|
brump
Junior Member
Posts: 81
|
Post by brump on Apr 4, 2018 19:35:30 GMT
wondering in the mqtt.cfg, do i need to put in the username/pwd? It´s not necessary. My mqtt.cfg only contains url and clientid. Your mqtt service are running perfectly?
|
|
brump
Junior Member
Posts: 81
|
Post by brump on Apr 4, 2018 19:40:29 GMT
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Apr 4, 2018 21:51:18 GMT
wondering in the mqtt.cfg, do i need to put in the username/pwd? It´s not necessary. My mqtt.cfg only contains url and clientid. Your mqtt service are running perfectly? ha! that was it. i installed the MQTT bindings and everything, but i never installed mosquitto! I just assumed it comes with openhabian. I installed it via 'sudo openhabian-config' -> optional components, and boom. it works now. thanks!
|
|
brump
Junior Member
Posts: 81
|
Post by brump on Apr 4, 2018 22:36:57 GMT
You're welcome!
Glad to have helped you!
|
|
|
Post by papa on Apr 5, 2018 11:48:35 GMT
ngy: "i never installed mosquitto! I just assumed it comes with openhabian. I installed it via 'sudo openhabian-config' -> optional components, and boom. it works now. thanks!"
papa: Yes, ngy, for our forum's software to work, one must somehow install mosquitto. openhabian-config makes it more convenient than for other operating systems, but we must take that extra step within openhabian-config. Congratulations on getting that working. Now enjoy developing your DIY Home Automation network.
Thanks brump, for offering help to ngy.
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Apr 23, 2018 20:06:22 GMT
Hi papa, brump,
So my RFM69HW radios finally came in, and soldered wires and got the nodes setup. One thing I noticed was I'm not getting a very stable connection. Please see my attached log:
Node 2 Version 2.2MhC GW2.5.1
Transmitting at 915 Mhz...
No connection...
No connection...
No connection...
No connection...
--RESET GATEWAY-- --RESET NODE-- Node 2 Version 2.2MhC GW2.5.1
Transmitting at 915 Mhz...
Node: 2 dev: 99 cmd: 0 Ival: 0 Fval: 0.00 RSSI: -27
Node: 2 dev: 2 cmd: 0 Ival: 0 Fval: 0.00 RSSI: -27
Node: 2 dev: 4 cmd: 0 Ival: 0 Fval: 3.29 RSSI: -26
No connection...
No connection...
No connection...
No connection...
--RESET NODE-- Node 2 Version 2.2MhC GW2.5.1
Transmitting at 915 Mhz...
Node: 2 dev: 99 cmd: 0 Ival: 0 Fval: 0.00 RSSI: -26
Node: 2 dev: 2 cmd: 0 Ival: 0 Fval: 0.00 RSSI: -27
No connection...
No connection...
--RESET GATEWAY-- --RESET NODE--
Node 2 Version 2.2MhC GW2.5.1
Transmitting at 915 Mhz...
Node: 2 dev: 99 cmd: 0 Ival: 0 Fval: 0.00 RSSI: -26
Node: 2 dev: 2 cmd: 0 Ival: 0 Fval: 0.00 RSSI: -27
No connection...
No connection...
No connection...
No connection...
No connection...
No connection...
No connection...
No connection...
Once the gateway starts up, the MQTT LED lights up, followed by the radio activity LED. they remain permanently on until I reboot the gateway. For the node, as you can see from the log, once it makes the initial connection, it reverts back to no connection (but the radio LED stays on on the gateway). Is this normal? I added the points where I hit the reset button on the gateway and arduinos.
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Apr 23, 2018 20:13:16 GMT
I also swapped the node out and plugged the gateway to the serial monitor and got this:
Node 2,2,0,0.00
Node 2,4,0,3.28
Node 2,9,1,3.28
--RESET NODE-- Node 2,99,0,0.00
Node 2,2,0,0.00
Node 2,4,0,3.28
--RESET GATEWAY-- Node 2,9,6,3.29
|
|
|
Post by papa on Apr 24, 2018 2:16:56 GMT
ngy, 1) When you built the Gateway, did you do this hack to protect your RFM69 radio from 5 volts? 2) When you programmed the Gateway, did you use this post about Downloading, Editing, & Installing Libraries. It contains two important library edits that help make gateway <> node communication reliable. If the above items 1) & 2) ^^ were already ok or if fixing them makes no difference ... RFM_MQTT_GW_25_pub4.ino (15.95 KB) << 3) Here is the slightly earlier Gateway version 2.5 to download. Customize that Gateway 2.5 sketch as necessary, upload to your Gateway unit, & try communication with the node. Let us know if that works better & if not, report your Serial Monitor results.
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Apr 24, 2018 13:59:25 GMT
Hi papa, answers to your questions:
1) yes definitely did. switch is set to 3.3v, and the VCC pin is bent out so that it does not engage with the ethernet shield 2) I did follow the post about installing libraries, making change to ethernet.h (to point to utility\w5100.h), and downloaded the RFM69 library 3) I will try the slightly earlier version of hte gateway.
Thanks,
|
|
|
Post by papa on Apr 25, 2018 12:24:17 GMT
ngy, did you also see zanyhunter's post about antenna length contributing to RFM69 communication problems: "I finally found the problem with the original radio. Weird stuff was happening with it. I could move it around, vibrate it, or anything and it wouldn't connect. It was only when I brought my finger CLOSE or TOUCHED the top of antenna where it immediately responded. Turns out that the antenna length was barely a few millimeters too short to achieve a full quarter wave, and therefore couldn't transmit a signal! Lengthened the antenna and now I have a third node that works flawlessly." Here's my somewhat researched post about antenna lengths for different RFM69 radio frequencies. Note that I've seen slightly different antenna length recommendations on various web sites. One may need to experiment with this: start antenna a little long, try communication, if not reliable, trim a little off, try communication again, etc. I suppose communication reliability could also be affected by radio frequencies from other nearby "broadcasting" devices. "Tuning" the antenna may help overcome radio frequency competition.
|
|
ngy
Junior Member
Posts: 58
|
Post by ngy on Apr 25, 2018 14:22:27 GMT
I definitely exhibited similar things, where if my finger was close or touched the antenna, it immediately responded. I measured my antenna cable to be about 82mm, but that was including a tiny bit i stripped off for soldering.
However, I found my problem was actually the w5100.h library. I'm using a desktop + a laptop computer, and I realized I only changed the library on the laptop, not the desktop computer where I compiled the sketch and uploaded to the arduino. Once I fixed that, transmission was stable.
I will play around with the antenna length again though.
Another interesting thing now, my openhab webpage isn't opening anymore. I can access the logs via openhabianpi:9001, and the samba shares on the windows computer, but opening openhabianpi:8080 refuses to connect. I've tried rebooting the service, but nothing is working.
Here's a bit of hte log:
2018-04-23 09:03:17.430 [INFO ] [er.internal.HomeBuilderDashboardTile] - Started Home Builder at /homebuilder
2018-04-23 09:03:18.407 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at http://10.0.0.10:8080
2018-04-23 09:03:18.431 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at https://10.0.0.10:8443
2018-04-23 09:03:29.139 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2018-04-23 09:03:32.314 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2018-04-23 09:03:32.455 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2018-04-23 09:03:32.571 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2018-04-23 09:03:33.600 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
2018-04-23 15:24:43.796 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI
2018-04-23 15:24:49.437 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Stopped HABmin servlet
2018-04-23 15:24:49.863 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Stopped Paper UI
2018-04-23 15:24:49.886 [INFO ] [panel.internal.HABPanelDashboardTile] - Stopped HABPanel
2018-04-23 15:24:49.900 [INFO ] [er.internal.HomeBuilderDashboardTile] - Stopped Home Builder
2018-04-23 15:24:49.928 [INFO ] [.dashboard.internal.DashboardService] - Stopped dashboard
2018-04-23 15:25:18.618 [INFO ] [er.internal.HomeBuilderDashboardTile] - Started Home Builder at /homebuilder
2018-04-23 15:25:20.146 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at http://10.0.0.10:8080
2018-04-23 15:25:20.152 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at https://10.0.0.10:8443
2018-04-23 15:25:30.543 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2018-04-23 15:25:34.214 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2018-04-23 15:25:34.348 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2018-04-23 15:25:34.527 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2018-04-23 15:25:35.454 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
==> /var/log/openhab2/events.log <==
2018-04-04 10:12:21.545 [thome.event.ExtensionEvent] - Extension 'package-standard' has been installed.
2018-04-04 10:12:33.616 [thome.event.ExtensionEvent] - Extension 'ui-homebuilder' has been installed.
2018-04-04 10:12:33.621 [thome.event.ExtensionEvent] - Extension 'ui-basic' has been installed.
2018-04-04 10:12:33.624 [thome.event.ExtensionEvent] - Extension 'ui-habpanel' has been installed.
2018-04-04 10:12:33.627 [thome.event.ExtensionEvent] - Extension 'ui-paper' has been installed.
2018-04-04 10:17:06.959 [thome.event.ExtensionEvent] - Extension 'action-mqtt' has been installed.
2018-04-04 11:39:15.420 [thome.event.ExtensionEvent] - Extension 'binding-mqtt1' has been installed.
2018-04-04 17:55:25.999 [thome.event.ExtensionEvent] - Extension 'binding-zwave' has been installed.
2018-04-04 17:58:10.802 [thome.event.ExtensionEvent] - Extension 'ui-habmin' has been installed.
2018-04-04 17:59:12.674 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:16292abaea9' changed from UNINITIALIZED to INITIALIZING
2018-04-04 17:59:53.420 [me.event.ThingUpdatedEvent] - Thing 'zwave:serial_zstick:16292abaea9' has been updated.
2018-04-04 17:59:53.467 [me.event.ThingUpdatedEvent] - Thing 'zwave:serial_zstick:16292abaea9' has been updated.
2018-04-04 17:59:53.479 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:16292abaea9' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2018-04-04 17:59:57.286 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:16292abaea9' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2018-04-05 02:57:58.075 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:16292abaea9' changed from ONLINE to UNINITIALIZED
2018-04-05 02:58:01.238 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:16292abaea9' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-04-05 02:58:58.228 [thome.event.ExtensionEvent] - Extension 'binding-zwave' has been uninstalled.
|
|
|
Post by papa on Apr 25, 2018 15:26:00 GMT
ngy: "I found my problem was actually the w5100.h library. ... Once I fixed that, transmission was stable."
papa: good news
ngy: "my openhab webpage isn't opening anymore ... opening openhabianpi:8080 refuses to connect"
papa: Sounds like you mean that the openhab dashboard is not opening for you. Did you try replacing "openhabianpi" with the Pi's IP address, something like 10.0.0.10:8080?
Can you directly open the openhab user interface you have chosen (basicui?) ? something like openhabianpi:8080/basicui/app?sitemap=[your sitemap] or 10.0.0.10:8080:8080/basicui/app?sitemap=[your sitemap] If you can open it, is it showing results from the nodes?
For that dashboard to respond, openhab 2 must be running. The following command should tell you: sudo /bin/systemctl status openhab2.service
|
|