Hi Karl, just upgraded and I am getting this error
piBeacon Error Line 12444 has error=Unknown format code 'd' for object of type 'float'
Any ideas?
Thanks
error in 116.332
Re: error in 116.332
It appears to be due to BLEconnect with my iPhones. I get this when trying to edit the device, and it works without error when I turn off the phone devices.
piBeacon Error setting up BLEconnect Line 3636 has error=range() integer end argument expected, got list.
piBeacon Error validateDeviceConfigUi pgm error, check log
piBeacon Error Line 12444 has error=Unknown format code 'd' for object of type 'float'
piBeacon Error Line 12444 has error=Unknown format code 'd' for object of type 'float'
piBeacon Error setting up BLEconnect Line 3636 has error=range() integer end argument expected, got list.
piBeacon Error validateDeviceConfigUi pgm error, check log
piBeacon Error setting up BLEconnect Line 3636 has error=range() integer end argument expected, got list.
piBeacon Error validateDeviceConfigUi pgm error, check log
piBeacon Error Line 12444 has error=Unknown format code 'd' for object of type 'float'
piBeacon Error Line 12444 has error=Unknown format code 'd' for object of type 'float'
piBeacon Error setting up BLEconnect Line 3636 has error=range() integer end argument expected, got list.
piBeacon Error validateDeviceConfigUi pgm error, check log
Re: error in 116.332
>>> piBeacon Error Line 12444 has error=Unknown format code 'd' for object of type 'float'<<<
in config set unit for pressure (changed mbar to mBar, and the default is not set)
>>> piBeacon Error setting up BLEconnect Line 3636 has error=range() integer end argument expected, got list. <<<
introduced in last version, changed code to better manage # of rpi etc.
will fix both today.
Karl
in config set unit for pressure (changed mbar to mBar, and the default is not set)
>>> piBeacon Error setting up BLEconnect Line 3636 has error=range() integer end argument expected, got list. <<<
introduced in last version, changed code to better manage # of rpi etc.
will fix both today.
Karl
Re: error in 116.332
should be fixed in v7.117.334
there was a .333 version hat had these fixes already, but they did not go to the plugin store, just on GitHub.
hopefully this fixes it .
Karl
there was a .333 version hat had these fixes already, but they did not go to the plugin store, just on GitHub.
hopefully this fixes it .
Karl