[SOLVED] MAP service starts too late at OH startup

[shotte (Ralf)]

Hi everyone,

I’m putting this here because I thing it should match. My issue is based on persistence and service start for mapping.

OH: latest stable version 2.4

Issue: When I start/restart OH I got tons of error messages like the one below (just one example). I tried cleaning cache and deleted contents from ‘var/lib/openhab2/cache/’ and 'var/lib/openhab2/tmp/’ but nothing helped. It seems to me that MAP service is started too late, because later on I have no similar problems any more.

I also checked forum entries like those:
[JS transformation service starts too late when openHAB startup]
[[SOLVED] Openhab 2.2 and upgrade to latest version 2.4]
[[SOLVED] MapDB persistence service not starting]
[OH2 first startup: MiOS binding started before MAP transform is installed]
but I could not get any further information to solve my problem. Any help is appreciated.

2019-05-30 10:59:51.473 [WARN ] [rest.core.item.EnrichedItemDTOMapper] - Failed transforming the state 'NULL' on item 'EG_EssenWohnen_Anwesenheit' with pattern 'MAP(anwesenheit.map):%s': Couldn't transform value because transformation service of type 'MAP' is not available.

Best reagrds,
Ralf

[rossko57]

openHAB 2.4 isn’t particularly clever about managing the order of starting up various services. Often this manifests as rules running before Items defined etc., but it seems likely your observation is the same kind of issue.

While there are hopefully proper fixes in the future, you can find a workaround “delayed rules load” here

Cleaning up the startup process / renaming rules (windows possible)

I’ve run in some issues with the current startup process. Everything is starting at once which leads to several exceptions, errors and other problems. In my case the most annoying problem is the Homematic-Channel not found-problem. According to my opinion, a reason is the triggering of rules during startup which leads to timing problems and other race conditions which then lead to further problems after startup. I often read about moving or renaming the rules and copying back after startup, so…

It’s worth taking a harder look at the source of your warnings - they may come from use of MAP in bindings/channels etc. The “rules” fix won’t address those; but maybe if this is happening before rules load you don’t care much anyway and it’s just a nuisance report?

[shotte (Ralf)]

Hi @rossko57 rossko57,

thank you for your quick response and this helpful link. This helped me with my MAP issue, even though it is just a workaround (because only rules are loaded later which take might eat up a lot of startup time).

Best regards,
Ralf

[rossko57]

Interesting to find another symptom of same illness.