Help with Luup Reloads
-
@therealdb No rush, just reporting back
@pabla 1.51-hotfix is on GitHub.
- programs duplication is now fixed, so a reconfiguration is OK
- IP is now a variable (and it's automatically migrated - don't worry)
- temp files are correctly deleted
- I've tracked the problem with infinite stations - and I'm working on a permanent fix. this seems to be related to reloads and I'll investigate this further in the next days.
Give it a try!
--
On a mission to automate everything. -
One thing to add here, a possibility: I notice that the plugin is using the 'ip' attribute to store the IP address of the controller. I have found that this causes a lot of instability. Luup has certain automatic things that it does in the background to try to open connections when the IP is stored on that attribute. It's all part of their built-in automatic I/O for serial and IP connections, which this plugin doesn't use. But Luup will try, try and retry forever to start and maintain a connection to that IP. I believe that this is at least one source of a memory leak -- I suspect their error handling on connection failure is not completely cleaning up after itself, so the system leaks memory, and/or possible even sockets. I discovered this some years ago and switched all of my plugins to just use state variables for the IP. My systems do not restart due to memory leaks, and memory usage is generally flat.
-
@pabla 1.51-hotfix is on GitHub.
- programs duplication is now fixed, so a reconfiguration is OK
- IP is now a variable (and it's automatically migrated - don't worry)
- temp files are correctly deleted
- I've tracked the problem with infinite stations - and I'm working on a permanent fix. this seems to be related to reloads and I'll investigate this further in the next days.
Give it a try!
-
@therealdb So I updated to the latest hot fix, and the files still aren't getting deleted. I have a fill from 11:06am local time and its 11:27am. Do they auto delete after a longer time?
@pabla nope, this should be performed at every http call. This is weird. I’ve just deleted mine with the plugin and it’s working. Try to delete them by hand for the last time and let’s see if it’s working from now on.
--
On a mission to automate everything. -
@pabla nope, this should be performed at every http call. This is weird. I’ve just deleted mine with the plugin and it’s working. Try to delete them by hand for the last time and let’s see if it’s working from now on.
-
@therealdb Manually deleted the files and they aren't auto deleting still. This is really weird
-
Okay good news, so I uploaded the file via WinSCP since I noticed I had doubles of each file type one of the doubles was a .lzo file type. Now the files are deleting properly too. Question for everyone: Does the .lzo compression make a difference? Every time I get Github files I decompress and then drag them into the Luup Files section under Develop Apps. But I have began to notice that I have a lot of files with the .lzo extension
-
When you drag them to the Upload button in Apps > Develop apps > Luup files, the uploader will LZO compress them, always. If you use WinSCP and copy uncompressed files, they stay uncompressed. When Luup looks for a file, it will select the uncompressed file before the compressed if both are present, and this is how things get goofed up -- if you have old uncompressed files and try to update via the uploader, Luup still sees/uses the uncompressed files and ignores the newer compressed files (it doesn't check timestamps -- that would be nice!). Personally, I always use the uploader, and I don't keep uncompressed plugin files on my Veras, even during development (I never edit on the Vera so it doesn't matter).
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
When you drag them to the Upload button in Apps > Develop apps > Luup files, the uploader will LZO compress them, always. If you use WinSCP and copy uncompressed files, they stay uncompressed. When Luup looks for a file, it will select the uncompressed file before the compressed if both are present, and this is how things get goofed up -- if you have old uncompressed files and try to update via the uploader, Luup still sees/uses the uncompressed files and ignores the newer compressed files (it doesn't check timestamps -- that would be nice!). Personally, I always use the uploader, and I don't keep uncompressed plugin files on my Veras, even during development (I never edit on the Vera so it doesn't matter).
@toggledbits That makes sense why the plugin wasnt working as expected. That explanation solves so many issues that I have had with plugins lol. Since I would alternate between WinSCP and Uploading via the web UI
-
When you drag them to the Upload button in Apps > Develop apps > Luup files, the uploader will LZO compress them, always. If you use WinSCP and copy uncompressed files, they stay uncompressed. When Luup looks for a file, it will select the uncompressed file before the compressed if both are present, and this is how things get goofed up -- if you have old uncompressed files and try to update via the uploader, Luup still sees/uses the uncompressed files and ignores the newer compressed files (it doesn't check timestamps -- that would be nice!). Personally, I always use the uploader, and I don't keep uncompressed plugin files on my Veras, even during development (I never edit on the Vera so it doesn't matter).
@toggledbits blimey that's poor. Don't know why I should be surprised, though!
C
-
Okay good news, so I uploaded the file via WinSCP since I noticed I had doubles of each file type one of the doubles was a .lzo file type. Now the files are deleting properly too. Question for everyone: Does the .lzo compression make a difference? Every time I get Github files I decompress and then drag them into the Luup Files section under Develop Apps. But I have began to notice that I have a lot of files with the .lzo extension
-
@toggledbits said in Help with Luup Reloads:
But Luup will try, try and retry forever to start and maintain a connection to that IP.
Yes, this is, indeed, an issue, although NOT one, I would say, for openLuup. It may well explain why Vera behaves (sort of) when you remove some plugins.
For some time, now, I had a Vera Edge running without any plugins or Z-wave devices, and, I have to say, it just runs and runs!
@akbooer said in Help with Luup Reloads:
For some time, now, I had a Vera Edge running without any plugins or Z-wave devices, and, I have to say, it just runs and runs!
Erhhh - so it works great when it's doing absolutely nothing - is that it?
@toggledbits said in Help with Luup Reloads:
When Luup looks for a file, it will select the uncompressed file before the compressed if both are present, and this is how things get goofed up -- if you have old uncompressed files and try to update via the uploader, Luup still sees/uses the uncompressed files and ignores the newer compressed files (it doesn't check timestamps -- that would be nice!).
Never knew that. I always used the up-loader, so never came across this one. Certainly explains why someone could disappear into the quicksand pretty quickly.
-
@akbooer said in Help with Luup Reloads:
For some time, now, I had a Vera Edge running without any plugins or Z-wave devices, and, I have to say, it just runs and runs!
Erhhh - so it works great when it's doing absolutely nothing - is that it?
@toggledbits said in Help with Luup Reloads:
When Luup looks for a file, it will select the uncompressed file before the compressed if both are present, and this is how things get goofed up -- if you have old uncompressed files and try to update via the uploader, Luup still sees/uses the uncompressed files and ignores the newer compressed files (it doesn't check timestamps -- that would be nice!).
Never knew that. I always used the up-loader, so never came across this one. Certainly explains why someone could disappear into the quicksand pretty quickly.
-
Mmmmm - interesting - I've had a very similar experience with a couple of Veras. One of the Veras; I recently turned off the WiFi and I have never heard from it since; even though it has always successfully conversed via a hardwired LAN interface for years.
akbooer I recommend you ditch the Edge - it's costing you money at about 0.24 kW hrs per day. Further still, I recommend you use openLuup. It works well and the developer? - don't stuff around. Please donate as he or she requests.
-
@akbooer said in Help with Luup Reloads:
For some time, now, I had a Vera Edge running without any plugins or Z-wave devices, and, I have to say, it just runs and runs!
Erhhh - so it works great when it's doing absolutely nothing - is that it?
@toggledbits said in Help with Luup Reloads:
When Luup looks for a file, it will select the uncompressed file before the compressed if both are present, and this is how things get goofed up -- if you have old uncompressed files and try to update via the uploader, Luup still sees/uses the uncompressed files and ignores the newer compressed files (it doesn't check timestamps -- that would be nice!).
Never knew that. I always used the up-loader, so never came across this one. Certainly explains why someone could disappear into the quicksand pretty quickly.
@a-lurker said in Help with Luup Reloads:
Never knew that. I always used the up-loader, so never came across this one. Certainly explains why someone could disappear into the quicksand pretty quickly.
I have a quick bash script calling curl to update files via the web interface automatically. It's very handy when developing. I suspect @rigpapa built something similar and much more, since he's also unit testing his plug-ins...
-
Anyway, I've removed the IP from every device, and I'll report back. The unit is OK ATM, but I'll check when back home from the office.
--
On a mission to automate everything. -
Anyway, I've removed the IP from every device, and I'll report back. The unit is OK ATM, but I'll check when back home from the office.
@therealdb the files seem to be deleting by themselves. The plug-in itself though is still unstable though, I observed some new behaviours. I will post on the thread I started about the counter.
