Offline
Hi Chriz, long time no see! I’m building another mirror for a friend. I was one of the first ones to order your glass back in 2016 :D
Please add another glass to the list with the following properties:
(Edit: Can’t remember if sub-cm measures are possible, if not, just round to 36)
I created a module that visualizes produced, stored and consumed energy in your house in a minimalistic way.
It is meant to be used when you have a solar plant and an energy storage system (optional) installed.
https://github.com/deg0nz/MMM-EnergyMonitor
The module relies on other modules that provide data for it. It gets data updates via notifications from these “data source” modules.
Depending in which direction the power flows, the arrows change and current values are updated.
I developed MMM-VartaESS for Varta Energy Storage Systems and MMM-Fronius2 for Fronius power converters as companion modules for this to provide the necessary data.
The README in the GitHub repo explains, how to send data updates.
@Jaunney I don’t see that this has ben answered yet.
collections = [“UUID1”, “UUID2”, “UUID3”] is what I use in my config and it works.
Of course, you need to add a new calender to your calender module to make them visible on the mirror. You need one for every UUID. If you look into your target sync folder on the Pi, there should be 3 .ics files for each UUID. Those are, in fact, 3 separate calendars
Hi,
I have another hint related to the systemd timer that was originally described in my tutorial.
It is advised to download the vdirsyncer.service and vdirsyncer.timer directly from the web.
You need to adjust the path to the executable in the vdirsyncer.service file!
It defaults to ExecStart=/usr/bin/vdirsyncer sync, which can be wrong.
But probably it is in ~/.local/bin. (Can be different depending on your installation. Just check location with which vdirsyncer.
This should make the initially described automatic sync work again.
@elliot1996 I would need more information to help you debug this. Are you sure you used the right directory for the file? And you used the --user option when executing systemctl?
Everything you need to know about systemd unit files is here: https://www.freedesktop.org/software/systemd/man/systemd.unit.html
The file must be in one of the directories mentioned at the top of the page.
@thisistheplace I never tried syncing VTODO. All I can do here, is to refer to the vdirsyncer docs regarding this topic: https://vdirsyncer.pimutils.org/en/stable/config.html?highlight=VEVENT#storage-caldav
Unfortunately you have to dig into that yourself, my time is very limted currently…
Awesome module! Thank you so much! I was just browsing around on this forum and immediately installed it. Good work.
@oneartur The example config only shows all the possible config values and is not meant for real world usage. There are some values in it that don‘t work.
Please start with an minimal possible config (the only mandatory entry is the stationId) and add adjustments to your needs.
@mdefrancesco Sorry for the late reply.
Hmm… that’ weird. Did you get it working by now?
If not:
Did you use the --user flag when activating the timer? And what does systemctl --user status vdirsyncer.timer say?
And did you try different times in the timer file? I could imagine that setting everything to 1 minute could cause problems…
@MZ-BER Hey! Thanks a lot! I’m happy you like it :)
If I remember correctly, the bus lines in Berlin have no colors. Maybe @derhuerst can verify that?!
If you can give me a source where to find the colors for each bus line, I can add this.
What we could do though, is distinguishing normal buses, Metro-Bus and X-Bus.
@htilburgs This is exactly what I‘m trying to prevent/workaround with this tutorial.
Using a public calendar URL allows anyone to see your calendars without any authentication at all. This way your calendars are open and accessible by anyone who knows the URL. (URLs can be crawled by machines ;))
This here is just a secure method to sync your calendars.
If you don‘t care about having your personal life available to anyone or anything, it‘s your business.
@Sammie1232 Seems like the folder and/or the file do not exist. Please create them if they are not there.
The folder needs to be owned by the current user. On a Raspi, this command would look like this: chown -R pi:pi /home/pi/.vdirsyncer
@yk Dis you activate the systemd unit for the timer? You can enable it with sudo systemctl enable vdirsyncer.timer you can also check via sudo systemctl status vdirsyncer.timer, is it’s enabled already. If so, it should work…
@showbizkid Did you create the .vdirsyncer folder first? Sounds like it is not present…
@nem1 Try to make the git pull and npm install without sudo.
You can also try to completely remove the module folder and clone it again. Sometimes this solves such problems.
I changed the module to use vbb-hafas directly instead of using the unavailabe endpoint 2.vbb.transport.rest. If you update your module, you should be able to see departures again (let’s see how long this will work…).
@AgP42: Note, that MMM-PublictransportBerlin parses VBB/Berlin-specific changes in the HAFAS-API, as @derhuerst described them here: https://github.com/public-transport/hafas-client/blob/master/p/vbb/readme.md.
If they don’t matter to you, you can leave it as it is and continue using MMM-PublicTransportHafas :)
The API is live again. Let’s see how long the new method is working… I have antoher solution on my roadmap to make this more reliable (hopefully :D)
@AgP42 The Problem was not your configuration, but the data source the module is getting it’s data from. When you get the shown error, the module was configured right.
You can find them here: https://github.com/deg0nz/MMM-PublicTransportBerlin/issues/
Additionally, you can check the avialability of the data source here: https://status.transport.rest
@nem1
This actually means what it says. VBB Data is currently not available. The API is down for some days now… The error has been reported.
You can check the status at https://status.transport.rest
Attention:
Due to changes in the API, the stationId must be a string now. If you experience errors, please check the updated readme and change your configuration to use a string for the ID.
This is also true for the directionStationId is you use this feature.
@OsCourt I think you need to use dav.php instead of cal.php on newer baikal versions. Also you need to use digest authentication with the calendar module of the mirror. It’s described in the readme of the module.