Ah, I think that is UI7 doing bad things to you. I’ll try it myself tomorrow and see what works.
It turns out that I’m running the latest EventWatcher on a Vera Edge with no difficulty. One action I could suggest is simply to delete the plugin entirely using the plugin pages (this will not delete the files) and then create a new EventWatcher device manually with device file D_EventWatcher.xml and implementation file I_EventWatcher.xml.
This is assuming the new files were all, in fact, uploaded correctly (sounds like you used the right approach.)
Thanks for your reply and support, really appreciate it.
I don’t like iit very much to delete the plugin and then creating it again manually
One last info, maybe this can help to come to an easy solution:\When in the plugin device under “control” I click on one of the blue items it opens this URL:
http://192.168.1.xxx/port_3480/data_request?id=lr_EventWatcher&report=cpu and it says “no handler”
(xxx = ip adress of my veraplus and this is correct)
[quote=“akbooer, post:8, topic:194404”]Indeed the logs show an error:
50 11/16/16 14:58:18.987 luup_log:838: EventWatcher: defining CLI... <0x772cb520>
50 11/16/16 14:58:18.997 luup_log:838: EventWatcher: Starting Event service... <0x772cb520>
50 11/16/16 14:58:18.998 luup_log:838: EventWatcher: Server listening on port 443 <0x772cb520>
10 11/16/16 14:58:18.998 AlarmManager::AddRelativeAlarm current time 1479304698 delay 10 type 7 <0x772cb520>
10 11/16/16 14:58:18.999 AlarmManager::AddAbsoluteAlarm alarm 0x1928f98 entry 0x1ede370 id 0 type 7 param=0x198d380 entry->when: 1479304708 time: 1479304698 bCancelFirst 0=0 <0x772cb520>
50 11/16/16 14:58:18.999 luup_log:838: EventWatcher: Starting Watch service... <0x772cb520>
01 11/16/16 14:58:19.000 LuaInterface::CallFunction_Startup-1 device 838 function init failed [string "local ABOUT = {..."]:1156: attempt to index local 'c' (a nil value) <0x772cb520>
01 11/16/16 14:58:19.000 LuImplementation::StartLua running startup code for 838 I_EventWatcher.xml failed <0x772cb520>The good news is that I understand that the condition that it reports would generate an error, the bad news is I simply cannot understand how that might happen. I’ve loaded the same version from GitHub onto both an openLuup development machine and one of my VeraLite machines and they both work perfectly.
There is, I suppose, the remote possibility of a download error. Can I ask that you re-install from the AltAppStore and try again?[/quote]
Hi,
I have now followed the exact things you have done here in this thread but i still have the same entries in the luup log as you stated above:
50 02/04/17 22:30:21.727 luup_log:353: EventWatcher: Starting Watch service... <0x7755a520>
01 02/04/17 22:30:21.727 e[31;1mLuaInterface::CallFunction_Startup-1 device 353 function init failed [string "ABOUT = {..."]:1158: attempt to index local 'c' (a nil value)e[0m <0x7755a520>
01 02/04/17 22:30:21.728 e[31;1mLuImplementation::StartLua running startup code for 353 I_EventWatcher.xml failede[0m <0x7755a520>
50 02/04/17 22:30:22.100 luup_log:351: ALTUI: startupDeferred, called on behalf of device:351 <0x75d5a520>I seem to have missed the spot in this thread where you say what exacly fixed the problem?
Could you please point me to how you managed to fix this?
Thank you very much in advance!
regards
Christian
Are you absolutely sure that you have downloaded and installed the latest version from GitHub?
Initially i thought you said that earlier in the thread that you had updated the version in the Alternate Appstore in AltUi so i installed that one. But now i have downloaded the GitHub version and installed that one just to be sure, with the same result I’m afraid.
Is it possible that there is something stuck in the system from the first one i installed from the Mios AppStore?
christian
They should be similar, if not identical.
Is it possible that there is something stuck in the system from the first one i installed from the Mios AppStore?
Yes, it must be something like that. If you look through the files on your system “Apps > Develop Apps > Luup files”, do you see any duplicates for any EventWatcher files? It’s possible that you have both compressed and uncompressed versions. Delete ALL EventWatcher files (D_xxx, S_xxx, I_xxx, L_xxx) and try again.
As I mentioned before, I’ve done a raw install from the App Store on a clean machine without any issues.
They should be similar, if not identical.
Is it possible that there is something stuck in the system from the first one i installed from the Mios AppStore?
Yes, it must be something like that. If you look through the files on your system “Apps > Develop Apps > Luup files”, do you see any duplicates for any EventWatcher files? It’s possible that you have both compressed and uncompressed versions. Delete ALL EventWatcher files (D_xxx, S_xxx, I_xxx, L_xxx) and try again.
As I mentioned before, I’ve done a raw install from the App Store on a clean machine without any issues.[/quote]
Now i deleted what ever i could find in the /etc/cmh-ludl path i also checked the /etc/cmh-lu path but there was nothing. Restarted the lua engine to make sure de Eventwatcher device was gone. And then transferd the files from github with the Upload button in Develop Apps and created a New device.
The exact same result:
50 02/05/17 16:58:31.758 luup_log:357: EventWatcher: Starting Watch service... <0x76dd2520>
01 02/05/17 16:58:31.759 e[31;1mLuaInterface::CallFunction_Startup-1 device 357 function init failed [string "ABOUT = {..."]:1158: attempt to index local 'c' (a nil value)e[0m <0x76dd2520>
01 02/05/17 16:58:31.759 e[31;1mLuImplementation::StartLua running startup code for 357 I_EventWatcher.xml failede[0m <0x76dd2520>
50 02/05/17 16:58:32.101 luup_log:351: ALTUI: startupDeferred, called on behalf of device:351 <0x757d2520>
Any other information i could provide that might help?
I’m currently running the latest version 1.7.2406.
christian
Today I got the same error. I removed and reinstalled eventWatcher (1.20140123) without effekt.
I run eventWatcher on veraEdge since more than a year without problems. Last week I made a vera upgrade to the newest softwarelevel without problems. Yesterday (when eventWatcher still was working) I renamed some devices and I installed the GetLogUtility, popp thermostat and aeon sirene. Maybe one of these changes was initiating the error?