Beta 60 Shutter widget

[dakriege]

Version 1.60 Beta

Updated Shutter widget is working. Open / Close and Partial using the slider.

[dakriege]

I forgot to mention that the Service never restarted after doing the 1.60 Beta update. I restarted the Service and the Update completed.

An issue that I found with the Shutter wizard is that if I open it with Chrome on my Laptop it displays a different looking Shutter widget.

I've tried clearing the cache and doing a hard reload.

If I open the 'Developer' mode on Chrome it doesn't report any errors.

If I open HomeGenie with Microsoft Edge it works fine.

[genemars]

Did you also try clearing site data?

Once this happened to me as well, but then I was not able to reproduce the issue again.

[dakriege]

Cleared site data. That fixed it.

From: Gene @.> Sent: Monday, October 9, 2023 8:29 AM To: genielabs/HomeGenie @.> Cc: dakriege @.>; Author @.> Subject: Re: [genielabs/HomeGenie] Beta 60 Shutter widget (Issue #471)

Did you also try clearing site data?

https://user-images.githubusercontent.com/6654265/273599588-95b4ac11-b3d0-4aeb-9fba-d54ddd6dc507.png

Once this happened to me as well, but then I was not able to reproduce the issue again.

— Reply to this email directly, view it on GitHub https://github.com/genielabs/HomeGenie/issues/471#issuecomment-1753016196 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDU3TE4O7B3OL6MLHRDD4LX6P3YPAVCNFSM6AAAAAA5YTLYTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJTGAYTMMJZGY . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AGDU3TDFEVL5V2NNZHLRH6DX6P3YPA5CNFSM6AAAAAA5YTLYTSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTIPTTYI.gif Message ID: @. @.> >

-- This email has been checked for viruses by AVG antivirus software. www.avg.com

[dakriege]

One thing I noticed on the ZWave widgets is that they don't seem to update in the background or do a refresh when you open the Dashboard. When you open the ZWave Dashboard the Widgets are shown in their last state. Using the new Shutter widget the Dashboard shows that one of the Shades is closed but it's actually open. It shows the last state as Closed a day ago. I have the ZWave Query Level program enabled and running. Since you can use the remote control that came with the Shades the state may be open / closed or partially closed so the Dashboard will need to refresh when it's opened.

[genemars]

I would suggest to deactivate the query level program and instead configure your Z-Wave devices to auto-report level changes to association group 1 (that is the z-wave controller). The parameter number to enable level report should be in the device manual. For example this door sensor uses parameter 10 to enable/disable automatic report of open/close status. Anyway, I think the real problem here is that the dashboard "snapshot" stored client-side is taking precedence over the actual devices status loaded from server (kind of desync). You can verify this by opening directly in the browser the API URL that returns the devices status, you'll see that devices properties are the correct one with actual data updated real-time.

http://ip_address:port/api/HomeAutomation.HomeGenie/Config/Modules.List

I thought that was already fixed, but I must have missed something :) Tomorrow I'll look into this and fix it.

[dakriege]

I did the Modules list as your recommended. The status level for the Shutter widget that is Open but shows Closed is 0.

I am unable to open the HomeGenie home page.

That has happened several times and requires a re-start on the service.

My home page URL is http://192.168.10.15:5006/ which I assumed defaults to index.html

http://192.168.10.15:5006/app/index.html is displayed in the URL parameter

Sometimes the Browser displays

http://192.168.10.15:5006/app/home/Z-Wave

The HomeGenie - YoT page just spins forever and never opens.

[genemars]

That gives me more clues. So the device seems not sending any basic report. You can try the API manually: http://server_address/api/HomeAutomation.ZWave/4/Basic.Get And see what the response value is. So having the manual of this device could help a lot to find out how to configure automatic report. Searching internet for this device manufacturer specific gives me no results. Not even a brand name. About the homepage not opening and loading spinner never disappearing, the only reason I can think of is that still AVG blocks the service for some reason. It would be helpful if you enable logging and then run HomeGenie in a terminal window instead of a background service, Just to find out if any error pops-up.

[dakriege]

If I use the API and do the Basic.Get I get the current status and it updates the Widgets.

I ordered a spare motor so I can do some testing without effecting the Blinds.

I will see if there is a sticker with manufacturer info.

Dave

From: Gene @.> Sent: Wednesday, October 11, 2023 6:38 AM To: genielabs/HomeGenie @.> Cc: dakriege @.>; Author @.> Subject: Re: [genielabs/HomeGenie] Beta 60 Shutter widget (Issue #471)

That gives me more clues. So the device seems not sending any basic report. You can try the API manually: http://server_address/api/HomeAutomation.ZWave/4/Basic.Get And see what the response value is. So having the manual of this device could help a lot to find out how to configure automatic report. Searching internet for this device manufacturer specific gives me no results. Not even a brand name. About the homepage not opening and loading spinner never disappearing, the only reason I can think of is that still AVG blocks the service for some reason. It would be helpful if you enable logging and then run HomeGenie in a terminal window instead of a background service, Just to find out if any error pops-up.

— Reply to this email directly, view it on GitHub https://github.com/genielabs/HomeGenie/issues/471#issuecomment-1757488968 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDU3TBPMRDNLHYKJSD2HS3X62ALLANCNFSM6AAAAAA5YTLYTQ . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AGDU3TGK2UUMPYSZZ4ZUUZ3X62ALLA5CNFSM6AAAAAA5YTLYTSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTIYETUQ.gif Message ID: @. @.> >

-- This email has been checked for viruses by AVG antivirus software. www.avg.com

[genemars]

If Basic.Get API is showing the correct value then also the Level Poll program should work. If the status level is not updated in the UI it's because the controller is not included in the association group 1 of your device. In order to do so, use the Z-Wave Device Manager from the settings page. For instance this is a dimmer (multilevel switch) that I use to control one of my lights.

You can see that node 1 is added to the association group 1.

In the following pictures you can also see the configuration parameter numbers used to configure automatic reports for this dimmer insert.

Even if your device is not present in HG database and configuration parameters are not listed like in the above picture, you can still enter them manually using the Generic Parameter form.

[genemars]

@dakriege I probably found the documentation of a similar device to yours: https://www.opensmarthouse.org/zwavedatabase/1567 It seems that the parameters are not documented. So the only thing you can do right now is adding the controller (node 1) to the association group 1 and then enable the Z-Wave Level Polling program as you did before since in this case is the only viable solution to synchronize the motor status with the UI. Let me know if it works.

[genemars]

I think this issue is now fixed by v1.4.0-beta.61