Release 315
4 November, 2014 - 01:45
xap-twitter was not deleting tweets after processing them.
thanks to Gary for pointing out this bug.
7 November, 2014 - 09:54
#3
Xively
Hi Brett...
Saw the 312 changes and have a clean .ini file (I removed all references to Pachybe)...
Re-instated the lua and re-started the xively function - attached debug messages....
hope this helps...
Elliot
| Attachment | Size |
|---|---|
| debug.txt | 9.99 KB |
7 November, 2014 - 13:20
#4
Hi Elliot, nice to see you
Hi Elliot, nice to see you back.
Im no expert but it does look like an issue with your Ini file. The section and key values look wrong.
Do you have a separate xively.ini file and what does it look like?
7 November, 2014 - 17:10
#5
Xively
Hi Garry...thanks, good to be back..took a while, but looking forward to getting the HAH back up and running!
Attached is the xively.ini file...as a further note, when xively process fails with no fault event in the log file - its completely blank!
Thanks for taking a look...
Elliot
EDIT: OK, its definitely the plugboard lua post to Xively that's causing the Xively feed to crash...I removed ALL (including the one I'd missed from before) the post to Xively from the luas and the inbuilt Xively function works as normal...so here's the bit of code that causes the function to fail..
-- postToXively1(1,"MainsW", tostring(MainsW))
-- Posting to Xively1
function postToXively1(id, tag, value)
xap.sendShort( string.format([[
xap-header
{
class=Xively.update
target=%s.Xively
}
datastream
{
id=%d
tag=%s
Value=%s
}]], cTbl.HAHprefix, id, tag, value) )
end
I've even tried forcing MainsW to a string, but to no avail...anyway can you see a fix/workarround?
Hopefully...
Elliot
FURTHER EDIT: NO ITS NOT.... the built in Xively feed failed after 5 heartbeats..!!...bugger!!
FURTHER FURTHER EDIT: YES IT IS....been merrily hearbeating for 30 mins now with no failure...?
| Attachment | Size |
|---|---|
| xap-xively.ini_.txt | 1.63 KB |
7 November, 2014 - 18:10
#6
I'm no expert either, the
I'm no expert either, the only thing which I can see that might cause a problem is maybe the "cTbl.HAHprefix" is corrupt and sending bad info which is causing it to crash.
Sorry I can't be more help.
Good to see you back.
7 November, 2014 - 18:29
#7
Ok I've had a very quick
Ok I've had a very quick scan. Your ini looks ok to me and you seem to be confirming xively ok without directed messages via lua.
i agree maybe it's cTbl.HAHprefix? Not sure what this is. Can you try just putting the xively target address in manually. I guess it's dbzoo.PELICAN.xively for you?
also the xively in the class is not capitalised in the wiki example, maybe try this too.
I do not update xively via lua anymore so cannot check this, I have all my info as xap messages and update via the service and the ini file settings.
ill keep thinking?!
Garry
7 November, 2014 - 18:53
#8
Xively
Thanks for the pointers....will have a go in a bit...out gigging tonight!!!!
Elliot
8 November, 2014 - 00:22
#10
Xively
Hi Brett - the Xively poster from the lua causes the SEGV - if I rem out the bit that uses the post to Xively then the in-built posting all works fine! I've attached a log...hope it shows the fault!
Elliot
| Attachment | Size |
|---|---|
| xivelyout.log_.txt | 72 KB |
Hi Brett
Just getting back into the swing of things - its been an arduous year family wise - so I just updated my livebox to 315 from 309 and did the changes I could see to get stuff working again - however for some reason Xively heartbeats for 2 mins from boot then dies! I've switched off all calls to xiively from the plugboard luas but to no avail - xFx messanger shows Xively alive at re-boot but no further heartbeats...any idea where I should look?
Hope things are going well ....
Elliot