Domoticz Community Forum

As you have seen on the previous post on this forum, there has been a major update/upgrade of Dashticz This was needed to move forward. Some packages were release older than 8 years old and not supported Also the structure has been changed and indeed can break some features (at this moment). Dashticz is having a lot of separate packages or features which are behaving differently The best is to raise an issue of GIt with a good description of the problem. It is hard to solve issue with general descripions with specific custom layouts / setups

Ok, we will have to wait till one of the maintainers/devs will look into it I guess. As I understand the documentation need to be updated as well, maybe that will clarify some issues. I guess that some of the old config items are replaced and/or obsolete which causes the crippled dashboard.

I have the same with upgrading from master 3.14. My 2nd Dashticz page is totally mixed up. I'll keep working with master 3.14 for now

Hi, Today I upgraded dashticz to the latest 4.05 version. I upgraded from version 3.14.x, which is using a custom config.js and custom.js file for displaying all items nicely tailored. With the new 4.0.5 version I'm using the same config.js and custom.css file used in the old version. When dashticz is loading I have noticed some issues on my defined pages: 1. Graphs are displayed in 50% of their available width 2. Standby screen does not have the correct background any more, and items (weather owm and clock) are overlapping. 3. several text items are shifted in height and increased in size, like the custom.css file is not used?

BTW: I am using it ever since then and really appreciate it. Thank you again! Would be nice to have it as an option built in in domoticz, so you don't have to run the command after every (beta) update.

Thanks for the report, and for the link to the V1/V2 migration notes. That link turns out to be a red herring for this particular error, so to be clear about what is going on: There are two independent things in this hardware type. 1. The API key polling (site overview, inverter telemetry, energy details, battery) is fine. That uses the documented monitoringapi.solaredge.com endpoints, which is what the V1 to V2 announcement applies to. I verified it still returns data today. V1 stays up until 1 November 2026, so we will migrate that part well before the deadline. Nothing for you to do there. 2. The "Web portal" part is what is broken, and it is not the V1/V2 change. That feature (site layout, strings, per optimizer data) used undocumented endpoints on monitoring.solaredge.com with plain username/password authentication. SolarEdge has now switched those off completely. They answer: Code: HTTP 410 Gonehttps://marketing.solaredge.com/legacy-api-sign-up-for-interest 410 means permanently removed, and the page they redirect to is their "Legacy API, sign up for interest" form. So no credential or setting on your side can fix it. What has been fixed The web portal login now uses the same OAuth2 sign-in flow the SolarEdge monitoring website itself uses, and reads the layout and optimizer data from the current endpoints. Site layout, strings and optimizers work again. The once per second error spam is fixed too. That was a separate bug where a failed layout fetch retried on every wor

I figured out what is the issue! Allowed CORS Origins field in domoticz was empty (never used that before), added my domoticz IP there and now the dashboard is loading. Now some troubelshooting to do because some items/graphs are resized.

Hi, My network is already defined within the trusted networks! config domoticz: 192.168.1.*;127.0.0.*;172.16.*;172.17.*;172.20.*;10.* And nothing changed there except adding the IP ranges of the synobridge config (troubleshooting the issue).

Have you added you Dashticz IP to the trusted networks in Domoticz? See some other post on this topic

Hi, This morning I updated my domoticz to the latest version available (using 2026.3 (build 18335)), and as well updated the dashticz dashboard to the latest 4.0.5 version. Old version was 2025.1 (build 16703), and dashticz 3.14.1.2 Domoticz is running fine, but the dashtizc dashboard is not loading. I get error: Can't access Domoticz via http://192.168.1.11:8085/ Check domoticz_ip in config.js For more help, visit the Dashticz documentation. Via F12 in my Firefox browser I can see the following error: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://192.168.1.11:8085/json.htm?type= ... uth&plan=0 . (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200. Domoticz error code: 0 error! Please, double check the path to Domoticz in Settings! My dashticz settings: config['domoticz_ip'] = ' http://192.168.1.11:8085 '; config['enable_websocket'] = 1; config['use_cors'] = 0; I played arround with the above websocket and cors settings (enable/disable), but the dashboard page still shows the error (after ctrl+F5) Any ideas how to further troubleshoot and solve the issue? In the old version domoticz and dashticz were running fine (except my TADO integration, which needed the latest domoticz, that's why updating)

I see people put that kind of data in a text sensor with a dzvents script. Yo can run that script once a day. There are loads of examples, search for "updatetext" in the forum.

Looks OK for me. Best to get another try to get the log on the moment you expect a water demand. Then you would see more logging pop up according your script when everything goes as expected. That logging could give some clues.