Issues 2020.2 (build 12020)

hestia · Post by **hestia** » Monday 11 May 2020 13:28

I've upgraded from 2020-04-26 to 12020 and 3 issue types happened
1/ Devices from external json are no longer updated
2/ Temp device zwaves are no longer updated
3/ DzVent device.renane error

I've reverted to previous version: 1 and 3 are ok

waaren · Post by **waaren** » Monday 11 May 2020 14:44

hestia wrote: ↑Monday 11 May 2020 13:28 I've upgraded from 2020-04-26 to 12020 and 3 issue types happened
1/ Devices from external json are no longer updated
2/ Temp device zwaves are no longer updated
3/ DzVent device.renane error

I've reverted to previous version: 1 and 3 are ok

I cannot replicate these issues.

Can you please share what you see in the log when you update using an external JSON (and please include the json call itself) and when you use dzVents rename method? Preferable with script debugging on

hestia · Post by **hestia** » Monday 11 May 2020 21:37

Thanks for your reply
strange! Perhaps an issue during the installation?
For the zwaves devices, it is almost always an issue with an update with PIR and temp sensor, so maybe not specific to this

For the error on the device rename, perhaps it was setIcon, it was there

Code: Select all

devWAKEUPTIME.setIcon(ICON_PAUSE)
devWAKEUPTIME.rename(WAKEUPTIME_NAME .. ' - ' .. LangDayName(P_alarmDate))

The error related, but w/o mention of the script name in the log:
dzVents: Error: (3.0.5) Error parsing xml to Lua table: /home/pi/domoticz/scripts/dzVents/../lua/xml2lua.lua:92: Unbalanced Tag (/head) [char=299]
More log around, sorry for the mess in the log, it is a simple copy / paste

Spoiler: show: 2020-05-11
06:45:03
Error
hestia
local6
domoticz
dzVents: Error: (3.0.5) Error parsing xml to Lua table: /home/pi/domoticz/scripts/dzVents/../lua/xml2lua.lua:92: Unbalanced Tag (/head) [char=299]
2020-05-11
06:45:02
Error
hestia
local6
domoticz
Error opening url: http://127.0.0.1:8080/json.htm?type=com ... il+-+Lundi
2020-05-11
06:45:02
Error
hestia
local6
domoticz
Error opening url: http://127.0.0.1:8080/json.htm?type=set ... mimage=237
2020-05-11
06:45:02
Notice
hestia
local6
domoticz
Set UserVariable alarmIndex = 3
2020-05-11
06:45:02
Notice
hestia
local6
domoticz
Set UserVariable alarmTime = 7:15
2020-05-11
06:45:02
Notice
hestia
local6
domoticz
Set UserVariable alarmDate = 11/5/2020
2020-05-11
06:45:02
Notice
hestia
local6
domoticz
Set UserVariable alarmStatus = PLAY
2020-05-11
06:45:02
Error
hestia
local6
domoticz
dzVents: Error: (3.0.5) Error parsing xml to Lua table: /home/pi/domoticz/scripts/dzVents/../lua/xml2lua.lua:92: Unbalanced Tag (/head) [char=299]
2020-05-11
06:45:02
Error
hestia
local6
domoticz
Error opening url: http://127.0.0.1:8080/json.htm?type=set ... mimage=236
2020-05-11
06:45:02
Error
hestia
local6
domoticz
dzVents: Error: (3.0.5) Error parsing xml to Lua table: /home/pi/domoticz/scripts/dzVents/../lua/xml2lua.lua:92: Unbalanced Tag (/head) [char=299]
2020-05-11
06:45:01
Notice
hestia
local6
domoticz
EventSystem: Script event triggered: /home/pi/domoticz/dzVents/runtime/dzVents.lua
2020-05-11
06:45:01
Info
vito
cron
CRON
(pi) CMD (/home/pi/domoticz/scripts/python/domo2vito.py gas >> /var/log/domoticz/domo2vitoG.log 2>> /var/log/domoticz/domo2vitoG.err )
2020-05-11
06:45:01
Info
vito
authpriv
CRON
pam_unix(cron:session): session opened for user pi by (uid=0)
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
EventSystem: Script event triggered: /home/pi/domoticz/dzVents/runtime/dzVents.lua
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Info: Reveil_V0R5: ------ Finished Reveil_V0R5
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: callback = nil
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: headers = nil
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: post data = nil
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: method = GET
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: url = http://127.0.0.1:8080/json.htm?type=com ... il+-+Lundi
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: callback = nil
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: headers = nil
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: post data = nil
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: method = GET
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: url = http://127.0.0.1:8080/json.htm?type=set ... mimage=237
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: => On alarmIndex 3
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: Processing device-adapter for Fake LMS: Alert sensor adapter
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: ==>> FAKE_LMS 1037 On
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: DUMMY
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: PlayLMS On 75 zzReveilInfo
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: callback = nil
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: headers = nil
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: post data = nil
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: method = GET
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: OpenURL: url = http://127.0.0.1:8080/json.htm?type=set ... mimage=236
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: PLAY Wakeup at 6h40 slot 06:45:00 2
2020-05-11
06:45:00
Notice
hestia
local6
domoticz
dzVents: Debug: Reveil_V0R5: Alarm date 2020-05-11 time 06:45:00

