Timeline picker to setup heating, light and so on

When you paste the URL directly and the timeline is visible and working, than i’m pretty sure it’s a cache problem. Can you please repeat the clearing of cache?

thanks for your help, so delete cache 3 times on phone and pc (windows) rebooting both and the problem remain, trying on firefox …is fine , trying on Chrome not working , trying on edge not working , trying on my older tablet android and there is working… ? same account chrome on all device and same sitemap , triggered item work fine, also clear cache on openhab-Cli and rebooting

I have no idea. There is the difference between chrome anf firefox?
All nessesary files are served from the integrated server in OH and this is the same for chrome and firefox.

Which version from OH do you using? But I don’t think it is OH.


You can try or check this and perhaps @Sefer has an additional idea.

i did right now and still the same , i don’t use the migrationToJSR223 version just this one " https://gitlab.com/RNTs_3/openhab-timeline-picker.git"

Okay, now is weekend. Perhaps we can look on the problem.
You wrote:

Can you post the output in the console in the dev tool?

here is the log from chrome

index.html:129 GET net::ERR_ABORTED 404 (Not Found)
index.html:130 GET net::ERR_ABORTED 404 (Not Found)
css:1 GET https://fonts.gstatic.com/s/roboto/v20/KFOmCnqEu92Fr1Mu4mxK.woff2 net::ERR_NAME_NOT_RESOLVED
index.html:130 GET net::ERR_ABORTED 404 (Not Found)
switchPointSet.js:7 Uncaught ReferenceError: Vue is not defined
at switchPointSet.js:7
(anonymous) @ switchPointSet.js:7

the timeline showup 2days then stay loading… but the rules and triggers work correctly

Please post a screenshot from the directorys and included files inside openhab-conf/html.

Here is the error :upside_down_face:

You need vue.js not the minified version.
vue-resource.js is also missing.

But, why the timelinepicker is working with firefox and wrong and missing files?

Don’t forget to clear the cache after inserting the files.

I don’t know why lol and work perfect on my android tablet

boom it’s worked !

again again…thanks a lot for your help :slight_smile:

@isoparme cool.
Then a nice weekend.

I had the same problem, as above. “vue-ressources” was missing in my case. The screenshot cured my problem. Thx a lot

What solutions have you all used for changing the weekly schedule between two or more different schedules?

It’s the school half term holiday here so my children’s room schedules have changed from being cool during the day to being warm all day. I assume I could create three transferitems per room, one for the live schedule, one for a school week and one for a holiday week and then could use a rule based on a button in a sitemap to allow the user copy either the school week or the holiday week transferitem to the live transferitem when a holiday starts or ends?

Has anyone done anything like this or anything else to make changing between different but regularly occurring schedules easier?


I used this function to set up my heating control for the rooms. Now I want to deactivate the TimePicker for this room by rule when a window is open.

Is it that easy to do this or do I have to manipulate the JSON file in a rule ?

Hi @dimmenhau,
i would suggest to create a additional item for each room as roommode. This mode should be select the right setpoint (auto, off). I think this way is much more flexible and you are not affected then the data struktur of JSON in transfer item is changed in a newer version.
When a window is opened you can persist the current mode for this romm, set the mode to off and after closing the window restore the persisted mode.

Hi all,

thanks for ur effort in building the timeline picker. I set it up today and just got one problem with it and don’t know where to look at :frowning: Everything is working so far but the webview doesn’t show my current timeline? After a refresh of the sitemap the timeline is all grey and looks empty again. But the timeline string item has the correct json values and also triggers the on/off events at the correct times. Any ideas where the problem could be located?