Domoticz

Gravityz wrote: Friday 01 September 2023 15:09 that looks fine, i use the same command

do you have the edomoticz plugin in homebridge?

yep.

i've got one temp sensor and 2 virtual switches exposed to homebridge.

ok, if you did not manually fixxed things in edomoticz that's your problem

look at this thread

you can solve the issue by manually changing the domoticz.js file IN HOMEBRIDGE.

https://github.com/PatchworkBoy/homebri ... issues/265

Gravityz wrote: Friday 01 September 2023 15:16 ok, if you did not manually fixxed things in edomoticz that's your problem

look at this thread

you can solve the issue by manually changing the domoticz.js file IN HOMEBRIDGE.

https://github.com/PatchworkBoy/homebri ... issues/265

YES, that was the problem, fixed it. !!!

exactly , now the domoticz log is clean

glad i could help

kiddigital wrote: Friday 09 June 2023 22:13

newpond wrote:…

If any one can see how to modify these to follow the new requirements, i would be grateful of any help.

var jurl=$.domoticzurl+"/json.htm?type=devices

thanks
Newpond

That one has to change ‘type=command&param=getdevices’

You can remove the ‘&jsoncallback=?’ as that is also not supported anymore.

The others should be ok

EDITED
I hope someone can help me please. I'm having trouble getting my frontpage working again after Domoticz update. I was getting two Rtype errors, one for devices and one for scenes. I have changed /json.htm?type=devices to /json.htm?type=command&param=getdevices and that seems to have fixed the devices issue but having changed /json.htm?type=scenes to /json.htm?type=command&param=getscenes I'm still getting a scenes R type error: [WebServer] Deprecated RType (scenes) for API request. Handled via fallback (getscenes), please use correct API Command!

markk wrote: Tuesday 31 October 2023 12:07 but having changed /json.htm?type=devices to /json.htm?type=command&param=getscenes I'm still getting a scenes R type error:

mmm... I guess you mean you changed:/json.htm?type=scenes to /json.htm?type=command&param=getscenes ?

jvdz wrote: Tuesday 31 October 2023 12:18

markk wrote: Tuesday 31 October 2023 12:07 but having changed /json.htm?type=devices to /json.htm?type=command&param=getscenes I'm still getting a scenes R type error:

mmm... I guess you mean you changed:/json.htm?type=scenes to /json.htm?type=command&param=getscenes ?

Oops, yes, sorry. That's exactly what I mean. I now corrected this typo.

Ça peut être lié à un soucis de rapport. Donc il faudrait que tu mettes une ampoule dont tu connais la consommation et ainsi je pourrais en déduire le bon ratio


Envoyé de mon iPhone en utilisant Tapatalk

markk wrote: Tuesday 31 October 2023 12:47 Oops, yes, sorry. That's exactly what I mean. I now corrected this typo.

Well then it must be that there is another API call using that old format API or something is cached.

markk wrote: Tuesday 31 October 2023 12:07
EDITED
I hope someone can help me please. I'm having trouble getting my frontpage working again after Domoticz update. I was getting two Rtype errors, one for devices and one for scenes. I have changed /json.htm?type=devices to /json.htm?type=command&param=getdevices and that seems to have fixed the devices issue but having changed /json.htm?type=scenes to /json.htm?type=command&param=getscenes I'm still getting a scenes R type error: [WebServer] Deprecated RType (scenes) for API request. Handled via fallback (getscenes), please use correct API Command!

Then there is another proces/application in your environment calling the deprecated API call. Also clear your browser cache, that also helps to get changes implemented in a browser environment.

So the rtype errors have now gone but no devices are showing on frontpage. I can see the incoming connection in the log: 192.168.0.39:8080/frontpage2/index.html. The index.html file is the same one that was working before I updated Domoticz

You probably made a type error somewhere so Domoticz does not understand what you are doing.

Do you see a white page or is there some general information from the index.html and no sensor values?

markk wrote: Tuesday 31 October 2023 18:25 So the rtype errors have now gone but no devices are showing on frontpage. I can see the incoming connection in the log: 192.168.0.39:8080/frontpage2/index.html. The index.html file is the same one that was working before I updated Domoticz

Hit F12 and goto the network tab to see the requests and the results returned.

I don’t know how to post a screenshot but when I hit F12 I can view my index.html file under the sources tab. Network tab shows a list of requests

And if they are ok (200) or not.. all ok?

Yes. All showing (200) but it is reporting an issue:

Because a cookie’s SameSite attribute was not set or is invalid, it defaults to SameSite=Lax, which prevents the cookie from being set in a cross-site context. This behavior protects user data from accidentally leaking to third parties and cross-site request forgery.
Resolve this issue by updating the attributes of the cookie:
Specify SameSite=None and Secure if the cookie is intended to be set in cross-site contexts. Note that only cookies sent over HTTPS may use the Secure attribute.
Specify SameSite=Strict or SameSite=Lax if the cookie should not be set by cross-site requests.
1 cookie
Name Domain & Path
DMZSID 192.168.0.XXX/

Joep123 wrote: Friday 02 June 2023 19:55

gizmocuz wrote: Friday 02 June 2023 14:04 For external API queries, RType queries have been replaced by normal queries.

I changed all my scripts (104):

Code: Select all

/json.htm?type=devices

into

Code: Select all

/json.htm?type=command&param=getdevices

and

Code: Select all

/json.htm?type=graph&

into

Code: Select all

/json.htm?type=command&param=graph&

The messages about "Depricated RType" don't appear anymore

I have 2 devices running on the old API which I cannot convert to the new API. Unfortunately, I do not have the source code for one, and for the other I am not able to compile the ESP8266 batch using the current libraries. So the Domoticz upgrade lock will probably last quite a long time for me...

One way could be to implement an reverse proxy that will translate the old API call to the new format as I posted here as solution when the Android App crashed when used on old domoticz versions: viewtopic.php?p=308169#p308169
The only thing you need to be able to do is change the used port on those devices you can't change the API format on from eg 8080 to 8082 when using that posted setup.

Thank you for that.
Simpler option is to maintain backward compatibility in domoticz itself and no disabling old format.
I already lost one way to access domoticz via old, not maintained from 2017 year app Imperihome because of changes in domoticz security.
Now another thing in next version will be lost. It shouldn't be like this.