I also have more log in a file if necessary... before I reverted

waaren · Post by **waaren** » Monday 11 May 2020 22:52

hestia wrote: ↑Monday 11 May 2020 21:37 strange! Perhaps an issue during the installation?

The error of unable to open the url is normally caused by the absence
in [setup][settings] of

: setup.png (14.08 KiB) Viewed 1606 times

No idea where the XML error comes from. Any scripts active around those times ?

hestia · Post by **hestia** » Monday 11 May 2020 22:57

I though it was a corruption in the package downloaded with https://www.domoticz.com/downloads/
As there was a new version: 2020.2.12038 / 2020-05-11, I did it again
And it failed!

Spoiler: show: 2020-05-11 22:39:30.133 Error: Error opening url: http://127.0.0.1:8080/json.htm?type=set ... mimage=237
2020-05-11 22:39:30.136 Error: Error opening url: http://127.0.0.1:8080/json.htm?type=com ... il+-+Mardi

An error from the distant server

Spoiler: show: Traceback (most recent call last):
File "/home/pi/domoticz/scripts/python/domo2vito.py", line 401, in <module>
last_rt=int(get_last_user_variable_value(user_idx['boilerRuntime']))
TypeError: int() argument must be a string or a number, not 'NoneType'

I'm going to revert again to see if the error disappear (I don't look at this very often...)

hestia · Post by **hestia** » Monday 11 May 2020 23:16

back to
Version: 2020.2
Build Hash: b63341bc0
Compile Date: 2020-04-26 13:47:55

external json ok for both servers

renamedevice ok

Spoiler: show: 2020-05-11 23:10:40.740 Status: dzVents: Debug: Reveil_V0R5: OpenURL: url = http://127.0.0.1:8080/json.htm?type=com ... il+-+Mardi
2020-05-11 23:10:40.740 Status: dzVents: Debug: Reveil_V0R5: OpenURL: method = GET
2020-05-11 23:10:40.740 Status: dzVents: Debug: Reveil_V0R5: OpenURL: post data = nil
2020-05-11 23:10:40.740 Status: dzVents: Debug: Reveil_V0R5: OpenURL: headers = nil
2020-05-11 23:10:40.740 Status: dzVents: Debug: Reveil_V0R5: OpenURL: callback = nil
2020-05-11 23:10:40.740 Status: dzVents: Debug: Reveil_V0R5: Constructed timed-command: Set Level 130
2020-05-11 23:10:40.741 Status: dzVents: Debug: Reveil_V0R5: Constructed timed-command: Set Level 130 NOTRIGGER

hestia · Post by **hestia** » Tuesday 12 May 2020 13:35

@waaren
I didn't saw your last reply before my message ; I experienced some response time issues on the forum yesterday.
Regarding the "Local Networks (no username/password):", I checked it and there was no changes.
I don't have the same way as you, but specific IPs: 127.0.0.1 ; 192.168.1.108 ; 192.168.1.121 ; 192.168.1.111

hestia · Post by **hestia** » Wednesday 13 May 2020 21:42

@waaren
following tests done:

http://192.168.1.103:8080/json.htm?type ... cmd=Toggle
from my PC 192.168.1.38

with Version: 2020.2 / Build Hash: b63341bc0 / Compile Date: 2020-04-26 13:47:55
and setting / Local Networks (no username/password) = 127.0.0.1 ; 192.168.1.38 ; 192.168.1.101 ; 192.168.1.31 ; 192.168.1.122
=> status "OK" / title "SwitchLight"

idem with 127.0.0.1 ; 192.168.1.* ; [...] '*' instead of exact list of IPs
=> OK also

with Version: 2020.2 (build 12038) / Build Hash: ac7b37e15 / Compile Date: 2020-05-11 17:20:01
same test with exact list of IPs
1/ setting / Local Networks (no username/password) = 127.0.0.1 ; 192.168.1.38 ; 192.168.1.101 ; 192.168.1.31 ; 192.168.1.122

=> 401 Unauthorized

2/ with 127.0.0.1 ; 192.168.1.* ; [...]
test ok

