I recently migrated from openzwave to zwave-UI, with a MQTT broker in between, this works. I can control my devices.
However, now my logging gets these error messages:
"Error: Invalid Number sValue: '%' for device idx: '%'"
I think it only shows up when I view the dashboard webpage or some other page of domoticz, but not entirely sure.
Any suggestion what this might have caused the error ? How can I find it out ?
migrated to zwave-ui, now getting strange errors in log
Moderators: leecollings, remb0
Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.
Use the following template when posting here:
Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....
If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly
If you are replying, please do not quote images/code from the first post
Please mark your topic as Solved when the problem is solved.
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.
Use the following template when posting here:
Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....
If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly
If you are replying, please do not quote images/code from the first post
Please mark your topic as Solved when the problem is solved.
-
WickedW
- Posts: 3
- Joined: Saturday 15 November 2025 17:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Netherlands
- Contact:
Re: migrated to zwave-ui, now getting strange errors in log
I think I resolved it:
WIth /json.htm?type=command¶m=devices_list I found a ghost device under idx 95.
I resolved it by creating a new device under the same name and replacing it with ?itself? and then magically the error stopped appearing.
WIth /json.htm?type=command¶m=devices_list I found a ghost device under idx 95.
I resolved it by creating a new device under the same name and replacing it with ?itself? and then magically the error stopped appearing.
Who is online
Users browsing this forum: Amazon [Bot], heggink and 1 guest