Try this link:

rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov

@sdetweil said in Default calendar - parsing of VEVENT:

uses the preloaded modules/default/calendar/vendor/ical.js

Ah, that was the missing link !
Now I understand where it comes from (I mean the ‘data’ stuff that calendarfetcher.js uses).

Will try with latest ical.js.

Thanks.

HI,

Can someone tell me how this Google event is parsed to the ‘data’ structure in calendarfetcher.js ?

basic.ics part. (correct):

BEGIN:VEVENT
DTSTART;VALUE=DATE:20200330
DTEND;VALUE=DATE:20200331
DTSTAMP:20200329T132348Z
UID:xxxl8quduqtvqbfe00fsk8xxx@google.com
CREATED:20200329T132240Z
DESCRIPTION:
LAST-MODIFIED:20200329T132240Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:TEST_ENTRY_FULLDAY
TRANSP:TRANSPARENT
END:VEVENT

calendarfetcher.js part (incorrect):

0|mm  | { type: 'VEVENT',
0|mm  |   params: [],
0|mm  |   start: { 2020-03-29T22:00:00.000Z tz: undefined, dateOnly: true },
0|mm  |   end: { 2020-03-30T22:00:00.000Z tz: undefined, dateOnly: true },
0|mm  |   dtstamp: { 2020-03-29T13:23:15.000Z tz: undefined },
0|mm  |   uid: 'xxxul8quduqtvqbfe00fsk8xxx@google.com',
0|mm  |   created: { 2020-03-29T13:22:40.000Z tz: undefined },
0|mm  |   description: '',
0|mm  |   lastmodified: { 2020-03-29T13:22:40.000Z tz: undefined },
0|mm  |   location: '',
0|mm  |   sequence: '0',
0|mm  |   status: 'CONFIRMED',
0|mm  |   summary: 'TEST_ENTRY_FULLDAY',
0|mm  |   transparency: 'TRANSPARENT' }

The background of this question, is that a full day event for tomorrow, is shown on the MM as Today.
Based on the start and end date from the calendar module, this may seem right, but does not match my correct Google calendar DTSTART and DTEND dates.

This annoys me already for some time (also happens for reoccurring full day events) and I wanted to see where it might go wrong.
Unfortunately I am not skilled enough to see where the actual parsing part takes place.
It seems to me ‘locale’ or timezone issue and converting to unixtime.

And it also annoys me that it shows as Today or in XX Days, when I would like to see it as Mon Mar 30th, like my normal events.

Greetings,

E.J.

@Hram2008 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

Has anyone been able to get this working with Axis camera products?

Yes, I have.

Please show your MMM-RTSPStream part from config.js.

@Egnos said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

Can you help me?

What platform are you on.
Raspberry Pi with Debian?

lsb_release -a

sudo apt-get install omxplayer

@Egnos said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

does this mean i have to uninstall the module RTSPStream’s and install only the component OMXplayer?

If you are able to install OMXPlayer, then you can give MMM-RTSPStream a try.
In principle it does work, depending on what you want to stream.
If it works for you, perfect, if it doesn’t, then try if omxplayer works standalone,
Actually testing omxplayer standalone is always a good thing before trying out MMM-RTSPStream.

@Egnos said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

E: Impossibile trovare il pacchetto omxplayer

To me it looks like it cannot install omxplayer.
You can try to install it manually.
The script does it using this command:

sudo apt install -y omxplayer

Perhaps another command is needed, or indeed the package to install omxplayer does not exist for your platform.

@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

now its working!

Great to hear!

When you add

omxRestart: 1,

in the

config: {

part, then when restarting MagicMirror, the omx_stream1 will be stopped and restarted too.
If you really want to stop MagicMirror and omx_stream1, then you will need to stop both:

pm2 stop MagicMirror
pm2 stop omx_stream1

Provided that you named you stream1 stream1.

@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

subtype=1 with h264

Can you try the subtype=1 option and remove the --info part from the command?

@Number_5

@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

Video: hevc

It looks like this is the problem.
The omxplayer cannot handle this, as it seems.

Do you have access to this Dahua Config Tool GUI stuff:
(I hope the picture shows)

Cannot upload a picture to the forum :disappointed_face: :face_with_steam_from_nose:

http://www.dh-vision.com/index.php/dahuaencoding

How many Channels do you have ?
Is there a channel with Compression H.264 (something not H.265) ?
Is there a Sub Stream that is enabled with Compression H.264 (something not H.265) ?
What Compresion options are there ?

We are looking for a "channel=X&subtype=Y"combination that might work.

@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

with subtype=0 the second attempt

And with subtype=1 and subtype=2 ?
And with channel=1&subtype=1 ?

You can leave out the omxplayer.log for the moment.

@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

401 Unauthorized

401 Unauthorized
means user password combination is not correct.

admin:roland

Note the : and of course your correct password.

@Number_5

One more thing.
Can you also try with subtype=1 and subtype=2 ?

Looks to be a decoding issue and subtype=0 might be too new for omxplayer.
Someone claims this is working:

channel=1&subtype=2

@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

401 Unauthorized

Did you supply your user and password iso xxx.xxx ?

@Number_5

Copy/paste error on my side

omxplayer --info --genlog --avdict rtsp_transport:tcp --win 786,424,1138,666 --live --video_queue 4 --fps 30 --no-osd 'rtsp://xxx.xxx@192.168.2.108:554/cam/realmonitor?channel=2&subtype=0'

Hope this works better.

@Number_5

Can you try this, to try to see what codec is used?

omxplayer --info --genlog --avdict rtsp_transport:tcp --win,424,1138,666 --live --video_queue 4 --fps 30 --no-osd 'rtsp://xxx.xxx@192.168.2.108:554/cam/realmonitor?channel=2&subtype=0'

@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

ok, sorry,

I am sorry too :-)

Did you change the actual password of your cam or just changed the text in the admin:roland!?1971 part ?

I do not have a Dahua cam, so I do not know where and how to set it.
Probably there is a GUI (a web page) where you can do this.
I guess you can open it like this:
http://192.168.2.108
But once you did set it to the password we are seeing right now, so you ought to know :-)

@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

after execute the commando "vi ~/MagicMirror/config/config.js " in commandline , the config.js openend

Yes, sorry about that, vi is a text editor.
Close it with :q! or [ESC]:q! (where [ESC] is the escape key)
Then use the editor of your choice, like nano.

nano ~/MagicMirror/config/config.js

@Number_5

Could you please change your admin password of your cam to something without characters like ! and & ?
When really needed, use + and/or _.

Perhaps omxplayer has a parsing problem.
Even tough we use single quotes to avoid this.
I get the same error when using ?.

Then try (with the changed password):

omxplayer --genlog --avdict rtsp_transport:tcp --win 786,424,1138,666 --live --video_queue 4 --fps 30 --no-osd 'rtsp://admin:roland_1971@192.168.2.108/cam/realmonitor?channel=2&subtype=0'

You can also try the vlc player ‘trick’.
IMHO it should not ask for user & password.

Also try to play with the port.
Either nothing, or :80 or :554.

Btw, 192.168.2.140.2.108 is not a valid IP address.
It is either 192.168.2.108 or 192.168.2.140.
I guess 192.168.2.140 is your MM / Rasperry Pi IP and 192.168.2.108 is your Dahua cam IP.

Good luck.

@sdetweil said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

no port specified, has camera ip that worked with vlc.

What bothers me, is the fact that vlc did not take the supplied user and password, but queried again for it.
omxplayer will not do that; will just fail to open.