==>> From my point of view regression confirmed regarding "Local Networks (no username/password)"

hestia · Post by **hestia** » Wednesday 13 May 2020 21:53

addendum:
to avoid the error on internal url:
2020-05-13 21:47:37.241 Error: Error opening url: http://127.0.0.1:8080/json.htm?type=set ... mimage=237
2020-05-13 21:47:37.255 Error: Error opening url: http://127.0.0.1:8080/json.htm?type=com ... il+-+Jeudi

I had to set 127.0.0.* ; 192.168.1.* instead of 127.0.0.1 ; 192.168.1.*

same type of issue around Local Networks (no username/password)

waaren · Post by **waaren** » Wednesday 13 May 2020 22:35

hestia wrote: ↑Monday 11 May 2020 21:37 The error related, but w/o mention of the script name in the log:
dzVents: Error: (3.0.5) Error parsing xml to Lua table: /home/pi/domoticz/scripts/dzVents/../lua/xml2lua.lua:92: Unbalanced Tag (/head) [char=299]

Can you check with build >= 12056 when it becomes available. I changed something in the XML handling that might solve this issue.

I do not completely understand what you write about the other issues with latest beta's

hestia · Post by **hestia** » Thursday 14 May 2020 0:16

I do not completely understand what you write about the other issues with latest beta's

I meant that both issues :
1/ "external json" (from 192.168....)
2/ "internal json" for .setIcon/ .rename (from 127...)
disappear with "*" in the ip address in "Local Networks (no username/password)"

"external json" OK with 192.168.1.* / KO with 192.168.1.38 ; 192.168.1.101 ; 192.168.1.31 ; 192.168.1.122
"internal json" OK with 127.0.0.* / KO with 127.0.0.1

Both seem to be related to "Local Networks (no username/password)" ; there might have been a change around this in a previous beta
And both have been working well with Version: 2020.2 / Build Hash: b63341bc0 / Compile Date: 2020-04-26.
Till more than 1 year for external json.

I'll test build >= 12056 when avalable

hestia · Post by **hestia** » Thursday 14 May 2020 20:27

Result of the test with last donwload
Arm 32bit (Raspberry/Cubie/...) 2020.2.12057 2020-05-14
Version: 2020.2 (build 12057)
Build Hash: 096d786a2
Compile Date: 2020-05-14 10:22:15
dzVents Version: 3.0.5
Python Version: 3.5.3 (default, Sep 27 2018, 17:25:39) [GCC 6.3.0 20170516]

: SettingLocalNetworks.png (25.45 KiB) Viewed 1460 times

the PC is 192.168.1.38
The only line ok is when all IP of the LAN in authorized

Still KO

waaren · Post by **waaren** » Thursday 14 May 2020 22:16

hestia wrote: ↑Thursday 14 May 2020 20:27 the PC is 192.168.1.38
The only line ok is when all IP of the LAN in authorized

Still KO

Tested this again on Intel NUC Debian build 12057 and RPI4 Debian build 12060 and cannot replicate it. Not with 127.0.0.1;192.168.192.165 and not with 127.0.0.*; 192.168.192.* and all combinations of this.
So it looks like there must be something else different in our set-up /environment.

hestia · Post by **hestia** » Thursday 14 May 2020 22:23

Thanks
Do you think I need to install domoticz on a new folder from the last release and after upgrade to the last beta?
Or another way to find out what is wrong?

waaren · Post by **waaren** » Thursday 14 May 2020 23:31

hestia wrote: ↑Thursday 14 May 2020 22:23 Thanks
Do you think I need to install domoticz on a new folder from the last release and after upgrade to the last beta?
Or another way to find out what is wrong?

Network security is not my strongest point to say the least. If there is no real security risc to goto the bottom of this my personal approach would be to set the field to 127.0.0.*;192.168.1.* and if it works leave it like that.
I cannot think of any reason within domoticz why it should not work but again I am not an expert and I don't know if settings in website protection and RemoteProxyIPs could influence this behavior.
If you want to compare settings between us then please feel free to ask; either here or via PM

hestia · Post by **hestia** » Thursday 14 May 2020 23:59

set the field to 127.0.0.*;192.168.1.* and if it works leave it like that.

I'm not very happy with this because any device of my network could access Domoticz.
For server like, it is not a big deal, but also from any PC or tablet, one could log into the GUI and be admin.
There no longer any user profiles ; or perhaps I missed something

compare settings between

How could we do this? Are there any files to share?

What is strange it that it was ok before the last beta upgrades

Another thing strange is this issue https://www.domoticz.com/forum/viewtopi ... ce#p221540
that disappeared with 2020.1 and is back today with the last beta : 3 times tonight

Spoiler: show: 2020-05-14 23:35:58.804 Error: dzVents: Error: (3.0.5) Discarding device. No last update info found: {["changed"]=true, ["timedOut"]=false, ["signalLevel"]=11266936, ["protected"]=false, ["switchTypeValue"]=0, ["switchType"]="On/Off", ["description"]="", ["name"]="Hauteur Cuve", ["deviceType"]="General", ["lastLevel"]=255, ["subType"]="Custom Sensor", ["deviceID"]="", ["lastUpdate"]="", ["rawData"]={"112.0"}, ["batteryLevel"]=2, ["data"]={["hardwareName"]="Unknown?", ["_state"]="112.0", ["hardwareType"]="Unknown?", ["protected"]=false, ["icon"]="trashcan", ["hardwareTypeValue"]=0, ["sensorType"]=1, ["unit"]=1, ["_nValue"]=0, ["hardwareID"]=2387056, ["sensorUnit"]="cm"}, ["id"]=280, ["baseType"]="device"}

The value ["rawData"]={"112.0"} is related to a dummy device updated by a json from a ESP-8266 on WiFi

waaren · Post by **waaren** » Friday 15 May 2020 0:15

hestia wrote: ↑Thursday 14 May 2020 23:59
compare settings between
How could we do this? Are there any files to share?

the only relevant settings in domoticz are in the preferences table.

Code: Select all

select * from preferences;

Key|nValue|sValue

SecStatus|1|
AuthenticationMethod|0|
WebUserName|0|xxxxxxxx
WebPassword|0|xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
WebLocalNetworks|0|127.0.0.1;192.168.192.*
SecPassword|0|xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ProtectionPassword|0|xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
WebRemoteProxyIPs|0|

hestia · Post by **hestia** » Friday 29 May 2020 22:50

I made several new tests regarding this issue with an old backup to go back in the past:

With this parameters
Local Networks (no username/password):
127.0.0.1 ; 192.168.1.38; 192.168.1.104 ; 192.168.1.111 ; 192.168.1.141

2 tests
1/ This url from my PC 192.168.1.38
http://192.168.1.35:8080/json.htm?type= ... cmd=Toggle
2/ a rename of device in a dzVents script

Version: 2020.1 (build 11875)
Build Hash: 8c5c9826f-modified
Compile Date: 2020-04-03 08:25:18
dzVents Version: 3.0.2

=> TEST url OK

Upgrade to (release):
Version: 2020.2
Build Hash: b63341bc0
Compile Date: 2020-04-26 13:47:55
dzVents Version: 3.0.2

=> TEST url OK
=> TEST Rename OK

Upgrade to (beta):
Version: 2020.2 (build 12067)
Build Hash: 0fc3c7b70
Compile Date: 2020-05-17 13:15:45
dzVents Version: 3.0.5

=> TEST url KO 401 Unauthorized
=> TEST Rename KO
2020-05-20 19:51:29.660 Error: Error opening url: http://127.0.0.1:8080/json.htm?type=com ... &name=test

NEW INSTALL (another directory)
Version: 2020.2
Build Hash: b63341bc0
Compile Date: 2020-04-26 13:47:55
dzVents Version: 3.0.2
Python Version: 3.5.3 (default, Sep 27 2018, 17:25:39) [GCC 6.3.0 20170516]
with Import DB

=> TEST url OK
=> TEST Rename OK

Install last beta (./updatebeta)

=> TEST url KO 401 Unauthorized
=> TEST Rename KO

Remove all blanks between IPs in the Local Networks (no username/password):
=> TEST url OK
=> Rename OK

It seems clear for me that the installation of some betas broked something!

waaren · Post by **waaren** » Saturday 30 May 2020 10:22

hestia wrote: ↑Friday 29 May 2020 22:50 It seems clear for me that the installation of some betas broked something!

Could well be that something changed in recent beta's in that area. From the top of my head, entering IPv6 addresses and IPv6 wildcards is allowed now.
Is my observation from this that everything works fine if you enter the addresses / wildcards without spaces or tabs correct?
If not can you try after adding ::1 to Local Networks (no username/password):

hestia · Post by **hestia** » Saturday 30 May 2020 14:19

everything works fine if you enter the addresses / wildcards without spaces or tabs correct?

YES

but:
it was difficult to found out
not really documented: I've just read again the comment => (Separate by a semicolon, For Example: 127.0.0.*;192.168.0.*), I have to say that there are not blanks in this example!
And the most important: it was ok before some betas with blanks and ko after installation without any information

So for me at the present time, I back to a normal situation, perhaps others have such an issue

Issues 2020.2 (build 12020) Topic is solved

Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 from build 12020

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Re: Issues 2020.2 (build 12020)

Who is online