Python Plugin: Smart Virtual Thermostat

[etampes]

Unfortunately adding my admin username and password to the SVT hardware settings did not resolve these errors for me

For me too, don’t work. And i filled the ip tables without login before update, so there is something wrong with new update or plugin have not enough permissions to login.

I solved the problem. In changelog they said
- Changed: Implicit adding local IP to 'trusted networks' has been removed. Needs to be set explicitly for security reasons!
so You should change your ip in settings, don`t use 127.0.0.*;192.168.0.*, Set IP explicitly, example:127.0.0.1;192.168.0.40 e.t.c, don`t forget to divide them by ;

This solved the issue for me, along with checking the “ Allow Basic-Auth authentication over plain HTTP (API only).” box and indeed adding “localhost” to the list. Thanks.

[southmind]

Unfortunetly no succes here,

i Have one setup witch runs 2023.1 build 15082 and has been update from previous versions witch works ok.

And a fresh install with 2023.1 stable and gives the error. settings all the same.

Same behaviour for me. I use 4 SmartVirtualThermostat and no one works with version 2023.1 . I tried to change IP in explicit IP in the setup without success. Always the same msg in logs : "the output is not a switch..." Tried to install 3 times the new version and then returned to the previous Domoticz version 2022.2.

[southmind]

The problem seems to be fixed by adding "localhost" to the existing explicit ip 127.0.0.1 ("localhost;127.0.0.1;192.0.x.x.x....")

[SigveM]

I just updated from Domoticz 2022.2 to 2023.2 today – and discovered that the SVT (Smart Virtual Thermostat) no longer works as it should. The SVT Thermostat Control (Off, Auto, Forced mode) is red. As a result, I can no longer automatically control room temperatures via SVT.

I have successfully used SVT for a few years, and never had an issue.

Before updating the Domoticz software I cloned my SD card and then applied the update. All parameters and settings should therefore be the identical between the 2 versions of Domoticz. And yet SVT does not work in version 2023.2. As soon as I go back to version 2022.2 everything works fine.

I can only surmise that the culprit is the User Management that came into existence with version 2023.1.

I have entered both “localhost” and my specific IP address (192.168.0.15) in the “Local Networks” field. Still no success.

Any thoughts on how to fix this?

For now version 2022.2 is the only choice for me.

[jake]

I am on a very recent 2023.2 beta and have no trouble.
What does the log say when you disable/enable the svt hardware?
Do you see a working python in the 'about' of Domoticz? Mine says python 3.9.2

[waltervl]

Also check the security setting "Allow Basic Authentication over plain HTTP" if you are using HTTP instead of HTTPS

[SigveM]

I still have no success with SVT under version 2023.2. As a matter of fact, it appears even worse than originally discovered.

The Thermostat Control (Off, Auto, Forced mode) is still red. It seems OK for about 5 seconds and then it turns red. And remains red.

I have also discovered that the system seemingly doesn't find any temp sensors. I get the message "No Temperature sensors found or added in the system" - and yet I see them all in the Devices. All correctly added, all correctly taking readings at usual intervals.

The Utility tab, which is where the SetPoint controls normally appear, is also empty.

I am logged in as admin (tried both original and new admin credentials, same result), and therefore should (I would think) have access to it all.

My Raspberry Pi is fully updated (done yesterday). But I do see that my Python is still showing version 3.7.3 (with a date of 29 June 2023). Is the Python version the culprit?

Reference is made to the security setting "Allow Basic Authentication over plain HTTP". For some reason I can't seem to find that one anywhere. Can anyone point me in the right direction, please?

[SigveM]

Issue resolved!

The missing temp sensors and missing SetPoints (tab "Utility") - all sorted out by clearing the cache of my browser and then refreshing each page.

Red Thermostat Control fixed by removing username and password from the SVT config panel (username and password were probably left over from the days of MyDomoticz or something similar).

