Jdbc sqlexception error "column name" pops up for a device and other stuff

I have a Zooz power Zen15 switch that I recently migrated to the C-7. Seems to have been working fine but this morning I just got this error... (app:1 is the "maker api")

And the maker call seems messed up BUT I can control the device from the device page no problem. I noticed that there seemed to be a similar issue in 2019 so wanted to report it in case there was some sort of funky regression rearing it's ugly head.

Things are a little slow and I may reboot just for giggles.

edit: the device is now working via maker without a reboot.

Is that the instance of maker API that your Node Red uses? If so, can you look at your node red logs and see what was going on at that exact moment?

1 Like

Yeah good thought! Will check it out..

Though that power switch doesn't do anything unless a small pump kicks in which it did not last night. There are no other sequences on NR related to this or on HE.

I feel like I get similar error messages when I remove a device from maker API but forget to do so from node red. I just can't remember the exact terminology of the error messages to know if it's the same.

EDIT: I have a couple of Tasmota devices that update virtual HE devices every 5 minutes and I sometimes get similar message for one update attempt.

I think SQL errors normally indicate database issues.
Could be wrong though.
Reboot or a soft reset usually cures these errors.

1 Like

Yep have done the same far too many times to count sadly. In this case it looks like the issue started with an HE system error that caused a very similar effect - device lost contact with NR. The odd bit was while it was not reporting in NR the HE device page was working fine.

I suspect it was/is a one-off glitch but when I searched the forums I found (from 2019) some staff looking into the issue so thought I'd report it.

This is a brand new C-7 and I only have HSM (not using currently) and Maker API apps and only 2 3rd party drivers - the Basic Z-Wave tool and @csteele's AeotecMultiSensor6 driver. No Zigbee devices either.. about as simple a setup as you can get. Also have never "just pulled the plug" on this hub..

1 Like

Found one from this morning!!! Just one but an update is sent every 5 minutes.

1 Like

Down the rabbit hole we go! :rabbit2: - now some of my S2 devices are not responding or getting out of sync.

I have an aeotec Nano (non S2) - when I manually turn on/off then on the device page it reflects the state just fine. Maker reflects this.

Right next to it is a Zooz V4 switch - when I do the same thing I get nothing - still says initial state unless I hit the "refresh" command (refresh page does nothing).

Turning on/off via the device page seems to work okay though. All my S2 devices except repeaters have no security/authentication set.

Note: I have not rebooted yet.

So it is definitely not picking up physical actions without tapping "refresh". Digital control is working great.

Tried both my front porch lamp post (Zen23 V4) and side porch light (Zen23 V3).. Interestingly my Zen24/v3 dimmer Mud Room Light right next to the side porch light switch is responding to physical controls... as is my livingroom sconces dimmer (same brand/ver - across from the front porch lamp post) mmmmm

Am going to reboot now (shutdown, pull plug, start up) to see if this changes anything.

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