BUG : Scenes are not returned by Domoticz.getAllDevices() as v<idx> like expected

[JRB202]

BUG : Scenes are not returned by Domoticz.getAllDevices(), only devices are returned

Demonstrated using custom.js :

function afterGetDevices(){
$.each(Domoticz.getAllDevices(), function (idx, device) {
console.log('DEBUG : idx = ' + idx + ' = ' + device.Name);
})
}
All existing Devices are well displayed
BUT ==> Existing scenes are not returned in this list.

I checked that syntax used in dashticz/js/domoticz-api.js is OK to query domoticz V2024.4 about scenes :
/json.htm?type=command&param=getscenes

[JRB202]

And as consequence this syntax in CONFIG.js do not work (When suggested by Documentation)
blocks['s1'] = {
title: 'My group 1'
}

The object generates a block containing :
Getting device s1

Even when s1 correspond to existing scene with idx = 1

[JRB202]

This problem is probably linked to : domoticz-api.js line 404 to 412 :
where I can se that logic is different when Web Socket are used or not :
function refreshAll() {
if (cfg.refresh_method || !useWS) {
return requestAllVariables().then(function () {
return requestAllDevices();
});
} else {
return requestAllVariables().then(requestAllScenes);
}
}

And currently with version Domoticz V2024.4, web sockets are not connecting anymore
See #1158

[lokonli]

It's working on my system, both with websockets as without.

The code above is correct:
requestAllDevices() also return all scenes. (Domoticz returns this in the JSO api call)

When using the websocket connection, then no update on the scenes state is received. So for that reason there is an additional call to get the scenes state.

[JRB202]

I confirm that problem with scenes is linked to websockets usage.

1. If Adding config['enable_websocket'] = true;
   and websockets are really connecting OK
   then Scenes are correctely returned in s

2. If Adding config['enable_websocket'] = false;
   then then Scenes are NOT returned in s

This is probably linked to domoticz-api.js code in line 404 to 412

[lokonli]

Also with config['enable_websocket'] = false; it should work.
(it is on my system ...)

It's a bit difficult to pinpoint what's causing the issue you have. Do you see other unexpected behavior?
Do you see other warnings/errors in DevTools console tab?

Do you make use of a room_plan?
Which Dashticz version are you using?
Can you try latest beta?

[JRB202]

I just upgraded to last beta Dashticz, and confirm no scene blocks are rendered with last Dashticz beta if not using WebSockets result is OK with WebSockets Scenes are not related to any room_plan No other error message

…

On Mon, Feb 12, 2024 at 9:46 AM Lokonli ***@***.***> wrote: Also with config['enable_websocket'] = false; it should work. (it is on my system ...) It's a bit difficult to pinpoint what's causing the issue you have. Do you see other unexpected behavior? Do you see other warnings/errors in DevTools console tab? Do you make use of a room_plan? Which Dashticz version are you using? Can you try latest beta? — Reply to this email directly, view it on GitHub <#1159 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHT5UEHG2TVEPOSD2LN42EDYTHJE3AVCNFSM6AAAAABDBSB5VWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZYGI2DOOBSGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>