Found the "Allow Basic Authentication over plain HTTP" switch. Turned it both on and off. No impact on the Thermostat Control being red or not. Prior to the 2 steps above (clearing cache and removing username / password), the Thermostat Control was red regardless of position of the "Allow Basic Authentication over plain HTTP" switch. After the 2 steps above, the Thermostat Control remained perfectly OK regardless of the "Allow Basic Authentication over plain HTTP" switch position.

The moment I removed “localhost” and my specific IP address (192.168.0.15) from the “Local Networks” field, the Thermostat Control immediately went red again. Putting those 2 back in again, all works fine.

My Python is still 3.7.3.

Main take-aways:
- Clear cache
- Have “localhost” and your specific IP address in the “Local Networks” field (no space after the semi-colon)
- Make sure "Accept new Hardware Devices" in the Settings panel is on
- Go to each SVT instance in "Hardware" and remove username / password. No need to Enable / Disable. Click on "Update" (even if username / password were already empty)
- The "Allow Basic Authentication over plain HTTP" switch in the Security tab has no impact on this

Thanks for the help provided.

[jake]

Thank you for your feedback. I think the newer version of python belongs to Debian bulseye and the 3.7.3 to buster.

[dorjey]

Hi everyone,
After updating Domoticz to the last version, the SVT plugin stopped working properly. Since then I’ve tried various solutions, including installing the 2023.2 version, or compiling a new version of Domoticz (Release 2023.1, thank you Chat GPP ), but didn't succeed.
I’m looking for any advice or alternative solutions to get SVT up and running again. Has anyone else experienced this issue or found a fix?
Thanks a lot for your help!

[waltervl]

It would help if you identify in more details what exactly is not working properly. Do you get errors? Is something not set properly? Does logging say something strange?

[dorjey]

Hi, thank you for your answer.I have updated Domoticz to the latest version (2024.2) on my RPI 3 and it does not seem to work with the latest version of SVT.

[jacobsentertainment]

I have a similar issue with this plugin, after the last update it seems not to be working stable anymore.
I tried several things like replacing temperature sensors and other settings. Nothing changes the reliable functioning of the plugin, only thing that does seem to work is going to hardware-"SVT plugin" and press adapt/aanpassen after that it works till the next stop.

Most seen behaviour on the plugin is that it just stps working, it doesnt switch on, noit even when I increase the temperature settings, when switching on manually it doesnt switch off after temperature is reached. And using any other switch options like pauze, boost, eco etc doesnt change any it need to be restarted by giving the plugin a kick in the but trough the hardware page.

The github page does not give info on recent plugin updates nor does the domoticz page..
Changed log to all debug details, but not much I recognize as a error..

Code: Select all

 2024-11-09 13:24:34.078 Vloer: Acquiring GIL for 'onHeartbeatCallback'
