HS4 4.2.13.6 Beta is available for testing!

[rjh]

UPDATE 7/19/22: This build has been released as 4.2.14.0. You may update through setup or see the HS4 forum.

HS4 4.2.13.6 is ready for testing. See the release notes for all the changes. If there are no issues, this will be a 4.2.14.0 release.

All Changes: Release Notes


Installing:

Before installing any Beta it is a good idea to back up your system! Run the backup from the tools menu. On Windows you can simply copy the HS4 folder to another folder. Just copy it back if needed.

* You can install this Beta from within HS4, just go to the General page in Setup (Windows or Linux)

See the release notes for download links.

Reverting to a previous version on Windows:

Uninstall HS4 (it will not remove any config files, plugins, etc.). Then install your previous version and install into the same folder as your previous install.

Reverting to a previous version on Linux:

On the PI-HUB/ZEE S2/SEL or your own Linux install. You can simply re-install the release version from setup.

[tenholde]

Is there some way to return a collection or list of all ControlUse objects define for a Feature?

[rmasonjr]

The HsFeature has a StatusControls object that has a StatusControlCollection. You might have to iterate through and see if the eControlUse properties are in there...

[racerfern]

7/11/2022 14:51:22 HomeSeer Error Error while getting feature 7302 : Object reference not set to an instance of an object.
7/11/2022 14:51:22 HomeSeer Error Error while getting feature 7302 : Object reference not set to an instance of an object.
7/11/2022 14:50:59 HomeSeer Error Error while getting feature 3953 : Object reference not set to an instance of an object.
7/11/2022 14:50:59 HomeSeer Error Error while getting feature 3954 : Object reference not set to an instance of an object.

7/11/2022 14:45:50 HomeSeer Warning Error handling UPNP request: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.

Those device reference numbers do not exist in my system.

EDIT- These errors only occur once within a few minutes of startup.

[bdickhaus]

After installing 4.2.13.6 I started getting script debug messages in the log. I made sure that the debug mode was set to 0 but the script debug messages continued. I went back to 4.2.13.0 and the messages stopped. Running on Linux.

[pistacheL0]

Saw that too.

[pistacheL0]

Anything been done for the thread/handle issue??

[John245]

rjh
I see the following issue.

Steps to reproduce.
1) create a virtual device
2) select bulk edit and create a copy
3) select both devices, select bulk edit and create a copy will result as shown below




4) deselect all selected devices for bulk action


4) Change the feature name of the feature at the top
After this bulk action is enabled for the two devices that were copied


---
John

[John245]

rjh
Although the value is updated in Node-RED the value will not update automatically in HomeSeer (will update when I refresh the page).

ksum or could this issue be a Node-RED issue?


---
John

[dsfarkas]

I thought that after upgrading to 4.2.13.6, the HomeSeer app on my iPhone quit working.

However, after removing and reinstalling 4.2.13.0, the HomeSeer app still doesn't work and gives the same error.

Here is the screen on my iPhone with either version:

[John245]

I thought that after upgrading to 4.2.13.6, the HomeSeer app on my iPhone quit working. Here is the screen on my iPhone:



However, after removing and reinstalling 4.2.13.0, the HomeSeer app still doesn't work and gives the same error.

+1
---
John

[ksum]

ksum or could this issue be a Node-RED issue?


---
John

I have not followed along on the thread and spud would know better, but here is what a quick test got me:

• I tested 2 Virtual Devices I previously created. I do not recall what specific version of HomeSeer these were created under, but it was HS4.
  • An On/Off device with no Features
    • Changed via Node-RED by defining the Status as a string of either On or Off
  • A Feature with numeric values as shown below
    • Changed via Node-RED by defining the Value as a numeric value
• 2 Browser (Chrome) Windows were open as separate windows and not tabs
• Both devices were changed via Node-RED and my browser updated the Device listed in the browser without user input.
• Both devices were changed via the HomeSeer Devices window in my browser and updated in Node-RED
• I am running:
  • HS4 Pro Edition 4.2.12.0 (Windows)
  • Node-RED v2.2.0
  • HomeSeer contrib 1.0.6

So I am not testing the subject version of HomeSeer nor the current release.

Second Virtual Device

[pistacheL0]

Anything been done for the thread/handle issue??

Got my response today. Nothing has been done.

[John245]

I have not followed along on the thread and spud would know better, but here is what a quick test got me:

• I tested 2 Virtual Devices I previously created. I do not recall what specific version of HomeSeer these were created under, but it was HS4.
  • An On/Off device with no Features
    • Changed via Node-RED by defining the Status as a string of either On or Off
  • A Feature with numeric values as shown below
    • Changed via Node-RED by defining the Value as a numeric value
• 2 Browser (Chrome) Windows were open as separate windows and not tabs
• Both devices were changed via Node-RED and my browser updated the Device listed in the browser without user input.
• Both devices were changed via the HomeSeer Devices window in my browser and updated in Node-RED
• I am running:
  • HS4 Pro Edition 4.2.12.0 (Windows)
  • Node-RED v2.2.0
  • HomeSeer contrib 1.0.6

So I am not testing the subject version of HomeSeer nor the current release.

Second Virtual Device

rjh spud ksum
Solved by restarting the laptop that was running the google browser.

---
John

[Pickles871]

Hi guys, I have updated to the latest Beta and all seems to be working fine except the saving of the list order for the legacy 'deviceutility', is still not saving. I am trying to migrate to the new HS4 device list but on many devices the main feature shows up and cannot be hidden without hiding all the features. I thought that had been fixed or am I mistaken. What is the solution to picking a list of only the features that I want but hiding the main feature if not required. Also in the legacy HS3 listing it is possible to have two features appearing in different places by ascribing different location, descriptions etc. In the HS4 listing they all appear under one device only or am I looking at this the wrong way? Cheers. Peter