Open Roellen opened 10 months ago
Both bugs are corrected in vis-2
Thanks! (actually I can't use vis-2 right now as no inventwo buttons are available yet)
Thanks! (actually I can't use vis-2 right now as no inventwo buttons are available yet)
Hi Roellen, same for me: Especially we use the universal switch from inventwo to control popups all over the project just by using several datapoints for opening or closing a couple of popups: e.g. for information, alarm, showing that a door was opened or a movement was detected etc etc. Having no alternative in vis-2 yet we cannot use vis-2 right now. Do you plan to migrate from inventwo to other widgets by starting a rather extensive change project? And by the way: I've seen cameras in your example... with which widget were you successful to link your cams into iOBroker-VIS? I still fail while trying to do so. Regards Michael
I just tried to use VIS2. When moving the browser-windows... VIS2 does not show up ANYTHING. After loading... it shows something... and then.. WHITE SCREEN. Maybe it's because I don't have a valid license yet. But iam still unsure what it means to convert from VIS1 to VIS2 without going back ever. And there is no help or info shown there about what this means. Will me VIS2 never work then?
However, my VIS1 made progress over the last 5 years and redoing everything is VIS2 is... some work. Maybe 20 hours, who knows.
Regarding the cameras in my VIS: You need to convert the camera stream so that it can be displayed in a browser. I used "motion eye" software. There is also "WEBRTC" https://github.com/AlexxIT/go2rtc Which you can install just by one click if you have proxmox installed. https://tteck.github.io/Proxmox/
WEBRTC needs much less CPU and RAM and it's "real time". So no stuttering in the video signal. And it can give you audio and videosignal at the same time. I can get the camera-stream out of my vis with finger-gesture... and I can make it "full screen" and stream it with apple airplay to another display for example.
Migrating to VIS2: I don't think that 20hours will be sufficient. But before we have a solution for the universal switch from inventwo to control popups in VIS1 we are not able to even start a VIS2-project, as these important "system" controls (i.e. the popups) are not working in VIS2 right now.
Thank you for your hints regarding cams in VIS: Yes, we do have Proxmox installed and the IOB is running in a Proxmox-VM. But I tried to understand the documentation given in "WEBRTC" https://github.com/AlexxIT/go2rtc - but unfortunately this is beyond my personal capabilities of handling a Proxmox->iOBroker->VIS system. I am afraid that there is no description that a non-Unix-guy can follow successfully. Example: "...install just by one click" means... what? Install in the IOB-VM? On console level in the IOB-VM? You see that I do not really know "how to".
Yeah... documentation is always a problem. I tried, for fun, to install iobroker on a raspberry pi. (which i never did before) And the documentation even for that is not that good. :-)
The easiest way to install the WEBRTC thing is to go to proxmox and to the "main shell". (the icon below the name "datacenter", then hit the "shell" button on the top right side. copy/paste (by using right butt on the mouse to insert the link... strg+c and strg+v does not seem to work here) bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/go2rtc.sh)"
Then there will automatically a vm beeing added and the WEBRTC will be installed automatically.
The easiest way to install... Thanks to your explanations I started this job. This is what the system then tells me:
In other words: I would have to update Proxmox first? OMG. Updating Proxmox seems to be hell on earth, or isn't it? Well, I even did not install Proxmox a couple of years ago, someone else did.
p.s.: Update of Proxmox executed following a YouTube-Clip. Seems to work fine, IOB up and running. So: Again following your advice then to install the go2rtc.
Following the updates, which to my astonishment went through without any issue, I retried your go2rtc advice.
And now I have a running go2rtc VM.
But I still don't see the cams and how to connect:
I can go to the go2rtc via browser and without understanding what is necessary to do next I just started it ans looked at "add" and found "onvif" and remembered that this has something to do with the streams of e.g. Reolink-cams.
And: The go2rtc searched in the local WLAN here and found something...
So is this correct? What are next steps please: Connect one of these streams to the go2rtc?
I can take one of the cams found and copy the url into the field above, clicking "test" shows success:
And then: How to implement go2rtc in the IOB? Please advise.
PLEASE consider this is no general discussion forum. So stick to the topic of the issue. Feel free to discuss at out forum https://forum.iobroker.net and post a link her if you prefer. But setting up camraequipment etc. seesm OT here.
@mcm1957: Yes, you are correct. Excuses if this caused any inconvenience. I opened a question in the forum.
@Roellen: Can you please post an answer here... https://forum.iobroker.net/topic/73885/go2rtc-iob-vis-widget
Your advice is highly appreciated. Cheers
No problem - one or two OT questions are always OK. But I did not see an end of the support discussion.
Anyway one Info related to this topic: Inventwo has released vis-2 widgets for testing: vis-2-widgets-inventwo I'll try to release it to latest soon, but should be available at npm already.
pls let us know when Inventwo has released or you have released vis-2 widgets. Then I can try the universal switch from inventwo to control popups in VIS2. As per today this does not work.
Describe the bug
Bug 1: Tabs are shown in two rows. (should be visible in just one row, otherwise the < > left and right buttons would not make much sense. Bug 2: When using two times the slider-tab in one View then both slider tabs will not work work correctly. There are missing Views. Which means... you can click on one tab but nothin is beeing displayed in the tab. If I remove the second slider-tab and use just one.. and then it works again.
To Reproduce
Just add the "slider-tab" widget to the VIS.
Expected behavior
One row only should be visible. Two slider-tab widget should work at the same time.
Screenshots & Logfiles
Video: https://www.youtube.com/watch?v=CH84W-vqZnU
Versions:
Additional context