Is the name of your sitemap home within the file itself?
sitemap home label="whatever"
{
Frame label="Demo"
{
Switch item=DEMOSW
}
}
Hi and thx for your reply.
My home.sitemap content:
sitemap home label=“AAdyssegaard”
{
Frame label=“Demo”
{
Switch item=DEMOSW
}
Frame label=“Koekken”
{
Switch item=DEMOSW
}
Frame Label=“Stuen”
{
Switch item=DEMOSW
}
Frame Label=“Sovevaerelse”
{
Switch item=DEMOSW
}
}
You have a capital “L” which should be a small case “l” in Label for your last two frames.
Wow, didn’t know it was so case sensitive. It did the trick, works now, thx a lot.
I’ll see if I can find documentation explaining file content syntax.
links are welcome, or suggestion to ‘must read’.
The openHAB docs are always a good place to start, the maintainer of openHABian, @ThomDietrich also does a great job of keeping it up-to-date along with contributors 
:
- See here for config syntax for manually defined items.
- The first time setup page is also a good read to get you started.
Hi all,
With this new openhabian version i decided to try openhabian again. With a clean installation, no upgrade from an older openhab install. (did an backup as described in the docs)
Unfortunately i have a problem with Z-Wave. My Z-Wave Serial Controller remains offline.
Looking for the cause, i found that the /dev/ttyAMA0 does not have the right access rights.
[18:37:25] openhabian@openHABianPi:~$ ll /dev/ttyAMA0
crw--w---- 1 root tty 204, 64 Jul 5 13:50 /dev/ttyAMA0
Performing the command:
[18:41:13] openhabian@openHABianPi:~$ sudo chmod 666 /dev/ttyACM0
[18:41:31] openhabian@openHABianPi:~$
does not change anything?!
With the normal hand installation of openhab 2.2.x this does work well.
Does anyone has an idee what causes this behaviour of a sudo command?
I thougt the user openhabian was default added to de sudoers…
Mayby i am overlooking something…
Thx for taking your time to point me in the right direction, i’ll look into it
did you execute the “Serial Port” menu entry, then restart the system?Thanks Thom for pointing me on this. I think i was doing things from the command prompt while with openhasbian i should do everything from the openhabian-config menu.
At the moment i even can’t reach openhab on port 8080 anymore. Decided to start al over again.
Hello,
i just upgraded my openHABian without any problems!
Now, i noted that the green LED (heart-beat) is not longer active 
First shock … my HABy is dead, but everything is working fine … puh
So, is this nice little features disabled in the latest release?
Thanks
I don’t know the rationale, but yes, it’s intentional.
You might be interessted in this. 
Hi @ThomDietrich,
just to let you know, “Frontail” is currently not installable via openhabian-config on Debian stretch.
Reason is, that node.js version 7.x is refusing installation because “stretch” is “currently not supported”.
(I’ve raised an issue on github/nodesource on that…)
Workaround is to force installation of node.js 8.x instead of 7.x manually via
curl -sL https://deb.nodesource.com/setup_8.x | bash -
apt-get install -y nodejs
Afterwards, you can go back to openhabian-config and install Frontail from menu
not sure if this is openHABian related:
Failed installing 'openhab-binding-http1': Permission denied
is it?
I found the solution
I burned the image on SD using Win32DiskImager instead of Etcher.
All worked perfectly
Hi @mstormi,
I have exactly the same problem like @boob (openHABian hassle-free openHAB Setup).
[14:32:09] backup@openHABianPi:/var/log/amanda/server/openhab-dir$ amcheck openhab-dir
Amanda Tape Server Host Check
-----------------------------
slot 1: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 2: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 3: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 4: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 5: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 6: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 7: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 8: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 9: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 10: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 11: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 12: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 13: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 14: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
slot 15: Error checking directory /srv/backup/slots/drive0/data/: No such file or directory
volume ''
Taper scan algorithm did not find an acceptable volume.
(expecting a new volume)
ERROR: No acceptable volumes found
NOTE: host info dir /var/lib/amanda/openhab-dir/curinfo/openHABianPi does not exist
NOTE: it will be created on the next run.
NOTE: index dir /var/lib/amanda/openhab-dir/index/openHABianPi does not exist
NOTE: it will be created on the next run.
Server check took 3.801 seconds
Amanda Backup Client Hosts Check
--------------------------------
Client check: 1 host checked in 4.530 seconds. 0 problems found.
(brought to you by Amanda 3.3.6)
No manual configuration. Only the openhasbian-config.
My share is connected via SMB/CIFS in fstab and is on a Synology. Dir is reachable and writable. The slots dirs are created and then I try amcheck leading to the errors above. I tried it multiple times with the configuration tool.
Any idea?
Thanks in advance!
HFM
Hmm, I wonder where that ‘drive0’ is coming from.
Can you tell me what’s the path to NAS you entered and post your config file (/etc/amanda/openhab-dir/amanda.conf).
Try cd /srv/backup/slots; sudo ln -s . drive0 and then retry amcheck.
And please make a Github issue of it.
I have installed the current version, using OH2.1. Additional services are NodeRed and frontail. Other that this, my installation is standard on an RPI3. Now, since the new version I can see rolling in random failure messages I never saw with OH2. Just like
[CODE]
2017-07-14 22:14:21.628 [ERROR] [ssories.AbstractHomekitAccessoryImpl] - Type RL_Treppenhaus is a org.eclipse.smarthome.core.library.items.RollershutterItem instead of the expected org.eclipse.smarthome.core.library.items.SwitchItem
[CODE]
I am using KNX, have bound my installation to the HomeKit and the Hue Binding (to use Alexa) which, again, worked flawlessly with OH2.
Same applies to the Astro Binding, where Offsets are obvisously no longer respected AND the configuration for Offset or earliest/latest settings are getting deleted from time to time.
I already reinstalled the Astro Binding, run upgrades and rebooted several times. Still, no success.
Anyone an idea where I should start looking for the root cause? Really puzzled…
Thanks
Frank
This seems to be a generic problem (not related to openHABian). A “general” note: openHAB 2.1 is more strict with regards to syntax when it comes to parsing configs (items, sitemaps, etc). There have been more checks implemented in the code (core and bindings according to my understanding). An error could exist in the configs and it would not show up in openHAB 2.0 but now (in 2.1) it will pop up.
I suggest that you open up a new thread, post this info (with the error) along with the configuration of your RL_Treppenhaus item
It looks like the Homekit binding doesn’t like your tag & item type combo 
Ah, that would explain the error. HomeKit currently does not support Rollershutters at all, therefore defining this KNX-Rollershutter-item as a light-item was a feasible workaround. Now as this is not really wrong behaviour by OH, it makes no sense to raise an request. It just means that OH2.1 will prevent us from some workarounds due to this strictness.
Bumr.
1 Like