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
Output Home.app refresh event #392
Comments
So basically you would like to hook into nrchkb/HapNodeJS internals? I don't see a problem, actually feature which will allow that is planned (plugin system). |
I think the get event is called when the home app opens up and "refreshes" the item state? If I understand, basically you want to poll another api in nodered whenever someone opens up the home app, right? |
Yes. I believe “get” event is there for this purpose. |
Together with NRCHKB 2.0.0 onSet and onChange will be merged into unified output called events
Until then node service2 might be released as experimental feature. Node output will look like: type HAPServiceNodeEvent = {name: CharacteristicEventTypes, context?: any}
type HAPServiceNodeOutput = {
payload: { [key: string]: any }
hap: {
oldValue?: any
newValue?: any
context?: any
event: HAPServiceNodeEvent
session?: {
sessionID?: SessionIdentifier,
username?: HAPUsername,
remoteAddress?: string,
localAddress?: string,
httpPort?: number,
}
}
name?: string
topic: string
} |
Anything with All of these messages are from one single output, correct? |
Indeed,? means that undefined is allowed so value can be empty :) |
So a switch node watching for
we would expect to see the same output as current first output? |
### Fixed - Fixed customCharacteristics incorrect refresh in UI - Implemented static accessoryUUIDs for subflows Enables the use of nrchkb nodes in subflows with backwards compatibility #393 - thanks @kevinkub - Fixed Custom MDNS Configuration not showing in UI for Standalone Accessory - Stop components from clearing other component's node.status call - Add missing advertiser selector in UI for Standalone Accessory - Not naming the host node causes a crash #424 - Do not output oldValue for onSet as it does not have access to old value ### Added - Notice during app launch: Node.js 10 will be deprecated in Node-RED 2.0.0 - Event output in Service 2 which is available in NRCHKB_EXPERIMENTAL #392 #437 - Status node to fetch Serialized Service #210 - Support for environment variables in characteristic properties #217 ### Changed - Updated hap-nodejs to 0.9.5 (added new iOS 15 Services and Characteristics) - Updated dependencies to latest versions - Changed `BatteryService` to `Battery` in demo examples as `BatteryService` is deprecated #381 - thanks @crxporter - Readme rework - thanks @crxporter - More descriptive error when incorrect Characteristic has been used in msg.payload - Add msg.hap.allChars to service nodes #438
This is available now in "experimental" using @Shaquu can you provide or point us to some quick nodes on how to enable experimental? |
@crxporter here it is described how to enable experimental mode |
What's the schedule to move this into the standard ... perhaps (initially) as an alternative node? |
Can we make a new output to fire whenever a HomeKit controller request the current value of the characteristic?
It could be necessary when the HomeKit node is used to control a TV which is based on webService API. Currently I am triggering a query to the TV periodically (say 1 min) to update the latest status of TV to Homekit node. So, currently status displaying on home.app may not be real time. If we can have a 'get' event output, we can fire an trigger of query to update the latest status in almost realtime.
The text was updated successfully, but these errors were encountered: