ePaper Anbindung an Google Kalender

Fragen zum LANCOM Wireless ePaper

Moderator: Lancom-Systems Moderatoren

Antworten
kbit
Beiträge: 1
Registriert: 08 Apr 2016, 09:01

ePaper Anbindung an Google Kalender

Beitrag von kbit » 08 Apr 2016, 09:21

Hallo Kollegen,

ich habe Probleme den Google Kalender mit dem ePaper Server zu verbinden.
Wir hatten die Lösung für eine Messe schon mal eingerichtet und da hatte es auch funktioniert. Nun habe ich es bei uns im Büro nochmal neu installiert und
ich bekomme ständig Fehler beim Auslesen des Kalenders.

Laut Log kann sich das Script zwar am Google Kalender anmelden (p.12 Datei) aber den Kalender nicht auslesen.
Die Installation habe ich nach der Anleitung im DEV-Center durchgeführt (wobei sich da bei Google die Menüs etwas geändert haben).

Ich habe bei den Benennungen des Raumes und der serviceaccoundid schon fast alles mögliche durchprobiert aber das ändert nichts an Fehlermeldungen.

Hat dazu jemand einen Tipp?


Hier die Konfigfiles und das Log:

calendar.properies:

# the used timezone when computing dates
time_zone=Europe/Berlin
# the number of events to be read from each calendar
number_events=2
# the google service account id used for fetching calendar data
serviceaccountid=xxxxxxxxxxxx@epaper-1061.iam.gserviceaccount.com (E-Mailadresse des Dienstekontos)

# list of resources (rooms) that will be read

# Room 0
resource0=Besprechung_IT (=Tag des Displays im ePaper Server)
# Room 1
#resource1=
# Room 2
#resource2=
# Room 3
#resource3=
# Room 4
#resource4=


log:

2016-04-08T09:12:05,927 [main] DEBUG Main - Reading calendar properties
2016-04-08T09:12:05,942 [main] DEBUG Utils - All properties were read successfully. Total lines: 4
2016-04-08T09:12:05,943 [main] INFO Main - Setting up calendar module
2016-04-08T09:12:07,625 [main] DEBUG Credential - Google authentication with service account successful.
2016-04-08T09:12:07,626 [main] DEBUG Main - Reading client properties
2016-04-08T09:12:07,626 [main] DEBUG Utils - All properties were read successfully. Total lines: 5
2016-04-08T09:12:07,626 [main] INFO Main - Setting up client module
2016-04-08T09:12:07,641 [main] DEBUG WePClient - Read property host: x.x.x.x (IP des ePaper Servers)
2016-04-08T09:12:07,642 [main] DEBUG WePClient - Read property port: 8001
2016-04-08T09:12:07,642 [main] DEBUG WePClient - Read property user: admin
2016-04-08T09:12:07,642 [main] DEBUG WePClient - Read property pass: admin
2016-04-08T09:12:07,644 [main] DEBUG Main - Reading service properties
2016-04-08T09:12:07,644 [main] DEBUG Utils - All properties were read successfully. Total lines: 3
2016-04-08T09:12:07,644 [main] INFO Main - Setting up WeP service
2016-04-08T09:12:07,661 [main] INFO Main - Starting WeP service
2016-04-08T09:12:07,672 [WeP Service Task] INFO WePService - updating -------------------------------------------------
2016-04-08T09:12:07,673 [WeP Service Task] INFO WePService - reading calendars
2016-04-08T09:12:09,426 [WeP Service Task] WARN CalendarReader - Service was unable to read calendar with id: Besprechung_IT
2016-04-08T09:12:09,426 [WeP Service Task] INFO WePService - reading WeP states
2016-04-08T09:12:09,441 [WeP Service Task] TRACE Request - creating connection
2016-04-08T09:12:09,441 [WeP Service Task] DEBUG Request - URL = http://x.x.x.x:8001/service/labelinfo
2016-04-08T09:12:09,441 [WeP Service Task] TRACE Request - Opening connection
2016-04-08T09:12:09,441 [WeP Service Task] TRACE Request - connection created
2016-04-08T09:12:09,441 [WeP Service Task] TRACE Request - creating authentication
2016-04-08T09:12:09,447 [WeP Service Task] TRACE Request - authentication created
2016-04-08T09:12:09,447 [WeP Service Task] TRACE Request - setting request method to GET
2016-04-08T09:12:09,467 [WeP Service Task] DEBUG Request - Response is: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><LabelInfoPagedResult records="4" totalRecords="4" totalPages="1" page="0" recordsPerPage="4"><LabelInfo><LabelId>C1020D51</LabelId><Type>G1 4.4</Type><WakeupTime>2016-04-08T09:02:23.805+02:00</WakeupTime><FirmwareVersion>3.0.1</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>251</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-64</Rssi><Lqi>35</Lqi><AccessPointId>66618</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>c2d3368e-50ac-4002-9217-c54b6bcf887e</TaskId><TaskType>IMAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2016-03-23T15:51:02.012+01:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D1010FB0</LabelId><Type>G1 7.4</Type><Tag>ITTECHNIK</Tag><WakeupTime>2016-04-08T08:57:29.372+02:00</WakeupTime><FirmwareVersion>3.0.1</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>251</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-64</Rssi><Lqi>41</Lqi><AccessPointId>66618</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>a5f92c8b-070f-4968-8b67-41e7d6d5e665</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2016-03-23T14:31:58.797+01:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D1044E73</LabelId><Type>G1 7.4</Type><WakeupTime>2016-04-08T09:02:25.797+02:00</WakeupTime><FirmwareVersion>3.0.3</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>251</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>1</CurrentPage><Rssi>-60</Rssi><Lqi>45</Lqi><AccessPointId>66618</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>a56dd76c-5c8a-4f1b-8f7d-47303203991f</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>1</Page><Status>SUCCESSFUL</Status><UpdatedAt>2016-03-23T13:37:39.466+01:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D1044ED3</LabelId><Type>G1 7.4</Type><Tag>Besprechung_IT</Tag><WakeupTime>2016-04-08T09:05:01.422+02:00</WakeupTime><FirmwareVersion>3.0.3</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>251</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-74</Rssi><Lqi>34</Lqi><AccessPointId>66618</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>288bf683-57dc-40a4-b153-a2013902fb16</TaskId><TaskType>IMAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2016-03-23T11:45:47.353+01:00</UpdatedAt></LabelInfo></LabelInfoPagedResult>
2016-04-08T09:12:09,467 [WeP Service Task] DEBUG WePClient - Received response: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><LabelInfoPagedResult records="4" totalRecords="4" totalPages="1" page="0" recordsPerPage="4"><LabelInfo><LabelId>C1020D51</LabelId><Type>G1 4.4</Type><WakeupTime>2016-04-08T09:02:23.805+02:00</WakeupTime><FirmwareVersion>3.0.1</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>251</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-64</Rssi><Lqi>35</Lqi><AccessPointId>66618</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>c2d3368e-50ac-4002-9217-c54b6bcf887e</TaskId><TaskType>IMAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2016-03-23T15:51:02.012+01:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D1010FB0</LabelId><Type>G1 7.4</Type><Tag>ITTECHNIK</Tag><WakeupTime>2016-04-08T08:57:29.372+02:00</WakeupTime><FirmwareVersion>3.0.1</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>251</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-64</Rssi><Lqi>41</Lqi><AccessPointId>66618</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>a5f92c8b-070f-4968-8b67-41e7d6d5e665</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2016-03-23T14:31:58.797+01:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D1044E73</LabelId><Type>G1 7.4</Type><WakeupTime>2016-04-08T09:02:25.797+02:00</WakeupTime><FirmwareVersion>3.0.3</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>251</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>1</CurrentPage><Rssi>-60</Rssi><Lqi>45</Lqi><AccessPointId>66618</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>a56dd76c-5c8a-4f1b-8f7d-47303203991f</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>1</Page><Status>SUCCESSFUL</Status><UpdatedAt>2016-03-23T13:37:39.466+01:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D1044ED3</LabelId><Type>G1 7.4</Type><Tag>Besprechung_IT</Tag><WakeupTime>2016-04-08T09:05:01.422+02:00</WakeupTime><FirmwareVersion>3.0.3</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>251</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-74</Rssi><Lqi>34</Lqi><AccessPointId>66618</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>288bf683-57dc-40a4-b153-a2013902fb16</TaskId><TaskType>IMAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2016-03-23T11:45:47.353+01:00</UpdatedAt></LabelInfo></LabelInfoPagedResult>
2016-04-08T09:12:09,940 [WeP Service Task] INFO WePService - updating WePs
2016-04-08T09:12:09,941 [WeP Service Task] DEBUG UpdateManager - generating tags
2016-04-08T09:12:09,941 [WeP Service Task] WARN UpdateManager - Calendar name is not set for calendar with id: Besprechung_IT - skipping calendar
2016-04-08T09:12:09,941 [WeP Service Task] DEBUG UpdateManager - Extracted tag 'null' from calendar: id=Besprechung_IT, name=null, events=[]
2016-04-08T09:12:09,942 [WeP Service Task] DEBUG UpdateManager - does a tagUpdater for tag 'ITTECHNIK' exist: false
2016-04-08T09:12:09,958 [WeP Service Task] DEBUG UpdateManager - does a tagUpdater for tag 'Besprechung_IT' exist: false
2016-04-08T09:12:09,958 [WeP Service Task] WARN UpdateManager - Skipping update of tag 'Besprechung_IT' as there is no calendar with matching name available
2016-04-08T09:12:09,959 [WeP Service Task] WARN UpdateManager - Skipping update of tag 'ITTECHNIK' as there is no calendar with matching name available

