P1 showing actual values but no history

Moderator: leecollings

Post Reply
JapieG
Posts: 13
Joined: Wednesday 02 September 2015 8:46
Target OS: Raspberry Pi / ODroid
Domoticz version: 2022.1
Location: Netherlands
Contact:

P1 showing actual values but no history

Post by JapieG »

Hello!

I moved my domoticz db from a dedicated raspberry pi to another one on docker. No problems, but one..

Since the day i moved the database there is no history written from the p1 sensor.

I see actual values, I see the last 24h of 5 minute data, but when the clock goes to 00:00 normally the 5 minute data is converted to a day in the last week, last month and last year graph. This does not happen. At 00:00 the history graphs, as well as the reports stay empty. When i check the db manually there is just no line written in the multi-meter-calendar db..

The gas usage from the same p1 sensor is normally logged. As well as all other sensors. Only this electricity one refuses to log history.

I see absolutely no errors in logs, no corrupted db, no strange values in db.

Tried docker containers domoticz:stable and domoticz:latest with no difference.

Another one with the same problem here: viewtopic.php?t=37279

But i do nit have sql errors so i think the cause of my error is another one.

Somebody with an idea? I am alteady missing two weeks of data now :-(
B5CE55A9-574B-40A2-9C9F-6F3C18258928.png
B5CE55A9-574B-40A2-9C9F-6F3C18258928.png (155.12 KiB) Viewed 484 times
067DFF04-05A1-45B3-BD04-568B27F3A187.png
067DFF04-05A1-45B3-BD04-568B27F3A187.png (186.7 KiB) Viewed 484 times
User avatar
waltervl
Posts: 5149
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: P1 showing actual values but no history

Post by waltervl »

Switching between stable and beta is not a good idea as the database configuration is different. You now have to stay on beta or use the backup of the latest stable database before you made the switch.

A database repair / check still would be a good idea. Make sure you have a backup ready!
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
JapieG
Posts: 13
Joined: Wednesday 02 September 2015 8:46
Target OS: Raspberry Pi / ODroid
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: P1 showing actual values but no history

Post by JapieG »

I went from stable to stable when the problem started. Then I went to :latest and used the backup of the stable to load it. But still the problem existed.

I did a check on the DB using SQL editor with no errors as a result.

I will stay at the beta now until next stable release. Everything is working fine. Except the above issue. I double checked my latest stable database backup, and the data is also not there. So the issue was already present in the stable release.
JapieG
Posts: 13
Joined: Wednesday 02 September 2015 8:46
Target OS: Raspberry Pi / ODroid
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: P1 showing actual values but no history

Post by JapieG »

I enabled the logdump in the docker container. Maybe i missed something last night lets see if any error comes up this night at 00:00.
JapieG
Posts: 13
Joined: Wednesday 02 September 2015 8:46
Target OS: Raspberry Pi / ODroid
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: P1 showing actual values but no history

Post by JapieG »

i was able to catch some logging, seems there is a crash at 00:00. I hope somebody can point me in the right direction
------------------------------------------------

2022-09-20 00:00:00.523 Status: dzVents: zz Verbruikt: 6.171
2022-09-20 00:00:00.523 Status: dzVents: zz Productie: 42.549
2022-09-20 00:00:00.523 Status: dzVents: zz dagCOP: 6.89
2022-09-20 00:00:00.524 Status: dzVents: Info: ------ Finished dagCOP
2022-09-20 00:00:00.525 Status: EventSystem: Script event triggered: /opt/domoticz/dzVents/runtime/dzVents.lua
2022-09-20 00:00:00.817 Sunrise: 07:18:00 SunSet: 19:39:00
2022-09-20 00:00:00.817 Day length: 12:21:00 Sun at south: 13:28:00
2022-09-20 00:00:00.817 Civil twilight start: 06:44:00 Civil twilight end: 20:13:00
2022-09-20 00:00:00.817 Nautical twilight start: 06:03:00 Nautical twilight end: 20:54:00
2022-09-20 00:00:00.817 Astronomical twilight start: 05:21:00 Astronomical twilight end: 21:36:00
2022-09-20 00:00:00.817 Status: EventSystem: reset all events...
2022-09-20 00:00:00.821 Status: dzVents: Write file: /opt/domoticz/userdata/scripts/dzVents/generated_scripts/Metersplitsing.lua
2022-09-20 00:00:00.822 Status: dzVents: Write file: /opt/domoticz/userdata/scripts/dzVents/generated_scripts/dagCOP.lua
2022-09-20 00:00:00.978 Error: Domoticz(pid:1, tid:16('MainWorker')) received fatal signal 6 (Aborted)
2022-09-20 00:00:00.978 Error: siginfo address=0x1, address=0xb6a8b0af
2022-09-20 00:00:01.037 Error: Failed to start gdb, will use backtrace() for printing stack frame

2022-09-20 00:00:01.038 Error: #0 /opt/domoticz/domoticz() [0x278834]
2022-09-20 00:00:01.038 Error: #1 /opt/domoticz/domoticz : signal_handler(int, siginfo_t*, void*) + 0x1f8 [0x2791f0]
2022-09-20 00:00:01.038 Error: #2 /lib/arm-linux-gnueabihf/libc.so.6 : + 0x25cb0 [0xb6a8bcb0]
2022-09-20 00:00:01.038 Error: #3 /lib/arm-linux-gnueabihf/libc.so.6 : + 0x17746 [0xb6a7d746]
2022-09-20 00:00:01.038 Error: Domoticz(pid:1, tid:16('MainWorker')) received fatal signal 4 (Illegal instruction) while backtracing
2022-09-20 00:00:01.038 Error: siginfo address=0xb6a7d280, address=0xb6a8b0af
2022-09-20 00:00:01.039 Error: #0 /opt/domoticz/domoticz() [0x278834]
2022-09-20 00:00:01.039 Error: #1 /opt/domoticz/domoticz : signal_handler(int, siginfo_t*, void*) + 0x260 [0x279258]
2022-09-20 00:00:01.039 Error: #2 /lib/arm-linux-gnueabihf/libc.so.6 : + 0x25cb0 [0xb6a8bcb0]
2022-09-20 00:00:01.039 Error: Domoticz(pid:1, tid:16('MainWorker')) received fatal signal 4 (Illegal instruction)
2022-09-20 00:00:01.039 Error: siginfo address=0xb6a7d280, address=0xb6a8b0af
2022-09-20 00:00:01.092 Error: Failed to start gdb, will use backtrace() for printing stack frame

2022-09-20 00:00:01.092 Error: #0 /opt/domoticz/domoticz() [0x278834]
2022-09-20 00:00:01.093 Error: #1 /opt/domoticz/domoticz : signal_handler(int, siginfo_t*, void*) + 0x1f8 [0x2791f0]
2022-09-20 00:00:01.093 Error: #2 /lib/arm-linux-gnueabihf/libc.so.6 : + 0x25cb0 [0xb6a8bcb0]
2022-09-20 00:00:03.070 Status: Domoticz V2022.1 (build 14498) (c)2012-2022 GizMoCuz
2022-09-20 00:00:03.070 Status: Build Hash: 02fa9174e, Date: 2022-09-07 08:04:34
2022-09-20 00:00:03.070 Status: Startup Path: /opt/domoticz/
2022-09-20 00:00:03.089 Sunrise: 07:18:00 SunSet: 19:39:00
2022-09-20 00:00:03.089 Day length: 12:21:00 Sun at south: 13:28:00
2022-09-20 00:00:03.089 Civil twilight start: 06:44:00 Civil twilight end: 20:13:00
2022-09-20 00:00:03.089 Nautical twilight start: 06:03:00 Nautical twilight end: 20:54:00
2022-09-20 00:00:03.089 Astronomical twilight start: 05:21:00 Astronomical twilight end: 21:36:00
2022-09-20 00:00:03.128 Status: PluginSystem: Started, Python version '3.7.3', 0 plugin definitions loaded.
2022-09-20 00:00:03.136 Active notification Subsystems: pushover (1/13)
2022-09-20 00:00:03.137 Status: WebServer(HTTP) startup failed on address :: with port: 8080: resolve: Host not found (authoritative) [asio.netdb:1], trying ::
2022-09-20 00:00:03.137 Status: WebServer(HTTP) startup failed on address :: with port: 8080: resolve: Host not found (authoritative) [asio.netdb:1], trying 0.0.0.0
2022-09-20 00:00:03.138 Status: WebServer(HTTP) started on address: 0.0.0.0 with port 8080
2022-09-20 00:00:03.142 Status: WebServer(SSL) startup failed on address :: with port: 443: resolve: Host not found (authoritative) [asio.netdb:1], trying ::
2022-09-20 00:00:03.144 Status: WebServer(SSL) startup failed on address :: with port: 443: resolve: Host not found (authoritative) [asio.netdb:1], trying 0.0.0.0
2022-09-20 00:00:03.146 Status: WebServer(SSL) started on address: 0.0.0.0 with port 443
2022-09-20 00:00:03.147 Status: Camera: settings (re)loaded
2022-09-20 00:00:03.148 Starting shared server on: 0.0.0.0:6144
2022-09-20 00:00:03.149 Status: TCPServer: shared server started...
2022-09-20 00:00:03.149 Status: RxQueue: queue worker started...
2022-09-20 00:00:03.511 Status: Incoming connection from: 172.17.0.1
2022-09-20 00:00:05.150 Status: SmartMeter: attempt connect to 192.168.1.246:8088
2022-09-20 00:00:05.150 Status: SolarEdge: Worker started...
2022-09-20 00:00:05.150 Status: Netatmo: Worker started...
JapieG
Posts: 13
Joined: Wednesday 02 September 2015 8:46
Target OS: Raspberry Pi / ODroid
Domoticz version: 2022.1
Location: Netherlands
Contact:

Re: P1 showing actual values but no history

Post by JapieG »

Since there is a crash going on i will move my question to bugs & problems
User avatar
waltervl
Posts: 5149
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: P1 showing actual values but no history

Post by waltervl »

At 0 00 hours an automatic backup is created when switched on. Is that the case? Then it could be related to disk malfunction or disk space.

Also the calendar tables summary are updated so this could indicate that you have an errournous database. Check the troubleshooting wiki for instructions https://www.domoticz.com/wiki/Troubleshooting
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest