-
Hi @toggledbits it is possible to have an array in the following way
["Window 1"]["Status On"]
["Window 2"]["Status On"]
["Window 3"]["Status Off"]
["Window 4"]["Status On"]That is, bidirectional.
How would this array be loaded? Normally we use Variable = ${{ ["Window 1", "Window 2", "Window 3", "Window 4"] }}, how would the array pair be loaded?.
Then the use, how would be a looping where I want to ask who has "Status On" and it returns me a new array with the part 1, that is the list of "Window"?
Or another search, I provide the information of the content of part 1, as "Window 2" and it would return me an array with the part 2 "Satus On".
Is it possible to have something like this?
Could you give the examples?
Thanks.
-
I've recently updated to latest build 21332 and notice in the Readme file that I should update nodejs to 16.13.0 or higher before end of March. I've had a go at doing this, but think I've not done it correctly as I get the following responses in the terminal:
pi@raspberrypi:~ $ node -v
v14.17.0
pi@raspberrypi:~ $ nodejs -v
v16.13.0Is this correct? If not then what steps do I need to carry out to update nodejs properly.
Any help from the group would be much appreciated.
-
Use case: Honeywell API gets easily flustered resulting in either one or both of my t-stats not receiving the change command/s. As such, I've written some "course correction" rulesets that basically look at the present situation and, if not matching what should be there, resends the command.
Now... logic says if the first send didn't get thru then APIs generally aren't going to like another one right on it's heels. To combat this, I've added a Restriction to the correction ruleset that says the status must exist for 420 seconds before it will fire. This (hopefully) also prevents a race state when the real rule set AND the correction spring into action at the same time.
I set a notification reaction to let me know a course correction had to be implemented but I've noticed that it fires even if the Restriction on the actual reaction never completes (is found unnecessary) and, as such, the correction ruleset never actually needs to fire.
The ask: can a notification be tied to fire ONLY if/when the action actually fires?
Hopefully that is clearer than mud.
Solved here https://smarthome.community/post/10319.
-
A few new functions have worked their way into Reactor's expression language over the last couple of months, and while they are documented in the change logs and documentation, it seems some of you are not aware of them, so I'm going to pick one out and highlight it, maybe do others later...
A lot of you build strings in expressions by simple concatenation, and there's nothing wrong with that, but there's a new function in the expression language that can help you clean things up, in particular when handling numeric values.
I've noticed many of you will round your results either on the calculation, or in some cases, in a separate variable. For example, say we have a pair of expressions that retrieves the indoor and outdoor temperature from a sensor and the weather service:
indoor = getEntity( 'hubitat>144' ).attributes.temperature_sensor.value' ) outdoor = getEntity( 'weather>home' ).attributes.wx.temperatureThe weather service, since it converts from degrees K in its reporting to degrees C, may have an irrational or repeating value (e.g. 8.233333333...). As a result, when you compute the difference, it, too, may have an irrational or repeating result, so you decide to round it to one decimal:
tempDiff = round( outdoor - indoor, 1 )Then, perhaps you have a rule that if the differential is greater than 10 degrees, you send a notification, and the notification uses all three variables in the message string:
${{ 'The outdoor temperature is ' + outdoor + 'C and the indoor temperature is ' + indoor + 'C; the difference is ' + tempDiff + 'C' }}This is fine, except that the outdoor temperature isn't rounded, so you decide to fix that. There are at least three ways: add a round() to the outdoor variable expression, or create a third variable like outdoorRounded = round( outdoor, 1 ), or, use the round() function into the substitution expression
${{ 'The outdoor temperature is ' + round( outdoor, 1 ) + 'C and the indoor temperature is ' + indoor + 'C; the difference is ' + tempDiff + 'C' }}It's all getting very messy... Let's use format() instead of string concatenation, and not worry about rounding the difference, so we keep the maximum precision possible for any calcs or tests that use it. We go back to:
indoor = getEntity( 'hubitat>144' ).attributes.temperature_sensor.value' ) outdoor = getEntity( 'weather>home' ).attributes.wx.temperature tempDiff = outdoor - indoorNow our string substitution:
${{ format( "The outdoor temperature is {0:.1f}C and the indoor temperature is {1:.1f}C; the difference is {2:.1f}C", outdoor, indoor, tempDiff ) }}Here, format() is building the message string. Each {} (curly-brace) pair denotes the substitution of a parameter to follow. The number first inside the opening curly brace is the parameter number, starting from 0 as the first parameter. So parameter 0 in this example refers to the variable outdoor, and 1 is indoor, and 2 is tempDiff. Using the numbers, parameters can be inserted in any order.
Each of these substitutions in the example includes an optional format specification. If no format specification is given (e.g. {0}), then the parameter is converted to a string with no special formatting, but since we can get numbers like 8.233333... it's desirable to use some formatting to make it pretty. The format is separated from the parameter number by the : (colon) in the substitution. The format we're using for all three parameters is .1f, which is <width>.<precision>f. Any number before the dot is a fixed field width, but since we want no extra spaces, we just don't specify a width (it's blank for our example), and the value will take as much space as it needs. The f at the end tells format() that the value is going to be formatted as a floating point number, and the .1 before the f tells the formatter to display a single decimal digit. So our 8.23333333 value would be displayed as 8.2, without using extra functions or variables, or dropping precision in a calculation. For clarity, 10.875 would be displayed/inserted as 10.9 in this example, because the formatter will round the displayed result to the specified number of decimal digits.
Tip: for simple string insertions that require no special formatting, format() will let you skip the parameter numbers if the parameters are in the same order as the substitutions, and the default format is (generic) string (s), so format( "{} x {} = {}", "alpha", "beta", "gamma" ) produces the string alpha x beta = gamma.
Docs for format are in the Reactor documentation under the heading Special Reactor Functions.
-
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed. -
Hi
Wanted to create a rule for monitoring the battery level of Z-Wave devices on my Vera hub.
I can select the battery level as the trigger OK.
But not sure how to handle the Reaction to send an alert / notification ?
If in the triggers I have multiple devices monitored for their battery level
39a2f0af-c2e4-450b-a1ce-f542df31d02d-image.png
How could I create say a TTS announcement or text alert that mentions the name of the device who's battery level has dropped below 10% ? The device that has triggered the rule.
I'd rather not have to create an individual rule for each device etc.
Any ideas?
Thanks
-
My trusty vera plus is starting to have some issues that are making me think that it is about to die. i now get constant luup reloads even though i've moved almost everything except for z-wave devices and the iphone locator off that machine. it is even booting off an ssd drive to minimize wear and tear on the internal memory. I've moved all my logic off box to MSR, so it is just a glorified zwave adapter. I would love to hear any ideas that would make moving 60ish devices off that box to something else as painless as possible. the thought of excluding and including the devices sends shivers down my spine, so anything that helps me migrate the network would be greatly welcomed. anyone have any suggestions?
-
I have 3 outside temperatures and I would like to pick the middle value of the 3 to use as the outside air temperature for calculations and logic.
The obvious, to me, mid() function does not seem to exist. What function can I use to pick the middle of the three values?
Thanks,
Tom -
I'm probably going to release my first pass at the MQTTController for Reactor (aka MSR) this week. It doesn't yet intrinsically know about a lot of devices, but you can train it for pretty much anything, I think, and it would be great if a couple of our heavy MQTT users could help check it out and maybe help contribute some device templates.
I'm hoping to package it up for mid-week, assuming the rest of life stays on track.
Success factors for the test: solid familiarity with MQTT, a big mix of devices, and comfortable editing YAML (for creating the templates/mappings).
-
Whenerver openLuup restarts or reloads Luup MQTTController can't reconnect and I have to restart Reactor to solve it.
[latest-21321]2021-11-24T07:39:17.842Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:39:17.844Z <MQTTController:ERR> Controller MQTTController#mqtt is off-line! [latest-21321]2021-11-24T07:39:32.849Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:40:15.473Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:40:30.475Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:40:52.696Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:41:07.702Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:41:40.213Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:41:55.217Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:57:39.113Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:57:54.114Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:58:16.396Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:58:31.399Z <MQTTController:NOTICE> attempting reconnect [latest-21321]2021-11-24T07:58:37.271Z <MQTTController:NOTICE> broker connection is offline; waiting for auto-reconnect [latest-21321]2021-11-24T07:58:52.278Z <MQTTController:NOTICE> attempting reconnect -
I have multiple sensors connected to via Bluetooth to a Tasmota device.
All sensors report their values in the SENSOR topic, how do I map those to individual entities? -
I can no longer access the Rule Sets menu after upgrading to build 21275. Nothing happens when I click on Rule Sets. Other menu options work fine. I have cleared history, hard refreshed the browser, Rebooted. Works fine in Firefox and google chrome. I have always used Safari.
Suggestions?Safari for Mac version 15.0
MSR Version 21275-df3d784
Synology Docker -
Hi, in Reactor there is "SendData" actions to change value for device's configurations without to use Lua. Is this possible also for MSR?
If not, which is the possible way to do it?Thanks in advance
-
Goal: xmas tree/mantel lights go on with outdoor lights (if mode = Evening) but shut off at 23:00 whilst outdoor remain until sunrise -20. Tree and mantel should only go one when someone is home, outdoor go on no matter what, hence the mode trigger.
Configurations
Ruleset "Arm For Xmas" triggers = date ranges (all vetted/proven in prior years, good to go here) and sunset/sunrise:Screen Shot 2021-11-21 at 12.05.18 PM.png
Ruleset "Xmas tree/mantel lights" triggers =
Screen Shot 2021-11-21 at 12.07.29 PM.png
Seeking confirmation that my use of start time from the "Arm For" and end time from the "Xmas tree/mantel" scene will play well together.
-
Noticed in the last few nights that my Global Reaction to turn on a mere six lights in the evenings the same two devices no longer turn on. One is a dimming smart bulb, the other is a wall outlet.
This has been running flawlessly for months - just in the last few nights I've noticed these two devices being left behind and yes, it's always these two devices only.
"What changed?"
No Hubitat firmware updates No new devices added to Hubitat list itemTwo MSR updates (the last two, I keep up with the latest) list itemHome Assistant releases (should have zero bearing, HA is nothing more than pretty dashboards) list itemAdded MQTT to MSRI did do a z-wave "repair" last night and am waiting to see if this helps.
Is there any maximum or cap on number of devices that should be included in a Global Reaction?
*Marked as solved as the question asked was answered. The issue persists but the question was answered.
-
I would like to consult, and maybe even suggest, the possibility that all devices have the common attribute binary_sensor.state.
I am in the process of switching from Vera to Hubitat, and I see huge benefits in Hubitat having very few attributes available to the devices, which makes the device lighter, and faster in my opinion.
But one point that bothers me is for example plug and switch has binary_sensor.state which basically replicates the state of the Tripped Vera.
In Hubitat motion devices don't have it (similar Tripped), the status is motion_sensor.state, in this case my suggestion is if it would be possible that MSR creates in these devices the attribute binary_sensor.state and equals automatically the motion_sensor.state.
Expandindo a solicitacao (asking is not prohibited 🙂 ) to thermostats for example, I imagine that the hvac_control.mode attribute, other than "off" which means the device is "on (heat, cool)", also has the binary_sensor.state set to "true" (heat, cool) for "on" and "false" for "off".
In summary, regardless of the hub, or type of device a standard attribute to indicate and command the "on" or "off" status, similar to Tripped that has Vera that creates a standard of the devices.
Thanks.
-
I can't get power_switch.state to reflect current state in the UI for Tasmota sonoff basic/dual/4channel pro.
It triggers a green glow in the Entities for the device but the value is never changed to true.Config:
"larmlampa_takfläkt_hall": name: "Larmlampa Takfläkt Hall" topic: "TakfläktHall" unit: "1" uses_template: tasmota_generic_relayLog:
[latest-21314]2021-11-16T18:03:02.003Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=tele/TakfläktHall/STATE, payload={"Time":"2021-11-16T19:03:00","Uptime":"35T11:31:51","Vcc":3.170,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Orion","RSSI":52,"APMac":"60:F4:45:E7:68:E6"}} [latest-21314]2021-11-16T18:03:02.006Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=openLuup/update/30009/TakfläktHall/tele, payload={"Time":"2021-11-16T19:03:00","Uptime":"35T11:31:51","Vcc":3.170,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Orion","RSSI":52,"APMac":"60:F4:45:E7:68:E6"}} [latest-21314]2021-11-16T18:03:02.007Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=openLuup/update/30009/TakfläktHall/Uptime, payload=35T11:31:51 [latest-21314]2021-11-16T18:03:02.008Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=openLuup/update/30009/TakfläktHall/Time, payload=2021-11-16T19:03:00 [latest-21314]2021-11-17T10:30:48.246Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=cmnd/TakfläktHall/POWER2, payload= [latest-21314]2021-11-17T10:30:48.246Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=cmnd/TakfläktHall/POWER1, payload= [latest-21314]2021-11-17T10:30:48.247Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER2":"OFF"} [latest-21314]2021-11-17T10:30:48.247Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER2":"OFF"} [latest-21314]2021-11-17T10:30:48.249Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER2":"OFF"} [latest-21314]2021-11-17T10:30:48.297Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER2, payload=OFF [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER2 for takfläkt_hall: OFF [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:48.298Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:48.304Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER1, payload=OFF [latest-21314]2021-11-17T10:30:48.304Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER1 for larmlampa_takfläkt_hall: OFF [latest-21314]2021-11-17T10:30:50.592Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER1":"ON"} [latest-21314]2021-11-17T10:30:50.593Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER1":"ON"} [latest-21314]2021-11-17T10:30:50.593Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER1":"ON"} [latest-21314]2021-11-17T10:30:50.596Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER1, payload=ON [latest-21314]2021-11-17T10:30:50.597Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER1 for larmlampa_takfläkt_hall: ON [latest-21314]2021-11-17T10:30:52.585Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/RESULT, payload={"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:52.586Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:52.587Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/RESULT for larmlampa_takfläkt_hall: {"POWER1":"OFF"} [latest-21314]2021-11-17T10:30:52.588Z <MQTTController:5:MQTTController.js:176> MQTTController#mqtt message topic=stat/TakfläktHall/POWER1, payload=OFF [latest-21314]2021-11-17T10:30:52.588Z <MQTTController:5:MQTTController.js:304> MQTTController#mqtt handling stat/TakfläktHall/POWER1 for larmlampa_takfläkt_hall: OFFpower_switch.state.PNG power_switch.state2.PNG
I've also tried some best guessing with a custom template without success, probably because of lacking knowledge from my side.
OT: Is ìnit in an upcoming build? Because how to handle a system restart is my next puzzle.
-
I am curious what this means ?
"New system capability button to express state of a single button or contact closure."
Thanks
-
Did MSR running on Docker ever gain the ability to do the R4V import? I recall it being a platform limitation for those who installed it on Synology NAS in particular.
EDITOR'S (@toggledbits) NOTE: This post was made in this thread: How To: Send TCP packet in Reaction
To my good friend @LibraSun , SHAME! This is a textbook example of thread-jacking: question/post in a topic that has nothing to do with the OP's topic/title, starting a second thread of discussion within that topic. Bad dog! No treats for you! 🐶
And yes, to the best of my knowledge, I'm getting all your DMs. I don't see any on this subject. -
Hi!
I have a Nest hello, and as a integration in Home Assistent. I would want to be able to create a automation/reaction when someone press the doorbell button. The problem is that this event/service will only appear as triggers (in HA):
3a763870-d062-4de7-be32-619120e3f90a-image.png I can't access the doorbell as an entity. I can only access it if I open the 'doorbell' device in HA.
My question is therefor; is it possible to access the doorbell and it's triggers within MSR?
I have MSR build 21307-1746e27 and HA core-2021.11.2.
Have a great day!
/Fanan
Is Telegram working?
-
Hi
I just enabled the Telegram profile in my notification.yaml file. I added my bot ID and Chat ID.
I then added a notify action in a rules Reaction, but no notification is received to my phone.
I can run the raw HTTPS request URL in a browser and that works OK and my notification is received OK.
Also I wasn't sure what this means and I tried it commented out and not.
default_disable_notification: "false"
Likewise with this one:
default_parse_mode: ""
Also I see there is a bug listed here already, maybe related?
Thanks
-
The bug (that is fixed and there is an announced update to the docker images with that fix) was simply that choosing the default format (parse mode) and notification were causing the UI to flag the fields as missing (they were not marked optional, so the UI assumes required). You can either update the docker image (if you are using docker), or just choose non-default/from-profile values in those drop-downs for testing.
Other than the UI glitch, I haven't heard of any issues.
I'll be spinning a new release today.
-
I am using normal Telegram since it was released, with the HTML and Markdown format settings.
I share below the configuration that I have if it helps in something.
# Telegram Telegram: profiles: default: # description - A friendly description of this profile (for menus) description: Default Family # # api_url - Access URL for Telegram API. Default is https://api.telegram.org/ api_url: https://api.telegram.org/ # # bot_token - (required) Bot Token, from Telegram. See: https://core.telegram.org/bots bot_token: "17______83:AAX____________________dBleUXslGTGk" # # default_chat_id - (required) Default chat ID to use if not specified in message. See # this link for how to get chat ID: # https://stackoverflow.com/questions/32423837/telegram-bot-how-to-get-a-group-chat-id default_chat_id: "-58_____24" # # default_disable_notification - Default notification flag, may be either "true" # or "false". The system default is "false" # (false == notification enabled/not disabled). default_disable_notification: "false" # # default_parse_mode - Default message format/parse mode. The system default is # blank, for plain text. Other options: MarkdownV2, HTML # See: https://core.telegram.org/bots/api#formatting-options default_parse_mode: "HTML" wilson: # description - A friendly description of this profile (for menus) description: Default Wilson # # api_url - Access URL for Telegram API. Default is https://api.telegram.org/ api_url: https://api.telegram.org/ # # bot_token - (required) Bot Token, from Telegram. See: https://core.telegram.org/bots bot_token: "17______83:AAER_UN_______________________lGTGk" # # default_chat_id - (required) Default chat ID to use if not specified in message. See # this link for how to get chat ID: # https://stackoverflow.com/questions/32423837/telegram-bot-how-to-get-a-group-chat-id default_chat_id: "154_____34" # # default_disable_notification - Default notification flag, may be either "true" # or "false". The system default is "false" # (false == notification enabled/not disabled). default_disable_notification: "false" # # default_parse_mode - Default message format/parse mode. The system default is # blank, for plain text. Other options: MarkdownV2, HTML # See: https://core.telegram.org/bots/api#formatting-options default_parse_mode: "HTML" -
Yes my notification.yaml file looks the same as above apart from I am not using HTML I left it blank for plain text.
I have created a Global Reaction as a test with a notify for Telegram. It's still not working. I've also updated to the very latest version of MSR that fixes those two fields being required vs optional.
This is what I see in the log file. They are not my real bot and chat ID's I have changed them.
2021-06-18T11:50:50.594Z <Engine:5:Engine.js:953> Engine#1 enqueued reaction re-kq29nxzw as 43 2021-06-18T11:50:50.595Z <Engine:5:Engine.js:1108> _process_reaction_queue() wake-up! 2021-06-18T11:50:50.599Z <Engine:5:Engine.js:1069> _process_reaction_queue() running task 43 { "tid": 43, "id": "re-kq29nxzw", "rule": --undef--, "__reaction": GlobalReaction#re-kq29nxzw, "next_step": 0, "status": 0, "ts": 1624017050481, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] } 2021-06-18T11:50:50.599Z <Engine:NOTICE> Starting reaction Test Telegram (re-kq29nxzw) 2021-06-18T11:50:50.600Z <Engine:5:Engine.js:1216> Engine#1 reaction re-kq29nxzw step 0 notify Telegram with { "message": "This is a TEST", "profile": "default" } 2021-06-18T11:50:50.601Z <Engine:5:NotifyTelegram.js:159> NotifyTelegram sending profile default notification request: This is a TEST 2021-06-18T11:50:50.604Z <Engine:INFO> Test Telegram all actions completed. 2021-06-18T11:50:50.605Z <Engine:5:Engine.js:1073> _process_reaction_queue() task returned, new status -1; task 43 2021-06-18T11:50:50.608Z <Engine:5:Engine.js:1108> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting 2021-06-18T11:50:50.697Z <Engine:ERR> NotifyTelegram failure response from endpoint: 404 Not Found 2021-06-18T11:50:50.699Z <Engine:ERR> NotifyTelegram fres=[object Response] 2021-06-18T11:50:50.700Z <Engine:INFO> NotifyTelegram request URL: https://api.telegram.org/botBBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN/sendMessage 2021-06-18T11:50:50.701Z <Engine:INFO> NotifyTelegram request body: {"text":"This is a TEST","chat_id":"314603256"} 2021-06-18T11:50:50.702Z <Engine:ERR> NotifyTelegram request to https://api.telegram.org/botBBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN/sendMessage failed: Error: NotifyTelegram request failed 2021-06-18T11:50:50.703Z <Engine:ERR> Engine#1 reaction re-kq29nxzw step 0 notification (Telegram) failed: Error: NotifyTelegram request failedMy raw HTTPS url's that I am currently using, the bot ID has an extra part at the beginning.
For example like this:
https://api.telegram.org/bot2188872596:BBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xNWhere as in the MSR log its removed the "2188872596:" part and just shows this:
https://api.telegram.org/botBBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xNWhich results in the 404 error etc.
Thanks
-
Did you include it in the config?
Edit: clarifying, by "it" I mean the number (bot ID) before the colon (and the colon). The
bot_tokenvalue in the config should be on the formnnnnnn:mixedlongstring. The object literally copies the entirebot_tokenstring onto the end of the URL; there's not filtering or editing of any kind, so your log post suggests it's not there.Did you enclose it in quotes?
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits said in Is Telegram working?:
Did you include it in the config?
Yes and No.
Seems I needed to restart Reactor engine.
I now see the correct full bot ID string in the log file OK.
Also I had to remove "bot" from the yaml file as MSR puts than in for you.
However its still not working.
I am still getting 404.
This is what I see now in the log:
2021-06-18T17:25:12.205Z <Engine:INFO> Enqueueing "Test Telegram" (re-kq29nxzw) 2021-06-18T17:25:12.210Z <Engine:5:Engine.js:953> Engine#1 enqueued reaction re-kq29nxzw as 6 2021-06-18T17:25:12.212Z <Engine:5:Engine.js:1108> _process_reaction_queue() wake-up! 2021-06-18T17:25:12.215Z <Engine:5:Engine.js:1069> _process_reaction_queue() running task 6 { "tid": 6, "id": "re-kq29nxzw", "rule": --undef--, "__reaction": GlobalReaction#re-kq29nxzw, "next_step": 0, "status": 0, "ts": 1624037112207, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] } 2021-06-18T17:25:12.216Z <Engine:NOTICE> Starting reaction Test Telegram (re-kq29nxzw) 2021-06-18T17:25:12.217Z <Engine:5:Engine.js:1216> Engine#1 reaction re-kq29nxzw step 0 notify Telegram with { "message": "This is a TEST", "profile": "default" } 2021-06-18T17:25:12.218Z <Engine:5:NotifyTelegram.js:159> NotifyTelegram sending profile default notification request: This is a TEST 2021-06-18T17:25:12.222Z <Engine:INFO> Test Telegram all actions completed. 2021-06-18T17:25:12.223Z <Engine:5:Engine.js:1073> _process_reaction_queue() task returned, new status -1; task 6 2021-06-18T17:25:12.226Z <Engine:5:Engine.js:1108> _process_reaction_queue() ending with 1 in queue; waiting for 1 (next delayed task) 2021-06-18T17:25:12.349Z <Engine:ERR> NotifyTelegram failure response from endpoint: 400 Bad Request 2021-06-18T17:25:12.351Z <Engine:ERR> NotifyTelegram fres=[object Response] 2021-06-18T17:25:12.352Z <Engine:INFO> NotifyTelegram request URL: https://api.telegram.org/bot2188872596:BBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN/sendMessage 2021-06-18T17:25:12.352Z <Engine:INFO> NotifyTelegram request body: {"text":"This is a TEST","chat_id":"314603256"} 2021-06-18T17:25:12.353Z <Engine:ERR> NotifyTelegram request to https://api.telegram.org/bot2188872596:BBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN/sendMessage failed: Error: NotifyTelegram request failed 2021-06-18T17:25:12.354Z <Engine:ERR> Engine#1 reaction re-kq29nxzw step 0 notification (Telegram) failed: Error: NotifyTelegram request failed -
You're now getting a 400, not a 404. That likely means that the chat ID is invalid. Is the bot a member of that chat?
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Oh yes sorry 400 not 404.
Chat ID is correct and yes I think it must be a member. Because I am using the same bot ID and the same chat ID in a raw HTTPS command and the notifications work and go to my "Vera Group" aka my chat ID.
This is the type of HTTPS command I've been using previously:
https://api.telegram.org/bot2188872596:BBF5RD5P-kDty8ZTB88e--GB5T5ENpId4xN/sendMessage?chat_id=-314603256&text=This is a test -
The chat ID in your HTTPS fetch has a minus sign at the front, while the chat ID in MSR does not. Check you configuration again.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Well spotted I didn't even notice that.
I added a minus sign also in the notification.yaml file and now its working from MSR.
-
@toggledbits minus is allowed, and is a message for a group. When it does not have a minus sign, it is for a single user.
-
@cw-kid this comment about having the letters bot in front is already added by MSR, we have to be careful, because when we copy the ID when it is generated in Telegram it comes with these letters bot in front that has to be removed when configuring. I had the same problem until I identified this in the log appearing twice botbot.
-
Where are you seeing that? I can't screenshot the Android app because it won't let me (security policy--smart!), but the response to
/newbotfrom BotFather does not contain the string "bot" in front of the key. Are you seeing it elsewhere? Maybe iOS? -
@wmarcolin said in Is Telegram working?:
I had the same problem until I identified this in the log appearing twice botbot.
Yes indeed, that is what I was seeing in the log file also.
-
Well first I don't remember how to get the ID, I don't remember when the number was generated
lolI think what may have created confusion, was that when using a direct call, as the example below is necessary to put the bot, but when configuring the MSR not, because the application already adds the information.
https://api.telegram.org/bot177_____83:AAER___________________________GTGk/getUpdates
I think the situation is closed, we just have to stay alert to some other user who mentions that Telegram is not working pass this orientation.
-
The key/token in the response from BotFather when creating the bot will not have 'bot' prepended to it, so that makes sense.
-
Yesterday I converted all my rules to use the now inbuilt notify for Telegram, rather than sending Http requests out as I was.
No further problems and everything seems to be working well.
Thanks for adding Telegram support, I had previously requested it, but at that time it sounded like it would not be added.