Search found 51 matches
- Wednesday 11 February 2026 22:37
- Forum: Switches and Scenes
- Topic: Error: GetJSonDevices: exception occurred : 'stoull'
- Replies: 10
- Views: 185
Re: Error: GetJSonDevices: exception occurred : 'stoull'
Thank you for your feedback. Hopefully someone will have an idea.
- Wednesday 11 February 2026 21:07
- Forum: Switches and Scenes
- Topic: Error: GetJSonDevices: exception occurred : 'stoull'
- Replies: 10
- Views: 185
Re: Error: GetJSonDevices: exception occurred : 'stoull'
No, the problem is not solved. I inspected the database with DB browser for sqlite and found no anomalies, especially in the stored Strings.
- Thursday 05 February 2026 18:14
- Forum: Bugs and Problems
- Topic: Crash with 2025.2 beta 17074
- Replies: 12
- Views: 343
Re: Crash with 2025.2 beta 17074
Happy end!
I have upgraded to trixie. https://forums.raspberrypi.com/viewtopi ... 6&start=50
domoticz is running!
I shall have some stuff to repair monit's parameters...
Thank you for your help.
I have upgraded to trixie. https://forums.raspberrypi.com/viewtopi ... 6&start=50
domoticz is running!
I shall have some stuff to repair monit's parameters...
Thank you for your help.
- Thursday 05 February 2026 16:16
- Forum: Bugs and Problems
- Topic: Crash with 2025.2 beta 17074
- Replies: 12
- Views: 343
Re: Crash with 2025.2 beta 17074
I can't revert because I do an update several times and backups are dated after the first update.
Two solutions:
- Waiting for another release?
- Try updating to Debian 13?
What do you think about that?
Two solutions:
- Waiting for another release?
- Try updating to Debian 13?
What do you think about that?
- Thursday 05 February 2026 12:26
- Forum: Bugs and Problems
- Topic: Crash with 2025.2 beta 17074
- Replies: 12
- Views: 343
Re: Crash with 2025.2 beta 17074
Thanks Chris for your reply. I'll wait a few hours and see if a new beta version is released before reverting to the old one.
I also think it's a problem with Bookworm.
I also think it's a problem with Bookworm.
- Thursday 05 February 2026 8:49
- Forum: Bugs and Problems
- Topic: Crash with 2025.2 beta 17074
- Replies: 12
- Views: 343
Crash with 2025.2 beta 17074
Hello, This morning I update from 2025.2 beta 17060 to 2025.2 beta 17074.
And domoticz crashes at opening:
● domoticz.service - LSB: Home Automation System
Loaded: loaded (/etc/init.d/domoticz.sh; generated)
Active: active (exited) since Thu 2026-02-05 08:37:58 CET; 3min 17s ago
Docs: man ...
And domoticz crashes at opening:
● domoticz.service - LSB: Home Automation System
Loaded: loaded (/etc/init.d/domoticz.sh; generated)
Active: active (exited) since Thu 2026-02-05 08:37:58 CET; 3min 17s ago
Docs: man ...
- Thursday 29 January 2026 17:18
- Forum: Switches and Scenes
- Topic: Error: GetJSonDevices: exception occurred : 'stoull'
- Replies: 10
- Views: 185
Re: Error: GetJSonDevices: exception occurred : 'stoull'
I put 1 day in short log settings and I see tomorrow...
Thank for your help
Thank for your help
- Thursday 29 January 2026 16:33
- Forum: Switches and Scenes
- Topic: Error: GetJSonDevices: exception occurred : 'stoull'
- Replies: 10
- Views: 185
Re: Error: GetJSonDevices: exception occurred : 'stoull'
Yes, I have already done it.
Integrity check is OK.
but I don't know where I search in the DB.
This message appears each time I click 'Log' regardless of the device.
Integrity check is OK.
but I don't know where I search in the DB.
This message appears each time I click 'Log' regardless of the device.
- Thursday 29 January 2026 15:33
- Forum: Bugs and Problems
- Topic: Message FCM in log
- Replies: 5
- Views: 88
Re: Message FCM in log
Thank you for your response, waltervi
- Thursday 29 January 2026 11:49
- Forum: Switches and Scenes
- Topic: Error: GetJSonDevices: exception occurred : 'stoull'
- Replies: 10
- Views: 185
Re: Error: GetJSonDevices: exception occurred : 'stoull'
Deleting and recreating a device is the key? (but I lost all old datas...)
- Thursday 29 January 2026 11:39
- Forum: Bugs and Problems
- Topic: Message FCM in log
- Replies: 5
- Views: 88
Re: Message FCM in log
2025.2 (built 17057)
- Thursday 29 January 2026 9:19
- Forum: Switches and Scenes
- Topic: Error: GetJSonDevices: exception occurred : 'stoull'
- Replies: 10
- Views: 185
Error: GetJSonDevices: exception occurred : 'stoull'
Hello,
This message appears in log ans I can't find to solve it.
I disable all my scripts: The problem is not here.
It appears when I click on log button of a device Smart P1 and a second time when I close the log graphs, for instance.
Thanks for your help
This message appears in log ans I can't find to solve it.
I disable all my scripts: The problem is not here.
It appears when I click on log button of a device Smart P1 and a second time when I close the log graphs, for instance.
Thanks for your help
- Thursday 29 January 2026 8:50
- Forum: Bugs and Problems
- Topic: Message FCM in log
- Replies: 5
- Views: 88
Message FCM in log
Hello
When I Apply setting, I have always this message:
2026-01-29 08:32:27.462 Status: FCM: Client Email not configured. Please configure in Settings > Notifications.
2026-01-29 08:32:27.462 Status: FCM: Private Key not configured. Please configure in Settings > Notifications.
2026-01-29 08:32 ...
When I Apply setting, I have always this message:
2026-01-29 08:32:27.462 Status: FCM: Client Email not configured. Please configure in Settings > Notifications.
2026-01-29 08:32:27.462 Status: FCM: Private Key not configured. Please configure in Settings > Notifications.
2026-01-29 08:32 ...
- Saturday 27 September 2025 18:46
- Forum: Bugs and Problems
- Topic: ...running for more than 10 seconds
- Replies: 2
- Views: 77
Re: ...running for more than 10 seconds
Thank you for your help.
I solved my problem: Two of my process used 'osCommand'. I converted them in asynchronous mode.
I solved my problem: Two of my process used 'osCommand'. I converted them in asynchronous mode.
- Friday 26 September 2025 8:18
- Forum: Bugs and Problems
- Topic: ...running for more than 10 seconds
- Replies: 2
- Views: 77
...running for more than 10 seconds
Hello,
For some time now, I have been consistently receiving this message every time the automatic backup starts:
2025-09-26 08:00:00.565 Status: Starting automatic database backup procedure...
2025-09-26 08:00:02.604 Status: Ending automatic database backup procedure...
2025-09-26 08:00:10.321 ...
For some time now, I have been consistently receiving this message every time the automatic backup starts:
2025-09-26 08:00:00.565 Status: Starting automatic database backup procedure...
2025-09-26 08:00:02.604 Status: Ending automatic database backup procedure...
2025-09-26 08:00:10.321 ...
- Saturday 02 August 2025 15:40
- Forum: Bugs and Problems
- Topic: bug with openURL after updating Domoticz?
- Replies: 14
- Views: 1547
Re: bug with openURL after updating Domoticz?
I don’t think so because the LUA script work fine in the same Time.
- Saturday 02 August 2025 7:36
- Forum: Bugs and Problems
- Topic: bug with openURL after updating Domoticz?
- Replies: 14
- Views: 1547
Re: bug with openURL after updating Domoticz?
I had created a token available during 72h.
No, my research is a failure.
Something is amazing: I leave the scripts #3 and #4 executing every minute during 48h.
On each call, URL response is effective.
Script #3 (LUA) : Always received a json, every minute.
Script #4 (dzvents): Sometime, 4 json ...
No, my research is a failure.
Something is amazing: I leave the scripts #3 and #4 executing every minute during 48h.
On each call, URL response is effective.
Script #3 (LUA) : Always received a json, every minute.
Script #4 (dzvents): Sometime, 4 json ...
- Wednesday 30 July 2025 17:46
- Forum: Bugs and Problems
- Topic: bug with openURL after updating Domoticz?
- Replies: 14
- Views: 1547
Re: bug with openURL after updating Domoticz?
I don't understand why Script #3 (LUA) is OK and not in Script #4 (dzvents).
Script #3
commandArray = {}
local getHTTP = function(cmd)
local config=assert(io.popen('curl -m 8 '..cmd))
local location = config:read('*all')
config:close()
return location
end
apikey = 'xxxxxxxxxxxxx'
cmd ...
Script #3
commandArray = {}
local getHTTP = function(cmd)
local config=assert(io.popen('curl -m 8 '..cmd))
local location = config:read('*all')
config:close()
return location
end
apikey = 'xxxxxxxxxxxxx'
cmd ...
- Tuesday 29 July 2025 13:50
- Forum: Bugs and Problems
- Topic: bug with openURL after updating Domoticz?
- Replies: 14
- Views: 1547
Re: bug with openURL after updating Domoticz?
domoticz beta updated (always on beta since 8 years)
No docker container for domoticz
NB: I use openURL (GET but without headers) in another events and they go fine.
In Debug, the format of the headers seems amazing to me... but I am not a specialist...
Debug:
2025-07-29 13:30:05.232 dzVents ...
No docker container for domoticz
NB: I use openURL (GET but without headers) in another events and they go fine.
In Debug, the format of the headers seems amazing to me... but I am not a specialist...
Debug:
2025-07-29 13:30:05.232 dzVents ...
- Tuesday 29 July 2025 10:18
- Forum: Others
- Topic: integration ismartgate in domoticz
- Replies: 17
- Views: 4235
Re: integration ismartgate in domoticz
Fantastic!!
I hav'nt sawn this add in the doc!
Thank you for your help.
I hav'nt sawn this add in the doc!
Thank you for your help.