openHABian hassle-free openHAB Setup

Hardware Server
, ,
1065

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 :slight_smile:

1066

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
1067

I think that this is the case.

I am also waiting for the rollershutter support in Homekit :slight_smile:

1068

Textual thing config?
Altitude is now part of the geo location …

1069

Nope. The location is correct. Funny thing is, i can see the dusk-start and dusk-stop event fire. Just not when it is expected :slight_smile:

CivilDusk ended today 21:54. With Offset set to “-10” the END-Event should have triggered 21:44, right?
The log stated 21:54 for CivilDusk End instead… (AND it did not run my rollershutters…)

What do you mean by “texual thing config” please, can you specify the question a litte bit more, please?

The items are all textual, as I am using KNX. The astro binding offset I configured in the paper UI. Does this answer your question?

1070

http://docs.openhab.org/addons/bindings/astro/readme.html#full-example

astro:sun:home [ geolocation="52.5200066,13.4049540,100", interval=60 ]

This also applies to the config via PaperUI:

Before the change: 56.123456,7.123456, after the change: 56.123456,7.123456,100 (where 100 is the altitude, but that is optional): openHAB 2.1 Release Notes · openhab/openhab-distro Wiki · GitHub

So if you have things files for astro and are using altitude, you have to adapt those.

BTW, my offsets and channel triggers are working fine with 2.1 and now 2.2 …
Also note another issue with the astro binding (if openHAB or the binding hasn’t been restarted for a while):

1 Like
1071

Ah, ok.
In this case no, the astro binding is only configured using PaperUI. Only the bindings, items, sitemaps, rules, persistence and transforms are using textual config.

The error you posted I haven’t run into yet. Interestingly enough, with the original HassbianVersion for OH 2.0 it ran for several weeks without any problems. Seems this error has been introduced by the most recent version?

1072

@ThomDietrich

First of all - Great job. I really appreciate openHABIAN and had so far never really problem with it. More and more i am using the additional tools from the menue. Recentyl i installed mosquitto with openhabian and stop my mosquitto pi for that. transfer worked like a charm.

Netxt step is to use grafana with openhabian and my influx db. Influx is installes on my NAS as a docker service. Starting to install grafana i recognized that it installs influx as well on my raspi. Becaus of my NAS Influxdb i do not need any further installations.

Is it possible to divide those two topics in the menue?

Thomas

1073

You sir are a genius. Really. I have been struggling for a l o n g time. I want to automate some functions in my mobile home but most (if not all) tutorials assumed I would have ethernet access.
I want to run all this from my 12v DC.
And now I can using a RPi version 3 and a Huawei mobile wifi device

Fantastic work, much appreciated

1 Like
1074

Sorry guys - anybody here has issues with astro binding since upgrade to openhab 2.1?
I have this simple rule, it worked til i upgraded:

rule "Spegni luce cucina all’inizio dell’alba"
when
Channel ‘astro:sun:home:civilDawn#event’ triggered START
then
sendCommand(Luce_Esterna_Cucina, OFF)
end

these are my triggered events:

2017-07-13 02:59:00.125 [ChannelTriggeredEvent ] - astro:sun:home:astroDawn#event triggered START
2017-07-13 04:03:00.096 [ChannelTriggeredEvent ] - astro:sun:home:astroDawn#event triggered END
2017-07-13 04:03:00.134 [ChannelTriggeredEvent ] - astro:sun:home:nauticDawn#event triggered START
2017-07-13 04:52:00.128 [ChannelTriggeredEvent ] - astro:sun:home:civilDawn#event triggered START
2017-07-13 04:52:00.131 [ChannelTriggeredEvent ] - astro:sun:home:nauticDawn#event triggered END
2017-07-13 05:30:00.257 [ChannelTriggeredEvent ] - astro:sun:home:civilDawn#event triggered END

i also noticed that during installation i got this:

2017-07-08 11:55:46.062 [temChannelLinkRemovedEvent] - Link ‘DawnStart_Time => astro:sun:home:civilDawn#start’ has been removed.
2017-07-08 12:17:48.683 [ItemChannelLinkAddedEvent ] - Link ‘DawnStart_Time-astro:sun:home:civilDawn#start’ has been added.

any idea?

1075

Hi just an update. I noticed that

  • astro:sun:data e astro:moon:data were not initialized
  • to initialize them, paper UI asked me also altitude (i don’t remember i filled this info months ago)

so what i did:

  1. removed and reinstalled astro binding via paper UI
  2. filled in altitude data
  3. run an apt-get upgrade, lot of stuff upgraded

this morning all my rules are fired correctly.

1076

That’s is a little bit hidden in the release notes:

1077

Thanks @sihui, so… probably missing altitude was my issue.

1078

I just started to use node red and i am wondering how to update to the newst version of node-red using openhabian.

Thomas

1079

Hi all,

using openHABian I moved the system partition to an external usb-drive (ssd).

With
sudo df

I get

Because of
/dev/sda1
and because openHAB is up and running, I assume that everything went well.

Problem:
I thought, the RPi3 should boot from USB mass storage now, without sd-card necessary.
But that don’t work. When I pull out the sd-card the RPi3 don’t boot anymore.
Maybe I misunderstood something?

1080

Yes. The openHABian “move” function needs an sd card, if you want to boot without an sd card at all you need to follow:

https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md

1 Like
1081

:ok_hand: What he said :slight_smile:

1082

Thanks a lot for clarifing that.

I’m not sure, if I can follow the link @sihui recommended because the first step in the linked tutorial is to do sudo apt-get update && sudo apt-get upgrade
but actually always when starting openhabian-config I get this warning:

And if I finally make it one further question just to clarifiy:
When RPi3 is booting from ssd: Can I still use openhabian-config with option “Upgrade system” to keep my system up to date?

I’m asking because of that treat: Because the new USB mass storage boot mode is provided through beta firmware you can‘t upgrade your system with apt-get upgrade anymore.

Sorry, but I’m confused, because you have to pay attention to so many things.
(Managing all this with openhabian-config would be a great thing.:smiley:)

My system is:

openHABian Configuration Tool [master]v1.3-291(308a39f)

1083

That is because you are still on the ua-netinst image which is deprecated! You should follow the steps on your screen.
See also:

1 Like
1084

That is also no longer valid, see: