-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to set _config_mode #594
Comments
Hi @prajgujarathi can you please remove this part?
What is the purpose of validating an exported config? |
Hi, @charbull Just to test the validation setup. If I remove that part, I get another error: while parsing a mapping Using a simple YMAL file: FAN_4:
|
Can you please start with an example from here: |
@charbull Isn't the config_metadata block required? @prajgujarathi try validating with:
|
@prajgujarathi Did that fix your issue? |
Yes, it did. Thank you. |
Great. Closing issue. |
fyi: the initialize is the default setup, it is not required. |
Describe the bug
I keep getting errors on valid YMAL files saying KeyError: 'No valid _config_mode is set' when trying to validate using instance_validator
To Reproduce
Steps to reproduce the behavior:
Go to folder digitalbuildings\tools
try validating the file using the validator using the command py .\toolkit.py --input file-path -v
Expected behavior
It errors out with error:
-py3.9.egg\validate\instance_parser.py", line 374, in _ValidateEntityContent
raise KeyError('No valid _config_mode is set')
KeyError: 'No valid _config_mode is set'
OS (please complete the following information):
windows
Here are the file contents:
CONFIG_METADATA:
operation: EXPORT
US-MTV-1804:
type: FACILITIES/BUILDING
id: FACILITIES/
device2715203:
type: HVAC/FAN_SS_DSP
cloud_device_id: 2550389110353931
translation:
exhaust_fan_run_command:
present_value: "points.efss_1.present_value"
states:
ON: "true"
OFF: "false"
schedule_run_command:
present_value: "points.schedule_1.present_value"
states:
ON: "true"
OFF: "false"
zone_air_cooling_temperature_setpoint:
present_value: "points.eff_clg_sp_1.present_value"
units:
key: "pointset.points.eff_clg_sp_1.units"
values:
degrees_fahrenheit: "°F"
unoccupied_zone_temperature_cooling_setpoint:
present_value: "points.unocc_clg_sp_1.present_value"
units:
key: "pointset.points.unocc_clg_sp_1.units"
values:
degrees_fahrenheit: "°F"
zone_air_unoccupied_heating_temperature_setpoint:
present_value: "points.unocc_htg_sp_1.present_value"
units:
key: "pointset.points.unocc_htg_sp_1.units"
values:
degrees_fahrenheit: "°F"
failed_alarm:
present_value: "points.ef_fail_1.present_value"
states:
ON: "true"
OFF: "false"
zone_air_heating_temperature_setpoint:
present_value: "points.eff_htg_sp_1.present_value"
units:
key: "pointset.points.eff_htg_sp_1.units"
values:
degrees_fahrenheit: "°F"
occupied_zone_temperature_cooling_setpoint:
present_value: "points.occ_clg_sp_1.present_value"
units:
key: "pointset.points.occ_clg_sp_1.units"
values:
degrees_fahrenheit: "°F"
zone_air_occupied_heating_temperature_setpoint:
present_value: "points.occ_htg_sp_1.present_value"
units:
key: "pointset.points.occ_htg_sp_1.units"
values:
degrees_fahrenheit: "°F"
exhaust_fan_run_status:
present_value: "points.efst_1.present_value"
states:
ON: "true"
OFF: "false"
zone_air_temperature_sensor:
present_value: "points.zone_temp_asvi_1.present_value"
units:
key: "pointset.points.zone_temp_asvi_1.units"
values:
degrees_fahrenheit: "°F"
connections:
US-MTV-1804: CONTAINS
The text was updated successfully, but these errors were encountered: