# BACNET Ignition driver unsupported objects? **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [July 20, 2021, 1:38pm UTC](https://forum.inductiveautomation.com/t/bacnet-ignition-driver-unsupported-objects/48982 "2021-07-20T13:38:16Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [December 10, 2021, 12:25pm UTC](https://forum.inductiveautomation.com/t/bacnet-ignition-driver-unsupported-objects/48982/5 "2021-12-10T12:25:46Z")
BACNET - add Schedule for a remote Device a possible workaround with this ticket > [@BACNET - add Schedule for a remote Device](https://forum.inductiveautomation.com/t/bacnet-add-schedule-for-a-remote-device/53503): > > Hi @Kevin.Herron, We would like to be able to add schedule object to a remote bacnet device with Ignition Bacnet driver. To my mind, Bacnet schedule has to be to read or write when requested by a user demand. So, is there a way to do this with ignition script with import of objects from the stack (bacnet4J) used in the Ignition bacnet driver ? As a feature request, some script functions exposed by the Ignition Bacnet driver to R/W bacnet object properties not exposed as tags or bacnet object… --- _[View the full topic](https://forum.inductiveautomation.com/t/bacnet-ignition-driver-unsupported-objects/48982)._