well that is strange
so the on screen updater isn't working as it should?

Thanks
I've fixed it by removing the www folder and running updatebeta from cmd

now it is working again

Do you get any errors in the Dev console (F12) of your browser when opening the domoticz page? LightsController.js:817 Uncaught ReferenceError: GenerateLiveSearchTextL is not defined at Object.<anonymous> (LightsController.js:817:25) at Function.each (jquery-3.6.0.min.js:2:3003) at Object.success ...

yes, saw that post with the search
and yes the only admin user has

no selected option

even used the clear button

and as mentioned before

Also creating a viewer user with limited content and login as this user the tabs are empty

thank you for your non helping response.
yes i did use the search, and that didn't solve as I mentioned the incognito browser, the hidden devices
the $ and so on.
SO did you read it before posting the default "use the search"

I've upgraded an older Domoticz version to current stable (and after that to current beta to check if beta fixed the troubles) After this upgrade all tabs exept "dashboard" are empty even in an incognito window The user is admin without the devices added. Also creating a viewer user with limited ...

For external API queries, RType queries have been replaced by normal queries. I changed all my scripts (104): /json.htm?type=devices into /json.htm?type=command&param=getdevices and /json.htm?type=graph& into /json.htm?type=command&param=graph& The messages about "Depricated RType" don't appear ...

looks nice this as alternative for openzwave Can someone here tell me: Is it updating the powerlevels as they should be (if turned on a switch there is power an if off the power is gone -> in ozw this is not always showing correct state) OZW has a controlpanel to click on check state , is this also ...

domoticz is really buggy for zwave with fibaro
a workaround to use both switches is restart Domoticz after the including of fgs224 is completed

yep still....
see this closed issue
https://github.com/domoticz/domoticz/issues/4352

had a pop rain sensor in the past. It's crap. It died because it got wather inside just below the counter

update: also seg fault when using

Domoticz2021.1 (build 13251)

using the lua script btw

Running RPI Raspbian Buster with Domoticz Domoticz2021.1 (build 13243) I see sometimes an incorrect HUE light state in Domoticz. According this wiki: https://www.domoticz.com/wiki/Simple_script_to_update_Philips_Hue_status I can run a script to fix the state. When adding this script Domoticz crashes ...

running Domoticz2020.2 (build 12763)

same issues: incorrect state Domoticz AND correct state Openzwave cp

henrivb wrote: ↑Friday 10 July 2020 16:29 @kjellb Popp Z-Rain is working fine with 2020.2 build 12200 and later. I am using it for a 4 days now using that version and it works great.

had one for about a year then it stopped working because the battery compartment was swimming in the rainwater from above :S and it died

it isn't solved. Still nodes not reporting their 3600 minutes power reports

What is in the logging of Domoticz in and around that time period? When was the corresponding Domoticz device updated the last time? 2020-12-21 09:02:09.783 Status: OpenZWave: Alarm received (Access Control: Door/Window Open), NodeID: 4 (0x04) 2020-12-21 09:02:09.990 Status: EventSystem: Script ...

nothing, see:
https://github.com/domoticz/domoticz/issues/4372

And today again:
Correct state in openzwavecp incorrect in domoticz:

root cause: the incorrect state in Domoticz. Openzwave cp state is always correct

see https://github.com/domoticz/domoticz/issues/4352

all battery powered devices?
Include them again