I installed the latest main branch 2018 Release 6.26 (vera bridge 18.6.22) and I get the following error messages when I do a luup reload. In the startup log:
The condition allows me to access the UI of altUI, however, I get continuous controller not responding messages and I cannot access the openLupp console. I also see some outdated device statuses on the device page (some devices show as on when they are off). If I then do a browser refresh, I cannot access the UI at all.
A reboot of the machine clears this condition and afterwards, all of openLuup seems to function normally-- until I reload the luup engine from the menu, whereby the condition reappears.
Edit: I did a complete deletion of the cmh-ludl folder and all subfolders. I then restored the folder using a complete backup I created last week (it may be a test version). The openLuup version # is 18.6.5 and verabridge 18.6.4. openLuup comes up with no problems from this restored version.
I then did an update using the plugin page without any parameters. First I updated verabridge, and I now see a dropdown in version to 18.3.2. openLuup works as expected without any problems.
Then an update to openLuup gets continuous controller did not respond messages in the UI. The following error is in the startup log:
I tried doing this entire routine twice with the same result so there is definitely something in this plugin that is causing openLuup to crash, though it performed without problem prior to the update.
Edit#2 And finally, after deleting the broadlink plugin, the latest version (18.3.23) of openLuup loads and runs correctly. I updated to development version 18.6.26 and everything seems to be running normally.
Reading your edits, I’m unsure as to whether of not you still have a problem?
I don’t know anything about the Broadlink plugin. It looks like it might be an error reading one of the device files. However, the problem is clearly mine. I 'll go and learn something about it.
Edit: your original error “error starting server: address already in use” is clearly from an unclosed IP connection. It definitely need a better error message to identify which one.
Edit2: It’s actually looks like the HTTP server, in which case you simply had an earlier copy of openLuup running, and not correctly shut down.
I had to reboot the machine each time, so doubtful that a server survived the reboot.
I’m now seeing this in the log. Sensor 17 is a motion sensor on my honeywell alarm panel. It is picked up by the EVL honeywell plugin. I don’t see anything on the variables page that looks out of place.
2018-06-26 23:53:25.515 luup.variable_set:: 17.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 1 now: 0 #hooks:0
2018-06-26 23:53:25.515 openLuup.context_switch:: ERROR: ./openLuup/luup.lua:289: attempt to index a number value
2018-06-26 23:53:25.515 openLuup.io:: ./openLuup/luup.lua:289: attempt to index a number value
The original condition is fixed in that I deleted the broadlink plugin, but I’d like to reinstall the device as it controls a minor part of my security system (TV monitors).
[quote=“Buxton, post:4, topic:199403”]I’m now seeing this in the log. Sensor 17 is a motion sensor on my honeywell alarm panel. It is picked up by the EVL honeywell plugin. I don’t see anything on the variables page that looks out of place.
2018-06-26 23:53:25.515 luup.variable_set:: 17.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 1 now: 0 #hooks:0
2018-06-26 23:53:25.515 openLuup.context_switch:: ERROR: ./openLuup/luup.lua:289: attempt to index a number value
2018-06-26 23:53:25.515 openLuup.io:: ./openLuup/luup.lua:289: attempt to index a number value[/quote]
I hope to have caught this error (although I’m unsure as to the root cause of the value being a number and not a string.) I have also improved the error message from the server startup module to be more explicit.
The original condition is fixed in that I deleted the broadlink plugin, but I'd like to reinstall the device as it controls a minor part of my security system (TV monitors).
Can you try this again with the latest development version (v18.6.27) ?
Edit: I have downloaded the BroadLink_Mk2 files and created a device in my development system with no problem.
I did the update and I’m still seeing the sensor error. I set a watch for the offending variable as follows;
if type(text) == “number” then _log (text, “MY ERROR " … name … " " … device … " " … text … " " …service … " End”) end
Here is the log entry:
2018-06-27 15:01:30.314 luup.variable_set:: 17.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 1 now: 0 #hooks:0
2018-06-27 15:01:30.314 MY ERROR Tripped 17 1530136890 urn:micasaverde-com:serviceId:SecuritySensor1 End:: 1530136890
2018-06-27 15:01:30.314 openLuup.context_switch:: ERROR: ./openLuup/luup.lua:291: attempt to index a number value
2018-06-27 15:01:30.314 openLuup.io:: ./openLuup/luup.lua:291: attempt to index a number value
lua:291 would be line 290 without my log watch edit.
Also reinstalled the broadlink plugin and all works as before. I have no idea what happened there as I went so far as reinstalling openLuup twice, and rebooted several times, and each time my machine deadlocked in what appeared to be a race condition.
Helpful, thanks. All is explained, and I hope that development release v18.6.28b fixes this.
Also reinstalled the broadlink plugin and all works as before. I have no idea what happened there as I went so far as reinstalling openLuup twice, and rebooted several times, and each time my machine deadlocked in what appeared to be a race condition.
Damn spirits.
Indeed, although there are supposed to be less of them around for openLuup!