SQL Logger insert issue after upgrade to indigo 7.4

Posted on
Sun Dec 29, 2019 11:38 pm
valo offline
Posts: 3
Joined: Dec 29, 2019

SQL Logger insert issue after upgrade to indigo 7.4

I updated indigo from 7.1 to .7.4 and after this the sql logger seems to have an issue with the INSERT INTO function.

Basically, nothing is recorded to the sqlite database at all. Does anybody have a clue on fixing the VALUES (?); issue? Something with character set?

SQL Logger Debug state change list for "Orgegon ute": {u'temperature': u'4.3'}
SQL Logger Debug INSERT INTO device_history_453361042 ("temperature") VALUES (?);
SQL Logger Debug (u'4.3',)
SQL Logger Debug state change list for "Orgegon ute": {u'display': u'4.3 C / 94%'}
SQL Logger Debug INSERT INTO device_history_453361042 ("display") VALUES (?);
SQL Logger Debug (u'4.3 C / 94%',)

Posted on
Mon Dec 30, 2019 7:39 am
FlyingDiver offline
User avatar
Posts: 4318
Joined: Jun 07, 2014
Location: Southwest Florida, USA

Re: SQL Logger insert issue after upgrade to indigo 7.4

What kind of device is that?

joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177

Posted on
Mon Dec 30, 2019 8:06 am
valo offline
Posts: 3
Joined: Dec 29, 2019

Re: SQL Logger insert issue after upgrade to indigo 7.4

That was a orgegon humidity/temperature sensor, I am using RFXCOM plugin for the 433 Mhz and then for zwave devices a AEOTEC Zwave stick.

The output seems to be similar regardless of device, below from a zwave switch with energy meter. Basically the VALUES part is left unpopulated.

SQL Logger Debug state change list for "Arbetsrummet": {u'curEnergyLevel.ui': u'43.2 W', u'curEnergyLevel': 43.2}
SQL Logger Debug INSERT INTO device_history_1807358163 ("curenergylevel_ui", "curenergylevel") VALUES (?, ?);
SQL Logger Debug (u'43.2 W', u'43.2')

Posted on
Mon Dec 30, 2019 8:48 am
valo offline
Posts: 3
Joined: Dec 29, 2019

Re: SQL Logger insert issue after upgrade to indigo 7.4

Well, this seems to have resolved it self. The issue was quite silly actually, nothing to do with the actual plug-in. After the upgrade I was pointing my reporting queries to wrong folder... well now I seems better.

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 1 guest