TESTING RELEASE

[nolio]

Hi,
On my side, i have too high cpu usage (r498). cpu is 100% on one core of the 4 of my raspberry pi 2 (see picture joint).

[Gene]

Jens, nolio,

It is important that you remove the old homegenie folder completely before. I just upped a new r499 package. Installed on my Pi and no high cpu at all, indeed it's a bit lower than usual.

g.

[Jens]

Hi Gene

did that by rm -rf /usr/local/bin/homegenie

even did not import the old config, I started from scratch with 498

It takes a while to happen, did you run your installation for more than a day?

Thanks

Jens

[nolio]

I have just updated to r499 (with dpkg+rm -rf) and run again, i will keep you inform it it happen again.

[Gene]

Try r499. I'll see tomorrow if I notice something with it.

Hi Gene

did that by rm -rf /usr/local/bin/homegenie

even did not import the old config, I started from scratch with 498

It takes a while to happen, did you run your installation for more than a day?

Thanks

Jens

[pim555]

Hi Pim,

can you try installing r499 (testing) and see if Z-Wave issues are now fixed?

https://sourceforge.net/projects/homegenie/upload/

to update follow this procedure:

- backup your configuration
- uninstall current hg with the command "dpkg --remove homegenie"
- completely remove the hg folder "sudo rm -rf /usr/local/bin/homegenie"
- install new r499 "sudo gdebi homegenie-beta_1.1.r499_all.deb"
- restore your backup

Cheers,
g.

Hi Gene,

Upgraded to r499. Findings so far:
- z-wave switch and shutter can be contrlled again
- after controlling or getting status from swicth and shuitter I get a time out message in the UI
- SP103 motion sensor is working but status cannot be read. Also, tamper signal seems to be always there (was also already in previous releases)
- Mulit-sensor is not working, not status can be retrieved. I did manage to remove and add the device again but am not able to get status/configuration.

Btw, I see a lot of posts regarding z-wave set-up. Is there somewhere a short manual that describes the process for adding a new z-wave device and that describes the exact functionality of discovery, remove, add and reset?

Regards
Pim

[Jens]

In regards to the high CPU, I did a sudo reboot and monitored via shell command top.

Once I compile or save a program, a second instance seems to fire up for mono

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND                 
21803 root      20   0 43816  25m  11m R  90.0  5.3   0:05.12 mono                   
21531 root      20   0  170m  81m  26m S   8.5 16.9   2:56.64 mono     

Not sure whether this has been ever since.

I did now install the "new 499" version from yesterday afternoon

Regards
Jens

[Gene]

High cpu during C# compile on small boards like pi is absolutely normal and it has been always like this. The question is: does the cpu return to normal after finish compiling/saving in your case? I made a few test and cpu goes back as normal after compiling/saving.

[Jens]

I was wondering about the second mono pid entry during compilation.

The current installation runs just since an hour, for now the cpu usage is around 20 percent.

I did recompile the youless energy sensor program, too. It seems that that lowered the CPU usage a little.


Regards
Jens

[Gene]

The second mono entry I guess it is the mono compiler service doing the job.

20% of cpu usage is really a lot. Something is wrong in your configuration. Perhaps some app doing a bad work.
On my setup (bananapi dual core) normally the cpu usage is 0% to 1% and sometimes (when some app is working and/or the web UI updating some widgets) it reaches a peak of 10%-15% for just a couple of seconds.
Consider that I've connected to hg X10 and Z-Wave interface and a dozen of custom apps (wizard script mostly).

[Jens]

I found the reason why.

One of my programs, using program.say ws the high runner. After compiling it again the CPU usage when down to 5 to 15 percent. This program started every morning to tell me the current temperature, that explains why the increase was visible after one day. It was part of my backup from an older release.

The next candidate was the youless energy monitoring widget after removing that one the CPU usage is around 3 percent. The program is still running and the new energy widget displays the current power.

Thanks
Jens

[skakben]

Hi,