patrickb
Beiträge: 2
Registriert: 22 Apr 2016, 11:41

Re: ePaper Anbindung an Google Kalender

Beitrag von patrickb » 22 Apr 2016, 11:44

Wir haben auch das gleiche Problem.
Etliche Variationen schon durch, nichts funktioniert. Würden uns über Hilfe freuen!!

Eine Frage: Ändert sich dann nach erfolgreichem auslesen der Calender auch das Bild auf den Displays?

patrickb
Beiträge: 2
Registriert: 22 Apr 2016, 11:41

Re: ePaper Anbindung an Google Kalender

Beitrag von patrickb » 17 Mai 2016, 16:21

Problem lag bei uns intern an der Firewall Einstellung.
Bei Lancom Support hat unsere Config Datei funktioniert und in einem anderen Netz auch!

#Done

AnasT
Beiträge: 1
Registriert: 02 Mai 2018, 19:00

Re: ePaper Anbindung an Google Kalender

Beitrag von AnasT » 09 Mai 2018, 18:38

Hallo Kollegen,
ich habe Probleme den Google Kalender mit dem ePaper Server zu verbinden.
es ist genau wie du hast,oder sehr ähnlich.
ich hab alle Firewalls ausgeschaltet aber das bringt nix. :(
Bitte helfe!!!
here ist mein log daten:
-------------------------------------------------------------------------------------------------------------------------------------
2018-05-09T18:35:53,808 [WeP Service Task] INFO WePService - updating -------------------------------------------------
2018-05-09T18:35:53,809 [WeP Service Task] INFO WePService - reading calendars
2018-05-09T18:35:53,811 [WeP Service Task] INFO WePService - reading WeP states
2018-05-09T18:35:53,811 [WeP Service Task] TRACE Request - creating connection
2018-05-09T18:35:53,811 [WeP Service Task] DEBUG Request - URL = http://20.x.x.x:8001/service/labelinfo
2018-05-09T18:35:53,811 [WeP Service Task] TRACE Request - Opening connection
2018-05-09T18:35:53,811 [WeP Service Task] TRACE Request - connection created
2018-05-09T18:35:53,811 [WeP Service Task] TRACE Request - creating authentication
2018-05-09T18:35:53,812 [WeP Service Task] TRACE Request - authentication created
2018-05-09T18:35:53,812 [WeP Service Task] TRACE Request - setting request method to GET
2018-05-09T18:35:53,816 [WeP Service Task] DEBUG Request - Response is: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><LabelInfoPagedResult records="5" totalRecords="5" totalPages="1" page="0" recordsPerPage="5"><LabelInfo><LabelId>D3087F1D</LabelId><Type>7.4 BWR</Type><Tag>CHARLOTTENBURG</Tag><WakeupTime>2018-05-09T18:21:23.149+02:00</WakeupTime><FirmwareVersion>3.0.5</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>203</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-72</Rssi><Lqi>25</Lqi><AccessPointId>84642</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>f323243f-8f3c-4b77-94df-8b228aef451c</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2018-05-02T13:19:54.396+02:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D3087F37</LabelId><Type>7.4 BWR</Type><Tag>FRIEDRICHSHAIN</Tag><WakeupTime>2018-05-09T18:21:25.014+02:00</WakeupTime><FirmwareVersion>3.0.5</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>203</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-64</Rssi><Lqi>13</Lqi><AccessPointId>84642</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>484655b4-f080-4af4-b96a-a9b18697b13c</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2018-05-02T13:19:54.391+02:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D3087F4C</LabelId><Type>7.4 BWR</Type><Tag>NEUKOLLN</Tag><WakeupTime>2018-05-09T18:29:25.955+02:00</WakeupTime><FirmwareVersion>3.0.5</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>235</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-69</Rssi><Lqi>9</Lqi><AccessPointId>84642</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>63fabf81-ef6e-493f-be1b-849a23ce8836</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2018-05-02T13:19:54.357+02:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D3087F7F</LabelId><Type>7.4 BWR</Type><Tag>KREUTZBURG</Tag><WakeupTime>2018-05-09T18:34:29.672+02:00</WakeupTime><FirmwareVersion>3.0.5</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>247</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-78</Rssi><Lqi>17</Lqi><AccessPointId>84642</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>86c28db4-3761-4c46-a762-1bf4bf2a6559</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2018-05-02T13:19:59.405+02:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D3087F97</LabelId><Type>7.4 BWR</Type><Tag>WILHERMSDORF</Tag><WakeupTime>2018-05-09T18:35:45.628+02:00</WakeupTime><FirmwareVersion>3.0.5</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>251</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-68</Rssi><Lqi>26</Lqi><AccessPointId>84642</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>1dc8e52b-6008-496b-9337-0f45f6db2658</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2018-05-02T13:19:59.400+02:00</UpdatedAt></LabelInfo></LabelInfoPagedResult>
2018-05-09T18:35:53,816 [WeP Service Task] DEBUG WePClient - Received response: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><LabelInfoPagedResult records="5" totalRecords="5" totalPages="1" page="0" recordsPerPage="5"><LabelInfo><LabelId>D3087F1D</LabelId><Type>7.4 BWR</Type><Tag>CHARLOTTENBURG</Tag><WakeupTime>2018-05-09T18:21:23.149+02:00</WakeupTime><FirmwareVersion>3.0.5</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>203</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-72</Rssi><Lqi>25</Lqi><AccessPointId>84642</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>f323243f-8f3c-4b77-94df-8b228aef451c</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2018-05-02T13:19:54.396+02:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D3087F37</LabelId><Type>7.4 BWR</Type><Tag>FRIEDRICHSHAIN</Tag><WakeupTime>2018-05-09T18:21:25.014+02:00</WakeupTime><FirmwareVersion>3.0.5</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>203</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-64</Rssi><Lqi>13</Lqi><AccessPointId>84642</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>484655b4-f080-4af4-b96a-a9b18697b13c</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2018-05-02T13:19:54.391+02:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D3087F4C</LabelId><Type>7.4 BWR</Type><Tag>NEUKOLLN</Tag><WakeupTime>2018-05-09T18:29:25.955+02:00</WakeupTime><FirmwareVersion>3.0.5</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>235</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-69</Rssi><Lqi>9</Lqi><AccessPointId>84642</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>63fabf81-ef6e-493f-be1b-849a23ce8836</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2018-05-02T13:19:54.357+02:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D3087F7F</LabelId><Type>7.4 BWR</Type><Tag>KREUTZBURG</Tag><WakeupTime>2018-05-09T18:34:29.672+02:00</WakeupTime><FirmwareVersion>3.0.5</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>247</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-78</Rssi><Lqi>17</Lqi><AccessPointId>84642</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>86c28db4-3761-4c46-a762-1bf4bf2a6559</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2018-05-02T13:19:59.405+02:00</UpdatedAt></LabelInfo><LabelInfo><LabelId>D3087F97</LabelId><Type>7.4 BWR</Type><Tag>WILHERMSDORF</Tag><WakeupTime>2018-05-09T18:35:45.628+02:00</WakeupTime><FirmwareVersion>3.0.5</FirmwareVersion><SecurityStatus>AES128</SecurityStatus><PowerStatus>GOOD</PowerStatus><SyncQuality>251</SyncQuality><LabelErrors>0</LabelErrors><CurrentPage>0</CurrentPage><Rssi>-68</Rssi><Lqi>26</Lqi><AccessPointId>84642</AccessPointId><ConnectionStatus>ONLINE</ConnectionStatus><TaskId>1dc8e52b-6008-496b-9337-0f45f6db2658</TaskId><TaskType>SWITCH_PAGE</TaskType><Page>0</Page><Status>SUCCESSFUL</Status><UpdatedAt>2018-05-02T13:19:59.400+02:00</UpdatedAt></LabelInfo></LabelInfoPagedResult>
2018-05-09T18:35:53,823 [WeP Service Task] INFO WePService - updating WePs
2018-05-09T18:35:53,823 [WeP Service Task] DEBUG UpdateManager - generating tags
2018-05-09T18:35:53,823 [WeP Service Task] DEBUG UpdateManager - does a tagUpdater for tag 'CHARLOTTENBURG' exist: true
2018-05-09T18:35:53,823 [WeP Service Task] DEBUG UpdateManager - does a tagUpdater for tag 'FRIEDRICHSHAIN' exist: true
2018-05-09T18:35:53,823 [WeP Service Task] DEBUG UpdateManager - does a tagUpdater for tag 'NEUKOLLN' exist: true
2018-05-09T18:35:53,823 [WeP Service Task] DEBUG UpdateManager - does a tagUpdater for tag 'KREUTZBURG' exist: true
2018-05-09T18:35:53,823 [WeP Service Task] DEBUG UpdateManager - does a tagUpdater for tag 'WILHERMSDORF' exist: true
2018-05-09T18:35:53,823 [WeP Service Task] WARN UpdateManager - Skipping update of tag 'FRIEDRICHSHAIN' as there is no calendar with matching name available
2018-05-09T18:35:53,823 [WeP Service Task] WARN UpdateManager - Skipping update of tag 'NEUKOLLN' as there is no calendar with matching name available
2018-05-09T18:35:53,823 [WeP Service Task] WARN UpdateManager - Skipping update of tag 'KREUTZBURG' as there is no calendar with matching name available
2018-05-09T18:35:53,823 [WeP Service Task] WARN UpdateManager - Skipping update of tag 'WILHERMSDORF' as there is no calendar with matching name available
2018-05-09T18:35:53,823 [WeP Service Task] WARN UpdateManager - Skipping update of tag 'CHARLOTTENBURG' as there is no calendar with matching name available

-------------------------------------------------------------------------------------------------------------------------------------

Antworten

Zurück zu „LANCOM Wireless ePaper“