2024-11-09 13:24:34.078 Vloer: Calling message handler 'onHeartbeat' on 'module' type object.
2024-11-09 13:24:34.078 Vloer: Calling domoticz API: http://192.168.178.72:8080/json.htm?type=command&param=getdevices&filter=temp&used=true&order=Name
2024-11-09 13:24:34.078 Vloer: Add authentification for user Jacobs
2024-11-09 13:24:34.119 Vloer: device: 22-Keuken temperatuur = 17.4
2024-11-09 13:24:34.119 Vloer: device: 173-Vloer temp backup = 39.8
2024-11-09 13:24:34.119 Vloer: device: 16-Buiten temp = 7.8
2024-11-09 13:24:34.119 (Vloer - Thermostat temp) Updating device from 0:'35.8' to have values 0:'28.6'.
2024-11-09 13:24:34.129 Vloer: Inside Temperature = 28.6
2024-11-09 13:24:34.129 Vloer: Outside Temperature = 7.8
2024-11-09 13:24:34.129 Vloer: Acquiring GIL for 'onHeartbeatCallback'
2024-11-09 13:24:35.954 Vloer: Pushing 'onCommandCallback' on to queue
2024-11-09 13:24:35.990 Vloer: Processing 'onCommandCallback' message
2024-11-09 13:24:35.990 Vloer: Acquiring GIL for 'onCommandCallback'
2024-11-09 13:24:35.990 Vloer: Calling message handler 'onCommand' on 'module' type object.
2024-11-09 13:24:35.990 Vloer: onCommand called for Unit 3: Command 'Off', Level: 0
2024-11-09 13:24:35.991 (Vloer - Thermostat Pause) Updating device from 0:'' to have values 0:''.
2024-11-09 13:24:36.005 Vloer: Acquiring GIL for 'onCommandCallback'
2024-11-09 13:24:38.985 Vloer: Pushing 'onCommandCallback' on to queue
2024-11-09 13:24:39.010 Vloer: Processing 'onCommandCallback' message
2024-11-09 13:24:39.010 Vloer: Acquiring GIL for 'onCommandCallback'
2024-11-09 13:24:39.010 Vloer: Calling message handler 'onCommand' on 'module' type object.
2024-11-09 13:24:39.010 Vloer: onCommand called for Unit 3: Command 'Off', Level: 0
2024-11-09 13:24:39.010 (Vloer - Thermostat Pause) Updating device from 0:'' to have values 0:''.
2024-11-09 13:24:39.023 Vloer: Acquiring GIL for 'onCommandCallback'
2024-11-09 13:24:44.031 Vloer: Pushing 'onHeartbeatCallback' on to queue
2024-11-09 13:24:44.081 Vloer: Processing 'onHeartbeatCallback' message
2024-11-09 13:24:44.081 Vloer: Acquiring GIL for 'onHeartbeatCallback'
2024-11-09 13:24:44.081 Vloer: Calling message handler 'onHeartbeat' on 'module' type object.
2024-11-09 13:24:44.082 Vloer: Acquiring GIL for 'onHeartbeatCallback'
2024-11-09 13:24:49.085 Vloer: Pushing 'onCommandCallback' on to queue
2024-11-09 13:24:49.089 Vloer: Processing 'onCommandCallback' message
2024-11-09 13:24:49.089 Vloer: Acquiring GIL for 'onCommandCallback'
2024-11-09 13:24:49.090 Vloer: Calling message handler 'onCommand' on 'module' type object.
2024-11-09 13:24:49.090 Vloer: onCommand called for Unit 3: Command 'Off', Level: 0
2024-11-09 13:24:49.090 (Vloer - Thermostat Pause) Updating device from 0:'' to have values 0:''.
2024-11-09 13:24:49.111 Vloer: Acquiring GIL for 'onCommandCallback'
2024-11-09 13:24:51.017 Vloer: Pushing 'onCommandCallback' on to queue
2024-11-09 13:24:51.065 Vloer: Processing 'onCommandCallback' message
2024-11-09 13:24:51.065 Vloer: Acquiring GIL for 'onCommandCallback'
2024-11-09 13:24:51.065 Vloer: Calling message handler 'onCommand' on 'module' type object.
2024-11-09 13:24:51.065 Vloer: onCommand called for Unit 3: Command 'Off', Level: 0
2024-11-09 13:24:51.065 (Vloer - Thermostat Pause) Updating device from 0:'' to have values 0:''.
2024-11-09 13:24:51.077 Vloer: Acquiring GIL for 'onCommandCallback'
2024-11-09 13:24:54.031 Vloer: Pushing 'onHeartbeatCallback' on to queue
2024-11-09 13:24:54.082 Vloer: Processing 'onHeartbeatCallback' message
2024-11-09 13:24:54.082 Vloer: Acquiring GIL for 'onHeartbeatCallback' 

[jacobsentertainment]

Is there a other way of re-setting the plugin then manual trough the hardware page?