Reboot loop, corrupt database etc

🛎️ Get Help
1

I was able to boot to safe mode once and changed all device event and state history to 11 and logging to minimum for all devices. Did cleanup and rebooted. I thought that it was to cure, but no. Back to rebooting loop. Usually, I can check few things and then it boots again. Sometimes corrupted database and sometimes just reboot. Logs won't reveal anything to me. Does someone have something to help me?

Live logs when It crashed three times

dev:8212023-06-12 18:20:05.568infoCar charger power is 0 W
dev:8202023-06-12 18:20:05.556infoCar charger power is 0 W
dev:972023-06-12 18:20:02.053infoIKEA Signaalitoistin : Refreshed
dev:3632023-06-12 18:20:00.043infoKausivalot Etukuisti XBMINI is off [physical]
dev:8212023-06-12 18:19:11.546infoCar charger power is 2.100000000000000088817841970012523233890533447265625 W
dev:8202023-06-12 18:19:11.533infoCar charger power is 2.100000000000000088817841970012523233890533447265625 W
dev:8212023-06-12 18:19:06.535infoCar charger power is 0 W
dev:8202023-06-12 18:19:06.522infoCar charger power is 0 W
dev:8212023-06-12 18:19:02.815infoCar charger power is 2.100000000000000088817841970012523233890533447265625 W
dev:8202023-06-12 18:19:02.764infoCar charger power is 2.100000000000000088817841970012523233890533447265625 W
dev:8212023-06-12 18:16:39.535infoCar charger power is 2.100000000000000088817841970012523233890533447265625 W
dev:8202023-06-12 18:16:39.469infoCar charger power is 2.100000000000000088817841970012523233890533447265625 W
dev:8412023-06-12 18:16:39.368infoEcho (v4.2.2.0) | Echo - Echo Flex at Cabin sauna Executing initialize()
dev:8402023-06-12 18:16:39.073infoEcho (v4.2.2.0) | Echo - Echo Dot at Cabin Executing initialize()
dev:7852023-06-12 18:16:38.958infoEcho (v4.2.2.0) | Echo - Echo Show Executing initialize()
dev:7832023-06-12 18:16:38.913infoEcho (v4.2.2.0) | Echo - Olohuone Executing initialize()
dev:7822023-06-12 18:16:38.809infoEcho (v4.2.2.0) | Echo - PETTERI's Sonos Beam Executing initialize()
dev:8212023-06-12 18:16:34.469infoCar charger power is 0 W
dev:8202023-06-12 18:16:34.460infoCar charger power is 0 W
dev:8412023-06-12 18:16:34.077errorEcho (v4.2.2.0) | getPlaylists Response Exception | Status: (404) | Msg: status code: 404, reason phrase: Not Found
dev:8402023-06-12 18:16:33.207errorEcho (v4.2.2.0) | getPlaylists Response Exception | Status: (404) | Msg: status code: 404, reason phrase: Not Found
dev:8412023-06-12 18:16:27.210infoEcho (v4.2.2.0) | Echo - Echo Flex at Cabin sauna Executing initialize()
dev:8412023-06-12 18:16:27.192infoEcho (v4.2.2.0) | Echo - Echo Flex at Cabin sauna Executing Installed...
app:6962023-06-12 18:16:27.021info EchoApp (v4.2.2.0) | Creating NEW Echo Speaks Device!!! | Device Label: (Echo - Echo Flex at Cabin sauna)
dev:8402023-06-12 18:16:26.243infoEcho (v4.2.2.0) | Echo - Echo Dot at Cabin Executing initialize()
dev:8402023-06-12 18:16:26.224infoEcho (v4.2.2.0) | Echo - Echo Dot at Cabin Executing Installed...
app:6962023-06-12 18:16:25.914info EchoApp (v4.2.2.0) | Creating NEW Echo Speaks Device!!! | Device Label: (Echo - Echo Dot at Cabin)
app:6962023-06-12 18:16:23.994errorEchoApp (v4.2.2.0) | wakeupServerResp Exception: java.lang.Exception: No response data exists for async request
app:6962023-06-12 18:16:23.989errorEchoApp (v4.2.2.0) | wakeupServerResp | Stack Trace: java.lang.Exception: No response data exists for async request at hubitat.scheduling.AsyncResponse.getData(AsyncResponse.groovy:71) at user_app_tonesto7_Echo_Speaks_468.wakeupServerResp(user_app_tonesto7_Echo_Speaks_468.groovy:2228)
app:6962023-06-12 18:16:23.919errorEchoApp (v4.2.2.0) | wakeupServerResp Server may be down / unreachable
app:6962023-06-12 18:16:23.867warn EchoApp (v4.2.2.0) | wakeupServerResp: 503
app:6962023-06-12 18:16:23.663info EchoApp (v4.2.2.0) | running initialize...
dev:8212023-06-12 18:16:18.449infoCar charger power is 2.100000000000000088817841970012523233890533447265625 W
dev:8202023-06-12 18:16:18.438infoCar charger power is 2.100000000000000088817841970012523233890533447265625 W
dev:8212023-06-12 18:16:13.429infoCar charger power is 0 W
dev:8202023-06-12 18:16:13.416infoCar charger power is 0 W
dev:8212023-06-12 18:16:00.467infoCar charger power is 2.29999999999999982236431605997495353221893310546875 W
dev:8202023-06-12 18:16:00.451infoCar charger power is 2.29999999999999982236431605997495353221893310546875 W
dev:3632023-06-12 18:15:59.539infoKausivalot Etukuisti XBMINI is off [physical]
dev:8212023-06-12 18:13:24.372infoCar charger power is 0 W
dev:8202023-06-12 18:13:24.359infoCar charger child_lock is off
dev:8202023-06-12 18:13:24.351infoCar charger fault is ok
dev:8202023-06-12 18:13:24.347infoCar charger power is 0 W
dev:8202023-06-12 18:13:24.328infoCar charger switch is off
dev:8202023-06-12 18:13:24.013infoRequesting cloud device specifications for bf89b4c18730dea352qcfo
dev:8202023-06-12 18:13:24.005infoRequesting cloud device specifications for bfb9ed9a36f041de07pvjn
dev:8202023-06-12 18:13:24.001infoReceived 2 cloud devices (has_more: null)
dev:8202023-06-12 18:13:23.382infoRequesting cloud devices batch
dev:8202023-06-12 18:13:23.379infoClearing json cache
dev:8202023-06-12 18:13:23.313infoSubscribing to Tuya MQTT hub device topic
dev:8202023-06-12 18:13:21.541infoConnecting to Tuya MQTT hub at ssl://m1.tuyaeu.com:8883
dev:8202023-06-12 18:13:21.289infoRequesting Tuya Home list
dev:8202023-06-12 18:13:21.279infoRequesting Tuya MQTT configuration
dev:8202023-06-12 18:13:21.222infoReceived Tuya access token (valid for 7200s)
dev:8202023-06-12 18:13:20.869infoStarting Tuya cloud authentication for petteri.joutseno@gmail.com
dev:8202023-06-12 18:13:20.844infoSetting Finland datacenter [country:Finland, countryCode:358, endpoint:https://openapi.tuyaeu.com]
dev:8202023-06-12 18:13:20.786infoDriver v0.3 initializing
dev:8202023-06-12 18:13:20.783infoDriver configuration updated
dev:8212023-06-12 18:12:51.211warndescription logging is: true
dev:8212023-06-12 18:12:51.207infoUpdated...
dev:7862023-06-12 18:12:48.600error Blink api - Unauthorized
dev:7862023-06-12 18:12:48.596error Blink api - Unauthorized
dev:8202023-06-12 18:12:02.294infoCar charger power is 0 W
dev:8202023-06-12 18:12:02.291debugCar charger status [code:cur_power, t:1686582722, 19:0, value:0]
dev:8202023-06-12 18:12:02.288debugCar charger status [code:cur_current, t:1686582722, 18:0, value:0]
dev:8202023-06-12 18:12:02.284debugCar charger workMode
dev:8202023-06-12 18:12:02.281debugGroups: [Car charger:[[code:cur_current, t:1686582722, 18:0, value:0], [code:cur_power, t:1686582722, 19:0, value:0]]]
dev:8202023-06-12 18:12:01.309debugCar charger status [code:cur_voltage, t:1686582721, value:2307, 20:2307]
dev:8202023-06-12 18:12:01.306infoCar charger power is 2.100000000000000088817841970012523233890533447265625 W
dev:8202023-06-12 18:12:01.303debugCar charger status [code:cur_power, t:1686582721, 19:21, value:21]
dev:8202023-06-12 18:12:01.300debugCar charger status [code:cur_current, t:1686582721, 18:15, value:15]
dev:8202023-06-12 18:12:01.296debugCar charger workMode
dev:8202023-06-12 18:12:01.293debugGroups: [Car charger:[[code:cur_current, t:1686582721, 18:15, value:15], [code:cur_power, t:1686582721, 19:21, value:21], [code:cur_voltage, t:1686582721, value:2307, 20:2307]]]
dev:3632023-06-12 18:12:00.799infoKausivalot Etukuisti XBMINI is off [physical]
dev:8202023-06-12 18:11:56.290debugCar charger status [code:cur_voltage, t:1686582716, value:2308, 20:2308]
dev:8202023-06-12 18:11:56.287infoCar charger power is 0 W
dev:8202023-06-12 18:11:56.284debugCar charger status [code:cur_power, t:1686582716, 19:0, value:0]
dev:8202023-06-12 18:11:56.281debugCar charger status [code:cur_current, t:1686582716, 18:0, value:0]
dev:8202023-06-12 18:11:56.278debugCar charger workMode
dev:8202023-06-12 18:11:56.274debugGroups: [Car charger:[[code:cur_current, t:1686582716, 18:0, value:0], [code:cur_power, t:1686582716, 19:0, value:0], [code:cur_voltage, t:1686582716, value:2308, 20:2308]]]
dev:8202023-06-12 18:11:47.286debugCar charger status [code:cur_voltage, t:1686582707, value:2307, 20:2307]
dev:8202023-06-12 18:11:47.283infoCar charger power is 2.29999999999999982236431605997495353221893310546875 W
dev:8202023-06-12 18:11:47.280debugCar charger status [code:cur_power, t:1686582707, 19:23, value:23]
dev:8202023-06-12 18:11:47.277debugCar charger status [code:cur_current, t:1686582707, 18:15, value:15]
dev:8202023-06-12 18:11:47.273debugCar charger workMode
dev:8202023-06-12 18:11:47.270debugGroups: [Car charger:[[code:cur_current, t:1686582707, 18:15, value:15], [code:cur_power, t:1686582707, 19:23, value:23], [code:cur_voltage, t:1686582707, value:2307, 20:2307]]]
dev:972023-06-12 18:10:08.050warnIKEA Signaalitoistin : Presence : Waiting for first presence report.
dev:972023-06-12 18:10:02.077infoIKEA Signaalitoistin : Refreshed
dev:3632023-06-12 18:08:02.068infoKausivalot Etukuisti XBMINI is off [physical]
dev:8202023-06-12 18:07:20.135debugCar charger status [code:add_ele, t:1686582439, 17:1, value:1]
dev:8202023-06-12 18:07:20.132debugCar charger workMode
dev:8202023-06-12 18:07:20.129debugGroups: [Car charger:[[code:add_ele, t:1686582439, 17:1, value:1]]]

Thanks

PJ

2

@support_team

3

If you could include a screenshot instead of a copy/paste of your logs, it would make them easier to read and review.

1 Like
4

Like I said those logs reveal absolutely nothing. So Lets try something else.

Big state sizes in here. Anything else? Should that stage size be reduced somehow?

image
image773×388 28.6 KB

5

Devices:

image
image827×435 31.1 KB

6

How about doing a soft reset from yourhubip:8081 and restore from last backed up database?

1 Like
7

No help. Done million times. DB size shows 6, so that is not an issue either. It has now been up almost nine hours once I set 3 as the event and size history for those chatty devices. Next crash and will build the system from the scratch.

8

If there is a bad device within your mesh, rebuilding isn't going to help as you will be introducing it back into the environment. @gopher.ny any thoughts?

9

Can you PM me the hub id? I'll take a look at the engineering logs.

4 Likes
10

Corrupt database again when I tried to see how it is. I almost thought that if I don't touch it, it will stay up, but this confirmed my thought wrong. @gopher.ny if you have had a chance to look at those engineering log, did you find anything suspicious?

11

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.