Ankündigung

Einklappen
Keine Ankündigung bisher.

NTP Binding startet nicht

Einklappen
X
 
  • Filter
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge

    NTP Binding startet nicht

    Hallo!

    Ich schaff es nicht, das NTP Binding zum Laufen zu bringen. Das Datum wird nicht auf den Bus geschickt und auch nicht in der Webapp angezeigt. Außerdem sollte es im Log eine Zeile mit "ntp binding has been started" geben, die aber nicht kommt. Bitte um Hilfe.

    Zeilen in der openhab.cfg:
    ntp:refresh=60000
    ntp:hostname=at.pool.ntp.org
    items:
    DateTime Datum "Datum [%1$tA, %1$td.%1$tm.%1$tY]" <calendar> { ntp = "Europe/Berlin:de_DE", knx="11.001:6/0/0, 10.001:6/0/1" }
    sitemap:
    Frame label="Datum" {
    Text item=Datum
    }
    Hier das log von einem Debug Startup, es werden nur das HTTP und das KNX binding gestartet.
    Launching the openHAB runtime in debug mode...
    Listening for transport dt_socket at address: 8001
    19:39:27.761 DEBUG o.o.b.h.internal.HttpActivator[:54] - HTTP binding has been started.
    19:39:27.783 DEBUG o.o.b.k.internal.KNXActivator[:51] - KNX binding has been started.
    osgi> 19:39:28.320 DEBUG o.o.c.s.i.SchedulerActivator[:56] - Scheduler has been started.
    19:39:28.358 INFO o.q.impl.StdSchedulerFactory[:1175] - Using default implementation for ThreadExecutor
    19:39:28.379 INFO o.q.core.SchedulerSignalerImpl[:61] - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
    19:39:28.380 INFO o.quartz.core.QuartzScheduler[:243] - Quartz Scheduler v.2.1.7 created.
    19:39:28.382 INFO org.quartz.simpl.RAMJobStore[:154] - RAMJobStore initialized.
    19:39:28.383 INFO o.quartz.core.QuartzScheduler[:268] - Scheduler meta-data: Quartz Scheduler (v2.1.7) 'openHAB-job-scheduler' with instanceId 'NON_CLUSTERED'
    Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
    NOT STARTED.
    Currently in standby mode.
    Number of jobs executed: 0
    Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 2 threads.
    Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

    19:39:28.384 INFO o.q.impl.StdSchedulerFactory[:1324] - Quartz scheduler 'openHAB-job-scheduler' initialized from specified file: './etc/quartz.properties'
    19:39:28.384 INFO o.q.impl.StdSchedulerFactory[:1328] - Quartz scheduler version: 2.1.7
    19:39:28.385 INFO o.quartz.core.QuartzScheduler[:534] - Scheduler openHAB-job-scheduler_$_NON_CLUSTERED started.
    19:39:28.389 DEBUG o.o.c.core.ConfigDispatcher[:166] - Processing openHAB default configuration file '/home/jo/Downloads/openhab-1.2.0/openhab-runtime-1.2.0.shs55/configurations/openhab_default.cfg'.
    19:39:28.390 DEBUG o.o.c.core.ConfigDispatcher[:188] - Processing openHAB main configuration file '/home/jo/Downloads/openhab-1.2.0/openhab-runtime-1.2.0.shs55/configurations/openhab.cfg'.
    19:39:28.624 DEBUG o.o.c.internal.CoreActivator[:124] - UUID file already exists at '/home/jo/Downloads/openhab-1.2.0/openhab-runtime-1.2.0.shs55/webapps/static/uuid' with content '8289309a-1623-4661-8077-89585f3de872'
    19:39:28.803 DEBUG o.o.c.internal.CoreActivator[:146] - Created file '/home/jo/Downloads/openhab-1.2.0/openhab-runtime-1.2.0.shs55/webapps/static/version' with content '1.2.0'
    19:39:28.803 INFO o.o.c.internal.CoreActivator[:92] - openHAB runtime has been started (v1.2.0).
    19:39:29.409 DEBUG o.o.m.i.i.ItemModelActivator[:44] - Registered 'item' configuration parser
    19:39:29.450 DEBUG o.o.c.a.i.AutoUpdateActivator[:51] - AutoUpdate binding has been started.
    19:39:29.458 INFO o.o.b.k.i.c.KNXConnection[:178] - Established connection to KNX bus on 224.0.23.12:3671 in mode ROUTER.
    19:39:29.591 DEBUG o.o.c.i.items.ItemRegistryImpl[:165] - Item provider 'GenericItemProvider' has been added.
    19:39:29.719 DEBUG o.o.m.p.i.PersistenceModelActivator[:43] - Registered 'persistence' configuration parser
    19:39:29.725 DEBUG o.o.c.t.i.TransformationActivator[:58] - Transformation Service has been started.
    19:39:29.759 DEBUG o.o.i.g.internal.GCalActivator[:54] - Google Calendar IO has been started.
    19:39:29.795 DEBUG o.o.i.g.i.p.GCalPresenceSimulation[:161] - Scheduled Google Calendar Upload-Job with interval '10'
    19:39:29.915 INFO o.o.m.c.i.f.FolderObserver[:163] - Loaded file 'shs55.items'
    19:39:29.915 DEBUG o.o.m.c.i.ModelRepositoryImpl[:83] - Configuration model 'presencesimulation.persist' can not be found
    19:39:29.922 DEBUG o.o.i.m.i.MultimediaActivator[:54] - Multimedia I/O bundle has been started.
    19:39:29.964 DEBUG o.o.i.s.i.DiscoveryServiceActivator[:47] - Discovery service has been started.
    19:39:30.442 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Luftfeuchtigkeit_Sensor_OG_Gang
    19:39:30.611 DEBUG o.o.m.s.i.SitemapModelActivator[:43] - Registered 'sitemap' configuration parser
    19:39:30.672 DEBUG o.o.i.r.internal.RESTActivator[:53] - REST API has been started.
    19:39:30.698 INFO o.o.i.s.i.DiscoveryServiceImpl[:92] - mDNS service has been started
    19:39:30.823 INFO o.a.cpr.AtmosphereFramework[:742] - Installing BroadcastFilter class(es) org.atmosphere.client.FormParamFilter
    19:39:30.828 INFO o.a.cpr.AtmosphereFramework[:1118] - Auto detecting atmosphere handlers /WEB-INF/classes/
    19:39:30.832 WARN o.a.cpr.AtmosphereFramework[:814] - Missing META-INF/atmosphere.xml but found the Jersey runtime. Starting Jersey
    19:39:30.846 INFO o.a.cpr.AtmosphereFramework[:364] - Installed AtmosphereHandler org.atmosphere.handler.ReflectorServletProcessor mapped to context-path: /*
    19:39:30.846 INFO o.a.cpr.AtmosphereFramework[:1173] - Auto detecting WebSocketHandler in /WEB-INF/classes/
    19:39:30.861 INFO o.a.cpr.AtmosphereFramework[:1099] - Atmosphere is using async support: org.atmosphere.container.JettyAsyncSupportWithWebS ocket running under container: jetty/8.1.3.v20120522 with WebSocket enabled.
    19:39:30.861 INFO o.a.cpr.AtmosphereFramework[:902] - Installed WebSocketProtocol org.atmosphere.websocket.protocol.SimpleHttpProtoc ol
    19:39:30.868 INFO o.a.h.ReflectorServletProcessor[:126] - Installing Servlet com.sun.jersey.spi.container.servlet.ServletContai ner
    19:39:30.934 INFO c.s.j.s.i.a.WebApplicationImpl[:791] - Initiating Jersey application, version 'Jersey: 1.11 12/09/2011 11:05 AM'
    19:39:30.936 INFO c.s.j.s.i.a.WebApplicationImpl[:802] - Adding the following classes declared in META-INF/services/jersey-server-components to the resource configuration:
    class org.atmosphere.jersey.AtmosphereResourceConfigurat or
    19:39:30.972 INFO c.s.j.s.i.a.DeferredResourceConfig[:97] - Instantiated the Application class org.openhab.io.rest.internal.RESTApplication
    19:39:31.134 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Ist_Temperatur_OG_Gang
    19:39:31.462 INFO o.a.cpr.AtmosphereFramework[:589] - Installed Default AtmosphereInterceptor [Android Interceptor Support, SSE Interceptor Support, JSONP Interceptor Support]. Set org.atmosphere.cpr.AtmosphereInterceptor.disableDe faults in your xml to disable them.
    19:39:31.462 WARN o.a.cpr.AtmosphereFramework[:509] - No BroadcasterCache configured. Broadcasted message between client reconnection will be LOST. It is recommended to configure the HeaderBroadcasterCache.
    19:39:31.463 WARN o.a.cpr.AtmosphereFramework[:533] - Neither TrackMessageSizeInterceptor or TrackMessageSizeFilter are installed. atmosphere.js may receive glued and incomplete message.
    19:39:31.463 INFO o.a.cpr.AtmosphereFramework[:537] - HttpSession supported: false
    19:39:31.463 INFO o.a.cpr.AtmosphereFramework[:538] - Using BroadcasterFactory: org.atmosphere.cpr.DefaultBroadcasterFactory
    19:39:31.464 INFO o.a.cpr.AtmosphereFramework[:539] - Using WebSocketProcessor: org.atmosphere.websocket.DefaultWebSocketProcessor
    19:39:31.464 INFO o.a.cpr.AtmosphereFramework[:540] - Using Broadcaster: org.atmosphere.jersey.JerseyBroadcaster
    19:39:31.465 INFO o.a.cpr.AtmosphereFramework[:541] - Atmosphere Framework 1.0.4 started.
    19:39:31.465 INFO o.o.i.r.i.RESTApplication[:158] - Started REST API at /rest
    19:39:31.467 DEBUG o.o.i.s.i.DiscoveryServiceImpl[:63] - Registering new service _openhab-server._tcp.local. at port 8080
    19:39:31.844 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item CO2_OG_Gang
    19:39:32.560 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Temperatur_Taupunkt_OG_Gang
    19:39:33.278 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Soll_Temperatur_OG_SZ
    19:39:34.097 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Ist_Temperatur_unabgeglichen_OG_Gang
    19:39:34.813 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Ist_Temperatur_OG_SZ
    19:39:35.633 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Ist_Temperatur_Sensor_OG_Gang
    19:39:38.209 DEBUG o.o.i.s.i.DiscoveryServiceImpl[:63] - Registering new service _openhab-server-ssl._tcp.local. at port 8443
    19:39:40.022 INFO o.o.m.c.i.f.FolderObserver[:163] - Loaded file 'shs55.sitemap'
    19:39:40.838 INFO o.o.u.w.i.s.WebAppServlet[:99] - Started Classic UI at /openhab.app
    19:39:41.194 DEBUG o.o.m.r.i.RuleModelActivator[:62] - Registered 'rules' configuration parser
    19:39:41.204 DEBUG o.o.m.r.i.engine.RuleEngine[:98] - Started rule engine

    Hier der output vom locale:
    LANG=de_AT.UTF-8
    LANGUAGE=
    LC_CTYPE="de_AT.utf8"
    LC_NUMERIC="de_AT.utf8"
    LC_TIME="de_AT.utf8"
    LC_COLLATE="de_AT.utf8"
    LC_MONETARY="de_AT.utf8"
    LC_MESSAGES="de_AT.utf8"
    LC_PAPER="de_AT.utf8"
    LC_NAME="de_AT.utf8"
    LC_ADDRESS="de_AT.utf8"
    LC_TELEPHONE="de_AT.utf8"
    LC_MEASUREMENT="de_AT.utf8"
    LC_IDENTIFICATION="de_AT.utf8"
    LC_ALL=de_AT.utf8

    Danke!!
    Jo

    #2
    doofe Frage ...

    ... das NTP Binding liegt aber im /addons Folder?

    Gruß,

    Thomas E.-E.
    Visualisierung, Rule/Logic-Engine, Integrationsplattform mit openhab (Supportforum)

    Kommentar


      #3
      Keine doofe Frage -&gt; Danke!

      Hallo!

      Das ist keine doofe Frage. Das ist das Problem. Danke für den Hinweis!!

      Gruß
      Jo

      Kommentar


        #4
        ;-) na dann viel Spaß beim DateTime senden ...

        Gruß,

        Thomas E.-E.
        Visualisierung, Rule/Logic-Engine, Integrationsplattform mit openhab (Supportforum)

        Kommentar

        Lädt...
        X