I am experiencing the same issues, my SP103 is constantly reporting level 0.01 and my Fibaro FGMS-001 keeps getting "ERR TIMEOUT" when trying to get/set variables in the UI, despite pushing the sync-button on the sensor.

However the new 499 release was a big improvement comparing to the prior release. Before 499r i could not get any info from the fibaro-sensor. Now i get correct level updates. So it works ok, but it would be great if the "ERR TIMEOUT" can be resolved.

Still, thanks for a superb home control software! i love it!

Hi Pim,

can you try installing r499 (testing) and see if Z-Wave issues are now fixed?

https://sourceforge.net/projects/homegenie/upload/

to update follow this procedure:

- backup your configuration
- uninstall current hg with the command "dpkg --remove homegenie"
- completely remove the hg folder "sudo rm -rf /usr/local/bin/homegenie"
- install new r499 "sudo gdebi homegenie-beta_1.1.r499_all.deb"
- restore your backup

Cheers,
g.

Hi Gene,

Upgraded to r499. Findings so far:
- z-wave switch and shutter can be contrlled again
- after controlling or getting status from swicth and shuitter I get a time out message in the UI
- SP103 motion sensor is working but status cannot be read. Also, tamper signal seems to be always there (was also already in previous releases)
- Mulit-sensor is not working, not status can be retrieved. I did manage to remove and add the device again but am not able to get status/configuration.

Btw, I see a lot of posts regarding z-wave set-up. Is there somewhere a short manual that describes the process for adding a new z-wave device and that describes the exact functionality of discovery, remove, add and reset?

Regards
Pim

[pim555]

Hi,

I am experiencing the same issues, my SP103 is constantly reporting level 0.01 and my Fibaro FGMS-001 keeps getting "ERR TIMEOUT" when trying to get/set variables in the UI, despite pushing the sync-button on the sensor.

However the new 499 release was a big improvement comparing to the prior release. Before 499r i could not get any info from the fibaro-sensor. Now i get correct level updates. So it works ok, but it would be great if the "ERR TIMEOUT" can be resolved.

Still, thanks for a superb home control software! i love it!

Hi Pim,

can you try installing r499 (testing) and see if Z-Wave issues are now fixed?

https://sourceforge.net/projects/homegenie/upload/

to update follow this procedure:

- backup your configuration
- uninstall current hg with the command "dpkg --remove homegenie"
- completely remove the hg folder "sudo rm -rf /usr/local/bin/homegenie"
- install new r499 "sudo gdebi homegenie-beta_1.1.r499_all.deb"
- restore your backup

Cheers,
g.

Hi Gene,

Upgraded to r499. Findings so far:
- z-wave switch and shutter can be contrlled again
- after controlling or getting status from swicth and shuitter I get a time out message in the UI
- SP103 motion sensor is working but status cannot be read. Also, tamper signal seems to be always there (was also already in previous releases)
- Mulit-sensor is not working, not status can be retrieved. I did manage to remove and add the device again but am not able to get status/configuration.

Btw, I see a lot of posts regarding z-wave set-up. Is there somewhere a short manual that describes the process for adding a new z-wave device and that describes the exact functionality of discovery, remove, add and reset?

Regards
Pim

I have another issue now as well (on top of the ERR TIMEOUT and am not sure if that is related to r499 or was present before as well. Due to the ERR_TIMEOUT I have been trying to remove and add my multi sensor a couple of times. Somewhere this has gone wrong and when I do a discovery, I now see left overs of the previous addition. For example I added the multi sensor as device #10, then tried to remove. The remove did not succeed so added again as device #11 but device #10 still shows up in discovery.

Is there a manual way of removing z-wave devices?

Regards
Pim

[dani]

Which ZWave key do you use ? If Aeon Labs yes you have to remove the node by pressinf to times the button key then the led flash rapidely. Then press  tree times faster the button on the node.

[kevin1]

Using 499...
(1) My HG is loading very slowly from remote chrome browser.  Sometimes it displays as all white with a bunch of the code showing instead of the actual UI/widgets
(2) My HG is not refreshing, if enable alarm for example, it does not show as enabled until I open a new tab (browser refresh doesn't help)