Moderator: leecollings
For what kind of device are you trying to set the volume?RapTile wrote: Friday 02 November 2018 20:53 The sliders for volume don't run as smooth as they do in domoticz.
Is that normal? it looks like the sliders want to set the value along the way they slide instead of setting the value when u let go of your mouse button.
It's for my TV and receiver but they are set as a dimmer i suppose.Lokonli wrote: Saturday 03 November 2018 18:01For what kind of device are you trying to set the volume?RapTile wrote: Friday 02 November 2018 20:53 The sliders for volume don't run as smooth as they do in domoticz.
Is that normal? it looks like the sliders want to set the value along the way they slide instead of setting the value when u let go of your mouse button.
I noticed that the slider for a dimmer block also didn't work very well. I'm preparing a fix for that.
I also had the problem causing double triggers and updates.RapTile wrote: Friday 02 November 2018 20:53 The sliders for volume don't run as smooth as they do in domoticz.
Is that normal? it looks like the sliders want to set the value along the way they slide instead of setting the value when u let go of your mouse button.
Code: Select all
function addSlider(idx, sliderValues) {
$(".slider" + idx).slider({
value: sliderValues.value,
step: sliderValues.step,
min: sliderValues.min,
max: sliderValues.max,
/*slide: function (event, ui) {
sliding = true;
slideDevice($(this).data('light'), ui.value);
},*/
change: function (event, ui) {
sliding = true;
slideDevice($(this).data('light'), ui.value);
},
stop: function (event, ui) {
sliding = false;
}
});
}
Thanks, ill give that a try later on!frustreerMeneer wrote: Monday 03 December 2018 9:25I also had the problem causing double triggers and updates.RapTile wrote: Friday 02 November 2018 20:53 The sliders for volume don't run as smooth as they do in domoticz.
Is that normal? it looks like the sliders want to set the value along the way they slide instead of setting the value when u let go of your mouse button.
You could try commenting out the slide function in addSlider in main.js like so:
Code: Select all
function addSlider(idx, sliderValues) { $(".slider" + idx).slider({ value: sliderValues.value, step: sliderValues.step, min: sliderValues.min, max: sliderValues.max, /*slide: function (event, ui) { sliding = true; slideDevice($(this).data('light'), ui.value); },*/ change: function (event, ui) { sliding = true; slideDevice($(this).data('light'), ui.value); }, stop: function (event, ui) { sliding = false; } }); }
Currently for most functionality you have to use the beta version of Dashticz.tileiran wrote: Thursday 20 December 2018 7:02 In latetest master, selector switch is not working on my dashbord then also 'weather' and 'currentweather_big' is not showing any icons in stand by when using new moving icons.
Is it the image on the button that is refreshed and start to play, or is it the stream that starts to play (like you pressed the button)?Bram81 wrote: Friday 18 January 2019 14:02 Hi guys,
I'm running Dashticz on a wall mounted Android tablet using the Fully browser. Main reason for using this browser is that the inbuild player is capable of handling RTSP so I can open the livestreams of my two Foscam babymonitors. So far so good. I've created two buttons for the cams on my dashboard showing snapshots. When being pushed on, the stream of the camera opens in fulll screen mode inside the Fully browser.
My problem is that, even though I've disabled video autoplay inside Fully settings, both streams keep being loaded automatically aprox 50 sec after I've loaded my Dashticz homescreen. I've tried to do some debugging connecting the tablet to a laptop and using chrome dev tools. I'm not an expert in this, but it seems that something in the Dashticz code is triggering the streams to play.
Does anyone know of a way to solve my problem? All suggestions and or help are much appreciated!
It is the stream that starts to play as if I pressed the button and that is the case for both camera's. My buttons are defined as follows:Lokonli wrote: Friday 18 January 2019 18:45
Is it the image on the button that is refreshed and start to play, or is it the stream that starts to play (like you pressed the button)?
Can you post the definition of the button from your CONFIG.js here?
There are two refresh parameters you can play with:
refresh and refreshiframe
You can add them to your button definition. They indicate the refresh period of the image in the button and of the linked iframe, in msec.
This might trigger the stream to autoplay. Default is 60000 (=60s). Just make the two parameters very big.
Try adding refreshiframe:6000000Bram81 wrote: Saturday 19 January 2019 15:15It is the stream that starts to play as if I pressed the button and that is the case for both camera's. My buttons are defined as follows:Lokonli wrote: Friday 18 January 2019 18:45
Is it the image on the button that is refreshed and start to play, or is it the stream that starts to play (like you pressed the button)?
Can you post the definition of the button from your CONFIG.js here?
There are two refresh parameters you can play with:
refresh and refreshiframe
You can add them to your button definition. They indicate the refresh period of the image in the button and of the linked iframe, in msec.
This might trigger the stream to autoplay. Default is 60000 (=60s). Just make the two parameters very big.
buttons.juul = {key:'Juul',width:12, isimage:true, refreshimage:100000, image: 'http://192.168.2.12:88/cgi-bin/CGIProxy ... >pwd=<pass>', url:"rtsp://<user>:<pass>@192.168.2.12:88/videoMain"}
buttons.david = {key:'David',width:12, isimage:true, refreshimage:100000, image: 'http://192.168.2.15:85//cgi-bin/CGIProx ... &pwd=<Pass>', url:"rtsp://<user>:<pass>@192.168.2.15/videoMain"}
I don't have refreshiframe defined, only refreshimage, and that refreshrate is not matching the aprox 50 sec after which the streams are triggered. Does this make sense to you?
I expect it will start playing after 1,5 hrs. I think you should make the time bigger than the dashticz refresh time. You can set this last one via the config['dashticz_refresh'] setting in your CONFIG.js (in minutes, not msec)Bram81 wrote: Saturday 19 January 2019 15:55 That seems to work for now, thanks!! Does this mean the refreshiframe value now is never reached because it starts over counting after the imagerefresh or will it still start playing the streams after 1,5 hrs?
Hi, it does start to play after 1,5 hrs even though the dashticz refresh time is set to 5 seconds. The autoplay does also start after the first start of dashticz of after a refresh. You're right it would be more than acceptable to need some more time to load but being able to only start a the stream after a button press. Do you know how to do that? Thanks for your help!!Lokonli wrote: Saturday 19 January 2019 17:43 [
I expect it will start playing after 1,5 hrs. I think you should make the time bigger than the dashticz refresh time. You can set this last one via the config['dashticz_refresh'] setting in your CONFIG.js (in minutes, not msec)
Does the stream also autoplay at the first start of Dashticz?
And when Dashticz refreshes?
Currently the frames are being refreshed in the background. To be honest, I don't see a good reason for that. An alternative solution could be to load the frame after the button is pressed. The only disadvantage is that it then will take a bit more time before the frame gets displayed, because the data has to be downloaded first. But I think that is acceptable.
What do you prefer?
I've created an issue for this on Github. I'll create a fix probably coming weekend.Bram81 wrote: Monday 21 January 2019 9:39Hi, it does start to play after 1,5 hrs even though the dashticz refresh time is set to 5 seconds. The autoplay does also start after the first start of dashticz of after a refresh. You're right it would be more than acceptable to need some more time to load but being able to only start a the stream after a button press. Do you know how to do that? Thanks for your help!!Lokonli wrote: Saturday 19 January 2019 17:43 [
I expect it will start playing after 1,5 hrs. I think you should make the time bigger than the dashticz refresh time. You can set this last one via the config['dashticz_refresh'] setting in your CONFIG.js (in minutes, not msec)
Does the stream also autoplay at the first start of Dashticz?
And when Dashticz refreshes?
Currently the frames are being refreshed in the background. To be honest, I don't see a good reason for that. An alternative solution could be to load the frame after the button is pressed. The only disadvantage is that it then will take a bit more time before the frame gets displayed, because the data has to be downloaded first. But I think that is acceptable.
What do you prefer?
Users browsing this forum: No registered users and 1 guest